John Casey wrote:
I'm not sure what decisions led to that approach over, say, creating a
trunk per plugin (ugly, I know)...but I'd think what's good for one
would work for all. It would also help to maintain consistency here,
IMO. So, I guess that leads me to say let's use one set of
trunk/tags/branches for all of this new shared space.
Probably ease of checkout when there is a parent element. There's no
harm in having a series of tags that are all different, though that
means they themselves don't match the layout. But in their case its ok,
I think the same holds here. +1 to one trunk.
| - how does this impact the bootstrap?
This will have the same impact on the bootstrap as any other project
that the core plugins depend on, but which isn't included in the core
distribution.
This is different to the plugins - it builds without them by downloading
the latest version, but you require specific versions of these libraries
that may not be in the remote repo (though you should only encounter
them when building the plugins, so...)
I think its ok, we might just need to do a bit more work here.
If you mean we shouldn't move maven-artifact into the shared space, I
agree 100%. :-) Did you have specific concerns about some of the other
projects that aren't quite so integral to Maven?
I was thinking of maven-archiver given it might require a newer version
of maven-project that ties it to that newer maven release, but thinking
about it, separating helps to separate chnages that require core updates
and changes that don't, so I don't think anything falls in this category
just now.
|
| Keeping them truely separate is probably the best alternative here. If
| maven-archiver is separate then it can get new versions and stick to 2.0
| which controls what the prerequisite release of maven the plugins have.
Yes, just as the plugins' specification of prerequisite maven version is
going to become crucial (if it's not already), the shared projects will
also have to depend on this feature. It will allow them to grow faster
than the main Maven distribution.
You can't use the maven requirement to sto pa dependency being used like
a plugin is, though - it would stop you building with that version of
Maven. I know that's a bit inconsistent. We should probably make the
plugins decide their minimum Maven version based on the lowest bounds of
all included maven-* libraries that are in the lib directory...
Anyway, its important that we don't use newer versions until its needed.
And let the version mediation sort it out.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
