pluginManagement is applied to plugins already found: as part of the
lifecycle, or in another build > plugins element. build > plugins
downloads and introduces the plugin and its dependencies.

For a prefix (jetty6) to be known, one of the following must be true:
a) the plugin is in one of th eplugin groups in settings.xml, which
defaults to o.a.m.plugins and o.c.mojo
b) the plugin must be introduced, either by the lifecycle or build > plugins

- Brett

On 1/11/06, Rinku <[EMAIL PROTECTED]> wrote:
>
> I think it was specified in <pluginManagement> when I looked at it this
> morning.
>
> Curious now - how we could avoid changes to settings.xml ? Brett, can
> you please explain a bit more how this (plug-in resolution) works
> without changes to settings.xml, and what is/are the situations suited
> to make changes to settings.xml?
>
> Thanks!
>
> Rahul
>
>
> Brett Porter wrote:
> > The plugin group isn't required if you have it in the POM. I am using
> > the Jetty6 plugin without the plugin repository or settings.xml
> > changes.
> >
> > Where is the plugin specified in your build? Is it in <plugins> or
> > <pluginManagement> ?
> >
> > - Brett
> >
> > On 1/11/06, Srepfler Srgjan <[EMAIL PROTECTED]> wrote:
> >
> >> Srepfler Srgjan wrote:
> >>
> >>
> >>> I've resolved the issue by adding to the settings.xml:
> >>> <settings>
> >>> <pluginGroups>
> >>>  <pluginGroup>org.mortbay.jetty</pluginGroup>
> >>> </pluginGroups>
> >>> </settings>
> >>> thanks to rinku on irc
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>>
> >>>
> >> Isn't this kind of behavior a bug?
> >> |pluginGroups| List of groupIds to search for a plugin when that plugin
> >> groupId is not explicitly provided.
> >> as I explicitly stated the groupId I see no reason why I had to specify
> >> this element, what do you guys think?
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to