March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-983) Console not showing up when staritng a EAP/SOA-P Instance

by Jim Tyrrell (JIRA)

Console not showing up when staritng a EAP/SOA-P Instance --------------------------------------------------------- Key: JBDS-983 URL: https://jira.jboss.org/jira/browse/JBDS-983 Project: JBoss Developer Studio Issue Type: Feature Request Affects Versions: 3.0.0.M4 Reporter: Jim Tyrrell For some reason starting a SOA-P instance by right clicking in the server view does not start/open the console for the output of the server as it is starting. For EAP and Seam projects this does not seem to be the case as often, but I think I have seen it. The current JBDS 3.0 M4 release does seem to not show the console unless I open the console via the Window -> Show View -> General -> Console and then I have to click an icon to enable the "Java Stack Trace Console". Once I have setup the console once as just noted even if I close it it will open as I expect. If I close JBDS and make sure that the console was not left open, I get the same behaviour when I try to right click on the SOA-P instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

21 hours, 16 minutes

5
8
0 / 0

[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-2719: ------------------------------------- [~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far. First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet). With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error. In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up. > Multiple Spring AOP problems when travel example is imported > ------------------------------------------------------------ > > Key: JBDS-2719 > URL: https://issues.jboss.org/browse/JBDS-2719 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, upstream > Affects Versions: 7.0.0.GA > Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > > There are Multiple Spring AOP Errors after travel example is imported: > {code} > Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException > {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

4 weeks

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-5287) Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file.

by Svetlana Yasenovich (JIRA)

Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file. ------------------------------------------------------------------------- Key: JBIDE-5287 URL: https://jira.jboss.org/jira/browse/JBIDE-5287 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Environment: JBoss Developer Studio Version: 3.0.0.M4 Build id: v200911180352M Reporter: Svetlana Yasenovich Priority: Minor 1. Open .xhtml file. 2. click 'Ctrl+A' -> all code selected 3. click 'Ctrl+Shift+/' (Source->Add Block Comment) ->all code commented 4. click 'Ctrl+A' 5. click 'Ctrl+Shift+\' (Source->Remove Block Comment) -> nothing happened Expected Result : Remove Block Comment for all code -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

7 months, 3 weeks

3
7
0 / 0

[JBoss JIRA] (JBIDE-15072) Seam 2.3.1+ examples maven projects "Duplicate component name" errors

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15072?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15072: ----------------------------------- Fix Version/s: LATER (was: 4.2.x) > Seam 2.3.1+ examples maven projects "Duplicate component name" errors > --------------------------------------------------------------------- > > Key: JBIDE-15072 > URL: https://issues.jboss.org/browse/JBIDE-15072 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, seam2 > Affects Versions: 4.1.0.Beta2 > Environment: WFK 2.3.0.CR1 > Reporter: Marek Schmidt > Assignee: Alexey Kazakov > Fix For: LATER > > > The new Seam 2.3 examples structure (since WFK 2.3.0.CR1) contains two components.xml files (one real, one for testing is src/test), which confuses JBDS and produces lots of > Duplicate component name: "..." components.xml /booking-web/src/main/webapp/WEB-INF line 24 Seam Problem > issues. > JBDS should understand src/test directory in a Maven project as something test resources go to and not be confused that a test components.xml file is also named components.xml and that it doesn't really conflict with components.xml file that goes into a deployment. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15072) Seam 2.3.1+ examples maven projects "Duplicate component name" errors

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15072?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15072: ----------------------------------- Component/s: upstream > Seam 2.3.1+ examples maven projects "Duplicate component name" errors > --------------------------------------------------------------------- > > Key: JBIDE-15072 > URL: https://issues.jboss.org/browse/JBIDE-15072 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, seam2, upstream > Affects Versions: 4.1.0.Beta2 > Environment: WFK 2.3.0.CR1 > Reporter: Marek Schmidt > Assignee: Alexey Kazakov > Fix For: LATER > > > The new Seam 2.3 examples structure (since WFK 2.3.0.CR1) contains two components.xml files (one real, one for testing is src/test), which confuses JBDS and produces lots of > Duplicate component name: "..." components.xml /booking-web/src/main/webapp/WEB-INF line 24 Seam Problem > issues. > JBDS should understand src/test directory in a Maven project as something test resources go to and not be confused that a test components.xml file is also named components.xml and that it doesn't really conflict with components.xml file that goes into a deployment. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13727) Enable generation of tests for Seam components

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13727?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13727: ----------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > Enable generation of tests for Seam components > ---------------------------------------------- > > Key: JBIDE-13727 > URL: https://issues.jboss.org/browse/JBIDE-13727 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: seam2 > Affects Versions: 4.0.0.Final, 4.1.0.Beta1 > Environment: JBDS 6.0.0.GA, JBDS 7.0.0.Beta1. JBDS 7.1.0.GA > Reporter: Tomas Remes > Assignee: Alexey Kazakov > Fix For: 4.3.x > > > Currently the test generation for Seam Action, Form is disabled (but not properly - see JBIDE-13596) because of previous Seam version (I guess 2.3.0.Final). In latest Seam version test can be already generated by seam-gen and are even valid and usable. > JBDS should enable and support this functionality again. -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15359) jQuery Mobile palette dialogs are not rendered properly while using XULRunner 1.9.2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15359?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-15359. ---------------------------------- > jQuery Mobile palette dialogs are not rendered properly while using XULRunner 1.9.2 > ----------------------------------------------------------------------------------- > > Key: JBIDE-15359 > URL: https://issues.jboss.org/browse/JBIDE-15359 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Yahor Radtsevich > Assignee: Alexey Kazakov > Fix For: 4.2.0.Beta2 > > > jQuery Mobile 1.3 is incompatible with XULRunner 1.9.2 (Firefox 3.6). > The reason is that jQuery Mobile scripts try to call [{{getComputedStyle(element, pseudoElt)}}|https://developer.mozilla.org/en-US/docs/Web/API/window.getC...] method omitting the second argument, while XULRunner 1.9.2 requires both arguments to be present. > Related Mozilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=567350 > Note: now the jQuery Mobile dialogs use WebKit insted of XULRunner 1.9.2, but potentially this may lead to Eclipse crashes (see JBIDE-9144). -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15359) jQuery Mobile palette dialogs are not rendered properly while using XULRunner 1.9.2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15359?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-15359. ------------------------------------ Fix Version/s: 4.2.0.Beta2 (was: 4.2.x) Resolution: Won't Fix > jQuery Mobile palette dialogs are not rendered properly while using XULRunner 1.9.2 > ----------------------------------------------------------------------------------- > > Key: JBIDE-15359 > URL: https://issues.jboss.org/browse/JBIDE-15359 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Reporter: Yahor Radtsevich > Assignee: Alexey Kazakov > Fix For: 4.2.0.Beta2 > > > jQuery Mobile 1.3 is incompatible with XULRunner 1.9.2 (Firefox 3.6). > The reason is that jQuery Mobile scripts try to call [{{getComputedStyle(element, pseudoElt)}}|https://developer.mozilla.org/en-US/docs/Web/API/window.getC...] method omitting the second argument, while XULRunner 1.9.2 requires both arguments to be present. > Related Mozilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=567350 > Note: now the jQuery Mobile dialogs use WebKit insted of XULRunner 1.9.2, but potentially this may lead to Eclipse crashes (see JBIDE-9144). -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15667) JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15667?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15667: ----------------------------------- Fix Version/s: LATER (was: 4.2.x) > JBDS doesn't display EL Knowledge Base problems in a Seam example after re-import > --------------------------------------------------------------------------------- > > Key: JBIDE-15667 > URL: https://issues.jboss.org/browse/JBIDE-15667 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: seam2, upstream > Affects Versions: 4.2.0.Alpha1 > Environment: JBDS 7.1.0.Alpha2 > Reporter: Ron Šmeral > Assignee: Alexey Kazakov > Fix For: LATER > > -- 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16910) Three items in our tp cannot be installed into clean luna m6

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16910?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16910: ------------------------------------- > What I don't understand is why doesn't the target-platform-validation see this missing dependency? In general, it should and used to fail when something is transitively missing... (in this case com.thoughtworks.xstream). I would suggest this is the issue you try to solve ;) If you could solve that and make transitive deps error appropriately, then issues like the one I posted will disappear ;) I don't need this in the re-spin at all, but, I don't know what may be broken by NOT including it. My use-case is a dev-only one, but I file it not usually for my benefit but rather to help you guys spot potentially more critical issues. So, its up to you all whether the changes you made need to make respin-b or not. But *I* don't really need them. > Three items in our tp cannot be installed into clean luna m6 > ------------------------------------------------------------ > > Key: JBIDE-16910 > URL: https://issues.jboss.org/browse/JBIDE-16910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Assignee: Nick Boldt > Fix For: 4.2.0.Beta2 > > Attachments: bugForNick.png > > > cd jbosstools-target-platforms > git checkout 4.40.x > mvn clean verify -Dmirror-target-to-repo.includeSources=true > cd ~/apps/eclipse > mkdir lunam6 > cd lunam6 > // acquire tar gz file > tar xvzf (filename for luna m6) > cd eclipse > ./eclipse > Help -> Install new software > Select "local", point to jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ > Wait for it to calculate what can or cannot be installed. See 3 items that cannot be installed (See screenshot) > Error: > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: Atlassian Connector for Eclipse Usage Monitoring 3.2.2.v20130909 (com.atlassian.connector.eclipse.monitor.feature.group 3.2.2.v20130909) > Missing requirement: Atlassian Connector for Eclipse Usage Data Collector 3.2.2.v20130909 (com.atlassian.connector.eclipse.monitor.core 3.2.2.v20130909) requires 'bundle com.thoughtworks.xstream 0.0.0' but it could not be found > Cannot satisfy dependency: > From: Atlassian Connector for Eclipse Usage Monitoring 3.2.2.v20130909 (com.atlassian.connector.eclipse.monitor.feature.group 3.2.2.v20130909) > To: com.atlassian.connector.eclipse.monitor.core [3.2.2.v20130909] > {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

11 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2014