Tom Huybrechts 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, b
>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.
But any poms that are consu
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 i
>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
>detai
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
