Maven plugin

[perlin75]

I'm not sure if this is the correct forum...but here it goes

We have a problem publishing our apps(.ear) to JBoss EAP (SOA-P 4.3) from JBDS 2.0. Probably because we're generating all eclipse project files with the maven-eclipse-plugin which only supports WTP 2.

Does anybody know how to solve this problem(other than waiting for a new version of the maven plugin with WTP 3.x support)?

The permanent solution I think would be that the JBoss community/JBoss.com should provide such a maven plugin that could generate the correct project files for JBDS X.X.
This would be a great feature for users with a combo of JBossAS+JBDS/JbossTools+Maven

[maxandersen]

How about using m2eclipse ?

[perlin75]

Last time I checked m2eclipse felt very imature with very poor WTP integration, but maybe I should give it one more chance.

[perlin75]

Hi agian,

this looks promising:

https://jira.jboss.org/jira/browse/JBIDE-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12461623#action_12461623

I don't agree that the maven-eclipse-plugin is "evil". Another way to see it is that project configuration should be handled by some central role in the organization/project (through the pom.xml in this case), not the developers, in order to streamline and standardize mulitiple development projects.

But then again, I'm no m2eclipse expert.

[snjeza]

For now you can try the Project Examples wizard. There is mavenized Seam Booking Example that uses m2eclipse.
See http://in.relation.to/Bloggers/UsingMavenWithJBossTools

[maxandersen]

m2eclipse has much better WTP support than the mvn eclipse plugin by its very nature of how it is done (use the latest version)

the maven eclipse plugin makes all the edits eclipse plugin do irrelevant (ie. they get overwritten if you dont manually update the mvn eclipseeclipse plugin settings).

With m2eclipse there is at least the design for having better 2-way integration.

I like that - you can choose which tool you want to have the control and still benefit from both maven and eclipse plugins.

[perlin75]

I've just installed the latest version of m2eclipse and I would like to deploy one of our projects(.ear) wich previously was generated using the maven-eclipse-plugin.

With m2eclipse doing the job the ear looks totally incorrect when deployed to EAP.

- No lib folder in the ear, even though I configured my ear plugin that way.

- A WEB-INF in the root of the exploaded ear???

- When enabling "workspace resolution" I get an error saying: Cannot copy a directory: C:\Projects\TEMP\JBDS\declaration\declaration\bl\target\classes; Did you package/install active project artifact

- When disabling the worspace resolution the build(install) goes through but the ear gets corrupted. I have a multimodule project with ear, ejb and war modules. The ejb and war modules are not packaged inside the ear when deploying to EAP.

Should I configure the ear, war plugins in any specific way in order to get m2eclipse to work?

[maxandersen]

Your questions are specific to how Maven works hence until I become a MAven expert I can't really help.

... but please take a look at the examples Snejzana referred to. That shows Maven driven Seam Ear projects.