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

[Snjezana Peco (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12479820#action_12479820 ] 

Snjezana Peco commented on JBIDE-4706:
--------------------------------------

> Click Project -> Properties -> Project Facets -> set checkbox "JBoss Maven Integration".
> Hyperlink "Further configuration available ..." appears.
> Click on it, and window "Add M2 capabilities to this Web Project" opens.
> It proposes incorrect values (no correlation with values from pom.xml) 

This is a bug in the JBoss Maven Integration and I will fix it.

> However, prj-jar-1.0-SNAPSHOT.jar should not be deployed at all. Neither in lib/, nor in lib/lib/.
> This dependency is for release Maven build. For debugging time .class files should be deployed on the server only (not jars made by Maven).

When you deploy the application to the JBoss Tools server using the JBoss Server View, you use JBoss deployer that isn't related to Maven.
The JBoss deployer doesn't unpack utility projects. It unpacks only EJB and WAR projects. WTP servers work the same way.

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