March 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-3235) Missing properties view for servers elements

by Max Rydahl Andersen (JIRA)

Missing properties view for servers elements -------------------------------------------- Key: JBIDE-3235 URL: https://jira.jboss.org/jira/browse/JBIDE-3235 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Reporter: Max Rydahl Andersen Fix For: 3.0.0.cr1 Before I could directly edit properties for ports in properties view. Now I need to right click and choose Change Value and get a non-standard edit in the tree. This I could probably live with if I could just double click the value and edit it like in properties view. Properties view was though also nice to give other details than just access to edit. i.e.. I could copy values to get the value of file names etc. I can't copy elements from the tree and get a textual representation. -- 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, 3 months

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-4093) Project archive isn't published to the deploy folder after changing temporary deploy directory.

by Anton Klimkovich (JIRA)

Project archive isn't published to the deploy folder after changing temporary deploy directory. ----------------------------------------------------------------------------------------------- Key: JBIDE-4093 URL: https://jira.jboss.org/jira/browse/JBIDE-4093 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0 Reporter: Anton Klimkovich Priority: Minor EXECUTE: Create seam web project EXECUTE: Open Server Overview EXECUTE: Set checkbox to Use workspace metadata EXECUTE: Add project to the server ASSERT: Project is deployed to \ws3\.metadata\.plugins\org.jboss.ide.eclipse.as.core\jboss-soa-p.4.3.0\deploy\ EXECUTE: Open Server Overview EXECUTE: Set checkbox to Use a custom deploy folder or Use the JBoss deploy folder. Save changes. EXECUTE: Press Publish to the server button FAILURE: Only seam-ds.xml is published. Seam.war isn't published to the deploy folder. -- 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, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-3663) Show a warning when the user tries to open the launch configuration but the server editor is dirty

by Adrian Mitev (JIRA)

Show a warning when the user tries to open the launch configuration but the server editor is dirty -------------------------------------------------------------------------------------------------- Key: JBIDE-3663 URL: https://jira.jboss.org/jira/browse/JBIDE-3663 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Affects Versions: 3.0.0.CR2 Environment: JBT N200901190612, java 1.5, windows XP Reporter: Adrian Mitev Something like "Server is not saved yet - the console configuration might be out of date. Do you want to save the serrver before opening the launch configuration ?" when users click the "open launch config". -- 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, 5 months

5
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2240) Speed up creation of runtime/servers, specially when creating clusters

by Galder Zamarreno (JIRA)

Speed up creation of runtime/servers, specially when creating clusters ---------------------------------------------------------------------- Key: JBIDE-2240 URL: http://jira.jboss.com/jira/browse/JBIDE-2240 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Galder Zamarreno We need to look at a way to streamline the creation of runtime/servers as I'm finding it really tedious, specially when it comes to clusters. First, I think It'd be nice to create a runtime and a server in a single step. This would fit very well my model where I take an EAP version, create a server configuration (could Tools do this for me as well? instead of me having to "cp -r server/default server/12345"), create a runtime for it and a server and the server's name to be exactly the same as the one from the runtime (no need to add the " Server" name clutter). Secondly, once I've created a server configuration + runtime + server, an ability to copy paste that one, having only to change the server configuration name (server/12345_1, server/12345_2....configurations) , runtime/server name and bind address (for those that don't do multiple IP addresses, enable binding manager and allow selecting the port collection, ports-01...etc). All this needs further baking and you have to take into account my specific use where I'm creating server configurations on a daily basis. -- 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, 5 months

5
4
0 / 0

[JBoss JIRA] Created: (JBIDE-1246) service beans code completion is broken

by Max Andersen (JIRA)

service beans code completion is broken --------------------------------------- Key: JBIDE-1246 URL: http://jira.jboss.com/jira/browse/JBIDE-1246 Project: JBoss Tools Issue Type: Bug Components: JBossAS Reporter: Max Andersen Assigned To: Rob Stryker Fix For: 2.1 While fixing the identification of service xml I found that the code completion is broken in service.xml It looks like the code is searching for code completions manually and assumes way too much about what the searchengine can/should find. e.g. PackageTypeSearcher.getPackage() assumes only one packagefragment per name will be found, but that is not the case if you have multiple projects with the same jar or simply uses the same package name in diffeerent projects. One way to solve it is to use the built in codecompetlion in JDT - an example of that is to be found in CompletionHelper.java in the hibernate plugins. -- 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, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1253) Editor for JBoss -ds.xml files

by Gavin King (JIRA)

Editor for JBoss -ds.xml files ------------------------------ Key: JBIDE-1253 URL: http://jira.jboss.com/jira/browse/JBIDE-1253 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King Configuring datasources is hard for many users. Let's help them out with a nice editor. -- 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, 5 months

7
6
0 / 0

[JBoss JIRA] Created: (JBIDE-1273) When hot code replace fails, offer "restart deployment "as an alternative

by Gavin King (JIRA)

When hot code replace fails, offer "restart deployment "as an alternative ------------------------------------------------------------------------- Key: JBIDE-1273 URL: http://jira.jboss.com/jira/browse/JBIDE-1273 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King The dialog box t hat eclipse pops up when hot code replace fails is very irritating, but it would be less irritating if it offered "restart deployment" as an alternative. Actually it should be smart enough to NOT pop this dialog at all for classes in src/action. So I think the Seam tools need to hijack this whole feature of eclipse. -- 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, 5 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-3113) Consolidation/clean up of preference pages

by John Graham (JIRA)

Consolidation/clean up of preference pages ------------------------------------------ Key: JBIDE-3113 URL: https://jira.jboss.org/jira/browse/JBIDE-3113 Project: Tools (JBoss Tools) Issue Type: Bug Components: common, drools, jbpm Affects Versions: 3.0.0.cr1 Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk Reporter: John Graham Priority: Minor JBT currently has three preference page categories: 1. Drools 2. JBoss jBPM 3. JBoss Tools The first two should be listed as subsections of the JBoss Tools category. Alternatively, I suggest that the top level category should just be JBoss: - JBoss -- Drools -- jBPM Also, the JBoss Tools and JBoss jBPM top level pages in each of these categories do not expose preferences, but rather the default buttons or simply a label ("JBoss Tools"). These top level pages should show overall JBT preferences. See the Java preferences or other examples in the Eclipse platform for this idea. (Also note that the DTP 1.6.x way of doing this is wrong... ;) ) -- 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, 5 months

6
19
0 / 0

[JBoss JIRA] Created: (JBIDE-1104) .sar file cannot be included in .ear file

by Juergen Zimmermann (JIRA)

.sar file cannot be included in .ear file ----------------------------------------- Key: JBIDE-1104 URL: http://jira.jboss.com/jira/browse/JBIDE-1104 Project: JBoss Tools Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.Beta4 Environment: JBoss Tools nightly build 20071017 Reporter: Juergen Zimmermann I need a .ear file which contains a .sar file (service archive for JBoss). Such a .sar file is declared in META-INF/jboss-app.xml of the EAR project "hska" as follows: <jboss-app> <security-domain>java:/jaas/hska</security-domain> <module> <service>hska.sar</service> </module> </jboss-app> I have a "General Project" named hskaSAR which has a META-INF subdirectory for the xml files of the .sar file. Creating hskaSAR/hska.sar via the "Project Archives" view of JBoss Tools works fine. However, there is no possibility to include the .sar file within the (exploded) .ear. I tried to edit and extend the file .settings/org.eclipse.wst.common.component within the EAR project as follows: <dependent-module deploy-path="/" handle="module:/classpath/lib/hskaSAR/hska.sar"> <dependency-type>uses</dependency-type> </dependent-module> However, this workaround doesn't work. -- 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, 6 months

6
23
0 / 0

[JBoss JIRA] Created: (JBIDE-3883) Manifest cleanup

by Max Rydahl Andersen (JIRA)

Manifest cleanup ----------------- Key: JBIDE-3883 URL: https://jira.jboss.org/jira/browse/JBIDE-3883 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Affects Versions: 3.0.0.GA Reporter: Max Rydahl Andersen Fix For: 3.1.0 After JBIDE-3873 it is about time we find time to set: Bundle-Require-Execution-Environment minimum versions boundaries for dependencies (add more if needed) -- 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, 6 months

5
30
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 March 2009