You can just package the custom lifecycle in a jar and declare the jar as a /project/build/extensions/extension
Note: 1. You cannot both produce and consume a build extension from the same reactor, as the extension that is being produced will affect the build plan, and the effects will not be known until after the build plan has been started. 2. You can produce a different version of the extension, eg reactor consumes version 1.0 but produces version 1.1-SNAPSHOT is ok On Thursday, 30 May 2013, Lisen Mu wrote: > Hi, > > Is there any easy way to customize the packaging behavior? like > > <packaging>my-jar</packaging> > > I googled around, and it seems to me that I have to make a maven plugin to > achieve this. I would expect something less heavyweighted than a maven > plugin to do this, for example, declaring it in my pom? > > Thanks! > -- Sent from my phone
