December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-16241) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Central]

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16241?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16241: ---------------------------------------- [~fbricon]: Is this something you can do ASAP ? > For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Central] > ------------------------------------------------------ > > Key: JBIDE-16241 > URL: https://issues.jboss.org/browse/JBIDE-16241 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.2.0.Alpha1 > > > For JBIDE 4.2.0.Alpha1 [Central]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1 > [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 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:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1; > {code} > mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Alpha1x > git push origin jbosstools-4.2.0.Alpha1x > {code} > 5. Close (do 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 Central 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16266) NLS missing messages in SeamProjectNewWizardTest

by Victor Rubezhny (JIRA)

Victor Rubezhny created JBIDE-16266: --------------------------------------- Summary: NLS missing messages in SeamProjectNewWizardTest Key: JBIDE-16266 URL: https://issues.jboss.org/browse/JBIDE-16266 Project: Tools (JBoss Tools) Issue Type: Bug Components: seam2 Affects Versions: 4.2.0.Alpha1 Reporter: Victor Rubezhny Priority: Trivial When running SeamProjectNewWizardTest JUnit Test the following Warnings appear: {code} Warning: NLS missing message: JBossASAdapterInitializer_AppServer32 in: org.jboss.tools.jst.firstrun.messages Warning: NLS missing message: JBossASAdapterInitializer_AppServer40 in: org.jboss.tools.jst.firstrun.messages Warning: NLS missing message: JBossASAdapterInitializer_AppServer42 in: org.jboss.tools.jst.firstrun.messages Warning: NLS missing message: JBossASAdapterInitializer_AppServer50 in: org.jboss.tools.jst.firstrun.messages Warning: NLS missing message: JBossASAdapterInitializer_CannotCreateDriver in: org.jboss.tools.jst.firstrun.messages Warning: NLS missing message: JBossASAdapterInitializer_CannotCreateProfile in: org.jboss.tools.jst.firstrun.messages Warning: NLS missing message: JBossASAdapterInitializer_CannotCreateServer in: org.jboss.tools.jst.firstrun.messages Warning: NLS missing message: JBossASAdapterInitializer_JBossASHypersonicEmbeddedDB in: org.jboss.tools.jst.firstrun.messages Warning: NLS missing message: JBossASAdapterInitializer_Runtime in: org.jboss.tools.jst.firstrun.messages {code} -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16252) Deployed module on OpenShift (server adapter) should be associated with '/'

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16252?page=com.atlassian.jira.plugi... ] Xavier Coulon closed JBIDE-16252. --------------------------------- Resolution: Cannot Reproduce Bug I couldn't reproduce the bug: the server adapter opens the browser at the expected location. Looks like the problem was more on the browser side, where hitting refresh returned a 404 error page for some unknown reason. > Deployed module on OpenShift (server adapter) should be associated with '/' > --------------------------------------------------------------------------- > > Key: JBIDE-16252 > URL: https://issues.jboss.org/browse/JBIDE-16252 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > > The deployed project on OpenShift is a module of the OpenShift Application Server Adapter. > When selecting this module and doing 'Show In>Web browser', the URL given to the browser ends with a '/app' context which is wrong, it should be '/'. > Otherwise, the user (or speaker in front of an audience ;-) ) will have a 404 error :-/ > Furthermore, when the user is used to select the module under a classic JBossAS 7 server adapter, he gets confused if he needs to select the server for the OpenShift deployed application. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13430) 'open' can open file in Eclipse AND the system editor

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13430?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-13430: ----------------------------------- As a workaround exists and Forge 2 is around the corner, this issue will not be fixed > 'open' can open file in Eclipse AND the system editor > ----------------------------------------------------- > > Key: JBIDE-13430 > URL: https://issues.jboss.org/browse/JBIDE-13430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final > Reporter: Matt Benson > Assignee: Koen Aers > Fix For: 4.1.x > > > There is a no-args version of the 'open' command that implicitly refers to the '.' resource, usable, for example, after using commands from the Java plugin to create a new type, leaving that new type's source file as the current context. It appears that the AllCommandsInterceptor looks for commands followed by a space and as such misses commands without arguments. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13430) 'open' can open file in Eclipse AND the system editor

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13430?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13430. ------------------------------- Resolution: Won't Fix > 'open' can open file in Eclipse AND the system editor > ----------------------------------------------------- > > Key: JBIDE-13430 > URL: https://issues.jboss.org/browse/JBIDE-13430 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final > Reporter: Matt Benson > Assignee: Koen Aers > Fix For: 4.1.x > > > There is a no-args version of the 'open' command that implicitly refers to the '.' resource, usable, for example, after using commands from the Java plugin to create a new type, leaving that new type's source file as the current context. It appears that the AllCommandsInterceptor looks for commands followed by a space and as such misses commands without arguments. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16016) Annotation @ElementCollection causes random Entity Error

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16016?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-16016: ------------------------------ Fix Version/s: 4.2.x > Annotation @ElementCollection causes random Entity Error > -------------------------------------------------------- > > Key: JBIDE-16016 > URL: https://issues.jboss.org/browse/JBIDE-16016 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.0.Final > Environment: Ubuntu 13.10 64-bit, Intel i-7, 4GB RAM > Reporter: Fabio Zanardi > Fix For: 4.2.x > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13210) Generate Hibernate/JPA Annotations is disabled in main menubar

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13210?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13210: ------------------------------ Fix Version/s: 4.2.x (was: 4.0.x) > Generate Hibernate/JPA Annotations is disabled in main menubar > -------------------------------------------------------------- > > Key: JBIDE-13210 > URL: https://issues.jboss.org/browse/JBIDE-13210 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.0.0.CR1 > Environment: JBDS 6.0.0.CR1b, L64 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.1.x, 4.2.x > > > Source -> Generate Hibernate/JPA is disabled (at least I didn't find any case when it's enabled). Operation works via context (on java file(s)) without problems. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13523) Include Hints plugin in Core

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13523?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13523: ------------------------------ Fix Version/s: 4.2.x (was: 4.1.x) > Include Hints plugin in Core > ---------------------------- > > Key: JBIDE-13523 > URL: https://issues.jboss.org/browse/JBIDE-13523 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.2.x > > > As for the F2F meeting in 2013, it has been decided that the Hint plugin should take part in core. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16265) JPA validation reports Strategy class "uuid2" could not be found

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16265?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-16265: ------------------------------ Fix Version/s: 4.2.0.Alpha2 > JPA validation reports Strategy class "uuid2" could not be found > ---------------------------------------------------------------- > > Key: JBIDE-16265 > URL: https://issues.jboss.org/browse/JBIDE-16265 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.1.CR1 > Reporter: Jim Boettcher > Priority: Minor > Fix For: 4.2.0.Alpha2 > > > An Entity class with the following: > @Id > @GeneratedValue(generator = "system-uuid") > @GenericGenerator(name = "system-uuid", strategy = "uuid2") > @Column(name = "id", unique = true) > private UUID id; > > gives the error: > Strategy class "uuid2" could not be found > changing the strategy to "uuid" will clear the error. > > My Project Facet has JPA 2.0 > The JPA configuration has: > Platform: Hibernate (JPA 2.0) > JPA implementation: > Disable Library Configuration > the Hibernate jars are on the project classpath -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16229) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [VPE]

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16229?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov closed JBIDE-16229. ------------------------------------------ Resolution: Done > For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [VPE] > -------------------------------------------------- > > Key: JBIDE-16229 > URL: https://issues.jboss.org/browse/JBIDE-16229 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.0.Alpha1 > > > For JBIDE 4.2.0.Alpha1 [VPE]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1 > [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 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:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1; > {code} > mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Alpha1x > git push origin jbosstools-4.2.0.Alpha1x > {code} > 5. Close (do 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 VPE 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, 4 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 December 2013