[JBoss JIRA] (JBIDE-20037) jboss-deployment-structure.xml is not used if added to an existing project
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20037?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-20037:
-------------------------------------
I've noticed similar things, but I've been unable to track down what could possibly be causing it. My debugging usually indicates that my code is run, and run properly, and so the bug could be somewhere in jdt / classpath management, where it delays or buffers changes in case of multiple changes.
I really have no evidence of this though, just an idea I thought sounded possible ;)
> jboss-deployment-structure.xml is not used if added to an existing project
> --------------------------------------------------------------------------
>
> Key: JBIDE-20037
> URL: https://issues.jboss.org/browse/JBIDE-20037
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Labels: respin-a
> Fix For: 4.3.0.Beta1
>
>
> This is a corner case of JBIDE-18377 which was fixed in 4.3.0.Beta1.
> When you import a project with an existing jboss-deployment-structure.xml, the modules that are defined in that file are now added as jars to the build path of the project (thanks to JBIDE-18377). But, as discovered by Rob, if you only add the file after the project was created, it will not be picked up ("due to aggressive caching and a missing listener").
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19946) running webservice test gives errors
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19946?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick updated JBIDE-19946:
--------------------------------------
Fix Version/s: 4.3.0.Beta2
> running webservice test gives errors
> ------------------------------------
>
> Key: JBIDE-19946
> URL: https://issues.jboss.org/browse/JBIDE-19946
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Reporter: Max Rydahl Andersen
> Assignee: Brian Fitzpatrick
> Fix For: 4.3.0.Beta2
>
>
> running 4.3.0.Beta1x with jdk's defined I get this error:
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> Retrieving document at 'file:/Users/max/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data/JBossWSTestProject/hello_world.wsdl'.
> null
> null
> Retrieving document at '/Users/max/code/jbosstools/jbosstools-webservices/tests/org.jboss.tools.ws.creation.core.test/target/work/data/JBossWSTestProject/hello_world.wsdl'.
> Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 272.543 sec <<< FAILURE! - in org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite
> testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSTopDownCommandTest) Time elapsed: 82.428 sec
> testDeployResult(org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest) Time elapsed: 127.267 sec <<< FAILURE!
> junit.framework.AssertionFailedError: ***********************
> Create Web Service Client...
> Create Web Service...
> Create Web Service Operation...
> Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
> at com.sun.proxy.$Proxy14.sayHello(Unknown Source)
> at org.example.www.helloworld.clientsample.ClientSample.main(ClientSample.java:14)
> Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:439)
> at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:83)
> at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
> at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
> at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
> at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
> ... 4 more
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.checkText(JBossWSJavaFirstCommandTest.java:163)
> at org.jboss.tools.ws.creation.core.test.command.JBossWSJavaFirstCommandTest.testDeployResult(JBossWSJavaFirstCommandTest.java:116)
> testInitialClientCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 15.26 sec
> testClientCodeGenerationCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 17.628 sec
> testRemoveClientJarsCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSClientCommandTest) Time elapsed: 14.25 sec
> testMergeWebXMLCommand(org.jboss.tools.ws.creation.core.test.command.JBossWSMergeWebXMLCommandTest) Time elapsed: 9.174 sec
> testJBIDE6175(org.jboss.tools.ws.creation.core.test.command.JBossWSClientSampleCreationCommandTest) Time elapsed: 6.416 sec
> Results :
> Failed tests:
> JBossWSJavaFirstCommandTest.testDeployResult:116->checkText:163 ***********************
> Create Web Service Client...
> Create Web Service...
> Create Web Service Operation...
> Exception in thread "main" javax.xml.ws.WebServiceException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
> at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
> at com.sun.proxy.$Proxy14.sayHello(Unknown Source)
> at org.example.www.helloworld.clientsample.ClientSample.main(ClientSample.java:14)
> Caused by: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
> at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:439)
> at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:83)
> at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
> at org.jboss.ws.core.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:59)
> at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:158)
> at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:291)
> at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19967) setNote on InputComponent should word wrap in GUIs
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19967?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-19967:
------------------------------------
Thanks. Now it works.
> setNote on InputComponent should word wrap in GUIs
> --------------------------------------------------
>
> Key: JBIDE-19967
> URL: https://issues.jboss.org/browse/JBIDE-19967
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: forge
> Affects Versions: 4.3.0.Alpha2
> Reporter: Claus Ibsen
> Assignee: George Gastaldi
> Labels: respin-a
> Fix For: 4.3.0.Beta1
>
> Attachments: Screen Shot 2015-06-06 at 2.10.06 PM.png, Screen Shot 2015-06-06 at 2.11.54 PM.png
>
>
> Thanks for setNote to set a description in the UI. This works nice. See screenshot.
> However if the text is long then its not word wrap. But you have to enlarge the UI Wizard to see all the text.
> But the title text in the top is word wrapping.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20085) JEE natures are not listed properly
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20085?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20085:
----------------------------------------
Actually, those project are not in the regular JEE shape (which is the one created by WebTools wizards), so they are not detected as JEE immediately. However, m2e with m2e-wtp will take care of enabling the necessary JEE natures on those projects. Unfortunately, it's really something not that can be controlled and known while doing the import...
> JEE natures are not listed properly
> -----------------------------------
>
> Key: JBIDE-20085
> URL: https://issues.jboss.org/browse/JBIDE-20085
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Attachments: natures.png, report-dialog.png
>
>
> I tried to import projects from https://github.com/jboss-developer/jboss-sandbox-quickstarts.git
> Even though they are JEE examples the only nature listed in the report was Maven nature. After import there are also JEE natures set correctly.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19810) easymport is slow and wrong compared to basic import
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19810?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19810:
-----------------------------------
Summary: easymport is slow and wrong compared to basic import (was: easymport is slow and wrong compared to basic import since it lets mvn overrule .project)
> easymport is slow and wrong compared to basic import
> ----------------------------------------------------
>
> Key: JBIDE-19810
> URL: https://issues.jboss.org/browse/JBIDE-19810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Reporter: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> when using git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.git it already has tons of projects with .project in it but also pom.xml. Resulting in slow and eventually wrong imported projects.
> This import is *really* slow with easyimport vs just using plain file import.
> Shouldn't easyimport honor existing .project files over presence of a pom.xml (or anything else) ?
> If not could we allow users to disable certain configurators for an import or even reorder priority so mvn wont win ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20070) Fix minor issues in RedDeer import
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20070?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-20070:
-----------------------------------
Fix Version/s: 4.3.0.Beta2
> Fix minor issues in RedDeer import
> ----------------------------------
>
> Key: JBIDE-20070
> URL: https://issues.jboss.org/browse/JBIDE-20070
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Priority: Minor
> Fix For: 4.3.0.Beta2
>
> Attachments: dialog.png
>
>
> When I try to import the whole RedDeer project (cloned from https://github.com/jboss-reddeer/reddeer.git) I can see that some folders have listed "Maven, Java" and some only "Maven" even though the directory structure seems the same to me (e.g. directory "plugins" and directory "features" contain only one pom file and set of other folders, but one has "Java" listed and one does not).
> List of minor issues:
> - the root folder (reddeer) has listed Maven, Eclipse project - I think the Eclipse project should not be there
> - features has listed "Maven" but plugins and tests have "Maven, Java"
> - all plugins in tests folder are correctly recognized as OSGI bundles except for the org.jboss.reddeer.workbench.test that has also "Java" nature
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20070) Fix minor issues in RedDeer import
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20070?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-20070:
--------------------------------------
Assignee: Mickael Istria
> Fix minor issues in RedDeer import
> ----------------------------------
>
> Key: JBIDE-20070
> URL: https://issues.jboss.org/browse/JBIDE-20070
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Beta2
>
> Attachments: dialog.png
>
>
> When I try to import the whole RedDeer project (cloned from https://github.com/jboss-reddeer/reddeer.git) I can see that some folders have listed "Maven, Java" and some only "Maven" even though the directory structure seems the same to me (e.g. directory "plugins" and directory "features" contain only one pom file and set of other folders, but one has "Java" listed and one does not).
> List of minor issues:
> - the root folder (reddeer) has listed Maven, Eclipse project - I think the Eclipse project should not be there
> - features has listed "Maven" but plugins and tests have "Maven, Java"
> - all plugins in tests folder are correctly recognized as OSGI bundles except for the org.jboss.reddeer.workbench.test that has also "Java" nature
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20064) composite install fails w/ incompatible dependencies
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20064?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20064:
----------------------------------------
I confirm that since Jenkins update the "script parameters" field for Groovy executor doesn't support line breaks anymore.
This change https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-g... did fix it in our case.
cc [~ogondza]
> composite install fails w/ incompatible dependencies
> ----------------------------------------------------
>
> Key: JBIDE-20064
> URL: https://issues.jboss.org/browse/JBIDE-20064
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_master/14656/console}
> [p2.dir] Software being installed: Eclipse Platform 4.5.0.v20150522-2234 (org.eclipse.platform.feature.group 4.5.0.v20150522-2234)
> [p2.dir] Software currently installed: Eclipse IDE for Java EE Developers 1.5.1.20120917-1257 (epp.package.jee 1.5.1.20120917-1257)
> [p2.dir] Only one of the following can be installed at once:
> [p2.dir] Eclipse Workbench User Guide 4.2.0.v20120829-072800 (org.eclipse.platform.doc.user 4.2.0.v20120829-072800)
> [p2.dir] Eclipse Workbench User Guide 4.5.0.v20150519-0824 (org.eclipse.platform.doc.user 4.5.0.v20150519-0824)
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Eclipse IDE for Java EE Developers 1.5.1.20120917-1257 (epp.package.jee 1.5.1.20120917-1257)
> [p2.dir] To: org.eclipse.platform.ide 0.0.0
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Eclipse Platform 4.2.1.v20120814-120134-9JF7BHVGFyMveli1uX6aTH0q-eAap6PAgOP5mO (org.eclipse.platform.feature.group 4.2.1.v20120814-120134-9JF7BHVGFyMveli1uX6aTH0q-eAap6PAgOP5mO)
> [p2.dir] To: org.eclipse.platform.doc.user [4.2.0.v20120829-072800]
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Eclipse Platform 4.5.0.v20150522-2234 (org.eclipse.platform.feature.group 4.5.0.v20150522-2234)
> [p2.dir] To: org.eclipse.platform.doc.user [4.5.0.v20150519-0824]
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Eclipse Platform 4.2.1.M20120914-1800 (org.eclipse.platform.ide 4.2.1.M20120914-1800)
> [p2.dir] To: org.eclipse.platform.feature.group [4.2.1.v20120814-120134-9JF7BHVGFyMveli1uX6aTH0q-eAap6PAgOP5mO]{code}
> Need to figure out what depends on Eclipse Workbench User Guide 4.2.0.v20120829-072800 (org.eclipse.platform.doc.user) from THREE YEARS AGO.
> Install should only care about Eclipse 4.5.0.v20150519-0824 or newer.
> ---
> Maybe the installer is picking up the wrong Eclipse baseline -
> *Eclipse IDE for Java EE Developers 1.5.1.20120917-1257* instead of *Eclipse Platform 4.5.0.v20150522-2234* ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20064) composite install fails w/ incompatible dependencies
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20064?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20064:
----------------------------------------
Got same issue for install-grnder. It seems like the update of Jenkins changes some behaviour in the groovy plugin. I have the impression that script parameters do not support line break anymore.
> composite install fails w/ incompatible dependencies
> ----------------------------------------------------
>
> Key: JBIDE-20064
> URL: https://issues.jboss.org/browse/JBIDE-20064
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta2
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_master/14656/console}
> [p2.dir] Software being installed: Eclipse Platform 4.5.0.v20150522-2234 (org.eclipse.platform.feature.group 4.5.0.v20150522-2234)
> [p2.dir] Software currently installed: Eclipse IDE for Java EE Developers 1.5.1.20120917-1257 (epp.package.jee 1.5.1.20120917-1257)
> [p2.dir] Only one of the following can be installed at once:
> [p2.dir] Eclipse Workbench User Guide 4.2.0.v20120829-072800 (org.eclipse.platform.doc.user 4.2.0.v20120829-072800)
> [p2.dir] Eclipse Workbench User Guide 4.5.0.v20150519-0824 (org.eclipse.platform.doc.user 4.5.0.v20150519-0824)
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Eclipse IDE for Java EE Developers 1.5.1.20120917-1257 (epp.package.jee 1.5.1.20120917-1257)
> [p2.dir] To: org.eclipse.platform.ide 0.0.0
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Eclipse Platform 4.2.1.v20120814-120134-9JF7BHVGFyMveli1uX6aTH0q-eAap6PAgOP5mO (org.eclipse.platform.feature.group 4.2.1.v20120814-120134-9JF7BHVGFyMveli1uX6aTH0q-eAap6PAgOP5mO)
> [p2.dir] To: org.eclipse.platform.doc.user [4.2.0.v20120829-072800]
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Eclipse Platform 4.5.0.v20150522-2234 (org.eclipse.platform.feature.group 4.5.0.v20150522-2234)
> [p2.dir] To: org.eclipse.platform.doc.user [4.5.0.v20150519-0824]
> [p2.dir] Cannot satisfy dependency:
> [p2.dir] From: Eclipse Platform 4.2.1.M20120914-1800 (org.eclipse.platform.ide 4.2.1.M20120914-1800)
> [p2.dir] To: org.eclipse.platform.feature.group [4.2.1.v20120814-120134-9JF7BHVGFyMveli1uX6aTH0q-eAap6PAgOP5mO]{code}
> Need to figure out what depends on Eclipse Workbench User Guide 4.2.0.v20120829-072800 (org.eclipse.platform.doc.user) from THREE YEARS AGO.
> Install should only care about Eclipse 4.5.0.v20150519-0824 or newer.
> ---
> Maybe the installer is picking up the wrong Eclipse baseline -
> *Eclipse IDE for Java EE Developers 1.5.1.20120917-1257* instead of *Eclipse Platform 4.5.0.v20150522-2234* ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months