September 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2774) Investigate use of Atlassian 3.2.x in JBT 4.1.1, JBDS 7.1, and JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2774?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2774: ----------------------------- Description: JBT 4.1.0 / JBDS 7.0.0 contains Atlassian 3.2.1 (JBIDE-13682) but a newer 3.2.2.v20130909 is available from: http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ Mirrored here: http://download.jboss.org/jbosstools/updates/requirements/atlassian/3.2.2... Please review to decide if we should include this for Beta1. was: JBT 4.1.0 / JBDS 7.0.0 contains Atlassian 3.2.1 (JBIDE-13682) but a newer 3.2.2.v20130909 is available from: http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ Need to pull a mirror and investigate including this for Beta1. > Investigate use of Atlassian 3.2.x in JBT 4.1.1, JBDS 7.1, and JBoss Central > ---------------------------------------------------------------------------- > > Key: JBDS-2774 > URL: https://issues.jboss.org/browse/JBDS-2774 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central > Affects Versions: 7.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 7.1.0.Beta1 > > > JBT 4.1.0 / JBDS 7.0.0 contains Atlassian 3.2.1 (JBIDE-13682) but a newer 3.2.2.v20130909 is available from: > http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ > Mirrored here: > http://download.jboss.org/jbosstools/updates/requirements/atlassian/3.2.2... > Please review to decide if we should include this for Beta1. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15547) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [LiveReload]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15547?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-15547. --------------------------------- Resolution: Done > For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [LiveReload] > --------------------------------------------------------- > > Key: JBIDE-15547 > URL: https://issues.jboss.org/browse/JBIDE-15547 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: livereload > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha2 > > > For JBIDE 4.1.1.Alpha2 [LiveReload]: Please perform the following tasks: > 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2 > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.1.Alpha2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2; > {code} > mvn clean verify -Dtpc.version=4.31.0.Alpha2 > {code} > 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch; > {code} > git checkout jbosstools-4.1.x > git pull origin jbosstools-4.1.x > git checkout -b jbosstools-4.1.1.Alpha2x > git push origin jbosstools-4.1.1.Alpha2x > {code} > 5. Close (not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2774) Investigate use of Atlassian 3.2.x in JBT/JBDS/Central

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2774?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2774: ----------------------------- CDW pm_ack: ? > Investigate use of Atlassian 3.2.x in JBT/JBDS/Central > ------------------------------------------------------ > > Key: JBDS-2774 > URL: https://issues.jboss.org/browse/JBDS-2774 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central > Affects Versions: 7.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 7.1.0.Beta1 > > > JBT 4.1.0 / JBDS 7.0.0 contains Atlassian 3.2.1 (JBIDE-13682) but a newer 3.2.2.v20130909 is available from: > http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ > Need to pull a mirror and investigate including this for Beta1. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2774) Investigate use of Atlassian 3.2.x in JBT 4.1.1, JBDS 7.1, and JBoss Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2774?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2774: ----------------------------- Summary: Investigate use of Atlassian 3.2.x in JBT 4.1.1, JBDS 7.1, and JBoss Central (was: Investigate use of Atlassian 3.2.x in JBT/JBDS/Central) > Investigate use of Atlassian 3.2.x in JBT 4.1.1, JBDS 7.1, and JBoss Central > ---------------------------------------------------------------------------- > > Key: JBDS-2774 > URL: https://issues.jboss.org/browse/JBDS-2774 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central > Affects Versions: 7.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 7.1.0.Beta1 > > > JBT 4.1.0 / JBDS 7.0.0 contains Atlassian 3.2.1 (JBIDE-13682) but a newer 3.2.2.v20130909 is available from: > http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ > Need to pull a mirror and investigate including this for Beta1. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2774) Investigate use of Atlassian 3.2.x in JBT/JBDS/Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2774?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2774: ----------------------------- CDW release: ? Status: New (was: New) Target Release: 7.1.0.GA > Investigate use of Atlassian 3.2.x in JBT/JBDS/Central > ------------------------------------------------------ > > Key: JBDS-2774 > URL: https://issues.jboss.org/browse/JBDS-2774 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central > Affects Versions: 7.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 7.1.0.Beta1 > > > JBT 4.1.0 / JBDS 7.0.0 contains Atlassian 3.2.1 (JBIDE-13682) but a newer 3.2.2.v20130909 is available from: > http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ > Need to pull a mirror and investigate including this for Beta1. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12029) No type for PathParam parameters in JAX-RS REST Web Services explorer

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12029?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-12029: ---------------------------------- Fix Version/s: 4.1.1.Beta1 4.2.0.Alpha1 (was: 4.1.1.Alpha2) > No type for PathParam parameters in JAX-RS REST Web Services explorer > --------------------------------------------------------------------- > > Key: JBIDE-12029 > URL: https://issues.jboss.org/browse/JBIDE-12029 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 3.3.0.CR1 > Reporter: Jaroslav Jankovič > Assignee: Xavier Coulon > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > Attachments: path_param.png > > > I think, it would be useful, if user knows the type of parameter of PathParam annotation. At least in "numerical-nonnumerical" cases. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2774) Investigate use of Atlassian 3.2.x in JBT/JBDS/Central

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2774: -------------------------------- Summary: Investigate use of Atlassian 3.2.x in JBT/JBDS/Central Key: JBDS-2774 URL: https://issues.jboss.org/browse/JBDS-2774 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: 3rd-party-certification, 3rd-party-dependencies, central Affects Versions: 7.1.0.Alpha2 Reporter: Nick Boldt Assignee: Len DiMaggio Fix For: 7.1.0.Beta1 JBT 4.1.0 / JBDS 7.0.0 contains Atlassian 3.2.1 (JBIDE-13682) but a newer 3.2.2.v20130909 is available from: http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ Need to pull a mirror and investigate including this for Beta1. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2774) Investigate use of Atlassian 3.2.x in JBT/JBDS/Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2774?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2774: ----------------------------- Workflow: CDW v1 (was: GIT Pull Request workflow ) Parent: (was: JBDS-2710) Issue Type: Feature Request (was: Sub-task) > Investigate use of Atlassian 3.2.x in JBT/JBDS/Central > ------------------------------------------------------ > > Key: JBDS-2774 > URL: https://issues.jboss.org/browse/JBDS-2774 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central > Affects Versions: 7.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Len DiMaggio > Fix For: 7.1.0.Beta1 > > > JBT 4.1.0 / JBDS 7.0.0 contains Atlassian 3.2.1 (JBIDE-13682) but a newer 3.2.2.v20130909 is available from: > http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ > Need to pull a mirror and investigate including this for Beta1. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15428) No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15428?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15428: ---------------------------------- Fix Version/s: 4.1.1.Beta1 4.2.0.Alpha1 (was: 4.1.1.Alpha2) > No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15428 > URL: https://issues.jboss.org/browse/JBIDE-15428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.1.1.Beta1, 4.2.0.Alpha1 > > Attachments: After import.png, After workaround.png, Before import.png > > > After importing Dynamic Web Project with JAX-RS support with HTTPMethod annotation without @Target and @Retention annotations, there is no error. > This looks like a regression of JBIDE-12690. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15541) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Forge]

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15541?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-15541. ------------------------------- Resolution: Done > For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [Forge] > ---------------------------------------------------- > > Key: JBIDE-15541 > URL: https://issues.jboss.org/browse/JBIDE-15541 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.1.1.Alpha2 > > > For JBIDE 4.1.1.Alpha2 [Forge]: Please perform the following tasks: > 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2 > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.1.1.Alpha2-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2; > {code} > mvn clean verify -Dtpc.version=4.31.0.Alpha2 > {code} > 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch; > {code} > git checkout jbosstools-4.1.x > git pull origin jbosstools-4.1.x > git checkout -b jbosstools-4.1.1.Alpha2x > git push origin jbosstools-4.1.1.Alpha2x > {code} > 5. Close (not resolve) this JIRA when done. > [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 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, 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 2013