Hi,
I've been using m2 and maven-eclipse-plugin for some time for developing
EJB3 apps. I've found it useful to have POM type projects responsible
for managing my ear build, in a structure something like:
mymodule
+- mymodule-build-config (type: POM)
+- mymodule-ear (type: ear)
+- mymodule-domain (type: jar)
+- mymodule-war (type: war)
The "build-config" module is responsible for linking into my POM
hierarchy (I have a team-build-config, department-build-config, etc. to
specify more general properties), and building the domain, war, and ear.
There is no pom.xml in the top level mymodule directory, as would be
suggested by a hierarchical layout: effectively, I just move that pom
into the build-config dir to make working with Eclipse a little easier.
This layout ends up being a hybrid of the hierarchical and flat
project layouts that I've seen suggested elsewhere.
The problem I have is that the maven-eclipse-plugin will not generate a
project for Eclipse out of a POM-type module. I've taken to hacking the
plugin to do this, but would much rather make it an option on the
upstream release (e.g. -DprojectForPom=true or some such). Am I missing
something that makes this unnecessary, or would this be a useful patch
for others? If so, I'd be happy to submit one to JIRA.
Cheers,
Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
