February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23623: ------------------------------- Fix Version/s: 4.4.4.AM1 (was: 4.4.3.Final) > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM1 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23623: ---------------------------------- Resolution: (was: Done) Assignee: Nick Boldt (was: Jeff MAURY) > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM1 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23623 at 2/16/17 2:54 PM: ------------------------------------------------------------- Should that be {code}git push origin ${git_branch}{code} where git_branch is one of master, 4.4.x, 4.4.3.x, etc? was (Author: nickboldt): Should that be {code}git push origin $\{git_branch}{code} where git_branch is one of master, 4.4.x, 4.4.3.x, etc? > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM1 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23623: ------------------------------------ Should that be {code}git push origin $\{git_branch}{code} where git_branch is one of master, 4.4.x, 4.4.3.x, etc? > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.3.Final > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23407) ConcurrentModificationException below ArquillianBuilder$1.visit (thrown in HashMap$HashIterator.nextNode)

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23407?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-23407: ---------------------------------- Fix Version/s: 4.5.x (was: 4.4.3.Final) > ConcurrentModificationException below ArquillianBuilder$1.visit (thrown in HashMap$HashIterator.nextNode) > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23407 > URL: https://issues.jboss.org/browse/JBIDE-23407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.4.2.AM2 > Reporter: Automated Error Reporting Bot > Assignee: Snjezana Peco > Fix For: 4.5.x > > > The following problem was reported via the automated error reporting: > Message: Problems occurred when invoking code from plug-in: "org.eclipse.core.resources". > java.util.ConcurrentModificationException: null > at java.util.HashMap$HashIterator.nextNode(HashMap.java:1437) > at java.util.HashMap$KeyIterator.next(HashMap.java:1461) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder$1.visit(ArquillianBuilder.java:173) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:64) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:75) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:75) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:75) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:75) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:75) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:75) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:75) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:75) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:75) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:75) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:48) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.buildDelta(ArquillianBuilder.java:128) > at org.jboss.tools.arquillian.core.internal.builder.ArquillianBuilder.build(ArquillianBuilder.java:112) > at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) > at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304) > at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360) > at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383) > at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144) > at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Bundles: > | org.eclipse.core.jobs | 3.8.0.v20160509-0411 | 3.8.0.v20160509-0411 | > | org.eclipse.core.runtime | 3.12.0.v20160606-1342 | 3.12.0.v20160606-1342 | > | org.jboss.tools.arquillian.core | 1.2.200.v20160808-1824 | 1.2.200.v20160808-1824 | > Operating Systems: > | MacOSX | 10.12.0 | 10.12.0 | > The above information is a snapshot of the collected data. Visit https://aer.ctrlflow.com/redhat/reviewers/#!/problems/580cd1e9e4b081752d6... for the latest data. > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23864) MavenResolver dont find project pom.xml

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23864?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-23864: ---------------------------------- Fix Version/s: 4.5.x (was: 4.4.4.AM1) > MavenResolver dont find project pom.xml > --------------------------------------- > > Key: JBIDE-23864 > URL: https://issues.jboss.org/browse/JBIDE-23864 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Environment: Eclipse Neon Release 4.6.2 > Reporter: Daniel Reis > Fix For: 4.5.x > > > Arquillian plugin cant find pom.xml of the project and dont recognize the classes addeds to archive, displaying many warnings. > The lines that start the warnings are: > File[] files = Maven.resolver().loadPomFromFile("pom.xml").importRuntimeDependencies().resolve().withTransitivity().asFile(); > return ShrinkWrap.create(WebArchive.class).addAsLibraries(files).addAsManifestResource(EmptyAsset.INSTANCE, "beans.xml"); > Thanks, > Daniel -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23903) Server adapter: waits endlessly if you dont unfold the project in the OpenShift explorer

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23903?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23903: ------------------------------------------ merged into master > Server adapter: waits endlessly if you dont unfold the project in the OpenShift explorer > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23903 > URL: https://issues.jboss.org/browse/JBIDE-23903 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Labels: openshift_v3, server_adapter > Fix For: 4.4.3.Final > > Attachments: failed-to-detect-pod.png, image-2017-02-15-17-38-29-607.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23623: ------------------------------------ Situation is improving. So JIRA numbers are now part of the commit message but I still add one problem. When running the second run (creating the maintenance branch 4.4.and updating pom, the push were refused because the script generates the following command: {code:java} git push origin master {code} which was refused by git. I have no log because I then ran the next run to update master but I fixed by walking into each git repo and issuing the command: {code:java} git push origin {code} > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.4.3.Final > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23960) For JBIDE 4.5.0.AM1: Prepare for 4.5.0.AM1 / 11.0.0.AM1 [updatesite]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23960?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-23960: ---------------------------------- Assignee: Nick Boldt > For JBIDE 4.5.0.AM1: Prepare for 4.5.0.AM1 / 11.0.0.AM1 [updatesite] > -------------------------------------------------------------------- > > Key: JBIDE-23960 > URL: https://issues.jboss.org/browse/JBIDE-23960 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Reporter: Jeff MAURY > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.0.AM1 > > > For JBIDE 4.5.0.AM1 [updatesite]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for updatesite task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23960) For JBIDE 4.5.0.AM1: Prepare for 4.5.0.AM1 / 11.0.0.AM1 [updatesite]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23960?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23960: ------------------------------------ bump up to parent pom version = 4.5.0.AM1-SNAPSHOT > For JBIDE 4.5.0.AM1: Prepare for 4.5.0.AM1 / 11.0.0.AM1 [updatesite] > -------------------------------------------------------------------- > > Key: JBIDE-23960 > URL: https://issues.jboss.org/browse/JBIDE-23960 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: updatesite > Reporter: Jeff MAURY > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.5.0.AM1 > > > For JBIDE 4.5.0.AM1 [updatesite]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.0.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.0.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.0.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for updatesite task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017