Brian E. Fox wrote:
I read about the new import scope in the 2.0.9 release notes. This
looks very promising to me, but I have a questions on the details of
how this works.
I looked in the mailing list history for discussions on this feature,
but couldn't find anything. There is a wiki page, but it has few
details (and no discussion).
Ralph is hopefully putting together some guides for this before we
release 2.0.9
I will do my best but I am leaving on vacation for a week tomorrow
night. I will try to get to it tonight.
Does this mean we'll start seeing dependencies in the repository that
cannot reliably be used by older Maven versions ?
Yes that is the case if you use the new scope. It makes me wonder if
this really is appropriate to add to 2.0.x given that we can't increment
the pom version.
The design pattern I would recommend is one where the pom being imported
contains nothing but the managed dependencies, i.e. it defines a library
of related artifacts. You wouldn't use such a pom in any other way so I
don't see this as a compatibility problem.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
