I've had some good luck integrating Maven Reactor with my product.  In this
process I've come up with a few questions (I couldn't find answers in the
Wiki):

I have

project.xml
maven.xml
        |
        --Project A (project.xml, maven.xml)
        |
        --Project B (project.xml, maven.xml)
        |
        --Project C (project.xml, maven.xml)

The root project and maven xml files just kickoff reactor to build
Project A, B, and C.  There is no source for the root project.

1) in my root maven.xml file I declare a property

<property name="projects.base.dir" value="${basedir}/projects" />
<echo>projects.base.dir = "${projects.base.dir}"</echo>

When the reactor runs I get different paths echoed to the screen.  Each
one is based on the Project A, B, and C.  I don't want that, I want
to persist my "projects.base.dir" and make it sticky.  Can I do that?

I guess for Project A, B, and C, Maven generates the environment
properties based on merging the project and maven files, so child 
elements take precedent over parent elements.  I think that is right.
Can I make some parent elements not-overridable?  Is each invocation 
of the project.xml file create some local stack of environment 
variables?

2) in my root maven.xml file I declare two goals "platform:clean" and
"platform:compile".  The first goal uses maven:reactor to clean each
subproject e.g. and only calls the "clean" goal

    <goal name="platform:clean">
        <maven:reactor
            basedir="${projects.base.dir}"
            includes="**/project.xml"
            goals="clean"
            banner="Cleaning"
            ignoreFailures="false"/>
    </goal>

my other goal "platform:compile" compiles each project and I want it to
first call "platform:clean" but fails and says "Unable to attain goal
[platform:clean]".

    <goal name="platform:compile">
        <maven:reactor
            basedir="${projects.base.dir}"
            includes="**/project.xml"
            goals="platform:clean, java:compile"
            banner="Generating"
            ignoreFailures="false"/>
    </goal>

Are we not allowed to chain custom goals like this?



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to