The shade plugin is perhaps relevant here.
On Mon, Jul 22, 2013 at 6:02 AM, Stephen Connolly < [email protected]> wrote: > You could do something with maven-invoker-plugin and have something else > generate the "filtered" pom file for you... you'd have to do some dancing > games though. > > I would suspect, though, that you have some anti-patterns in your pom in > the first place. Perhaps you should re-evaluate how and why you think you > need these different profiles. > > > On 22 July 2013 10:59, Baptiste MATHUS <[email protected]> wrote: > > > Hi, > > > > IIRC, I don't think this is possible. > > > > My 2 cents. > > Le 22 juil. 2013 11:20, "Kristian Freed" <[email protected]> a > > écrit : > > > > > I have a POM file that contains a profile used specifically during > > > development, and another (default) used for release builds. In the POM > > that > > > gets installed and deployed when building a release build, I do not > want > > to > > > expose any traced of the development profile, as these should not be > seen > > > by users of the library being built. > > > > > > Is there a way I can get Maven to generate and install/deploy the > > > "effective" POM resulting after profiles have been replied, i.e. one > > where > > > properties have been replaced with their effective values, only the > > > dependencies listed in active profiles show up etc? > > > > > > Cheers, > > > > > > Kristian > > > > > >
