[JBoss JIRA] (JBIDE-14396) Imported maven projects sometimes fail to resolve required classpath dependencies for tests
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14396?page=com.atlassian.jira.plugi... ]
Lincoln Baxter III commented on JBIDE-14396:
--------------------------------------------
Is this something that we would need to have plugin writers take into account, or would this be one of those automatically-installed M2E plugins that shows up when you import something new?
> Imported maven projects sometimes fail to resolve required classpath dependencies for tests
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-14396
> URL: https://issues.jboss.org/browse/JBIDE-14396
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven, upstream
> Affects Versions: 4.1.0.Alpha2
> Reporter: Lincoln Baxter III
> Attachments: m2e-forge.site-0.0.1-SNAPSHOT.zip
>
>
> Example project: https://github.com/forge/core/tree/M2ECLIPSE-BUG
> Steps to reproduce:
> * Import all modules into the workspace.
> * Select "aesh-tests" project.
> * Run as -> JUnit Test
> You should see the test fail to launch because of the following Class not found exception:
> {code}
> java.lang.NoClassDefFoundError: Lorg/jboss/forge/aesh/TestShellConfiguration;
> at java.lang.Class.getDeclaredFields0(Native Method)
> at java.lang.Class.privateGetDeclaredFields(Class.java:2300)
> at java.lang.Class.getDeclaredFields(Class.java:1745)
> at org.junit.runners.model.TestClass.<init>(TestClass.java:49)
> at org.junit.runners.ParentRunner.<init>(ParentRunner.java:75)
> at org.junit.runners.BlockJUnit4ClassRunner.<init>(BlockJUnit4ClassRunner.java:57)
> at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:29)
> at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:21)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
> at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
> at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:26)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.<init>(JUnit4TestReference.java:33)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassReference.<init>(JUnit4TestClassReference.java:25)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.createTest(JUnit4TestLoader.java:48)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.loadTests(JUnit4TestLoader.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:452)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: java.lang.ClassNotFoundException: org.jboss.forge.aesh.TestShellConfiguration
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 25 more
> {code}
> This can be solved by manually adding required projects in the workspace as classpath dependencies of the JUnit launch configured for the project being tested, but this is obviously not right, and should be configured automatically by the M2E integration.
--
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
[JBoss JIRA] (JBIDE-14396) Imported maven projects sometimes fail to resolve required classpath dependencies for tests
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14396?page=com.atlassian.jira.plugi... ]
Lincoln Baxter III commented on JBIDE-14396:
--------------------------------------------
Hmmm, okay, I kind-of get that. But... wouldn't the dependencies be the same?
> Imported maven projects sometimes fail to resolve required classpath dependencies for tests
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-14396
> URL: https://issues.jboss.org/browse/JBIDE-14396
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven, upstream
> Affects Versions: 4.1.0.Alpha2
> Reporter: Lincoln Baxter III
> Attachments: m2e-forge.site-0.0.1-SNAPSHOT.zip
>
>
> Example project: https://github.com/forge/core/tree/M2ECLIPSE-BUG
> Steps to reproduce:
> * Import all modules into the workspace.
> * Select "aesh-tests" project.
> * Run as -> JUnit Test
> You should see the test fail to launch because of the following Class not found exception:
> {code}
> java.lang.NoClassDefFoundError: Lorg/jboss/forge/aesh/TestShellConfiguration;
> at java.lang.Class.getDeclaredFields0(Native Method)
> at java.lang.Class.privateGetDeclaredFields(Class.java:2300)
> at java.lang.Class.getDeclaredFields(Class.java:1745)
> at org.junit.runners.model.TestClass.<init>(TestClass.java:49)
> at org.junit.runners.ParentRunner.<init>(ParentRunner.java:75)
> at org.junit.runners.BlockJUnit4ClassRunner.<init>(BlockJUnit4ClassRunner.java:57)
> at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:29)
> at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:21)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
> at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
> at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:26)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.<init>(JUnit4TestReference.java:33)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassReference.<init>(JUnit4TestClassReference.java:25)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.createTest(JUnit4TestLoader.java:48)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.loadTests(JUnit4TestLoader.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:452)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: java.lang.ClassNotFoundException: org.jboss.forge.aesh.TestShellConfiguration
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 25 more
> {code}
> This can be solved by manually adding required projects in the workspace as classpath dependencies of the JUnit launch configured for the project being tested, but this is obviously not right, and should be configured automatically by the M2E integration.
--
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
[JBoss JIRA] (JBIDE-14363) Creation of 'core' component in base
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14363?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-14363:
---------------------------------------
I don't mind to have new, but I still lake the idea of cleaning org.jboss.tools.common.core and org.jboss.tools.common.ui better.
> Creation of 'core' component in base
> ------------------------------------
>
> Key: JBIDE-14363
> URL: https://issues.jboss.org/browse/JBIDE-14363
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Affects Versions: 4.1.0.Beta1
> Reporter: Rob Stryker
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1
>
>
> The creation of a 'core' with minimal dependencies, preferably ONLY platform, is required. The component will have the following requirements:
> 1) Only code designed for re-use can live there
> 2) Only fully and properly java-doc'd code can live there
> 3) Only code for use by TWO OR MORE components can live there.
> 4) Addition of dependencies for this component will be strictly regulated
> 5) Code must be properly tested and have tests cases demonstrating it.
> 6) Code relating to non-platform requirements (such as egit, maven, wtp) will receive additional bundles and features to keep these dependencies separate. FOr example:
> {code}
> org.jboss.tools.core.platform
> org.jboss.tools.core.platform.ui
> org.jboss.tools.core.wtp
> org.jboss.tools.core.wtp.ui
> {code}
> Bundles such as these would require test bundles, as well as features that keep them separate.
> {code}
> org.jboss.tools.core.platform.feature
> org.jboss.tools.core.wtp.feature
> {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
[JBoss JIRA] (JBIDE-14396) Imported maven projects sometimes fail to resolve required classpath dependencies for tests
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14396?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-14396:
-------------------------------------
classifier jars are usually by-products of a regular build. For instance an "ejb-client" would contain a [subset of the regular jar produced for an ejb|http://maven.apache.org/plugins/maven-ejb-plugin/examples/generating-...].
>From a workspace standpoint, when the projects are built incrementally, we have no way of knowing how a particular classifier is produced and what it should contain/expose.
> Imported maven projects sometimes fail to resolve required classpath dependencies for tests
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-14396
> URL: https://issues.jboss.org/browse/JBIDE-14396
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven, upstream
> Affects Versions: 4.1.0.Alpha2
> Reporter: Lincoln Baxter III
> Attachments: m2e-forge.site-0.0.1-SNAPSHOT.zip
>
>
> Example project: https://github.com/forge/core/tree/M2ECLIPSE-BUG
> Steps to reproduce:
> * Import all modules into the workspace.
> * Select "aesh-tests" project.
> * Run as -> JUnit Test
> You should see the test fail to launch because of the following Class not found exception:
> {code}
> java.lang.NoClassDefFoundError: Lorg/jboss/forge/aesh/TestShellConfiguration;
> at java.lang.Class.getDeclaredFields0(Native Method)
> at java.lang.Class.privateGetDeclaredFields(Class.java:2300)
> at java.lang.Class.getDeclaredFields(Class.java:1745)
> at org.junit.runners.model.TestClass.<init>(TestClass.java:49)
> at org.junit.runners.ParentRunner.<init>(ParentRunner.java:75)
> at org.junit.runners.BlockJUnit4ClassRunner.<init>(BlockJUnit4ClassRunner.java:57)
> at org.jboss.arquillian.junit.Arquillian.<init>(Arquillian.java:50)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at org.junit.internal.builders.AnnotatedBuilder.buildRunner(AnnotatedBuilder.java:29)
> at org.junit.internal.builders.AnnotatedBuilder.runnerForClass(AnnotatedBuilder.java:21)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
> at org.junit.internal.builders.AllDefaultPossibilitiesBuilder.runnerForClass(AllDefaultPossibilitiesBuilder.java:26)
> at org.junit.runners.model.RunnerBuilder.safeRunnerForClass(RunnerBuilder.java:59)
> at org.junit.internal.requests.ClassRequest.getRunner(ClassRequest.java:26)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.<init>(JUnit4TestReference.java:33)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestClassReference.<init>(JUnit4TestClassReference.java:25)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.createTest(JUnit4TestLoader.java:48)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestLoader.loadTests(JUnit4TestLoader.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:452)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: java.lang.ClassNotFoundException: org.jboss.forge.aesh.TestShellConfiguration
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 25 more
> {code}
> This can be solved by manually adding required projects in the workspace as classpath dependencies of the JUnit launch configured for the project being tested, but this is obviously not right, and should be configured automatically by the M2E integration.
--
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
[JBoss JIRA] (JBIDE-14363) Creation of 'core' component in base
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14363?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-14363:
---------------------------------------
I believe this is to late to start it for 4.1.x stream.
> Creation of 'core' component in base
> ------------------------------------
>
> Key: JBIDE-14363
> URL: https://issues.jboss.org/browse/JBIDE-14363
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Affects Versions: 4.1.0.Beta1
> Reporter: Rob Stryker
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta1
>
>
> The creation of a 'core' with minimal dependencies, preferably ONLY platform, is required. The component will have the following requirements:
> 1) Only code designed for re-use can live there
> 2) Only fully and properly java-doc'd code can live there
> 3) Only code for use by TWO OR MORE components can live there.
> 4) Addition of dependencies for this component will be strictly regulated
> 5) Code must be properly tested and have tests cases demonstrating it.
> 6) Code relating to non-platform requirements (such as egit, maven, wtp) will receive additional bundles and features to keep these dependencies separate. FOr example:
> {code}
> org.jboss.tools.core.platform
> org.jboss.tools.core.platform.ui
> org.jboss.tools.core.wtp
> org.jboss.tools.core.wtp.ui
> {code}
> Bundles such as these would require test bundles, as well as features that keep them separate.
> {code}
> org.jboss.tools.core.platform.feature
> org.jboss.tools.core.wtp.feature
> {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
[JBoss JIRA] (JBIDE-14434) insert new jquery mobile page - add back button
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14434?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-14434:
----------------------------------------
Yes the problem with 65-bit JVM. But anyway we have fixed this issue in Beta1 so both 32 and 64 JVM should work on Mac.
We tested our fix for all platform we have: Mac (32,64) / Windows 7,8 (32/64) / Ubuntu with different sets of installed browsers. And our preview seems to work there. But you never now... It would be grate if you test the latest nightly build so we will have time to fix problems (if any) in beta1.
> insert new jquery mobile page - add back button
> -----------------------------------------------
>
> Key: JBIDE-14434
> URL: https://issues.jboss.org/browse/JBIDE-14434
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Burr Sutter
> Assignee: Viacheslav Kabanovich
> Fix For: 4.1.0.Beta1
>
> Attachments: jquery_mobile_page.png
>
>
> When using the Page jquery Mobile palette option, it would be great if the "property sheet" could ask if the user wishes to have a back button automatically. This is useful for pages 2+ in a multi-page 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
13 years, 1 month