You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by John Fallows <jo...@gmail.com> on 2005/06/24 17:21:12 UTC
[m2] Custom Plugins for alpha-3
I have written some custom plugins for M2 with a groupId different
from "org.apache.maven.plugins".
However, after upgrading to alpha-3, it seems as though the automatic
detection of new plugin versions is always using the
"org.apache.maven.plugins" groupId to determine the RELEASE version.
Unfortunately, this is causing a build failure, because my custom
plugins are in a different groupId, so this automatic check cannot
succeed.
Is this a known issue?
Kind Regards,
John Fallows.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Custom Plugins for alpha-3
Posted by John Fallows <jo...@gmail.com>.
> Thanks for the diagnosis. Can you put it in JIRA for us?
Done, issue MNG-527.
http://jira.codehaus.org/browse/MNG-527
Kind Regards,
John Fallows.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Custom Plugins for alpha-3
Posted by Brett Porter <br...@gmail.com>.
Thanks for the diagnosis. Can you put it in JIRA for us?
Many thanks!
Cheers,
Brett
On 6/25/05, John Fallows <jo...@gmail.com> wrote:
> Hi Brett,
>
> This looks like there is an issue with having multiple
> pluginRepositories specified in pom.xml.
>
> When determining the RELEASE version, the build fails immediately if
> the first pluginRepository does not contain the plugin at all. The
> second pluginRepository does not get a chance to service the request.
>
> If the order of pluginRepository entries is reversed, such that the
> first entry actually contains the requested plugin, then the RELEASE
> version is determined and the build succeeds.
>
> Kind Regards,
> John Fallows.
>
> On 6/24/05, Brett Porter <br...@gmail.com> wrote:
> > Hi John,
> >
> > The alpha-2 version behaved the same way in this respect. If you
> > specify your plugin in the pom it should work - can you provide a bit
> > more detail about how it is configured in the pom and whether you are
> > running it from the command line?
> >
> > You may have found a bug, but we regularly use 2 different plugins not
> > in that group to test with as well and they are working fine (see
> > modello in the m2 source tree).
> >
> > Cheers,
> > Brett
> >
> > On 6/25/05, John Fallows <jo...@gmail.com> wrote:
> > > I have written some custom plugins for M2 with a groupId different
> > > from "org.apache.maven.plugins".
> > >
> > > However, after upgrading to alpha-3, it seems as though the automatic
> > > detection of new plugin versions is always using the
> > > "org.apache.maven.plugins" groupId to determine the RELEASE version.
> > >
> > > Unfortunately, this is causing a build failure, because my custom
> > > plugins are in a different groupId, so this automatic check cannot
> > > succeed.
> > >
> > > Is this a known issue?
> > >
> > > Kind Regards,
> > > John Fallows.
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Custom Plugins for alpha-3
Posted by John Fallows <jo...@gmail.com>.
Hi Brett,
This looks like there is an issue with having multiple
pluginRepositories specified in pom.xml.
When determining the RELEASE version, the build fails immediately if
the first pluginRepository does not contain the plugin at all. The
second pluginRepository does not get a chance to service the request.
If the order of pluginRepository entries is reversed, such that the
first entry actually contains the requested plugin, then the RELEASE
version is determined and the build succeeds.
Kind Regards,
John Fallows.
On 6/24/05, Brett Porter <br...@gmail.com> wrote:
> Hi John,
>
> The alpha-2 version behaved the same way in this respect. If you
> specify your plugin in the pom it should work - can you provide a bit
> more detail about how it is configured in the pom and whether you are
> running it from the command line?
>
> You may have found a bug, but we regularly use 2 different plugins not
> in that group to test with as well and they are working fine (see
> modello in the m2 source tree).
>
> Cheers,
> Brett
>
> On 6/25/05, John Fallows <jo...@gmail.com> wrote:
> > I have written some custom plugins for M2 with a groupId different
> > from "org.apache.maven.plugins".
> >
> > However, after upgrading to alpha-3, it seems as though the automatic
> > detection of new plugin versions is always using the
> > "org.apache.maven.plugins" groupId to determine the RELEASE version.
> >
> > Unfortunately, this is causing a build failure, because my custom
> > plugins are in a different groupId, so this automatic check cannot
> > succeed.
> >
> > Is this a known issue?
> >
> > Kind Regards,
> > John Fallows.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Custom Plugins for alpha-3
Posted by Brett Porter <br...@gmail.com>.
Hi John,
The alpha-2 version behaved the same way in this respect. If you
specify your plugin in the pom it should work - can you provide a bit
more detail about how it is configured in the pom and whether you are
running it from the command line?
You may have found a bug, but we regularly use 2 different plugins not
in that group to test with as well and they are working fine (see
modello in the m2 source tree).
Cheers,
Brett
On 6/25/05, John Fallows <jo...@gmail.com> wrote:
> I have written some custom plugins for M2 with a groupId different
> from "org.apache.maven.plugins".
>
> However, after upgrading to alpha-3, it seems as though the automatic
> detection of new plugin versions is always using the
> "org.apache.maven.plugins" groupId to determine the RELEASE version.
>
> Unfortunately, this is causing a build failure, because my custom
> plugins are in a different groupId, so this automatic check cannot
> succeed.
>
> Is this a known issue?
>
> Kind Regards,
> John Fallows.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org