I think that's actually the problem. When I execute 'mvn
help:active-profiles' this is the output:
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'help'.
[INFO]
----------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO] task-segment: [help:active-profiles] (aggregator-style)
[INFO]
----------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Cannot execute mojo: active-profiles. It requires a project with an
existing pom.xml, but the build is not using one.
[INFO]
------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO]
------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Wed Oct 10 16:03:55 CEST 2007
[INFO] Final Memory: 2M/6M
[INFO]
------------------------------------------------------------------------
This indicates that, when you don't have a POM, your profile isn't loaded.
So in my case it won't find my 'pluginRepository', because it is specified
in my profile.
It looks to me that it is then impossible to execute a goal from a custom
plugin, which is not in the central repository, without having a POM. This
seems a bit odd to me. I really need this feature to perform a 'checkout' on
my SCM (CA Harvest) using my maven plugin without a POM.
Regards,
Duncan Doyle
On 10/10/07, Tim Kettler <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> From your description I would guess that your profile simply is not
> activated. Run 'mvn help:active-profiles' to ensure your profile is
> active.
>
> -Tim
>
> Duncan Doyle schrieb:
> > Hello,
> >
> > I've created a custom Maven2 plugin for our SCM system (CA Harvest).
> This
> > plugin is deployed in our internal remote repository. This remote
> repository
> > is configured as a pluginRepository in my 'settings.xml ' file. The
> plugin's
> > groupId ('org.test.tools.maven.harvest') has been specified in the
> > <pluginGroups> section in my 'settings.xml' file.
> >
> > The plugin's 'checkout' goal needs to be executed from the commandline
> > without a POM (because the project's POM is in the SCM system). When I
> > execute the command 'mvn harvest:checkout' I get the following output:
> >
> > [INFO] Scanning for projects...
> > [INFO] Searching repository for plugin with prefix: 'harvest'.
> > [INFO] org.test.tools.maven.harvest: checking for updates from central
> > Returning NULL
> > [INFO] org.apache.maven.plugins : checking for updates from central
> > [INFO] org.codehaus.mojo: checking for updates from central
> > [INFO] artifact org.apache.maven.plugins:maven-harvest-plugin: checking
> for
> > updates from central
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] The plugin 'org.apache.maven.plugins:maven-harvest-plugin' does
> not
> > exist or no valid version could be found
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] For more information, run Maven with the -e switch
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 1 second
> > [INFO] Finished at: Wed Oct 10 15:27:54 CEST 2007
> > [INFO] Final Memory: 3M/6M
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > It looks to me that only the 'central' repository is scanned for the
> plugin,
> > although I have correctly specified my internal remote repository in the
> > <profile> section of my ' settings.xml' file. Furthermore, when I
> specify my
> > internal remote repository as a mirrorOf 'central' the plugin is found.
> So,
> > why doesn't maven scan my internal remote repository for the needed
> plugin
> > when the repository is specified in as a pluginRepository in my '
> > settings.xml' file?
> >
> > The plugin can be used when it is specified in the build section of a
> POM
> > (which is done to be able to run the harvest:update goal on a project to
> > update the sources from the SCM), which to me indicates that my
> > configuration is correct. It just doesn't look for the plugin when the
> maven
> > command is issued without a POM.
> >
> > With kind regards,
> >
> > Duncan Doyle
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
