I've not yet looked at maven internal code about how one might implement this ( to be honest, at this point in time I'm not sure even know WHERE to look, other than poking around classes named "Profile" :)
So yes - intuition on my part and just logic really. How adding something like this to the system affects the build stability is highly important, main reason I was thinking that it SHOULDN'T support version ranges. From immediate thoughts I don't think this would be any more unstability to the mix that the existing profile support doesn't already add to the mix ( profiles in ~/.m2/settings.xml being among the most unstable/unpredicatble IMHO ). Is there currently any way of maven telling a user WHERE a profile was included from? -pl allows you to select profiles but there doesn't seem to be any option to LIST profiles? I could see that being very handy, also failing the build if a non-existing profile is requested ( maven currently only WARNs about the non existing profile ). -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree On Sun, Dec 4, 2011 at 5:50 AM, Jason van Zyl <ja...@tesla.io> wrote: > The profile mechanism is how any new mixin system would work. No other > mechanism internally is really suited to provide full access to the model > in the right place. Not sure if you looked at the code or this is intuition > on your part but your analysis is correct in that it's collaboration with > the profile mechanism. This is how mixins should work.
