September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15312) Update all AS versions AND manifest.mf dependency version ranges

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15312?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-15312 at 9/7/13 5:53 PM: ------------------------------------------------------------ PR, if you agree that 3.4.101 should be 3.4.101-SNAPSHOT: https://github.com/jbosstools/jbosstools-server/pull/145 https://github.com/jbosstools/jbosstools-server/pull/146 was (Author: nickboldt): PR, if you agree that 3.4.101 should be 3.4.101-SNAPSHOT: https://github.com/jbosstools/jbosstools-server/pull/145 > Update all AS versions AND manifest.mf dependency version ranges > ----------------------------------------------------------------- > > Key: JBIDE-15312 > URL: https://issues.jboss.org/browse/JBIDE-15312 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > API has been added in both branch and master. THis requires an update of version ranges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15438) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Aerogear]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15438?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15438: ------------------------------------ Spinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >=38 > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Aerogear] > ------------------------------------------------------- > > Key: JBIDE-15438 > URL: https://issues.jboss.org/browse/JBIDE-15438 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 0) Make sure your component(s) has no remaining jiras for 4.1.1.Alpha1 in jira. > 1) Make sure you component(s) version number has changed micro version if it had changes since 4.1.0 was released! > > You can use this to change it for a subtree: > {code} mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<component-version>-SNAPSHOT{code} > 2) Make sure your component uses 4.1.1.Alpha1-SNAPSHOT as the version for jboss tools parent. > Should look something like this: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.1.Alpha1-SNAPSHOT</version> > </parent>{code} > 3) Make sure your component builds and passes its tests when run locally. > {code}$ mvn clean verify -Dtpc.version=4.31.0.Alpha1{code} > 4) Make a branch for the Alpha1 builds to use. > This would be made on jbosstools-4.1.x, thus the steps would be something like: > {code} $ git checkout jbosstools-4.1.x > $ git pull origin jbosstools-4.1.x > $ git checkout -b jbosstools-4.1.1.Alpha1x > $ git push origin jbosstools-4.1.1.Alpha1x{code} > 5) Resolve the jira related to branching for your component or comment on it why it can not be done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15312) Update all AS versions AND manifest.mf dependency version ranges

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15312?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15312: ------------------------------- Priority: Blocker (was: Major) > Update all AS versions AND manifest.mf dependency version ranges > ----------------------------------------------------------------- > > Key: JBIDE-15312 > URL: https://issues.jboss.org/browse/JBIDE-15312 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > API has been added in both branch and master. THis requires an update of version ranges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15312) Update all AS versions AND manifest.mf dependency version ranges

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15312?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15312: ------------------------------------ Escalate to blocker as releasing Alpha1 with plugins that don't include a 4th part (qualifier) might prevent updating them later (Alpha2, Beta1, CR1, Final). > Update all AS versions AND manifest.mf dependency version ranges > ----------------------------------------------------------------- > > Key: JBIDE-15312 > URL: https://issues.jboss.org/browse/JBIDE-15312 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > API has been added in both branch and master. THis requires an update of version ranges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15312) Update all AS versions AND manifest.mf dependency version ranges

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15312?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-15312 at 9/7/13 5:21 PM: ------------------------------------------------------------ Reopen for clarification from [~rob.stryker] and [~maxandersen]: Why did you set plugin and feature versions to 3.4.101 instead of 3.4.101-SNAPSHOT? Dropping the SNAPSHOT also drops the .Alpha, .Beta, .CR, .Final qualifier + timestamp + build number. 3.4.101: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.1.1.Alp... 3.4.101: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.1.x/arc... Was that intentional, or did you accidentally run the tycho-versions-plugin:set-version mojo without the -SNAPSHOT ending? FWIW, I think these are OK: 2.4.101-SNAPSHOT: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.1.1.Alp... 1.4.1-SNAPSHOT: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.1.1.Alp... 1.0.1-SNAPSHOT: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.1.1.Alp... 2.4.101-SNAPSHOT: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.1.x/as/... 1.4.1-SNAPSHOT: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.1.x/jmx... 1.0.1-SNAPSHOT: https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.1.x/wtp... 2.5.0-SNAPSHOT: https://github.com/jbosstools/jbosstools-server/blob/master/as/pom.xml#L12 1.5.0-SNAPSHOT: https://github.com/jbosstools/jbosstools-server/blob/master/jmx/pom.xml#L13 1.1.0-SNAPSHOT: https://github.com/jbosstools/jbosstools-server/blob/master/wtp/pom.xml#L12 3.5.0-SNAPSHOT: https://github.com/jbosstools/jbosstools-server/blob/master/archives/pom.... was (Author: nickboldt): Reopen for clarification from [~rob.stryker] and [~maxandersen]: Why did you set plugin and feature versions to 3.4.101 instead of 3.4.101-SNAPSHOT? Dropping the SNAPSHOT also drops the .Alpha, .Beta, .CR, .Final qualifier + timestamp + build number. Was that intentional, or did you accidentally run the tycho-versions-plugin:set-version mojo without the -SNAPSHOT ending? > Update all AS versions AND manifest.mf dependency version ranges > ----------------------------------------------------------------- > > Key: JBIDE-15312 > URL: https://issues.jboss.org/browse/JBIDE-15312 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > API has been added in both branch and master. THis requires an update of version ranges. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15467) should JBT have a category for "stuff not in Abridged" ?

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15467?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-15467: -------------------------------------- I would prefer if CordovaSim and aerogear.hybrid were in a category like "Hybrid Mobile Development Tools" > should JBT have a category for "stuff not in Abridged" ? > -------------------------------------------------------- > > Key: JBIDE-15467 > URL: https://issues.jboss.org/browse/JBIDE-15467 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.1.1.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Alpha2 > > > The Marketplace entry for JBT includes all the features in the "Abridged JBoss Tools" category, but there are a number of features not included therein. > So for those users installing from the update site itself, not the Marketplace, should these be grouped into a single category, perhaps called "Additional JBoss Tools"? > {code} > org.jboss.tools.arquillian.feature > org.jboss.tools.common.mylyn.feature > org.jboss.tools.gwt.feature > org.jboss.tools.maven.gwt.feature > org.jboss.tools.aerogear.hybrid.feature > org.jboss.tools.vpe.cordovasim.feature > org.jboss.tools.central.themes.feature > org.jboss.tools.birt.feature > org.jboss.tools.forge.ext.feature > {code} > Added bonus (from a releng P.O.V., not an end user one) is that having such a category would make it easier to maintain the full list of features to be included in these job configs, to ensure we're properly doing full JBT co-installation testing: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... > [~burrsutter] [~maxandersen] [~koen.aers] [~gercan] WDYT? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15467) should JBT have a category for "stuff not in Abridged" ?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15467: ---------------------------------- Summary: should JBT have a category for "stuff not in Abridged" ? Key: JBIDE-15467 URL: https://issues.jboss.org/browse/JBIDE-15467 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, updatesite Affects Versions: 4.1.1.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.1.1.Alpha2 The Marketplace entry for JBT includes all the features in the "Abridged JBoss Tools" category, but there are a number of features not included therein. So for those users installing from the update site itself, not the Marketplace, should these be grouped into a single category, perhaps called "Additional JBoss Tools"? {code} org.jboss.tools.arquillian.feature org.jboss.tools.common.mylyn.feature org.jboss.tools.gwt.feature org.jboss.tools.maven.gwt.feature org.jboss.tools.aerogear.hybrid.feature org.jboss.tools.vpe.cordovasim.feature org.jboss.tools.central.themes.feature org.jboss.tools.birt.feature org.jboss.tools.forge.ext.feature {code} Added bonus (from a releng P.O.V., not an end user one) is that having such a category would make it easier to maintain the full list of features to be included in these job configs, to ensure we're properly doing full JBT co-installation testing: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... [~burrsutter] [~maxandersen] [~koen.aers] [~gercan] WDYT? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15438) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Aerogear]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15438?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15438: ------------------------------- Description: For JBIDE 4.1.1.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 0) Make sure your component(s) has no remaining jiras for 4.1.1.Alpha1 in jira. 1) Make sure you component(s) version number has changed micro version if it had changes since 4.1.0 was released! You can use this to change it for a subtree: {code} mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<component-version>-SNAPSHOT{code} 2) Make sure your component uses 4.1.1.Alpha1-SNAPSHOT as the version for jboss tools parent. Should look something like this: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.1.1.Alpha1-SNAPSHOT</version> </parent>{code} 3) Make sure your component builds and passes its tests when run locally. {code}$ mvn clean verify -Dtpc.version=4.31.0.Alpha1{code} 4) Make a branch for the Alpha1 builds to use. This would be made on jbosstools-4.1.x, thus the steps would be something like: {code} $ git checkout jbosstools-4.1.x $ git pull origin jbosstools-4.1.x $ git checkout -b jbosstools-4.1.1.Alpha1x $ git push origin jbosstools-4.1.1.Alpha1x{code} 5) Resolve the jira related to branching for your component or comment on it why it can not be done. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] was: For JBIDE 4.1.1.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; 4. Close (not resolve) this JIRA when done. [Aerogear] [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Aerogear] > ------------------------------------------------------- > > Key: JBIDE-15438 > URL: https://issues.jboss.org/browse/JBIDE-15438 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 0) Make sure your component(s) has no remaining jiras for 4.1.1.Alpha1 in jira. > 1) Make sure you component(s) version number has changed micro version if it had changes since 4.1.0 was released! > > You can use this to change it for a subtree: > {code} mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<component-version>-SNAPSHOT{code} > 2) Make sure your component uses 4.1.1.Alpha1-SNAPSHOT as the version for jboss tools parent. > Should look something like this: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.1.Alpha1-SNAPSHOT</version> > </parent>{code} > 3) Make sure your component builds and passes its tests when run locally. > {code}$ mvn clean verify -Dtpc.version=4.31.0.Alpha1{code} > 4) Make a branch for the Alpha1 builds to use. > This would be made on jbosstools-4.1.x, thus the steps would be something like: > {code} $ git checkout jbosstools-4.1.x > $ git pull origin jbosstools-4.1.x > $ git checkout -b jbosstools-4.1.1.Alpha1x > $ git push origin jbosstools-4.1.1.Alpha1x{code} > 5) Resolve the jira related to branching for your component or comment on it why it can not be done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15454) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Portlet]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15454?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-15454. ------------------------------ > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Portlet] > ------------------------------------------------------ > > Key: JBIDE-15454 > URL: https://issues.jboss.org/browse/JBIDE-15454 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: portal-gatein > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; > 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; > 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; > 4. Close (not resolve) this JIRA when done. [Portlet] > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Portlet task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15437) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15437?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15437: ------------------------------------ Based on [~dgolovin]'s triage, I've reopened and rejected these four JIRA: birt: JBIDE-15449 forge: JBIDE-15450 hibernate: JBIDE-15445 portlet: JBIDE-15454 Additionally, these are rejected: xulrunner: JBIDE-15441 freemarker: JBIDE-15455 And this was never assigned a JIRA, as still unchanged since JBT 4.0.x: gwt > For JBIDE 4.1.1.Alpha1: Code Freeze + Branch > -------------------------------------------- > > Key: JBIDE-15437 > URL: https://issues.jboss.org/browse/JBIDE-15437 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha1 > > > For JBIDE 4.1.1.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. > Otherwise: > 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; > 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; > 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; > 4. Close (not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-2755 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 2013