John Casey wrote:
In my simple setup my top-level maven.xml contains:o How do you use Reactor? (And are dependencies from your project.xmlSimple trial and error, no more than 10-15 minutes will answer most of your questions. As for properties, the last I looked, they're documented in each plugin's docs which were (at least at one time) linked up on the maven site.
involved in using reactor? I still don't know.)
This one in particular stumps me, and I really have no recourse but to dig into the source code and try to understand what the reactor even does in a specific way, before attempting to understand how to configure my projects to use it. This is something I poked at quite a bit last night, with no luck. Since I only have an hour or two a night to do such things, with my wife and job taking the rest, I cannot afford to dig in up to the waist to understand the purpose and structure of the reactor plugin. I just want a synopsis of what specifically it does (not the vague answer on the plugin's site) and how to use it. Sticky implications (i.e. inheritance of dependencies) I will tackle when I have a problem, but I can't even _get_started_.
<goal name="project"
description="Build each project's workspace">
<maven:reactor basedir="${basedir}"
glob="*/project.xml"
goals="project"
banner="Building project"
ignoreFailures="true"
/>
</goal>
This essentially tells maven to "cd to each subdirectory and achieve the 'build' goal'. My subprojects consist of two jarfiles and two webapps. One jar depends on the other and each webapp on both jars. Their respective project.xml files specify these things in their <dependencies> sections. I was pleasantly surprised to see that the reactor inspected these dependencies and builds things in the correct order. One caveat is that the 'project' goal of each of my jarfiles must either list jar:install as either a prereq or invoke it as an <attainGoal> (otherwise the jar won't be put into the local library repository and, thus, won't be available to the subsequent subprojects).
Remember that maven is built with maven. Rather than digging into the source at every speedbump it might be more useful to dig into how maven builds itself. At least in this case, that's how I figured out the reactor stuff.
The following URL _isn't_even_linked_to_ from the plugin docs. I had to
guess at it.
http://jakarta.apache.org/turbine/maven/plugins/reactor/index.html
Regards,
John
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
