August 2009 - jbosstools-issues - Jboss List Archives

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

by Max Rydahl Andersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plu... ] Max Rydahl Andersen moved JBDS-804 to JBIDE-4706: ------------------------------------------------- Project: Tools (JBoss Tools) (was: Developer Studio) Key: JBIDE-4706 (was: JBDS-804) > 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 > 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 > Attachments: container.zip, libs_issue.zip, screenshot-1.jpg, screenshot-2.jpg > > > 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

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-4622) Add icon for "Pending..." tree item of Hibernate CC

by Vitali Yemialyanchyk (JIRA)

Add icon for "Pending..." tree item of Hibernate CC --------------------------------------------------- Key: JBIDE-4622 URL: https://jira.jboss.org/jira/browse/JBIDE-4622 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.1.0.M2 Reporter: Vitali Yemialyanchyk Assignee: Vitali Yemialyanchyk Priority: Minor Fix For: 3.1.0.M3 This is a simple nice feature, I remember this functionality was implemented coupled with some patch, which hasn't get into the trunk. -- 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, 9 months

1
3
0 / 0

[JBoss JIRA] Created: (JBIDE-4695) Seam Generate Entities layout folder check is broke

by David Thompson (JIRA)

Seam Generate Entities layout folder check is broke --------------------------------------------------- Key: JBIDE-4695 URL: https://jira.jboss.org/jira/browse/JBIDE-4695 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.M2 Environment: Running on Galileo with JBoss Tools 3.1.0M3 Reporter: David Thompson Priority: Blocker Created project with seam-gen, imported into Eclipse. Checked the org.jboss.tools.seam.core.prefs and seam.project.web.root.folder is set to /projectName/view The layout directory exists within /projectName/view. Right click on the project and select New->Seam Generate Entities Red x appears with error stating "Folder '/ProjectName/layout' doesn't exist". However if you create the /ProjectName/layout folder and then generate the entities they are placed in /ProjectName/view/layout as they should. It appears the new check added in JBIDE-4012 isn't using the seam.project.web.root.folder property. -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4577) JBossAS 5.1 not supported for EJB and Web projects

by Juergen Zimmermann (JIRA)

JBossAS 5.1 not supported for EJB and Web projects -------------------------------------------------- Key: JBIDE-4577 URL: https://jira.jboss.org/jira/browse/JBIDE-4577 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.1.0.M2 Environment: Eclipse 3.5, WTP 3.1, JBossAS-Tools Nightly 2.1.0.M2-N200907061943-H341 Reporter: Juergen Zimmermann When creating an EJB and/or Web project there are no "EAR Libraries" provided to have the JARs of JBossAS 5.1 available. A screenshot will be provided. See also https://jira.jboss.org/jira/browse/JBIDE-3374 which claims to be resolved. -- 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, 9 months

3
11
0 / 0

[JBoss JIRA] Created: (JBIDE-4699) Execute the bpel validator when build bpel project

by Denny Xu (JIRA)

Execute the bpel validator when build bpel project ---------------------------------------------------- Key: JBIDE-4699 URL: https://jira.jboss.org/jira/browse/JBIDE-4699 Project: Tools (JBoss Tools) Issue Type: Task Components: bpm Affects Versions: 3.1.0.M3 Reporter: Denny Xu Assignee: Denny Xu Fix For: 3.1.0.M3 Currently, the bpel validator can only be activated manually and it can not be executed when the project is building. -- 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, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4679) JBT 3.1.0.M3 build's tests are failing to resolve xulrunner, etf, bpel, jbt.tests, so tests are failing.

by Nick Boldt (JIRA)

JBT 3.1.0.M3 build's tests are failing to resolve xulrunner, etf, bpel, jbt.tests, so tests are failing. -------------------------------------------------------------------------------------------------------- Key: JBIDE-4679 URL: https://jira.jboss.org/jira/browse/JBIDE-4679 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.1.0.M3 Reporter: Nick Boldt Assignee: Denis Golovin JBT 3.1.0.M3 build's tests are failing to resolve xulrunner, etf, bpel, jbt.tests, so tests are failing. No idea what's changed or why this is happening. Last good build was Build #100 (Jul 24, 2009 12:00:54 PM) http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... Current failure: http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-nightly-3... Build #112 (Jul 29, 2009 2:28:17 AM) [echo] [eclipse.fetch] Missing directory entry: plugin(a)org.mozilla.xpcom,1.8.1.3-20070904. [echo] [eclipse.fetch] Missing directory entry: bundle(a)org.mozilla.xpcom,1.8.1.3-20070904. [echo] [eclipse.fetch] Missing directory entry: plugin(a)org.mozilla.xulrunner.carbon.macosx,1.8.1.3-20070904. [echo] [eclipse.fetch] Missing directory entry: bundle(a)org.mozilla.xulrunner.carbon.macosx,1.8.1.3-20070904. [echo] [eclipse.fetch] Missing directory entry: plugin(a)org.mozilla.xulrunner.gtk.linux.x86,1.8.1.3-20070904. [echo] [eclipse.fetch] Missing directory entry: bundle(a)org.mozilla.xulrunner.gtk.linux.x86,1.8.1.3-20070904. [echo] [eclipse.fetch] Missing directory entry: plugin(a)org.mozilla.xulrunner.gtk.linux.x86_64,1.8.1.4-20080112. [echo] [eclipse.fetch] Missing directory entry: bundle(a)org.mozilla.xulrunner.gtk.linux.x86_64,1.8.1.4-20080112. [echo] [eclipse.fetch] Missing directory entry: plugin(a)org.mozilla.xulrunner.win32.win32.x86,1.8.1.3-20070904. [echo] [eclipse.fetch] Missing directory entry: bundle(a)org.mozilla.xulrunner.win32.win32.x86,1.8.1.3-20070904. [echo] [eclipse.fetch] Missing directory entry: plugin(a)org.eclipse.birt.integration.wtp.ui. [echo] [eclipse.fetch] Missing directory entry: bundle(a)org.eclipse.birt.integration.wtp.ui. [echo] [eclipse.fetch] Missing directory entry: fragment(a)org.eclipse.ant.optional.junit. [echo] [eclipse.fetch] Missing directory entry: bundle(a)org.eclipse.ant.optional.junit. [echo] [eclipse.fetch] Missing directory entry: plugin(a)org.eclipse.test. [echo] [eclipse.fetch] Missing directory entry: bundle(a)org.eclipse.test. [echo] [eclipse.fetch] Missing directory entry: plugin(a)org.jboss.tools.test. [echo] [eclipse.fetch] Missing directory entry: bundle(a)org.jboss.tools.test. [echo] [eclipse.fetch] Missing directory entry: plugin(a)org.jboss.tools.bpel.ui.test. [echo] [eclipse.fetch] Missing directory entry: bundle(a)org.jboss.tools.bpel.ui.test. -- 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, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDS-441) faces-config.xml, JSF web.xml config, struts.config.xml, struts web.xml config descriptors

by Svetlana mukhina (JIRA)

faces-config.xml, JSF web.xml config, struts.config.xml, struts web.xml config descriptors ------------------------------------------------------------------------------------------ Key: JBDS-441 URL: https://jira.jboss.org/jira/browse/JBDS-441 Project: Developer Studio Issue Type: Sub-task Reporter: Svetlana mukhina Assignee: Max Rydahl Andersen -- 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, 9 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-4072) Add option to show a grid in the GPD (jBPM Editor)

by Joao Paulo Viragine (JIRA)

Add option to show a grid in the GPD (jBPM Editor) -------------------------------------------------- Key: JBIDE-4072 URL: https://jira.jboss.org/jira/browse/JBIDE-4072 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Joao Paulo Viragine Priority: Minor Add option to show a grid in the GPD (jBPM Editor) -- 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, 9 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-2534) Ability to define default "File Filters" for new Servers

by Galder Zamarreno (JIRA)

Ability to define default "File Filters" for new Servers --------------------------------------------------------- Key: JBIDE-2534 URL: https://jira.jboss.org/jira/browse/JBIDE-2534 Project: Tools (JBoss Tools) Issue Type: Task Reporter: Galder Zamarreno Ability to define default "File Filters" for new Servers with *-log4j.xml as example. -- 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, 9 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2009