May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-82) Modify the staging repository for target platform distribution management.

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-82: ------------------------------- Summary: Modify the staging repository for target platform distribution management. Key: JBTIS-82 URL: https://issues.jboss.org/browse/JBTIS-82 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Components: target-platform Affects Versions: 4.0.0, 4.1.0 Reporter: Paul Leacu Assignee: Paul Leacu -- 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, 11 months

1
0
0 / 0

[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: -------------------------------------------- Adding "aesh-test-harness" and "aesh-spi" to the JUnit test classpath manually will workaround this issue. > 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 > Affects Versions: 4.1.0.Alpha2 > Reporter: Lincoln Baxter III > > 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14397) Add JRE vs JDK detector at AS launch

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-14397: ------------------------------------- Summary: Add JRE vs JDK detector at AS launch Key: JBIDE-14397 URL: https://issues.jboss.org/browse/JBIDE-14397 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Affects Versions: 4.1.0.Alpha2 Reporter: Denis Golovin JDK is required, getting this installed and configured inside of JBDS/Eclipse is a challenge for the newbie -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14337) Portal Quickstarts are not displayed after changing target runtime to portal

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14337?page=com.atlassian.jira.plugi... ] Peter Palaga commented on JBIDE-14337: -------------------------------------- Thanks for the hint, Snježa. Indeed, the descriptor is under my control. I have changed the {{allowed-types}} to {{org.jboss.ide.eclipse.as.runtime.71, org.jboss.ide.eclipse.as.runtime.eap.61}} because those two will be the supported servers with GateIn 3.6. I have uploaded the changed file, but I still cannot see the change over HTTP: http://download.jboss.org/gatein/quickstarts/gatein-3.6/project-examples-.... Hopefully, that is some kind of caching issue that will self-heal soon. > Portal Quickstarts are not displayed after changing target runtime to portal > ---------------------------------------------------------------------------- > > Key: JBIDE-14337 > URL: https://issues.jboss.org/browse/JBIDE-14337 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Portal/GateIn > Affects Versions: 4.1.0.Beta1 > Environment: gatein-master (3.6.0.Beta02-SNAPSHOT) - eap 6.1 bundle > Eclipse 4.3 M6 Kepler + JBT 4.1.0.Beta1 > Reporter: Filip Kiss > Assignee: Peter Palaga > Labels: JPP61-Test-dev > Fix For: 4.1.0.Beta1 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14396) Imported maven projects sometimes fail to resolve required classpath dependencies for tests

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created JBIDE-14396: ------------------------------------------ Summary: 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 Affects Versions: 4.1.0.Alpha2 Reporter: Lincoln Baxter III 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

12 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14390) JSF 'New Project' preferences and wizard should have matching labels for the same fields

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14390?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14390: ----------------------------------- Fix Version/s: 4.1.0.Beta2 > JSF 'New Project' preferences and wizard should have matching labels for the same fields > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14390 > URL: https://issues.jboss.org/browse/JBIDE-14390 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Fix For: 4.1.0.Beta2 > > Attachments: JSF_NewProjectPreferences.png, JSF_NewProjectWizard1.png, JSF_NewProjectWizard2.png > > > 1. Window>Preferences>JBoss Tools>Web>JSF>Project, New Project tab has the following labels (screen capture attached): > * Version > * Project Template > * Use Default Path > * Projects Root > * Servlet Version > 2. File>New>Project>JBoss Tools Web>JSF>JSF Project wizard, page 1 and 2 have the following labels (screen captures attached): > * Use default path > * Location > * JSF Environment > * Template > * ServletVersion > List 1 and 2 refer to the same things but use different labels. The labels should be identical. I would suggest changing: > In preferences: > Version -> JSF Version > Use Default Path -> Use default path > Projects Root -> Location > In the wizard: > JSF Environment -> JSF Version > Template -> Project Template > ServletVersion -> Servlet Version -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14390) JSF 'New Project' preferences and wizard should have matching labels for the same fields

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14390?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-14390: -------------------------------------- Assignee: Viacheslav Kabanovich > JSF 'New Project' preferences and wizard should have matching labels for the same fields > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14390 > URL: https://issues.jboss.org/browse/JBIDE-14390 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Viacheslav Kabanovich > Fix For: 4.1.0.Beta2 > > Attachments: JSF_NewProjectPreferences.png, JSF_NewProjectWizard1.png, JSF_NewProjectWizard2.png > > > 1. Window>Preferences>JBoss Tools>Web>JSF>Project, New Project tab has the following labels (screen capture attached): > * Version > * Project Template > * Use Default Path > * Projects Root > * Servlet Version > 2. File>New>Project>JBoss Tools Web>JSF>JSF Project wizard, page 1 and 2 have the following labels (screen captures attached): > * Use default path > * Location > * JSF Environment > * Template > * ServletVersion > List 1 and 2 refer to the same things but use different labels. The labels should be identical. I would suggest changing: > In preferences: > Version -> JSF Version > Use Default Path -> Use default path > Projects Root -> Location > In the wizard: > JSF Environment -> JSF Version > Template -> Project Template > ServletVersion -> Servlet Version -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14393) openshift-java-client: should have integration test that asserts that app type is not reported in embedded cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14393?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14393: ------------------------------------------ the new integration test is as follows: {code:title=EmbeddedCartridgeResourceIntegrationTest} @Test public void shouldNotContainTypeInEmbeddedCartridges() throws SocketTimeoutException, OpenShiftException { // pre-conditions final IStandaloneCartridge jbossAs = LatestVersionOf.jbossAs().get(user); assertThat(jbossAs).isNotNull(); IApplication application = ApplicationTestUtils.ensureHasExactly1Application(jbossAs, domain); // operation List<IEmbeddedCartridge> embeddedCartridges = application.getEmbeddedCartridges(); // verification assertThat(embeddedCartridges).doesNotSatisfy(new Condition<List<?>>() { @Override public boolean matches(List<?> values) { for(Object value : values) { if (!(value instanceof ICartridge)) { continue; } if (jbossAs.getName().equals(((ICartridge)value).getName())) { return true; }; } return false; } }); } {code} > openshift-java-client: should have integration test that asserts that app type is not reported in embedded cartridges > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14393 > URL: https://issues.jboss.org/browse/JBIDE-14393 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > > In JBIDE-12321 we faced an issue where OpenShift would report the application type as embedded cartridge (which it does in protocol 1.2+). We should have an integration test that assert that this is not the case -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14393) openshift-java-client: should have integration test that asserts that app type is not reported in embedded cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14393?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-14393 at 5/7/13 12:25 PM: ------------------------------------------------------------------- the new integration test is as follows (https://github.com/openshift/openshift-java-client/blob/master/src/test/j...): {code:title=EmbeddedCartridgeResourceIntegrationTest} @Test public void shouldNotContainTypeInEmbeddedCartridges() throws SocketTimeoutException, OpenShiftException { // pre-conditions final IStandaloneCartridge jbossAs = LatestVersionOf.jbossAs().get(user); assertThat(jbossAs).isNotNull(); IApplication application = ApplicationTestUtils.ensureHasExactly1Application(jbossAs, domain); // operation List<IEmbeddedCartridge> embeddedCartridges = application.getEmbeddedCartridges(); // verification assertThat(embeddedCartridges).doesNotSatisfy(new Condition<List<?>>() { @Override public boolean matches(List<?> values) { for(Object value : values) { if (!(value instanceof ICartridge)) { continue; } if (jbossAs.getName().equals(((ICartridge)value).getName())) { return true; }; } return false; } }); } {code} was (Author: adietish): the new integration test is as follows: {code:title=EmbeddedCartridgeResourceIntegrationTest} @Test public void shouldNotContainTypeInEmbeddedCartridges() throws SocketTimeoutException, OpenShiftException { // pre-conditions final IStandaloneCartridge jbossAs = LatestVersionOf.jbossAs().get(user); assertThat(jbossAs).isNotNull(); IApplication application = ApplicationTestUtils.ensureHasExactly1Application(jbossAs, domain); // operation List<IEmbeddedCartridge> embeddedCartridges = application.getEmbeddedCartridges(); // verification assertThat(embeddedCartridges).doesNotSatisfy(new Condition<List<?>>() { @Override public boolean matches(List<?> values) { for(Object value : values) { if (!(value instanceof ICartridge)) { continue; } if (jbossAs.getName().equals(((ICartridge)value).getName())) { return true; }; } return false; } }); } {code} > openshift-java-client: should have integration test that asserts that app type is not reported in embedded cartridges > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14393 > URL: https://issues.jboss.org/browse/JBIDE-14393 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > > In JBIDE-12321 we faced an issue where OpenShift would report the application type as embedded cartridge (which it does in protocol 1.2+). We should have an integration test that assert that this is not the case -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14393) openshift-java-client: should have integration test that asserts that app type is not reported in embedded cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14393?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14393: ------------------------------------------ openshift-bot ran the integration tests and since they're successful it merged the topic-branch into master. Resolving as DONE > openshift-java-client: should have integration test that asserts that app type is not reported in embedded cartridges > --------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14393 > URL: https://issues.jboss.org/browse/JBIDE-14393 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > > In JBIDE-12321 we faced an issue where OpenShift would report the application type as embedded cartridge (which it does in protocol 1.2+). We should have an integration test that assert that this is not the case -- 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, 11 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 May 2013