Yes, If the apache projects like say Axis2 and Geronimo set up their
pom's in a certain fashion (using m2's scope=provided mechanism), end
users will have to add incubator repos explicitly/consciously and
won't get podling jars pulled in w/o their knowledge.
-- dims
On 3/16/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Davanum Srinivas wrote:
> #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
Actually, both cases appear to be the same because in case #1, unless the
user is not part of collaborative effort, someone else could have added the
repository to the pom.xml for the project. Apparently, Maven doesn't
require the user to authorize each repository, and just assumes that it must
be OK if someone stuck it in a pom.xml file.
> here's what we can do to make #2 a conscious decision.
Would that imply anything about the need for a separate repository?
Remember, the motivation for it was, as you stated above, to make sure that
the end user expressed the specific intent of relying upon incubator
artifacts. That's the goal. The repository was a mechanism.
--- 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]
