But Maven doesn't know about it before it invokes it (the plugin has no way to declare to Maven what it *will* do, it imperatively tells Maven what to do when Maven invokes it); so it cannot know upfront whether it has to invoke the build-helper's attach-artifact in Module B (i.e. invoke a phase to which the build-helper's attach-artifact is bound) to fulfill the requirements of Module A.
On Thu, Mar 27, 2014 at 3:27 PM, mkarg <[email protected]> wrote: > Again, I am talking particularly about that problem I actually posted > originally, in which Maven does know for sure that the needed artifact is > provided, as I am invoking the build helper's plugin's attach-artifact goal > which does nothing else but tell Maven exactly that! > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/multi-module-phases-sequence-tp5789365p5789704.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Thomas Broyer /tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/>
