Hello Stephen, sounds a bit like Jenkins' Maven2 job type ;-)
Regards Mirko -- Sent from my mobile Am 03.03.2016 13:12 schrieb "Stephen Connolly" < stephen.alan.conno...@gmail.com>: > I had an evil idea... > > https://github.com/stephenc/reactor-snapshot-maven-plugin > > So the idea is to let you do things and resume quicker while doing things > that need the reactor artifacts when you don't want to invoke the full > lifecycle > > e.g. > > mvn package > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:take > > mvn > > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:restore > javadoc:jar > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:take > > mvn > > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:restore > source:jar > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:take > > mvn > > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:restore > install:install deploy:deploy > > mvn > > com.github.stephenc.maven:reactor-snapshot-maven-plugin:1.0-SNAPSHOT:restore > site > > Now this might ultimately need an extension helper so that things like -rf > will work better... but I wanted to try it out first. > > > The issue I have is persisting and looking up the artifact handlers... the > current way is hacky in the extreme and relies on the sisu injection > picking the same order (which may not always be valid due to the lifecycle > goals you might specify) > > > So, anyone care to tell me the "right" way to hack this! > > > -Stephen >