August 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-825) JBoss CSS Editing Perspective is created

by Svetlana mukhina (JIRA)

JBoss CSS Editing Perspective is created ----------------------------------------- Key: JBDS-825 URL: https://jira.jboss.org/jira/browse/JBDS-825 Project: JBoss Developer Studio Issue Type: Task Components: Doc - VisualWebTools, Doc - RHDS GSG Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Fix For: 3.0.0.M2 Update the guides , see the linked task -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Updated: (JBIDE-4706) Maven integration issues: setting facets on maven projects and deploying ear on JBoss

by Snjezana Peco (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ] Snjezana Peco updated JBIDE-4706: --------------------------------- Component/s: UpStream Fix Version/s: 3.1.0.M4 (was: 3.1.0.M3) > Maven integration issues: setting facets on maven projects and deploying ear on JBoss > ------------------------------------------------------------------------------------- > > Key: JBIDE-4706 > URL: https://jira.jboss.org/jira/browse/JBIDE-4706 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, UpStream > Environment: Eclipse 3.5 > m2eclipse (0.9.9.20090720) > JBoss Tools AS M3 developer version > Subclipse SVN plugin 1.6.3 > Reporter: Alexander Lengson > Assignee: Snjezana Peco > Fix For: 3.1.0.M4 > > Attachments: container.zip, libs_issue.zip, screenshot-1.jpg, screenshot-2.jpg, without_vars.zip, without_vars_pure_maven.zip > > > Using Maven command line, I created four projects: > container - the parent Maven project. It also serves as a container for other projects > prj-jar - a shared library used by all other EJBs > prj-ejb - sample EJB > prj-ear - EE container for jar and ejb > Apache plugins for Maven (both for ejb and ear) are used. > I've performed the following steps: > * imported container into SVN > * opened Eclipse 3.5 with M3 JBoss AS Tools and dev version of m2eclipse (0.9.9.20090720) > * right-clicked on container and chosen "Checkout as Maven project" > * waited for the process to be finished > And the following likely are bugs and/or open questions: > * for prj-jar: 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already. > * for prj-ejb: the same, i.e. 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already. > * for prj-ear: the same. > * for container: "JBoss Maven Integration" facet is not set and can not be selected. What another facet should be set to meet requirements? > * for prj-ejb: there is no Project Facet checked at all. > * for prj-ejb: when I check EJB 3.0 and then click Further Configuration, it does not propose sensible defaults (instead they are as always: src for sources, build/classes for compiled) > * for prj-ejb: If I provided values for src and build folder mistakenly, it does not allow to change them (even uncheck/check again shows only form with all fields greyed) > * for prj-ejb: after checking Java 6.0 and EJB 3.0, there are still errors in Problems View: > EJB Module 3.0 requires Java 5.0 or newer. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart > One or more constraints have not been satisfied. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart > Java compiler level does not match the version of the installed Java project facet. prj-ejb Unknown Faceted Project Problem (Java Version Mismatch) --- survives Eclipse restart > * for prj-ear: Java EE module dependencies are not checked (they may be suggested from the pom.xml) > * for prj-ear: Maven plugin maven-ear-plugin has the option to put all referenced libraries into Lib directory: > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-ear-plugin</artifactId> > <version>2.3.2</version> > <configuration> > <includeLibInApplicationXml>true</includeLibInApplicationXml> > ... > That builds the EAR which contains lib/ folder inside and all references libs like: > drools-api-5.0.1.jar > drools-core-5.0.1.jar > hsqldb-1.8.0.10.jar > joda-time-1.6.jar > mvel2-2.0.10.jar > prj-jar-1.0-SNAPSHOT.jar > That can be assured by running command: > container>mvn install > Eclipse does not put those libraries into deploy dir while making "Full Publish" which causes server startup errors. > It's reasonable to copy these libraries onto server when using JBoss Server View and debugging server from Eclipse. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-4706) Maven integration issues: setting facets on maven projects and deploying ear on JBoss

by Snjezana Peco (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-4706: -------------------------------------- This issue is described in https://issues.sonatype.org/browse/MNGECLIPSE-1585 There is a patch for it. > Maven integration issues: setting facets on maven projects and deploying ear on JBoss > ------------------------------------------------------------------------------------- > > Key: JBIDE-4706 > URL: https://jira.jboss.org/jira/browse/JBIDE-4706 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Environment: Eclipse 3.5 > m2eclipse (0.9.9.20090720) > JBoss Tools AS M3 developer version > Subclipse SVN plugin 1.6.3 > Reporter: Alexander Lengson > Assignee: Snjezana Peco > Fix For: 3.1.0.M3 > > Attachments: container.zip, libs_issue.zip, screenshot-1.jpg, screenshot-2.jpg, without_vars.zip, without_vars_pure_maven.zip > > > Using Maven command line, I created four projects: > container - the parent Maven project. It also serves as a container for other projects > prj-jar - a shared library used by all other EJBs > prj-ejb - sample EJB > prj-ear - EE container for jar and ejb > Apache plugins for Maven (both for ejb and ear) are used. > I've performed the following steps: > * imported container into SVN > * opened Eclipse 3.5 with M3 JBoss AS Tools and dev version of m2eclipse (0.9.9.20090720) > * right-clicked on container and chosen "Checkout as Maven project" > * waited for the process to be finished > And the following likely are bugs and/or open questions: > * for prj-jar: 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already. > * for prj-ejb: the same, i.e. 0.0.1-SNAPSHOT "JBoss Maven Integration" facet is not checked. After checking further configuration suggests "0.0.1-SNAPSHOT" instead of "1.0-SNAPSHOT" as declared in pom.xml already. > * for prj-ear: the same. > * for container: "JBoss Maven Integration" facet is not set and can not be selected. What another facet should be set to meet requirements? > * for prj-ejb: there is no Project Facet checked at all. > * for prj-ejb: when I check EJB 3.0 and then click Further Configuration, it does not propose sensible defaults (instead they are as always: src for sources, build/classes for compiled) > * for prj-ejb: If I provided values for src and build folder mistakenly, it does not allow to change them (even uncheck/check again shows only form with all fields greyed) > * for prj-ejb: after checking Java 6.0 and EJB 3.0, there are still errors in Problems View: > EJB Module 3.0 requires Java 5.0 or newer. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart > One or more constraints have not been satisfied. prj-ejb line 1 Maven Problem --- disappears after Eclipse restart > Java compiler level does not match the version of the installed Java project facet. prj-ejb Unknown Faceted Project Problem (Java Version Mismatch) --- survives Eclipse restart > * for prj-ear: Java EE module dependencies are not checked (they may be suggested from the pom.xml) > * for prj-ear: Maven plugin maven-ear-plugin has the option to put all referenced libraries into Lib directory: > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-ear-plugin</artifactId> > <version>2.3.2</version> > <configuration> > <includeLibInApplicationXml>true</includeLibInApplicationXml> > ... > That builds the EAR which contains lib/ folder inside and all references libs like: > drools-api-5.0.1.jar > drools-core-5.0.1.jar > hsqldb-1.8.0.10.jar > joda-time-1.6.jar > mvel2-2.0.10.jar > prj-jar-1.0-SNAPSHOT.jar > That can be assured by running command: > container>mvn install > Eclipse does not put those libraries into deploy dir while making "Full Publish" which causes server startup errors. > It's reasonable to copy these libraries onto server when using JBoss Server View and debugging server from Eclipse. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-4655) Mavenized Project Examples and Seam Web Project wizard with JBoss Maven Integration facet don't work when using WTP 3.1 final

by Snjezana Peco (JIRA)

Mavenized Project Examples and Seam Web Project wizard with JBoss Maven Integration facet don't work when using WTP 3.1 final ----------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4655 URL: https://jira.jboss.org/jira/browse/JBIDE-4655 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, project-examples, UpStream Affects Versions: 3.1.0.M3 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.1.0.M3 Deployment has been changed between WTP 3.1M7 and WTP 3.1.0. WTP 3.1.0 ignores <wb-module deploy-name="xxxx"> in .settings/org.eclipse.wst.common.component -- 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, 7 months

4
22
0 / 0

[JBoss JIRA] Created: (JBIDE-4762) Need to let the users a possibility to enable JSF CA for old projects.

by Victor Rubezhny (JIRA)

Need to let the users a possibility to enable JSF CA for old projects. ---------------------------------------------------------------------- Key: JBIDE-4762 URL: https://jira.jboss.org/jira/browse/JBIDE-4762 Project: JBoss Tools Issue Type: Feature Request Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.M3 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.1.0.M3 Because of new builder is created for CA Knowledge Base the users, who installed M3 revision of JBoss Tools, are lost the CA on their old projects. We need to allow them to enable CA functionality on these projects. 1. The special kind of proposal is to be shown with suggestion to enable JSF code completion on this project 2. Possibility to enable JSF code completion from project properties -- 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, 7 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4770) The quick-fix is to be present to allow to specify the KB-nature and KB-builder on the project.

by Victor Rubezhny (JIRA)

The quick-fix is to be present to allow to specify the KB-nature and KB-builder on the project. ------------------------------------------------------------------------------------------------ Key: JBIDE-4770 URL: https://jira.jboss.org/jira/browse/JBIDE-4770 Project: JBoss Tools Issue Type: Sub-task Affects Versions: 3.1.0.M3 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 3.1.0.M3 -- 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, 7 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4776) CA not show proposals when it's should

by Maxim Areshkau (JIRA)

CA not show proposals when it's should -------------------------------------- Key: JBIDE-4776 URL: https://jira.jboss.org/jira/browse/JBIDE-4776 Project: JBoss Tools Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.M2 Reporter: Maxim Areshkau Assignee: Victor Rubezhny Fix For: 3.1.0.M3 #1 import project https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js... #2 open page TestChangeUriInInnerNodes.xhtml #3 go to line 14 and position 14 and inset 'rich:validateA' #4 call CA 'rich:validateA|' ASSERT SHOUD BE PROPOSAL rich:validateAll This reason of fail JBIDE788Test.testCAforIncludeTaglibInInenerNodes -- 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, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-4766) CA not shows message bundle proposals

by Maxim Areshkau (JIRA)

CA not shows message bundle proposals ------------------------------------- Key: JBIDE-4766 URL: https://jira.jboss.org/jira/browse/JBIDE-4766 Project: JBoss Tools Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.1.0.M2 Reporter: Maxim Areshkau Assignee: Alexey Kazakov Fix For: 3.1.0.M3 Create jsf 1.2 kick start project or import this one https://svn.jboss.org/repos/jbosstools/trunk/jsf/tests/org.jboss.tools.js... and open page testCAMessageBundlesAndEL.xhtml and try CA for message bundles. It's not works. -- 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, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (JBDS-740) Links as Pronounce

by Svetlana mukhina (JIRA)

Links as Pronounce ------------------ Key: JBDS-740 URL: https://jira.jboss.org/jira/browse/JBDS-740 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 2.0.0.GA Reporter: Svetlana mukhina Assignee: Svetlana mukhina Priority: Minor Fix For: 2.1.0 Links as Pronounce should be replace with more meaningful phrases (e.g. "here" with "JBoss Tools Forum") -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-4797) [default] label doesn't wrok correctly with JSF Pages from Preferences

by Yura Zhishko (JIRA)

[default] label doesn't wrok correctly with JSF Pages from Preferences ---------------------------------------------------------------------- Key: JBIDE-4797 URL: https://jira.jboss.org/jira/browse/JBIDE-4797 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.1.0.M3 Reporter: Yura Zhishko Assignee: Alexey Kazakov Priority: Minor Attachments: screenshot-1.jpg 1) Open Preferences->JBoss Tools->Web->JSF Pages ASSERT: Blank - marked as [default] 2) Choose Blank in pages list 3) Press Add button ASSERT: Add page template dialog should be opened. 4) Press Cancel RESULT: [default] label has gone. 5) Choose Blank again RESULT: "Set Default" button is disabled, so, this page is still as [default] template page, but there is no [default] label (screenshot-1). -- 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, 7 months

3
4
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 August 2009