January 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1074) JBDS 2.1.1 Release Notes point to the wrong update website

by Stelios Koussouris (JIRA)

JBDS 2.1.1 Release Notes point to the wrong update website ---------------------------------------------------------- Key: JBDS-1074 URL: https://jira.jboss.org/jira/browse/JBDS-1074 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: documentation Affects Versions: 2.1.0 Reporter: Stelios Koussouris The JBDS 2.1.1 say You can find instructions on how to update JBDS 2.0 to 2.1.1 here - http://jboss.com/products/devstudio/update/ instead of http://www.jboss.com/products/devstudio/update/ -- 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

16 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-1013) Possibility to change Server Main Class added

by Svetlana mukhina (JIRA)

Possibility to change Server Main Class added --------------------------------------------- Key: JBDS-1013 URL: https://jira.jboss.org/jira/browse/JBDS-1013 Project: JBoss Developer Studio Issue Type: Task Components: Doc - JBossAS Affects Versions: 2.1.0 Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.1.0-doc Update "Edit Configuration" wizard screens, mention about the possibility -- 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

16 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDS-1072) Initialize server deployment path property for jBPM

by Koen Aers (JIRA)

Initialize server deployment path property for jBPM --------------------------------------------------- Key: JBDS-1072 URL: https://jira.jboss.org/jira/browse/JBDS-1072 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Reporter: Koen Aers Fix For: 3.0.0.CR2 On the deployment page of the process editor, there is a property indicating the uri to be used to deploy the process. There is a preference for this property that initially contains the path for the jBPM standalone runtime (i.e. jbpm-console/upload). This value should be changed because in SOA-P another path is used (i.e. gpd-deployer/upload, see JBPM-2678). -- 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

16 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4279) Seam feature includes DTP and we don't have a "overall" node for JBoss tools

by Max Rydahl Andersen (JIRA)

Seam feature includes DTP and we don't have a "overall" node for JBoss tools ---------------------------------------------------------------------------- Key: JBIDE-4279 URL: https://jira.jboss.org/jira/browse/JBIDE-4279 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.1.0.M1 Reporter: Max Rydahl Andersen See http://screencast.com/t/DMkIT4hi Seam is viewed as "parent" for DTP (which is wrong) And we should look at if we could create a JBoss Tools overall feature ...and still allow individual install/updates though. -- 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

16 years, 2 months

2
6
0 / 0

[JBoss JIRA] Created: (JBDS-830) Spaces in project path causes JTA exception

by Ondrej Skutka (JIRA)

Spaces in project path causes JTA exception ------------------------------------------- Key: JBDS-830 URL: https://jira.jboss.org/jira/browse/JBDS-830 Project: JBoss Developer Studio Issue Type: Bug Components: seam Affects Versions: 2.1.0 Reporter: Ondrej Skutka Priority: Critical Fix For: 2.1.0 Steps to reproduce: 1) Create a new Seam project with database 2) Go to Hibernate Configurations view 3) Unfold the configuration following exception is thrown: org.hibernate.console.HibernateConsoleRuntimeException: Could not create JPA based Configuration Could not create JPA based Configuration <No message> java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException: <no message> java.lang.reflect.InvocationTargetException javax.persistence.PersistenceException: java.lang.IllegalArgumentException: Unable to visit JAR file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes. Cause: Illegal character in path at index 18: file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes java.lang.IllegalArgumentException: Unable to visit JAR file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes. Cause: Illegal character in path at index 18: file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes java.lang.IllegalArgumentException: Unable to visit JAR file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes. Cause: Illegal character in path at index 18: file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes Unable to visit JAR file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes. Cause: Illegal character in path at index 18: file:/C:/Documents and Settings/jbossqa/workspace.jbds/ear220CR2v2-ejb/build/classes Furturemore you cannot generate seam entities, because of "Couldn't connect to Database". -- 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

16 years, 2 months

5
19
0 / 0

[JBoss JIRA] Created: (JBIDE-5701) Add warning panel to VPE about possible missing natures

by Maxim Areshkau (JIRA)

Add warning panel to VPE about possible missing natures -------------------------------------------------------- Key: JBIDE-5701 URL: https://jira.jboss.org/jira/browse/JBIDE-5701 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.1.0.CR1 Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.2.next Vpe can work not correctly if in project doesn't exist jsfnature or jsf capabilities, so we need way to infrom user about it. -- 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

16 years, 2 months

3
17
0 / 0

[JBoss JIRA] Created: (JBDS-832) Some titles are not correct in Welcome screen.

by Alexey Kazakov (JIRA)

Some titles are not correct in Welcome screen. ---------------------------------------------- Key: JBDS-832 URL: https://jira.jboss.org/jira/browse/JBDS-832 Project: JBoss Developer Studio Issue Type: Bug Affects Versions: 3.0.0.M2 Reporter: Alexey Kazakov Assignee: Victor Rubezhny Fix For: 3.0.0.M2 See sreenshot. -- 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

16 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (JBDS-682) Make Seam Runtimes 1.2.AP and 2.0.FP as default in spite of user's additional platform selection.

by Anton Klimkovich (JIRA)

Make Seam Runtimes 1.2.AP and 2.0.FP as default in spite of user's additional platform selection. -------------------------------------------------------------------------------------------------- Key: JBDS-682 URL: https://jira.jboss.org/jira/browse/JBDS-682 Project: Developer Studio Issue Type: Feature Request Components: installer Affects Versions: 2.1.0 Reporter: Anton Klimkovich EXECUTE: On step 5 of installation select Yes chechbox to install JBoss Enterprise Application Platform EXECUTE: On step 5 add SOA-P EXECUTE: Window - JBoss tools -> Web -> Seam ASSERT: Seam Runtime 1.2.AP and 2.0.FP should be default runtimes Seam Runtimes are checked as default now depending on user's additional platform selection. Since Soa-P doesn't contain seamGen for seam 1.2 I think Seam Runtimes 1.2.AP and 2.0.FP as default will be better. -- 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

16 years, 2 months

3
8
0 / 0

[JBoss JIRA] Created: (JBDS-1075) Should JBDS work around SWT/GTK button-click bug or move up to latest Eclipse 3.5.2 milestone?

by Nick Boldt (JIRA)

Should JBDS work around SWT/GTK button-click bug or move up to latest Eclipse 3.5.2 milestone? ---------------------------------------------------------------------------------------------- Key: JBDS-1075 URL: https://jira.jboss.org/jira/browse/JBDS-1075 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Reporter: Nick Boldt Assignee: Max Rydahl Andersen With the latest GTK+ 2.17.x/2.18.x in Linux (32- or 64-bit), Eclipse buttons in dialogs and other places are not working for me if clicked with the mouse. Also cannot see anything in the tree when trying to install updates. Solution, as documented here [1], is to > export GDK_NATIVE_WINDOWS=true before running JBDS; we could do what Fedora did for Eclipse 3.5.1 in Fedora 12: instead of simply running ./eclipse, we run a bash script which does the above export before running ./eclipse. [1]http://wiki.eclipse.org/IRC_FAQ#Eclipse_buttons_in_dialogs_and_other_pl... Should we do this to avoid a flurry of support problems? Or start building JBDS with the latest Eclipse 3.5.2 milestone? -- 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

16 years, 2 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5713) Incoherent module assembly structure

by Fred Bricon (JIRA)

Incoherent module assembly structure ------------------------------------ Key: JBIDE-5713 URL: https://jira.jboss.org/jira/browse/JBIDE-5713 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.CR1 Environment: Vista, JBT 3.1.CR1 Reporter: Fred Bricon Priority: Minor I was a bit puzzled -and kinda worried- after opening the module assembly page of an EJB project. As you can see on the following screenshot (incoherent_module_assembly_structure.jpg), the page indicates EJB dependencies of my testEJB2 project should be exported in the resulting jar. Fortunately, they aren't (hence the minor priority), but it's pretty disturbing. My understanding of the module assembly page is that : - it's just a GUI over ./settings/org.eclipse.wst.common.component - it should reflect the content of the produced assembly. i.e everything in this page should be present in the resulting .jar/.ear/.sar, whatever. well, it's also probable I misunderstood a lot :-) regards, Fred Bricon -- 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

16 years, 2 months

4
11
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 January 2010