June 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-3996) VPE - it is possible to get unsynchronized Visual/Source

by Vitali Yemialyanchyk (JIRA)

VPE - it is possible to get unsynchronized Visual/Source -------------------------------------------------------- Key: JBIDE-3996 URL: https://jira.jboss.org/jira/browse/JBIDE-3996 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.0.0.CR2 Reporter: Vitali Yemialyanchyk Assignee: Maxim Areshkau Priority: Minor try to Undo/Redo -> Ctrl-Z/Ctrl-Y type something in between: <a>Sawsdcwdsve</a> do all these quickly - press Ctrl-S you could get unsynchronized Visual/Source. for <a>Sawsdcwdsve</a> I saw: Save As I think the key word here to reproduce it is "quickly". -- 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, 1 month

6
17
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, 1 month

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, 1 month

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, 1 month

4
15
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, 1 month

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, 1 month

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, 1 month

2
6
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, 1 month

3
8
0 / 0

[JBoss JIRA] Created: (JBDS-366) Welcome screen: view of Create New is incorrectly, and there is strange behavior

by Tatyana Romanovich (JIRA)

Welcome screen: view of Create New is incorrectly, and there is strange behavior -------------------------------------------------------------------------------- Key: JBDS-366 URL: http://jira.jboss.com/jira/browse/JBDS-366 Project: Developer Studio Issue Type: Bug Affects Versions: 1.1.0.CR1 Environment: JBoss Developer Studio Version: 1.1.0 Build id: 200806161541-nightly Build date: 06/16/2008 15:46 Reporter: Tatyana Romanovich Assigned To: Maxim Areshkau Priority: Trivial EXECUTE: Open JBDS with empty workspace EXECUTE: select Getting Started on the Welcome screen EXECUTE: move mouse over the each links 1. FAILURE: green badge on the icon appears only for "Viewlets and Tutorials" point (see Welcome1.png) EXECUTE: select any item (click on the right of link) EXECUTE: move mouse over another items icon 2. FAILURE: both icons have green badge at the same time (see Welcome2.png) EXECUTE: Select "Create New..." 3. FAILURE: "Create jBPM Process Project" is subitem of "Create Seam Project". Is it right? (see Welcome3.png) EXECUTE: Select "Perspectives" EXECUTE: Select any item -> Welcome window gets smaller EXECUTE: Verify Welcome window 4. FAILURE: Welcome to JBDS appears (Is it right? ) EXECUTE: Try to select Perspectives link 5. FAILURE: Perspectives can't be displayed -- 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

16 years, 1 month

4
20
0 / 0

[JBoss JIRA] Created: (JBDS-340) Intro/Welcome screen cleanup

by Max Rydahl Andersen (JIRA)

Intro/Welcome screen cleanup ---------------------------- Key: JBDS-340 URL: http://jira.jboss.com/jira/browse/JBDS-340 Project: Developer Studio Issue Type: Task Components: ui/branding Reporter: Max Rydahl Andersen Assigned To: Max Rydahl Andersen Fix For: 2.0.0.alpha Splashscreen support has improved in Ganymede, same has the intro and welcome screen setup. SWT did some changes to allow xulrunner to be configured at startup - we should make sure we do what is needede there. If that happens we should be able to remove our big code duplication and just use the normal welcome screen mechanism and hopefully create a JBDS branded version. -- 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

16 years, 1 month

4
14
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 June 2009