February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13383) Support running on Eclipse Kepler (4.3) platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13383?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13383: ------------------------------- Assignee: Denis Golovin > Support running on Eclipse Kepler (4.3) platform > ------------------------------------------------ > > Key: JBIDE-13383 > URL: https://issues.jboss.org/browse/JBIDE-13383 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, target-platform, updatesite > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > Attachments: full-reactor-summary-with-compilation-errors.txt > > > Kepler is coming and it have many improvements performance wise over Juno and is the only version certified to run on Windows 8 afaics. It is also the first version where WTP static web project becomes more usable. and of course the general notion that Kepler is the only version we can actually get fixes into. > Migration guide for Eclipse Platform (currently empty - I've posted question on http://dev.eclipse.org/mhonarc/lists/eclipse-dev/ to check if better new doc) > http://htmlpreview.github.com/?https://github.com/eclipse/eclipse.platfor... > Migration tips for WTP (this time there are *Actual* changes!) > http://wiki.eclipse.org/New_Help_for_Old_Friends_VIII > Last years migration: JBIDE-11549 (Juno), JBIDE-8624 (Indigo). > Please link related Kepler runtime/build issues to this issue. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13611) forge failing to compile due to two poms w/ the same GAV

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13611?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-13611: ----------------------------------- This was resolved earlier > forge failing to compile due to two poms w/ the same GAV > -------------------------------------------------------- > > Key: JBIDE-13611 > URL: https://issues.jboss.org/browse/JBIDE-13611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Koen Aers > > {code} > [ERROR] Two or more projects in the reactor have the same identifier, please make sure that <groupId>:<artifactId>:<version> is unique for each project: > {org.jboss.tools.forge.features:org.jboss.tools.forge.feature:1.2.0-SNAPSHOT=[/mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.feature/pom.xml, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.ext.feature/pom.xml], > org.jboss.tools.forge.features:org.jboss.tools.forge.test.feature:1.2.0-SNAPSHOT=[/mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.test.feature/pom.xml, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.ext.test.feature/pom.xml]} -> [Help 1] > {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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13611) forge failing to compile due to two poms w/ the same GAV

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13611?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-13611. ------------------------------- Resolution: Done > forge failing to compile due to two poms w/ the same GAV > -------------------------------------------------------- > > Key: JBIDE-13611 > URL: https://issues.jboss.org/browse/JBIDE-13611 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.0.Alpha1, 4.1.0.Alpha2 > Reporter: Nick Boldt > Assignee: Koen Aers > > {code} > [ERROR] Two or more projects in the reactor have the same identifier, please make sure that <groupId>:<artifactId>:<version> is unique for each project: > {org.jboss.tools.forge.features:org.jboss.tools.forge.feature:1.2.0-SNAPSHOT=[/mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.feature/pom.xml, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.ext.feature/pom.xml], > org.jboss.tools.forge.features:org.jboss.tools.forge.test.feature:1.2.0-SNAPSHOT=[/mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.test.feature/pom.xml, /mnt/hudson_workspace/workspace/jbosstools-forge_master/sources/features/org.jboss.tools.forge.ext.test.feature/pom.xml]} -> [Help 1] > {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

13 years, 1 month

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 updated JBIDE-13430: ------------------------------ Fix Version/s: 4.1.x > '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

13 years, 1 month

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.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.1.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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13537) Unable to create EAP6.1 server [4.0.1 maintenance]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13537?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-13537: -------------------------------- Labels: (was: respin-a) > Unable to create EAP6.1 server [4.0.1 maintenance] > --------------------------------------------------- > > Key: JBIDE-13537 > URL: https://issues.jboss.org/browse/JBIDE-13537 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, runtime-detection > Affects Versions: 4.1.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.0.1.Final > > Attachments: New Server Runtime Environment _002.png, New Server Runtime Environment _003.png > > > EAP6.1 is detected via runtime detection but nothing happens when I click OK to create runtime. Also manually adding it through Runtime Enviroment -> add -> EAP6.x does not work. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13573) Add "Forge Preferences" action to Forge Console

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13573?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13573: ------------------------------ Fix Version/s: 4.1.x > Add "Forge Preferences" action to Forge Console > ----------------------------------------------- > > Key: JBIDE-13573 > URL: https://issues.jboss.org/browse/JBIDE-13573 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.1.0.Alpha1 > Reporter: Snjezana Peco > Assignee: Koen Aers > Fix For: 4.1.x > > > It would be good to have this action or, at least, the Debug/Run toggle button in the Forge Console view. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13446) Forge pick-up command throws NPE

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13446?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13446: ------------------------------ Fix Version/s: 4.0.x (was: 4.0.1.Final) > Forge pick-up command throws NPE > -------------------------------- > > Key: JBIDE-13446 > URL: https://issues.jboss.org/browse/JBIDE-13446 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Environment: OS X Mountain Lion > Apple JDK 1.6 32bit > JBDS 6.0.0.GA / JBT master nightly 4.1.0.Alpha1-v20130129-1449-B6053 on Eclipse Kepler M4 > And: > Fedora 17, JDK 1.7.0_13, JBDS 6.0.0 GA - all 64-bit > Reporter: Martin Malina > Assignee: Koen Aers > Priority: Critical > Fix For: 4.0.x, 4.1.x > > > When playing around w/ Ticket Monster [1] I found out that Show in -> Forge console does not work for me on a project or directory in Project Explorer. > It throws this exception: > {code} > [no project] workspace $ set VERBOSE true > [no project] workspace $ pick-up /Users/rasp/jbossqa/JBDS/nightly-jbt-2013-01-30/workspace/jboss-javaee6-webapp > java.lang.NullPointerException***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces) > [no project] workspace $ > at org.apache.maven.RepositoryUtils.getLayout(RepositoryUtils.java:214) > at org.apache.maven.RepositoryUtils.toRepo(RepositoryUtils.java:200) > at org.apache.maven.RepositoryUtils.toRepos(RepositoryUtils.java:190) > at org.apache.maven.project.DefaultProjectBuilder$InternalConfig.<init>(DefaultProjectBuilder.java:662) > at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:102) > at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:86) > at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:304) > at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:393) > at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:171) > at org.jboss.forge.shell.project.DependencyInstallerImpl.isInstalled(DependencyInstallerImpl.java:170) > at org.jboss.forge.git.GitAPIFacet.isInstalled(GitAPIFacet.java:42) > at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153) > at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208) > at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186) > at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178) > at org.jboss.forge.project.services.ProjectFactory.findProjectRecursively(ProjectFactory.java:117) > at org.jboss.forge.shell.project.ProjectInitializer.doInit(ProjectInitializer.java:91) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) > at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) > at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628) > at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75) > at org.jboss.forge.shell.project.CurrentProject.setCurrentResource(CurrentProject.java:80) > at org.jboss.forge.shell.ShellImpl.setCurrentResource(ShellImpl.java:1239) > at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.setCurrentResource(ShellImpl$Proxy$_$$_WeldClientProxy.java) > at org.jboss.forge.shell.plugins.builtin.PickupResourcePlugin.run(PickupResourcePlugin.java:85) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.forge.shell.command.Execution.perform(Execution.java:134) > at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109) > at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47) > at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:818) > at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:841) > at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:631) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48) > at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125) > at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305) > at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54) > at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163) > at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299) > at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188) > at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59) > at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282) > at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265) > at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234) > at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622) > at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616) > at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:172) > at java.lang.Thread.run(Thread.java:722) > {code} > This happens in both JBDS 6 and JBT 4.1 nightly, but not in JBDS 5. It's probably only reproducible on Mac - psrna verified this on Linux today and it worked for him. I tried two different instances of JBDS 6 and one instance of JBT 4.1.0.Alpha1 nightly installed on Eclipse Kepler M4. > Please let me know if I should create a FORGE issue. > The forge runtime versions: > JBDS 6: org.jboss.tools.forge.runtime_1.1.0.Final-v20121205-1934-B69 > JBT nightly: org.jboss.tools.forge.runtime_1.2.0.Alpha1-v20130128-1407-B204 > [1] http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/#_... -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13637) 'Go to Selection' command throws error

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13637?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13637: ------------------------------ Fix Version/s: 4.1.x 4.0.x (was: 4.0.1.Final) (was: 4.1.0.Alpha2) > 'Go to Selection' command throws error > -------------------------------------- > > Key: JBIDE-13637 > URL: https://issues.jboss.org/browse/JBIDE-13637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Final > Reporter: Pavol Srna > Assignee: Koen Aers > Fix For: 4.0.x, 4.1.x > > > When clicked on 'Go to Selection' button in Forge view the selected resource in Project Explorer should be picked-up in forge console. But what I get is: ***ERROR*** No such command. This happens only when using the command for the first time, all the following attempts to use that command are working. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13302) Entities generation is running in UI thread and causes IDE freeze when it cannot connect to DB

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13302?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13302: ------------------------------ Fix Version/s: 4.0.2.Final (was: 4.0.1.Final) > Entities generation is running in UI thread and causes IDE freeze when it cannot connect to DB > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-13302 > URL: https://issues.jboss.org/browse/JBIDE-13302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.0.0.Final > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.0.2.Final > > > Connection is executed in UI thread which is blocking IDE mainly when connection cannot be established > Steps: > EXE: Create JPA project > EXE: Stop database prepared for the project > EXE: Run JPA Tools -> Generate Entities from tables > ASSERT: UI should be responsive and it should be possible to cancel action -- 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

13 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 2013