>> the workaround Delany sketched in his answer sounds viable. Would you >> agree? > > Delany found a smart workaround to try to have full control about > order in effective POM, then on build plan: nice idea, even if > cumbersome If you don't play too much with profiles, inheritance, and > don't expect too much control at execution level (instead of plugin), > I suppose our effective POM building algorithm should not change the > order in the future. Then you're still playing at your own risk with > implementation details, but it may work sufficiently well.
Thanks, that comment helps me weigh risk vs. benefit. :-) >> Actually, that would be awesome. I just cannot say if I can make it, >> because I have a quite demanding daytime job as an Agile Coach too >> and only program in my sparetime as a hobby. > > same here you know for every Maven committers Actually, I would assume that the vast majority of Maven committers, even if doing OSS work in their sparetime, are professional developers or something close to development and coding such as software architects or development team leads, in their daytime jobs. The last time I really made money by coding was almost 20 years ago during my first career and before becoming a consultant. > Maven Shade Plugin is not part of the plugins I usually work on. > Please put the link to your PR, I can add it to my already long > personal TODO list and see if I have some spare time https://github.com/apache/maven-shade-plugin/pull/88 https://issues.apache.org/jira/browse/MSHADE-252 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
