May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14447) Server project's root pom needs to use latest parent pom version Beta1 when building its Beta1 bits

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-14447: ---------------------------------- Summary: Server project's root pom needs to use latest parent pom version Beta1 when building its Beta1 bits Key: JBIDE-14447 URL: https://issues.jboss.org/browse/JBIDE-14447 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.0.Beta1 Reporter: Nick Boldt Assignee: Rob Stryker Fix For: 4.1.0.Beta1 Rob, for the 3rd time, you need to fix your root pom to point at Beta1, not Alpha2. -- 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-14442) openshift-java-client: provide nice descriptions for standalone and embeddable cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14442?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14442: ------------------------------------- Git Pull Request: https://github.com/openshift/openshift-java-client/pull/51, https://github.com/jbosstools/jbosstools-openshift/pull/117 (was: https://github.com/openshift/openshift-java-client/pull/51) > openshift-java-client: provide nice descriptions for standalone and embeddable cartridges > ----------------------------------------------------------------------------------------- > > Key: JBIDE-14442 > URL: https://issues.jboss.org/browse/JBIDE-14442 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta1 > > > since we upgraded the client to protocol 1.2 (JBIDE-12320) we can now offer display name and descriptions in the client: > IStandaloneCartridge#getDisplayName > IStandaloneCartridge#getDescription > IEmbeddedCartridge#getDisplayName > IEmbeddedCartridge#getDescription -- 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] (JBDS-2534) JBDS70_0311: [Deleted] (Dev) (P2) Marketplace - simplify delivery

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2534?page=com.atlassian.jira.plugin.... ] Jiri Pallich closed JBDS-2534. ------------------------------ Resolution: Won't Fix The JDBS70_0311 requirement has been DeCommitted > JBDS70_0311: [Deleted] (Dev) (P2) Marketplace - simplify delivery > ----------------------------------------------------------------- > > Key: JBDS-2534 > URL: https://issues.jboss.org/browse/JBDS-2534 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Nick Boldt > Priority: Critical > Fix For: 7.0.0.Beta1 > > > JBDS only on Marketplace (no more JBoss Tools entry). -- 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] (JBDS-2533) JBDS70_0310: [Deleted] (Dev) (P2) JBT Incubator Site to contain all the stuff currently in JBT that does NOT make it to JBDS

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2533?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2533: ------------------------------- Summary: JBDS70_0310: [Deleted] (Dev) (P2) JBT Incubator Site to contain all the stuff currently in JBT that does NOT make it to JBDS (was: JBDS70_0310: [Commit] (Dev) (P2) JBT Incubator Site to contain all the stuff currently in JBT that does NOT make it to JBDS) > JBDS70_0310: [Deleted] (Dev) (P2) JBT Incubator Site to contain all the stuff currently in JBT that does NOT make it to JBDS > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2533 > URL: https://issues.jboss.org/browse/JBDS-2533 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Nick Boldt > Fix For: 7.0.0.Beta2 > > > Possible JBDS incubator site needed too > Special handling for the "incubating" items (plugins that are not fully supported like BIRT) vs those plugins which are found in JBDS -- 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] (JBDS-2533) JBDS70_0310: [Deleted] (Dev) (P2) JBT Incubator Site to contain all the stuff currently in JBT that does NOT make it to JBDS

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2533?page=com.atlassian.jira.plugin.... ] Jiri Pallich closed JBDS-2533. ------------------------------ Resolution: Won't Fix The JDBS70_0310 requirement has been DeCommitted > JBDS70_0310: [Deleted] (Dev) (P2) JBT Incubator Site to contain all the stuff currently in JBT that does NOT make it to JBDS > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2533 > URL: https://issues.jboss.org/browse/JBDS-2533 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Nick Boldt > Fix For: 7.0.0.Beta2 > > > Possible JBDS incubator site needed too > Special handling for the "incubating" items (plugins that are not fully supported like BIRT) vs those plugins which are found in JBDS -- 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] (JBDS-2534) JBDS70_0311: [Deleted] (Dev) (P2) Marketplace - simplify delivery

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2534?page=com.atlassian.jira.plugin.... ] Jiri Pallich updated JBDS-2534: ------------------------------- Summary: JBDS70_0311: [Deleted] (Dev) (P2) Marketplace - simplify delivery (was: JBDS70_0311: [Commit] (Dev) (P2) Marketplace - simplify delivery) > JBDS70_0311: [Deleted] (Dev) (P2) Marketplace - simplify delivery > ----------------------------------------------------------------- > > Key: JBDS-2534 > URL: https://issues.jboss.org/browse/JBDS-2534 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Nick Boldt > Priority: Critical > Fix For: 7.0.0.Beta1 > > > JBDS only on Marketplace (no more JBoss Tools entry). -- 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-14434) insert new jquery mobile page - add back button

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14434?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-14434: ------------------------------------- On a 64-bit JVM? My Mac has JVM challenges in general - but I can also test on Windows 32-bit and 64-bit JVMs. > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-14444) Drag & Drop of image into HTML editor - h:image

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14444?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-14444: -------------------------------------- Assignee: Alexey Kazakov > Drag & Drop of image into HTML editor - h:image > ----------------------------------------------- > > Key: JBIDE-14444 > URL: https://issues.jboss.org/browse/JBIDE-14444 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Burr Sutter > Assignee: Alexey Kazakov > Fix For: 4.1.0.Beta1 > > Attachments: 2013-05-14_0739.png > > > While editing a HTML5 file, I should not be prompted with an "h:image" option when dragging & dropping an image. Also, the URL to the image should be relative to the webapp directory - not using "src/main/webapp/img/myimage.png". > http://www.screencast.com/t/i1lHwudk -- 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-14436) jquery mobile button id property

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14436?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-14436: ------------------------------------- Yes, I think any widget should have an ID property. But I have not explored all the widgets yet :-) > jquery mobile button id property > -------------------------------- > > Key: JBIDE-14436 > URL: https://issues.jboss.org/browse/JBIDE-14436 > 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_button.png > > > A button should have an id property - for references in JS > $("#mybutton").click(function() { > // $.ajax(... > }); -- 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-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... sorry for the late reply. Had a busy day yesterday. Question about unknown classifiers. If it's a JAR, why would you not add all the classes? Why just a subset? In fact - why do anything differently from the Eclipse classpath, or Maven? It does not make sense to me to require a separate plugin just to configure this. If anything, I would think that you would use a separate plugin to instead deviate from this - what I would call - expected behavior. Maybe I don't understand the other scenarios, but why would you want anything else? ~Lincoln > 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

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