[JBoss JIRA] (JBIDE-2934) JBoss Tools Palette is not functioning correctly with m2eclipse when POM Editor feature is enabled
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-2934?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-2934.
--------------------------------
Closing, nothing to do.
> JBoss Tools Palette is not functioning correctly with m2eclipse when POM Editor feature is enabled
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-2934
> URL: https://issues.redhat.com/browse/JBIDE-2934
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 2.1.2
> Environment: JDK 1.5.06, Eclipse 3.3.2, JBoss Tools 2.1.2.GA, m2eclipse 0.9.6
> Reporter: Mehmet Salgar
> Assignee: Snjezana Peco
> Priority: Major
>
> I have a long runnning project which I initially started with JBoss
> Tools and m2eclipse 0.9.4 configuration and our WTP applicaiton and
> JBoss Tools are working perfectly.
> For a while I didn't work at the FE side to watch functionalty but now I have a
> task there and I see that JBoss Tools Palette is not letting me work with JSF
> components.
> During the time I had updated my configuration to JBoss Tools 2.1.2.GA and
> m2eclipse 0.9.6...
> To research the problem I installed brand new
> eclipse and installed JBoss Tools 2.1.2.GA also new, and a new JSF
> project (with JBoss Tools or Eclipse wizard I don't know exactly)
> JBoss Tools Palette was functional. To further analyze the problem I
> install m2eclipse plugin 0.9.6 (http://m2eclipse.sonatype.org/update/site.xml)
> then JBoss Tolls Palette stop working.
> I didn't introduced any Maven nature to test project(maven enabled)
> just installed m2eclipse plugin....
> After little bit research and helps in the forums, I discovered if POM Editor feature
> of the m2eclipse enabled, this looks like preventing that JBoss Tools Palette receive
> events(totally my speculation, I have no idea what is going on there)...
> This problem is also reported in JIRA for m2eclipse under (http://jira.codehaus.org/browse/MNGECLIPSE-967)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-2934) JBoss Tools Palette is not functioning correctly with m2eclipse when POM Editor feature is enabled
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-2934?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-2934:
---------------------------------
Component/s: maven
> JBoss Tools Palette is not functioning correctly with m2eclipse when POM Editor feature is enabled
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-2934
> URL: https://issues.redhat.com/browse/JBIDE-2934
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 2.1.2
> Environment: JDK 1.5.06, Eclipse 3.3.2, JBoss Tools 2.1.2.GA, m2eclipse 0.9.6
> Reporter: Mehmet Salgar
> Assignee: Snjezana Peco
> Priority: Major
>
> I have a long runnning project which I initially started with JBoss
> Tools and m2eclipse 0.9.4 configuration and our WTP applicaiton and
> JBoss Tools are working perfectly.
> For a while I didn't work at the FE side to watch functionalty but now I have a
> task there and I see that JBoss Tools Palette is not letting me work with JSF
> components.
> During the time I had updated my configuration to JBoss Tools 2.1.2.GA and
> m2eclipse 0.9.6...
> To research the problem I installed brand new
> eclipse and installed JBoss Tools 2.1.2.GA also new, and a new JSF
> project (with JBoss Tools or Eclipse wizard I don't know exactly)
> JBoss Tools Palette was functional. To further analyze the problem I
> install m2eclipse plugin 0.9.6 (http://m2eclipse.sonatype.org/update/site.xml)
> then JBoss Tolls Palette stop working.
> I didn't introduced any Maven nature to test project(maven enabled)
> just installed m2eclipse plugin....
> After little bit research and helps in the forums, I discovered if POM Editor feature
> of the m2eclipse enabled, this looks like preventing that JBoss Tools Palette receive
> events(totally my speculation, I have no idea what is going on there)...
> This problem is also reported in JIRA for m2eclipse under (http://jira.codehaus.org/browse/MNGECLIPSE-967)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-6066) Wizard for Session Beans doesn't support "No-Interface Session Beans"
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-6066?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-6066:
---------------------------------
Component/s: server
> Wizard for Session Beans doesn't support "No-Interface Session Beans"
> ---------------------------------------------------------------------
>
> Key: JBIDE-6066
> URL: https://issues.redhat.com/browse/JBIDE-6066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 3.1.0.GA
> Reporter: Juergen Zimmermann
> Priority: Major
> Attachments: screenshot-wizard-session-bean.jpg
>
>
> I'm not sure if this is part of WTP or JBoss Tools.
> EJB 3.1 is implemented in JBoss 6.0.0.M2 and provides "no-interface session beans" in addition to stateless/stateful session beans.
> However, when using the wizard to create a new session bean, then only stateless or stateful session beans with either a local or remote interface can be created. I'll provide a screenshot to illustrate the issue.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-1528) Deploy or EAR/WAR should suggest deploying ds.xml too
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-1528?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-1528:
---------------------------------
Component/s: server
> Deploy or EAR/WAR should suggest deploying ds.xml too
> ------------------------------------------------------
>
> Key: JBIDE-1528
> URL: https://issues.redhat.com/browse/JBIDE-1528
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Reporter: Samuel Mendenhall
> Priority: Major
> Fix For: 2.1.0.CR1
>
>
> Create a Seam project, deploy it, then remove it from the jboss server in the servers view. Right click on the project and Run As -> Run on Server then the main project ear/war will only be added to the project. The datasource file is no longer there, therefore, when the war is deployed it will fail because it needs the datasource. If I right click on the server and go to Add and Remove Projects, only the main project shows up, the datasouce does not.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-7425) How to ask JBoss Tools not to deploy jaxb-impl-2.1.3.jar?
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-7425?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-7425:
---------------------------------
Component/s: server
> How to ask JBoss Tools not to deploy jaxb-impl-2.1.3.jar?
> ---------------------------------------------------------
>
> Key: JBIDE-7425
> URL: https://issues.redhat.com/browse/JBIDE-7425
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Burrsitis Sutter
> Priority: Major
> Attachments: server.log
>
>
> My Spring Travel application fails to deploy via JBDS4 Beta1 to AS6 because of jaxb-impl-2.1.3.jar.
> Video coming, along with logs and resulting .war
> Stack trace
> 15:14:55,475 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to PostClassLoader: name=vfs:///C:/servers/jboss-6.0.0.20100911-M5v2/jboss-6.0.0.20100911-M5/server/default/deploy/travel.war state=ClassLoader mode=Manual requiredState=PostClassLoader: org.jboss.deployers.spi.DeploymentException: Error during deploy: vfs:///C:/servers/jboss-6.0.0.20100911-M5v2/jboss-6.0.0.20100911-M5/server/default/deploy/travel.war
> at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) [:2.2.0.Alpha7]
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:185) [:2.2.0.Alpha7]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1832) [:2.2.0.Alpha7]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1550) [:2.2.0.Alpha7]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1491) [:2.2.0.Alpha7]
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:379) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:2044) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:1083) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.executeOrIncrementStateDirectly(AbstractController.java:1322) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1246) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1139) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:939) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:654) [jboss-dependency.jar:2.2.0.Alpha10]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.change(DeployersImpl.java:1983) [:2.2.0.Alpha7]
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:1076) [:2.2.0.Alpha7]
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:679) [:2.2.0.Alpha7]
> at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.process(MainDeployerPlugin.java:106) [:6.0.0.20100911-M5]
> at org.jboss.profileservice.dependency.ProfileControllerContext$DelegateDeployer.process(ProfileControllerContext.java:130) [:0.1.0.Alpha1]
> at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.deploy(HDScanner.java:240) [:0.1.0.Alpha1]
> at org.jboss.profileservice.deployment.hotdeploy.HDScanner$HDScanAction.complete(HDScanner.java:192) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.TwoPCActionWrapper.doComplete(TwoPCActionWrapper.java:59) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.complete(AbstractTwoPhaseModificationAction.java:74) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.actions.AbstractTwoPhaseModificationAction.prepare(AbstractTwoPhaseModificationAction.java:94) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.ModificationSession.prepare(ModificationSession.java:87) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.AbstractActionController.internalPerfom(AbstractActionController.java:234) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.AbstractActionController.performWrite(AbstractActionController.java:213) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:150) [:0.1.0.Alpha1]
> at org.jboss.profileservice.management.AbstractActionController.perform(AbstractActionController.java:135) [:0.1.0.Alpha1]
> at org.jboss.profileservice.deployment.hotdeploy.HDScanner.scan(HDScanner.java:146) [:0.1.0.Alpha1]
> at org.jboss.profileservice.deployment.hotdeploy.HDScanner.run(HDScanner.java:90) [:0.1.0.Alpha1]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) [:1.6.0_20]
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) [:1.6.0_20]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) [:1.6.0_20]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) [:1.6.0_20]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) [:1.6.0_20]
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) [:1.6.0_20]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20]
> at java.lang.Thread.run(Thread.java:619) [:1.6.0_20]
> Caused by: java.lang.Error: Error visiting "/C:/servers/jboss-6.0.0.20100911-M5v2/jboss-6.0.0.20100911-M5/server/default/deploy/travel.war/WEB-INF/lib/jaxb-impl-2.1.3.jar/com/sun/xml/bind/v2/schemagen/XmlSchemaGenerator$Namespace.class"
> at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:268) [jboss-classloading-vfs.jar:2.2.0.Alpha8]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:407) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:409) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.vfs.VirtualFile.visit(VirtualFile.java:395) [jboss-vfs.jar:3.0.0.CR5]
> at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:102) [jboss-classloading-vfs.jar:2.2.0.Alpha8]
> at org.jboss.deployers.vfs.plugins.classloader.VFSDeploymentClassLoaderPolicyModule.visit(VFSDeploymentClassLoaderPolicyModule.java:181) [:2.2.0.Alpha7]
> at org.jboss.scanning.plugins.DeploymentUnitScanner.scan(DeploymentUnitScanner.java:111) [:1.0.0.Alpha6]
> at org.jboss.scanning.spi.helpers.UrlScanner.scan(UrlScanner.java:96) [:1.0.0.Alpha6]
> at org.jboss.scanning.deployers.ScanningDeployer.deploy(ScanningDeployer.java:90) [:1.0.0.Alpha6]
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) [:2.2.0.Alpha7]
> ... 37 more
> Caused by: java.lang.RuntimeException: Error visiting resource: VFSResourceContext @ com/sun/xml/bind/v2/schemagen/XmlSchemaGenerator$Namespace.class / BaseClassLoader@1534d8c{vfs:///C:/servers/jboss-6.0.0.20100911-M5v2/jboss-6.0.0.20100911-M5/server/default/deploy/travel.war}, visitor: org.jboss.scanning.annotations.plugins.GenericAnnotationVisitor@1d7dfda
> at org.jboss.scanning.plugins.visitor.IgnoreSetErrorHandler.handleError(IgnoreSetErrorHandler.java:56) [:1.0.0.Alpha6]
> at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.visit(ReflectResourceVisitor.java:91) [:1.0.0.Alpha6]
> at org.jboss.scanning.annotations.plugins.AnnotationsScanningPlugin.visit(AnnotationsScanningPlugin.java:89) [:1.0.0.Alpha6]
> at org.jboss.scanning.spi.helpers.ScanningPluginWrapper.visit(ScanningPluginWrapper.java:112) [:1.0.0.Alpha6]
> at org.jboss.classloading.plugins.visitor.FederatedResourceVisitor.visit(FederatedResourceVisitor.java:101) [jboss-classloading.jar:2.2.0.Alpha8]
> at org.jboss.classloading.plugins.vfs.VFSResourceVisitor.visit(VFSResourceVisitor.java:264) [jboss-classloading-vfs.jar:2.2.0.Alpha8]
> ... 51 more
> Caused by: java.lang.reflect.GenericSignatureFormatError
> at sun.reflect.generics.parser.SignatureParser.error(SignatureParser.java:103) [:1.6.0_20]
> at sun.reflect.generics.parser.SignatureParser.parseSimpleClassTypeSignature(SignatureParser.java:262) [:1.6.0_20]
> at sun.reflect.generics.parser.SignatureParser.parseClassTypeSignatureSuffix(SignatureParser.java:270) [:1.6.0_20]
> at sun.reflect.generics.parser.SignatureParser.parseClassTypeSignature(SignatureParser.java:244) [:1.6.0_20]
> at sun.reflect.generics.parser.SignatureParser.parseFieldTypeSignature(SignatureParser.java:228) [:1.6.0_20]
> at sun.reflect.generics.parser.SignatureParser.parseTypeArgument(SignatureParser.java:319) [:1.6.0_20]
> at sun.reflect.generics.parser.SignatureParser.parseTypeArguments(SignatureParser.java:287) [:1.6.0_20]
> at sun.reflect.generics.parser.SignatureParser.parseSimpleClassTypeSignature(SignatureParser.java:260) [:1.6.0_20]
> at sun.reflect.generics.parser.SignatureParser.parseClassTypeSignatureSuffix(SignatureParser.java:270) [:1.6.0_20]
> at sun.reflect.generics.parser.SignatureParser.parseClassTypeSignature(SignatureParser.java:244) [:1.6.0_20]
> at sun.reflect.generics.parser.SignatureParser.parseFieldTypeSignature(SignatureParser.java:228) [:1.6.0_20]
> at sun.reflect.generics.parser.SignatureParser.parseTypeSignature(SignatureParser.java:359) [:1.6.0_20]
> at sun.reflect.generics.parser.SignatureParser.parseTypeSig(SignatureParser.java:157) [:1.6.0_20]
> at sun.reflect.generics.repository.FieldRepository.parse(FieldRepository.java:34) [:1.6.0_20]
> at sun.reflect.generics.repository.FieldRepository.parse(FieldRepository.java:24) [:1.6.0_20]
> at sun.reflect.generics.repository.AbstractRepository.<init>(AbstractRepository.java:56) [:1.6.0_20]
> at sun.reflect.generics.repository.FieldRepository.<init>(FieldRepository.java:30) [:1.6.0_20]
> at sun.reflect.generics.repository.FieldRepository.make(FieldRepository.java:48) [:1.6.0_20]
> at java.lang.reflect.Field.getGenericInfo(Field.java:85) [:1.6.0_20]
> at java.lang.reflect.Field.getGenericType(Field.java:223) [:1.6.0_20]
> at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl$1.run(IntrospectionTypeInfoFactoryImpl.java:202) [jboss-reflect.jar:2.2.0.Alpha9]
> at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl$1.run(IntrospectionTypeInfoFactoryImpl.java:190) [jboss-reflect.jar:2.2.0.Alpha9]
> at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_20]
> at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getFields(IntrospectionTypeInfoFactoryImpl.java:189) [jboss-reflect.jar:2.2.0.Alpha9]
> at org.jboss.reflect.plugins.ClassInfoImpl.getDeclaredFields(ClassInfoImpl.java:432) [jboss-reflect.jar:2.2.0.Alpha9]
> at org.jboss.scanning.plugins.visitor.ClassHierarchyResourceVisitor.handleClass(ClassHierarchyResourceVisitor.java:81) [:1.0.0.Alpha6]
> at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.doVisit(ReflectResourceVisitor.java:108) [:1.0.0.Alpha6]
> at org.jboss.scanning.plugins.visitor.ReflectResourceVisitor.visit(ReflectResourceVisitor.java:86) [:1.0.0.Alpha6]
> ... 55 more
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months
[JBoss JIRA] (JBIDE-2269) On linux, some of default window sizes are too small
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-2269?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-2269:
---------------------------------
Component/s: common
> On linux, some of default window sizes are too small
> ----------------------------------------------------
>
> Key: JBIDE-2269
> URL: https://issues.redhat.com/browse/JBIDE-2269
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 2.1.0.CR1
> Reporter: Galder Zamarreño
> Priority: Major
> Fix For: LATER
>
> Attachments: JBIDE-2269-Add and Remove Projects-Default.png, JBIDE-2269-Add and Remove Projects-Expanded.png, JBIDE-2269-New Server Runtime-Default.png, JBIDE-2269-New Server Runtime-Expanded.png
>
>
> On Linux (Gnome), default window sizes for "New Server" and
> "New Server Runtime" wizards are too small. I'm always having
> to make them bigger.
> In the case of "New Server" specially to add/remove deployable
> archives from different projects. Without expanding it, I can't see the
> full name of most of my project archives.
> In the case of "New Server Runtime", this is to be able to see
> most of the server configurations in a AS/EAP instance. With the
> default size, I can only see one.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 10 months