On 17 August 2010 16:33, Trevor Harmon <[email protected]> wrote: > On Aug 16, 2010, at 5:19 PM, Trevor Harmon wrote: > >> On Aug 16, 2010, at 5:04 PM, Justin Edelson wrote: >> >>> http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html >> >> Thanks, that looks like just what I need. > > I experimented some more with this issue, and it turns out I don't need > build-helper at all. If I bind the osxappbundle and launch4j plugins to the > package phase, they're automatically deployed to my repository when doing > "mvn deploy" (or "mvn release:perform"). Strangely, this doesn't happen if I > bind them to the deploy phase instead. >
the order of execution within a phase is loosely defined, but in general it is lifecycle first, so that deploy:deploy will run before your goals if you bind them to the deploy phase > I'm not sure what's going on behind the scenes. I assume there's some code > inside the two plugins that knows what to do for the deploy phase. Is this > common behavior for these types of plugins? > > Anyway, I've decided to keep the plugins attached to my package phase, > despite the increase in build time. Things are simpler that way, and the > delta is a lot less than the last time I tested these plugins -- no more than > 10 seconds or so. (This new SSD drive I got is da bomb...) > > Trevor > > > --------------------------------------------------------------------- > 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]
