> Hi Wayne - that seems a very inefficient approach, having 5 or 6 separate > modules to > manage to achieve a single assembly. The point is that maven does have phases, > goals, lifecycles - why not use them? The MavenProject object already > provides the
Not saying this is ideal for all scenarios. Just saying it is one solution that works out of the box and it leaves the door open for customization you may need along the way. People here oftentimes say they "just want to do X" and so we provide some advice. Then they come back a week later and say well actually they need variants of X for different clients, environments, architectures, etc so they share how they've been going down the path of profiles which most of us here believe is the wrong way to do things. I'm just trying to ensure you know TMTOWTDI (perl-ism). :) > ...I think dividing the construction of a single atomic component into > multiple modules > because the plugins cannot be chained together is more unappealing. I don't disagree. As I said, this is based on my assumption (perhaps wrong) that you have left a great many details out of your original query, and the next few emails will describe a monstrous beast you have created with profiles and binding plugins to various lifecycles etc in an effort to do "all the work" in a single project/module. ;-) > BTW I haven't touched Ant in at least 6 years, so I doubt I'm an > "Ant-oriented person". :-) Didn't mean you were necessarily Ant-oriented. I know you've released some Maven plugins lately. Thanks for your work in the Maven ecosystem! :) Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
