plugins not unpacking in my local repository

[Da...@wellsfargo.com]

I created a local plugin that sets up our developer's local environment
(sets build.properties files and creates the maven.local.repo directory in a
standard location) in order to get developers working under maven in a quick
and easy fashion.  I successfully installed and deployed it using
plugin:install and plugin:deploy respectively.  The plugin works similar to
the genapp plugin in that it copies a standard build.properties file located
in the plugin to the user's home directory.  All this works as expected.
The next test was to remove my build.properties file and the
maven.local.repo directory to simulate a complete new install of maven with
the addition of my plugin.  Unfortunately, when I invoke my goal that
initializes my environment, the build fails when it tries to copy the
plugin's copy of the build.properties file to my home directory because the
directory this file resides does not exist.  i.e. maven did not
automatically unpack the plugin in the ${maven.local.repo}/plugins
directory.  This might be a bug, I don't know.  Is there a way to force
maven to unpack the plugin  or is it the ultimate responsibility of the
plugin to unpack itself?  Any help would be appreciated.

Thanks,

- Dan


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: plugins not unpacking in my local repository

[Ben Walding <be...@walding.com>]

Have a look at http://wiki.codehaus.org/maven/MigratingFromBeta9ToBeta10

Consider the use of the return key to break up your emails, as that is 
just a crime against paragraphs! :P

Are you using b10?


Daniel.B.Brown@wellsfargo.com wrote:

>I created a local plugin that sets up our developer's local environment
>(sets build.properties files and creates the maven.local.repo directory in a
>standard location) in order to get developers working under maven in a quick
>and easy fashion.  I successfully installed and deployed it using
>plugin:install and plugin:deploy respectively.  The plugin works similar to
>the genapp plugin in that it copies a standard build.properties file located
>in the plugin to the user's home directory.  All this works as expected.
>The next test was to remove my build.properties file and the
>maven.local.repo directory to simulate a complete new install of maven with
>the addition of my plugin.  Unfortunately, when I invoke my goal that
>initializes my environment, the build fails when it tries to copy the
>plugin's copy of the build.properties file to my home directory because the
>directory this file resides does not exist.  i.e. maven did not
>automatically unpack the plugin in the ${maven.local.repo}/plugins
>directory.  This might be a bug, I don't know.  Is there a way to force
>maven to unpack the plugin  or is it the ultimate responsibility of the
>plugin to unpack itself?  Any help would be appreciated.
>
>Thanks,
>
>- Dan
>
>
>---------------------------------------------------------------------
>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