On Dec 18, 2008, at 8:34 AM, Jason van Zyl wrote:
On 18-Dec-08, at 1:35 AM, Ralph Goers wrote:
OK - I'm looking forward to seeing this. I understand the
programmatic aspect in the use case you describe with the IDE, but
not with something like the release capability. IIUC this would
allow our organization to create a standard way of doing something
and then somehow make it available to everyone.
Exactly.
That would be a good thing. But I don't understand how that could
work without locating it in a remote repo just as a pom is
currently located. And while it may not be required to have an
artifactId, version and groupId in the programmatic case I simply
can't think of a good reason not to require it anyway.
In this case you definitely need a coordinate to find it. The mixin
case just can support bits where there isn't a complete coordinate.
I don't know if in practice that would be useful yet. I need a
coordinate for my example.
From what you are describing it sounds like a mixin will
essentially just be a pom (hopefully with a different extension)
that uses somewhat different rules to merge with the pom
referencing it. If that indeed is what it is then I like the idea,
but the devil is in the details - as it always is around here.
Since this isn't inheritance the rules specified in the current
document probably don't completely apply to mixins. For example,
if the mixin defines a plugin and the project referencing it does
also what happens? I wouldn't necessarily expect the same behavior
as I would with the parent/child relationship.
The mixin would be contributed as if you had placed all the elements
in your POM yourself. So essentially you contribute a set of
properties to the model, and then the transformation process is run.
So we need to define what bits go where but then the spec kicks in.
The behavior probably wouldn't be exactly like parent/child because
it is a composition model. Trying out the two examples I mentioned
should be relatively easy but I don't expect I want to try that
until alpha-3 or 4. I just want to write tests for a while and do
some refactoring and stamp out regressions.
I am in complete agreement with what you are describing here.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
