This looks like the right directory structure to me. Each directory
with a pom.xml file would be an Eclipse project. Why do you think this
won't work?
Justin
On Feb 27, 2009, at 8:25 AM, "John Wooten" <[email protected]>
wrote:
I'm trying to set up the structure below which was suggested as an
appropriate structure for maven when there were multiple products
depending upon common modules.
/areteq
/pom.xml - super pom - contains site information, etc.?
/modules
/foundation
/pom.xml - to create the foundation jar (common to all
products)
/src .. in all of these
/engine
/pom.xml - to create the engine jar ( common to all
products )
/pre-processors
/pom.xml - to create all pre-processor jars
/pre-processor1
/pom.xml - to create pre-processor1 jar
/pre-processor2
/ etc.
/post-processors
/renderers
/products
/pom.xml - to create all products and test?
/product1
/pom.xml - to create product1 and test? Contains list of
child modules it depends upon?
/src - not clear there is much here except for resources,
data, configurations.
/product2
etc.
However, it is difficult to also use this with Eclipse as one cannot
have a project "areteq" and then have other projects, viz.
"foundation" under that.
I want to be able to use "foundation" as an eclipse project for
interactive development and debugging, but use the maven pom's to do
integrated testing
documentation, profiling, etc.
Do I make foundation a separate eclipse project, but use the maven
structure inside of it, and then just have pom's in the areteq
project that refer to the
eclipse projects ( i.e. directories ) using relative paths? Right
now "areteq" and "foundation" are at the same directory level.
John W.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
