On 3/20/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > Does <skip>true</skip> mean skip the normal mojo? I can't quite track > why one <skip> is false, the other true.
It's a gross hack to work around it. The test mojo takes a skip parameter to honour -Dmaven.test.skip=true. So, in this definition, the default is to skip it (skipping the built in one), then add a second goal with your new configuration that is not skipped. > It mostly definately did. I had to cut-and-paste it into each module's > pom.xml. Ok, I don't quite understand why that is. Unfortunately, I don't have the time to investigate right now, but I hope the above works for you. > I hate to say this, but a flow chart showing how Maven decides what to > do, how it instantiates Mojos, the algorithm used to collect > configuration information, might be useful. Sounds like a good idea. I'll keep a note of it. > What I didn't see was how I could displace the original Mojo and just > leave my own. It's not something you can normally do - it just happens that the test mojo has a skip parameter that does what was needed to omit it. > Its pretty important for the underlying structure to be known, or even > knowable. I don't like "Cargo Cult" approaches > (http://www.physics.brocku.ca/etc/cargo_cult_science.html). Yep, I agree. > Thanks for the help! I'm off to figure out to convert reams of > Forrest XML documentation into Maven XML or APT. I believe the incubator did this to go from forrest to Anakia (xdoc). Geir might be able to help explain how it was done. A new version of the site plugin should be out shortly that has much improved multi-module support. Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
