Hi Wayne, I want to give a small sample to make it more clear what I am requiring from MIXIN feature:
Project M is the base artifact for all modeling artifacts and defines the plugin sce.model with the required dependencies. Project I is the base artifact for all implementation artifacts and defines the plugin sce.compile with the required dependencies. Project A is the aggregation and defines an application <version>2.0.0</version> And has two modules "AM" and "AI" Project AM is the model artifact of the application A and has as a parent A and as a MIXIN M. Project AI is the implementation artifact of the application A and has as a parent A and as a MIXIN I. AM gets the version from A through the parent relationship. AM gets the plugin sce.model from the MIXIN relationship to M. AI gets the version from A through the parent relationship. AI gets the plugin sce.compile from the MIXIN relationship to I. I hope this makes it more clear what I would expect the MIXIN feature to do. Regards Richard -----Original Message----- From: ext Wayne Fay [mailto:[email protected]] Sent: Wednesday, April 13, 2011 6:49 AM To: Maven Users List Subject: Re: Expected implementation date for Maven MIXIN Feature > The only solution out of this problem I understood when reading the > Internet is the MIXIN feature. You can find in the Internet references I guess I don't understand the requirement very well. Some practical examples might be helpful for all of us. > Do you consider to include the MIXIN feature into Maven 3.0 as an > important update? Personally, no, I don't need it. I won't prevent someone else from adding it, if it makes sense. > If I am taking the time Maven 3.0 was release and add that to Maven 3.1 > it will be years? It would be really of much help to get some statements > on this from the Maven core team member. Maven is open source. The best way for something like this to get done is for someone who cares about this issue and perhaps needs it for their own projects/work to roll up their sleeves and take a stab at an implementation. Assuming it works and makes sense, the changed code could be donated back and considered for inclusion in a future release of Maven. Even if it wasn't accepted, there is nothing stopping someone from continuing to run (and support) their own internal build of Maven with additional features (this happens now and then). Short of this, you can find an existing Jira issue and vote/watch it or file one if you can't find an issue that captures the mixin feature, and then just wait for someone who cares more about it than you do to implement it on your behalf. Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
