That is probably what we would have done if we hadn't had to deal
with the {subproject}/build having to be svn:externals-ized into each
one.
I was pleasantly surprised (after making my changes to the 4 or 5
tests in core) to run 'mvn install' in struts/action/build/ and see
the reactor kick off and fully build/test/install all/some of SAF.
Same for compile, test, and a few other targets.
--
James Mitchell
On Apr 5, 2006, at 9:06 PM, Wendy Smoak wrote:
On 4/5/06, James Mitchell <[EMAIL PROTECTED]> wrote:
Also, I'm about to start another thread related to our build...it is
(more or less) notes as I go through the various project.xml,
pom.xml, etc, etc for each of the pieces of the action1 puzzle.
What do you think about moving the build files (project.xml,
maven.xml, etc.,) up to the 'struts/current/action' level? That would
be closer to Maven's default project structure.
--
Wendy
---------------------------------------------------------------------
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]
