maven-2.0-RC
Hi,
I've created a m2 plugin and deployed it as a SNAPSHOT to an internal
(distinct from my local) repository.
When building projects that use this plugin, the plugin resolves and
works as expected when it is already in my local repository.
If I clean out my local repository (the p
As you can see from the trace, it is not attempting to use your
internal repository. You need to add a element.
-Brett
On 10/18/05, andrew <[EMAIL PROTECTED]> wrote:
> maven-2.0-RC
>
> Hi,
>
> I've created a m2 plugin and deployed it as a SNAPSHOT to an internal
> (distinct from my local) repos
Brett Porter wrote:
> As you can see from the trace, it is not attempting to use your
> internal repository.
Yes, hence my question.
> You need to add a element.
I'm a bit confused here.
According to the pom.xml and settings.xml descriptors there is no
element.
There is a element that con
For anyone like me who takes their time getting to the DTD (or just
misses the blindingly obvious :) I managed to get my plugins resolving
correctly [1].
Is there any reason why m2 couldn't default to checking your 'normal'
repositories for plugins if no pluginRepositories are defined?
Thanks,
..
Yes, we should really decouple this in some way.
ie, there are a list of repositories, and then artifacts declare which
they want to use by key.
- Brett
On 10/20/05, andrew <[EMAIL PROTECTED]> wrote:
> For anyone like me who takes their time getting to the DTD (or just
> misses the blindingly ob
