Noel,
There are 2 ways here
#1) End user using an Incubator podling m2 artifact directly: End
users need to specify our repo in their pom.xml explicity. this is a
conscious decision.
#2) End user using a regular Apache project that depends on incubator
podling artifact: End users won't have to touch their pom.xml and the
podling jars are automatically downloaded. So we lose the benefit
here.
*BUT* here's what we can do to make #2 a conscious decision. Say
Axis2...we depend on woden. If we mark woden jar with scope=provided
[1], then the end user has to do a conscious import just like they did
in #1. So there is a way to enforce the policy if we wish.
thanks,
dims
[1]
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
On 3/15/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Daniel Kulp wrote:
> Noel J. Bergman wrote:
> > As I understand it, so please correct me if I am wrong, if I download
> > a program that builds using Maven, and it has dependencies in its
> > pom.xml on Incubator artifiacts, then if Incubator artifacts are
> > conflated with ASF artifacts, then when I built the program, it will
> > automatically download the Incubator artifacts from the repository
> > without my being aware of the dependency. However, if the Incubator
> > artifacts are segregated into a separate repository, then Maven will
> > not download them until I, the downstream user, add that repository to
> > Maven. Is that correct or incorrect?
> If my project directly depends on incubator artifacts, I would need to
> put the incubator repository in my pom. However, if I depend on
> another project that depends on incubator artifacts, I wouldn't because
> most likely, their poms have a repository entry for the incubator.
Ah, so the goal of requiring users to make the deliberate and explicit
decision to use Incubator artifacts is not satisfied because Maven requires
users to inspect every POM for every dependent in the entire chain.
> anything from the incubator that it needs will automatically be grabbed
> without me knowing about it.
If that is true, and we cannot fix Maven, then I agree with great
disappointment (and hardly the first time regarding Maven) there is little
point to a separate repository. We're not getting the desired benefit.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
