July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20171: ------------------------------------ After discussion today on build.next call, the consensus seems to be that this failure is expected & good. [~maxandersen] Do you agree? If so, viable solutions are: a) rebuild Xulrunner w/ latest parent pom to get Eclipse-SourceReference set to the same SHA as the buildinfo.json file I created by hand. b) don't include a buildinfo.json file in http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/ > buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA > ------------------------------------------------------------------- > > Key: JBIDE-20171 > URL: https://issues.jboss.org/browse/JBIDE-20171 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Since the addition of a check that verifies exactly this condition: > https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6... > I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json. > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console} > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json > [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences > [ERROR] commitId . > [ERROR] If you have locally built projects which are aggregated here, > [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. > [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. > [ERROR] -> [Help 1]{code} > This happened after I put a buildinfo.json file here: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > I've since moved the file here to temporarily work around the build failure: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20171: ------------------------------- Description: Since the addition of a check that verifies exactly this condition: https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6... I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json. {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console} [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences [ERROR] commitId . [ERROR] If you have locally built projects which are aggregated here, [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. [ERROR] -> [Help 1]{code} This happened after I put a buildinfo.json file here: http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... I've since moved the file here to temporarily work around the build failure: http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... was: {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console} [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences [ERROR] commitId . [ERROR] If you have locally built projects which are aggregated here, [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. [ERROR] -> [Help 1]{code} This happened after I put a buildinfo.json file here: http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... I've since moved the file here to temporarily work around the build failure: http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA > ------------------------------------------------------------------- > > Key: JBIDE-20171 > URL: https://issues.jboss.org/browse/JBIDE-20171 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Since the addition of a check that verifies exactly this condition: > https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6... > I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json. > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console} > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json > [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences > [ERROR] commitId . > [ERROR] If you have locally built projects which are aggregated here, > [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. > [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. > [ERROR] -> [Help 1]{code} > This happened after I put a buildinfo.json file here: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > I've since moved the file here to temporarily work around the build failure: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20171) buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20171?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-20171: ---------------------------------- Assignee: Nick Boldt > buildinfo.json reader fails if upstream MANIFEST.MF contains no SHA > ------------------------------------------------------------------- > > Key: JBIDE-20171 > URL: https://issues.jboss.org/browse/JBIDE-20171 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Since the addition of a check that verifies exactly this condition: > https://github.com/jbosstools/jbosstools-maven-plugins/commit/916f4521ba6... > I've now got a situation where it's OK to have no SHA in the MANIFEST.MF, but a SHA in buildinfo.json. > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sites.aggregate.site_master/10216/console} > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-xulrunner.json > [ERROR] contains 2edce933f7d64efbb4d7a5b16be8dadae8de766e, but upstream project's MANIFEST.MF has Eclipse-SourceReferences > [ERROR] commitId . > [ERROR] If you have locally built projects which are aggregated here, > [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. > [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. > [ERROR] -> [Help 1]{code} > This happened after I put a buildinfo.json file here: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... > I've since moved the file here to temporarily work around the build failure: > http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20148) releng scripts is an outdated version; jobs are not seeing latest from Nexus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20148?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20148: ---------------------------------------- Parent pom still references older versions of publish scripts: https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > releng scripts is an outdated version; jobs are not seeing latest from Nexus > ---------------------------------------------------------------------------- > > Key: JBIDE-20148 > URL: https://issues.jboss.org/browse/JBIDE-20148 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Labels: needinfo, nexus > Fix For: 4.3.0.Beta2 > > > I've made some commits in the 4.3.x branch [0] of the build-ci repo, which should echo more details into the log. > [0] https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.3.x > And the latest commits ARE built and available in Nexus [1], [2]: > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... [2] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Yet, no such output appears when the job is run, which makes me think that the -d and --del flags are NOT being passed to the script. > Here's a snippet from https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... : > {code} > + /qa/tools/opt/apache-maven-3.2.5//bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/.repository -B -U -fae -e -P hudson,unified.target,pack200,fetch-source-zips -Djbosstools_site_stream=master > ... > [INFO] --- exec-maven-plugin:1.3.2:exec (deploy-snapshot-updatesite) @ org.jboss.tools.site.core --- > ... > rsync -arzq --protocol=28 /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/repository/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/ > {code} > Yet when I run THE SAME SCRIPT from the workspace via shell, I get what I want: > {code} > + . /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/publish/rsync.sh -s /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo -t mars/snapshots/updates/core/master --del > ... > [DEBUG] RSYNCFLAGS = --del > ... > [INFO] rsync -arzq --protocol=28 --del /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/ > ++ rsync -arzq --protocol=28 --del ... tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/ > {code} > So... what am I doing wrong? Why isn't the mojo using the latest version of the rsync script, but it's IN the workspace [3] ? > [3] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19598) Use "Build other project (extended)" to cascade aggregation

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19598: ----------------------------------- Priority: Minor (was: Major) > Use "Build other project (extended)" to cascade aggregation > ----------------------------------------------------------- > > Key: JBIDE-19598 > URL: https://issues.jboss.org/browse/JBIDE-19598 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > > In order to decide whether to cascade aggregation when components are build, we could use the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs (site, coretests-site) when component has SCM changes. > This would require changing all 17 component jobs (per stream = 34 jobs), but would eliminate the need for the composite-install test jobs [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19759 at 7/1/15 11:33 AM: ------------------------------------------------------------------- The users can for now launch the v3 new application wizard via the context menu in OpenShift explorer. We went out of time for the proper fix in 4.3.0.Beta1 was (Author: adietish): The users can for now launch the v3 new application wizard via context menu. We went out of time for the proper fix in 4.3.0.Beta1 > Application wizard: cannot launch v3 application wizard via File->New->OpenShift > -------------------------------------------------------------------------------- > > Key: JBIDE-19759 > URL: https://issues.jboss.org/browse/JBIDE-19759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.3.0.Beta2 > > Attachments: empty-v2-wizard-page.png, no-application-wizard.png > > > If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. > This is very important since that's what a newbie user will come across when hitting "New OpenShift Application" from central. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20063) locked up machine with "Loading descriptor" ...

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20063?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20063: -------------------------------------- Assignee: Fred Bricon (was: Viacheslav Kabanovich) [~fbricon] could you please take a look? > locked up machine with "Loading descriptor" ... > ----------------------------------------------- > > Key: JBIDE-20063 > URL: https://issues.jboss.org/browse/JBIDE-20063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, maven > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.3.0.Beta2 > > > when loaded javaee7-samples I ended up with frozen eclipse showing this: > https://www.dropbox.com/s/ttx9ppieads5m7n/Screenshot%202015-06-13%2001.31... > its so frozen I cannot even get a stacktrace from jps. > I tried looking for "Loading descriptor" in common and batch but no luck so maybe it is not in batch this is happening but something is definitely locking up ;/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20063) locked up machine with "Loading descriptor" ...

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20063?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20063: ----------------------------------- Component/s: maven > locked up machine with "Loading descriptor" ... > ----------------------------------------------- > > Key: JBIDE-20063 > URL: https://issues.jboss.org/browse/JBIDE-20063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch, maven > Reporter: Max Rydahl Andersen > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > > when loaded javaee7-samples I ended up with frozen eclipse showing this: > https://www.dropbox.com/s/ttx9ppieads5m7n/Screenshot%202015-06-13%2001.31... > its so frozen I cannot even get a stacktrace from jps. > I tried looking for "Loading descriptor" in common and batch but no luck so maybe it is not in batch this is happening but something is definitely locking up ;/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20170) WebTools server adapter installer installs only a subset of what should be installed

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20170?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20170: ---------------------------------------- I believe the discovery mechanism of WTP will prefer resolving using the p2 property, rather than the category: https://github.com/jbosstools/jbosstools-server/blob/master/as/features/o... Whether the UI seems to resolve via category first. > WebTools server adapter installer installs only a subset of what should be installed > ------------------------------------------------------------------------------------ > > Key: JBIDE-20170 > URL: https://issues.jboss.org/browse/JBIDE-20170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, server, updatesite, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.0.Beta2 > > > Steps to repro: > {code}1. open clean Eclipse JEE > 2. open Servers view > 3. click 'No servers are avail... click to create new server..." > 4. click "Download additional server adapters" > (Site used to resolve IUs is http://download.jboss.org/jbosstools/updates/webtools/mars/ which symlinks to http://download.jboss.org/jbosstools/mars/development/updates/core/ ) > 5. wait while the stuff loads. select "JBoss AS Server Adapter" or whatever it was called > 6. wait as metadata loads again > 7. click Next, accept license, etc. restart when prompted > {code} > Feature that should have been installed: > {code:title=https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/category.xml#L99-L103} > <feature id="org.jboss.ide.eclipse.as.feature"> > <category name="org.eclipse.wst.server.core.serverAdapter"/> > </feature> > {code} > Feature that instead gets installed: > {code}org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_3.1.0.Beta1-v20150612-2158-B25{code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20002) Explorer: Delete multiple OpenShift resources at once

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20002?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20002: ------------------------------------- Fix Version/s: 4.3.0.Beta2 > Explorer: Delete multiple OpenShift resources at once > ----------------------------------------------------- > > Key: JBIDE-20002 > URL: https://issues.jboss.org/browse/JBIDE-20002 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Minor > Labels: explorer, openshift_v3 > Fix For: 4.3.0.Beta2 > > > It would be nice to have a feature allowing removing more resources at once: > 1) Multiselect on some specific type of resource (e.g. pods) and deleting them via context menu "Delete resources..." which pop up dialog "Do you really want to delete selected resources?" with Yes, No, Cancel. > 2) Deleting specific resources - from context menu on Pods / Builds etc. I would like to choose "Delete resources..." to remove all underlying resources. > 3) Delete all resources. Should be accessible from context menu of a project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2015