Thank you very much for all your hints :-).
Regards Mirko
On Wed, Jul 25, 2012 at 10:28 AM, Tamás Cservenák wrote:
> Mirko,
>
> so, you want to have your mojo run at last reactor module being built
> (having your mojo defined)?
>
> Then take a peek at this:
> https://github.com/sonatype/nexus-m
Mirko,
so, you want to have your mojo run at last reactor module being built
(having your mojo defined)?
Then take a peek at this:
https://github.com/sonatype/nexus-maven-plugins/tree/master/nexus-staging-maven-plugin
and (as it uses) this:
https://github.com/sonatype/mojo-commons/blob/master/src
Hi Mirko!
You may try doing the same trick as the cobertura-maven-plugin does when
aggregate is set to true.
1. Every module executes the plugin, but the plugin updates the same file
in the directory of the project from which the build was started. In you
case you may, for example, calculate SHA1
Hello Brett,
unfortunately, binding it to Lifecycle.INSTALL without a custom
lifecycle seems not to be good enough. During the run of "mvn
install", "install" will be run in every module seperately (first
parent, the reactor projects). Now after install:install succeeded in
the parent, my goal foo
Binding the mojo in the install phase will run it after anything already
executed in the install phase, which should be sufficient for your use case
(you can probably even run it in the package phase since everything attaching
artifacts will happen there).
- Brett
On 25/07/2012, at 7:08 AM, Mi
Mirko,
The best way to accomplish this in a plugin you control the source for is to
create a custom lifecycle.
See
http://www.sonatype.com/books/mvnref-book/reference/writing-plugins-sect-plugins-lifecycle.html.
Brian
On Jul 25, 2012, at 12:08 AM, Mirko Friedenhagen wrote:
> Hello,
>
> in a
