What!? You mean the developers don't pick up messages telepathically? :o) But really, I'm not sure if it's really that clever. It's a little like filing a ticket saying "rm -rf ~ deletes my home directory".
- hugi On 31.7.2011, at 18:42, Anders Hammar wrote: > If you file a jira ticket ([1]) suggesting this it could actually get > implemented instead of just being a clever idea... > > /Anders > > [1] http://jira.codehaus.org/browse/MNG > > On Sun, Jul 31, 2011 at 17:16, Hugi Thordarson <[email protected]> wrote: > >> Hi again, >> >>>> You inspired me to do quick search for "outputDirectory" in all the POMs >> and I found this little bugger in all the projects' common parent pom: >>>> >>>> <reporting> >>>> <outputDirectory /> >>>> </reporting> >>>> >>>> Not sure what purpose it served - but once removed, the projects behave >> as expected in Maven 3 :). >>> >>> Glad you figured it out. Having an empty outputDirectory must make it >>> default to the modules working directory. Then your clean would >>> convert the build into a digital Ouroboros of disaster. >> >> Yes, that's what I figured (and confirmed by building some javadocs). >> >> >>> Maybe Maven 3, in its aim to better inform users about code smells, >>> should warn users of this perilous condition. >> >> Yes, that would be clever. Although Maven 3 is really just doing the right >> thing with a somewhat silly configuration :-). >> >> Thanks again, >> - hugi >> --------------------------------------------------------------------- >> 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]
