September 2009 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-4859) JBT Update site has uncategorized features

by Nick Boldt (JIRA)

JBT Update site has uncategorized features ------------------------------------------ Key: JBIDE-4859 URL: https://jira.jboss.org/jira/browse/JBIDE-4859 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.1.0.M3 Reporter: Nick Boldt Assignee: Koen Aers Fix For: 3.1.0.M3 Checking the latest JBT 3.1.0.M3 build #H262, I see a number of uncategorized features. Some of these are acceptable; for example, Freemarker and JMX's source features are not exposed as categorized features (only their SDKs are). This is good. I also see that JBoss Profiler is NOT listed on the categorized site (as it was deliberately removed from the list - but since it's still being built, it's still available, just hidden). This too is good. However, these subfeatures are also not listed under the categorized site: * Common Tools for jBPM 3 and jBPM 4 * Flow Language Common Tools * jBPM 4 Graphical Editor and Tools Should any of those be listed under the main JBT site category? (Also, "featureName" is most likely the two Maven source features... I'll fix that.) -- 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

6
43
0 / 0

[JBoss JIRA] Created: (JBIDE-3161) Equinox Transforms plugin for JBDS

by Rob Stryker (JIRA)

Equinox Transforms plugin for JBDS ---------------------------------- Key: JBIDE-3161 URL: https://jira.jboss.org/jira/browse/JBIDE-3161 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.0.0.beta1 Reporter: Rob Stryker Assignee: Snjezana Peco Priority: Critical Fix For: 3.0.0.cr1 Develop a plugin which will be able to transform / invalidate other plugins in an installation. First iteration could be just a core with a hard-coded list of plugins / extension points which we want invalidated. The goal here is to have all appropriate plugins in our installation, but disable the ones we do not want. Currently, JBDS removes the webtools jboss server-tools jar entirely, which makes the update site fail. What we need here is to have the webtools jboss server-tools jar IN hte installation, and loaded as a plugin, but have all of its extension points invalidated so it is effectively an empty non-contributing plugin. org.eclipse.jst.server.generic.jboss_1.5.205.v200805140145 is the plugin we need invalidated. We need it's plugin.xml to be essentially empty with just base <plugin></plugin> tags. -- 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
54
0 / 0

[JBoss JIRA] Created: (JBIDE-2820) Add supports for new jsf 2.0 elements

by Maxim Areshkau (JIRA)

Add supports for new jsf 2.0 elements -------------------------------------- Key: JBIDE-2820 URL: https://jira.jboss.org/jira/browse/JBIDE-2820 Project: Tools (JBoss Tools) Issue Type: Sub-task Affects Versions: 3.0.0.alpha Reporter: Maxim Areshkau Assignee: Maxim Areshkau Fix For: 3.0.0.beta1 Add supports for new jsf 2.0 elements h:head, h:body ... -- 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

6
10
0 / 0

[JBoss JIRA] Created: (JBDS-641) launcher on desktop not getting created

by Prabhat Jha (JIRA)

launcher on desktop not getting created --------------------------------------- Key: JBDS-641 URL: https://jira.jboss.org/jira/browse/JBDS-641 Project: Developer Studio Issue Type: Bug Components: installer Affects Versions: 2.0.0.GA Reporter: Prabhat Jha I tried the installer bits from http://reports.qa.atl.jboss.com/binaries/RHDS/nightly/2.0.0.GA/2009030209... When I created the option to put a launcher on desktop, it was not successful. [prabhat@localhost tooling]$ java -jar jbdevstudio-eap-linux-gtk-2.0.0.GA-N200903020901-H1485.jar PackageListener, install.log=/tmp/jbdevstudio-install-58598.log creating Logfile: 'IzPack_Logfile_at_1236025274545.txt' in: '/tmp' /home/prabhat/Desktop/JBoss Developer Studio 2.0.0.GA-N200903020901-H1485-1236025396329.desktop (No such file or directory) -- 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
15
0 / 0

[JBoss JIRA] Created: (JBDS-847) Runtime setup should use Java Execution Environment instead of specific VM

by Max Rydahl Andersen (JIRA)

Runtime setup should use Java Execution Environment instead of specific VM -------------------------------------------------------------------------- Key: JBDS-847 URL: https://jira.jboss.org/jira/browse/JBDS-847 Project: JBoss Developer Studio Issue Type: Sub-task Reporter: Max Rydahl Andersen Assignee: Denis Golovin -- 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
20
0 / 0

[JBoss JIRA] Created: (JBIDE-4244) JVM crashes and null pointer exceptions running JUnits on RHEL4 x86_64

by Nick Boldt (JIRA)

JVM crashes and null pointer exceptions running JUnits on RHEL4 x86_64 ---------------------------------------------------------------------- Key: JBIDE-4244 URL: https://jira.jboss.org/jira/browse/JBIDE-4244 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.GA Reporter: Nick Boldt Assignee: Max Rydahl Andersen Attachments: consoleText.jvm.crashes.and.NPEs.when.building.on.RHEL4.txt, jvmerrors.zip Instead of the usual 1900-2000 tests, when I run JBDS on a RHEL4 box, we get around 600-700 tests; the rest crash or throw errors. See attached console log & jvm errors. I don't know if we support RHEL4 as a runtime platform, so feel free to close this as wontfix if we do not. -- 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
20
0 / 0

[JBoss JIRA] Created: (JBIDE-4500) xcss templates should be copied to the classpath on deploy

by Jacques Lemire (JIRA)

xcss templates should be copied to the classpath on deploy ---------------------------------------------------------- Key: JBIDE-4500 URL: https://jira.jboss.org/jira/browse/JBIDE-4500 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.1.GA Environment: winxp x86, jdk6, jboss5 Reporter: Jacques Lemire In projects generated through "File" -> "New" -> "Seam web project", the facelets template "layout/template.xhtml" contains the following component in the "head" section: layout/template.xhtml: <a:loadStyle src="resource:///stylesheet/theme.xcss"/> This component, from a4j should transform the "richfaces templatable css" (xcss) file into a real CSS file and render as a <link> tag containing an a4j resource url. In projects created from the command-line seam-gen script, the output is as expected: <link class='user' rel='stylesheet' type='text/css' href='/testxcss/a4j/s/3_2_2.SR1stylesheet/theme.xcss/DATB/eAFrvajdHLp8hjQAEgwDtA__' /> However, using jboss tools, I get: <link class='user' rel='stylesheet' type='text/css' href='/SeamThemeTest/stylesheet/theme.xcss' /> This version does not work, however, as the xcss file is returned to the browser as is. By looking at the differences between the seam-gen project and the jbosstools project, i noticed the following section of the build.xml ant file generated by seam-gen: <copy todir="${war.dir}/WEB-INF/classes"> <fileset dir="${basedir}/resources"> <include name="**/*.xcss"/> </fileset>  <fileset dir="${basedir}/view"> <include name="**/*.xcss"/> </fileset> </copy> This step is not done by jbosstools (3.1.0), and indeed, by doing a quick web search, I fell on the following jira: https://jira.jboss.org/jira/browse/JBAS-6034, which states that: > [...] that would work in 4.2.x but not in jboss5 where the root of the war is no longer a part of the war's classpath (and never should have been!) Please fix it as soon as possible, as this problem affects any generated site and is pretty difficult to debug. On the other hand, it should be very easy to fix. -- 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

7
24
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: (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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2009