September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23158) Update parent pom in main branch after codefreeze branching

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23158?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23158: ------------------------------------ Is this not a dupe of JBIDE-23159? > Update parent pom in main branch after codefreeze branching > ----------------------------------------------------------- > > Key: JBIDE-23158 > URL: https://issues.jboss.org/browse/JBIDE-23158 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > The script which creates branches for a release when codefreezing and also update parent poms in those branches should also update parent pom in the main (master or maintenance) branch. > For example if we update pom in just created 4.4.1.x branch to 4.4.1.Final then we also need to update the parent pom in master to 4.4.2.AM1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23158) Update parent pom in main branch after codefreeze branching

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23158?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-23158. -------------------------------- Resolution: Done > Update parent pom in main branch after codefreeze branching > ----------------------------------------------------------- > > Key: JBIDE-23158 > URL: https://issues.jboss.org/browse/JBIDE-23158 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > The script which creates branches for a release when codefreezing and also update parent poms in those branches should also update parent pom in the main (master or maintenance) branch. > For example if we update pom in just created 4.4.1.x branch to 4.4.1.Final then we also need to update the parent pom in master to 4.4.2.AM1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23159) Bump plugin/feature/component versions in main branch when creating branches for Final/GA release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23159?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23159: ------------------------------------ Because we missed this step for 4.4.1.Final / 4.4.2.AM1, here's a second job that creates a second set of Task JIRAs and emails: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... > Bump plugin/feature/component versions in main branch when creating branches for Final/GA release > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23159 > URL: https://issues.jboss.org/browse/JBIDE-23159 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > The script which creates branches for a Final/GA release when codefreezing should also bump plugin/feature/component versions in main branch (master or maintenance). > The script should probably have a parameter which tells what segment of the version we want to increment: X.Y.Z -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23159) Bump plugin/feature/component versions in main branch when creating branches for Final/GA release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23159?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-23159. -------------------------------- Resolution: Done > Bump plugin/feature/component versions in main branch when creating branches for Final/GA release > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23159 > URL: https://issues.jboss.org/browse/JBIDE-23159 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Fix For: 4.4.2.AM1 > > > The script which creates branches for a Final/GA release when codefreezing should also bump plugin/feature/component versions in main branch (master or maintenance). > The script should probably have a parameter which tells what segment of the version we want to increment: X.Y.Z -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23197) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Forge]

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23197?page=com.atlassian.jira.plugi... ] George Gastaldi closed JBIDE-23197. ----------------------------------- Resolution: Done > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Forge] > --------------------------------------------------------------- > > Key: JBIDE-23197 > URL: https://issues.jboss.org/browse/JBIDE-23197 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Friendly Jira Robot > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Forge]: 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.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {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 Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23201) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Freemarker]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23201?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-23201. ---------------------------------- Assignee: Alexey Kazakov Resolution: Done > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Freemarker] > -------------------------------------------------------------------- > > Key: JBIDE-23201 > URL: https://issues.jboss.org/browse/JBIDE-23201 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: freemarker > Reporter: Friendly Jira Robot > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Freemarker]: 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.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {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 Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23200) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Arquillian]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23200?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-23200. --------------------------------- Resolution: Done > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Arquillian] > -------------------------------------------------------------------- > > Key: JBIDE-23200 > URL: https://issues.jboss.org/browse/JBIDE-23200 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Arquillian]: 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.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {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 Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23197) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Forge]

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23197?page=com.atlassian.jira.plugi... ] George Gastaldi reassigned JBIDE-23197: --------------------------------------- Assignee: George Gastaldi > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Forge] > --------------------------------------------------------------- > > Key: JBIDE-23197 > URL: https://issues.jboss.org/browse/JBIDE-23197 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Friendly Jira Robot > Assignee: George Gastaldi > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Forge]: 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.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {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 Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23200) For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Arquillian]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23200?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-23200: ------------------------------------- Assignee: Snjezana Peco > For JBIDE 4.4.2.AM1: Prepare for 4.4.2.AM1 / 10.2.0.AM1 [Arquillian] > -------------------------------------------------------------------- > > Key: JBIDE-23200 > URL: https://issues.jboss.org/browse/JBIDE-23200 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Friendly Jira Robot > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.4.2.AM1 > > > For JBIDE 4.4.2.AM1 [Arquillian]: 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.4.2.AM1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.2.AM1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.2.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.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {code} > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final > {code} > mvn clean verify -Dtpc.version=4.60.1.Final > {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 Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4053) Installing software has encountered a problem

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4053?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4053: -------------------------------- Assignee: Nick Boldt > Installing software has encountered a problem > --------------------------------------------- > > Key: JBDS-4053 > URL: https://issues.jboss.org/browse/JBDS-4053 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM1 > > > Could be a simple network timeout but wanted to document this anyway. > Installed rh-eclipse46-devstudio-1.0-1.20160919.1438.el7.x86_64.rpm as in JBDS-4021 then attempted to install EVERYTHING from Central (including the 3rd party connectors like ZeroTurnaround and Android). > Result was some errors: > {code} > An error occurred while collecting items to be installed > session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > Unable to read repository at https://devstudio.redhat.com/targetplatforms/jbtcentraltarget/4.60.1.Fina.... > Premature end of Content-Length delimited message body (expected: 10094; received: 7811 > Unable to read repository at https://devstudio.redhat.com/targetplatforms/jbtcentraltarget/4.60.1.Fina.... > Premature end of Content-Length delimited message body (expected: 10148; received: 3767 > Unable to read repository at https://devstudio.redhat.com/targetplatforms/jbtcentraltarget/4.60.1.Fina.... > Premature end of Content-Length delimited message body (expected: 26195; received: 2419 > Unable to read repository at https://devstudio.redhat.com/targetplatforms/jbtcentraltarget/4.60.1.Fina.... > Premature end of Content-Length delimited message body (expected: 914884; received: 9157 > Unable to read repository at https://devstudio.redhat.com/targetplatforms/jbtcentraltarget/4.60.1.Fina.... > Premature end of Content-Length delimited message body (expected: 93971; received: 23986 > Unable to read repository at https://devstudio.redhat.com/targetplatforms/jbtcentraltarget/4.60.1.Fina.... > Premature end of Content-Length delimited message body (expected: 70715; received: 9158 > Unable to read repository at https://devstudio.redhat.com/targetplatforms/jbtcentraltarget/4.60.1.Fina.... > Premature end of Content-Length delimited message body (expected: 1012304; received: 394684 > Unable to read repository at https://devstudio.redhat.com/targetplatforms/jbtcentraltarget/4.60.1.Fina.... > Premature end of Content-Length delimited message body (expected: 93028; received: 9158 > Unable to read repository at https://devstudio.redhat.com/targetplatforms/jbtcentraltarget/4.60.1.Fina.... > Premature end of Content-Length delimited message body (expected: 13404956; received: 367722 > Unable to read repository at https://devstudio.redhat.com/targetplatforms/jbtcentraltarget/4.60.1.Fina.... > Premature end of Content-Length delimited message body (expected: 2342929; received: 358287 > Unable to read repository at https://devstudio.redhat.com/targetplatforms/jbtcentraltarget/4.60.1.Fina.... > Premature end of Content-Length delimited message body (expected: 6106359; received: 21287{code} > Also: > {code} > Unable to read repository at https://devstudio.redhat.com/targetplatforms/jbtcentraltarget/4.60.1.Fina.... > org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 13838; received: 5115 > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:180) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:74) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > {code} > Cannot download bundle at https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/10...: Premature end of Content-Length delimited message body (expected: 96752; received: 3766 > org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 96752; received: 3766 > at org.apache.http.impl.io.ContentLengthInputStream.read(ContentLengthInputStream.java:180) > at org.apache.http.conn.EofSensorInputStream.read(EofSensorInputStream.java:137) > at java.io.FilterInputStream.read(FilterInputStream.java:133) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer$1.performFileTransfer(AbstractRetrieveFileTransfer.java:178) > at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:74) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016