October 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-374) hotkey methods for project archiver description

by Svetlana mukhina (JIRA)

hotkey methods for project archiver description ----------------------------------------------- Key: JBDS-374 URL: http://jira.jboss.com/jira/browse/JBDS-374 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assigned To: OLga Chikvina Fix For: 2.0.0.alpha describe new hotkey methods for project archiver -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBDS-386) ESB Editor is Extended

by Svetlana mukhina (JIRA)

ESB Editor is Extended ---------------------- Key: JBDS-386 URL: https://jira.jboss.org/jira/browse/JBDS-386 Project: Developer Studio Issue Type: Task Components: Doc - ESB Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.0.0.alpha Update the guide according to https://jira.jboss.org/jira/browse/JBIDE-2022 -- 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

14 years, 7 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4930) JBoss AS driver, Full Publish on EAR module doesn't publish lib/foo.jar

by Darryl Miles (JIRA)

JBoss AS driver, Full Publish on EAR module doesn't publish lib/foo.jar ----------------------------------------------------------------------- Key: JBIDE-4930 URL: https://jira.jboss.org/jira/browse/JBIDE-4930 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M2 Reporter: Darryl Miles I have an EAR with a WAR inside. I moved an incorrectly placed JAR library from the $WAR/WEB-INF/lib/ to $EAR/lib/ dir. I did this outside of eclipse (with file manager). I then issued a "Refresh" (F5) on the toplevel for the EAR project node (in Project Explorer) and then WAR project node. Eclipse correctly fixed the file structure changes in the view of the Project explorer. I then did a "Full Publish" on the EAR module I have added under the "JBoss 5.1.0.GA Server Runtime" in the "Servers View". This should have corrected the difference between the deploy directory file structure and what the Project Explorer has of the file structure. The JAR file I move was removed from the WAR but it was never published to the EAR. I just tested this and the easiest way to reproduce: * Setup workspace with EAR project and WAR project. WAR is inside EAR. * Setup empty JBoss AS runtime. * Add the EAR module to the JBoss AS runtime. * Click Publish on JBoss AS runtime (no need to start it). * Now outside of Eclipse place a JAR in $EAR/lib/ (/project-ear/EarContent/lib/) from your system file manager / Windows Explorer etc... * Now "Full Publish" on JBoss AS runtime (alright nothing should happen as even the Project Explorer can't see it yet, but go and manually check that is in the deploy/* dir right now. * Now "Refresh" on the toplevel of the EAR "project-ear". Eclipse project explorer should now display the JAR. * Now "Incremental Publish" or "Full Publish" (either will do as nether do the correct thing at this point). Manually check whats in the deploy/* dir and see that you JAR is not there. Workaround: * Now delete the module from the JBoss AS runtime. * Now re-add it and publish. (Confirm that the JAR is not in the deploy/* for the EAR). What is it that adding the module does that a "Full Publish" doesn't. As a user I'd expect a "Full Publish" to re-validate every item on both sides (Eclipse view and deploy/* view of file structure and fix the differences). -- 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

14 years, 7 months

3
4
0 / 0

[JBoss JIRA] Resolved: (JBIDE-4852) OpenOn doesn't work inside <jsp:root> container

by Sergey Dzmitrovich (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-4852?page=com.atlassian.jira.plu... ] Sergey Dzmitrovich resolved JBIDE-4852. --------------------------------------- Resolution: Done Assignee: Yura Zhishko (was: Sergey Dzmitrovich) > OpenOn doesn't work inside <jsp:root> container > ----------------------------------------------- > > Key: JBIDE-4852 > URL: https://jira.jboss.org/jira/browse/JBIDE-4852 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor core > Affects Versions: 3.1.0.M2 > Reporter: Denis Maliarevich > Assignee: Yura Zhishko > Fix For: 3.1.0.M4 > > Attachments: correctTest.jsp, test.jsp > > > OpenOn doesn't work inside <jsp:root> container when user tries to open referenced url/file/page from <jsp:include> and <jsp:directive.include>. > Steps to reproduce: > 1. Open JBDS. > 2. Create a new JSF project. > 3. Create "include.jsp" file under WebContent folder (this file could be empty). > 4. Add "test.jsp" and "correctTest.jsp" files to WebContent folder. > 5. Try OpenOn mechanism on both files: correctTest.jsp - should work fine, test.jsp - should fail. -- 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

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDS-731) Wikipedia articles on Tools and JBDS

by Svetlana mukhina (JIRA)

Wikipedia articles on Tools and JBDS ------------------------------------ Key: JBDS-731 URL: https://jira.jboss.org/jira/browse/JBDS-731 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Michael Sorokin Fix For: 2.0.1 It's necessary to update the following articles: http://en.wikipedia.org/wiki/JBoss_Tools http://en.wikipedia.org/wiki/JBDS -- 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

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4958) Mapping Diagram should show only relevant items for diagram primary start items, but now it shows the whole Console Configuration diagram in any case

by Vitali Yemialyanchyk (JIRA)

Mapping Diagram should show only relevant items for diagram primary start items, but now it shows the whole Console Configuration diagram in any case ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4958 URL: https://jira.jboss.org/jira/browse/JBIDE-4958 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.0.M3, 3.1.0.M4 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Critical Fix For: 3.1.0.M4 -- 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

14 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-4136) Use recommended packaging for Seam EAR projects

by Pete Muir (JIRA)

Use recommended packaging for Seam EAR projects ----------------------------------------------- Key: JBIDE-4136 URL: https://jira.jboss.org/jira/browse/JBIDE-4136 Project: Tools (JBoss Tools) Issue Type: Task Components: Seam Reporter: Pete Muir Assignee: Max Rydahl Andersen Priority: Critical Fix For: 3.0.1.GA JBT uses MANIFEST.MF for setting up artifact classpath, whilst Seam recommends the use of the EAR lib/ directory. By not following this recommendation, JBT users are running in to a number of classloading problems. -- 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

14 years, 7 months

4
28
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2009