RE: Why are plugin deps always copied to $MAVEN_HOME/plugins?

2004-01-26 Thread Brett Porter
There's an issue in JIRA for resolving all this. As it stands, to install or
use plugin dependencies, you need write permission to the plugins directory.
At work we use a specific group just for this directory. If this isn't
satisfactory, I'd suggest individual installs. We are going that way anyway,
having each user run maven on their PC rather than the remote server.

- Brett

> -Original Message-
> From: __matthewHawthorne [mailto:[EMAIL PROTECTED] 
> Sent: Friday, 23 January 2004 10:19 AM
> To: Maven Users List
> Subject: Why are plugin deps always copied to $MAVEN_HOME/plugins?
> 
> 
> If a dependency has plugin, it seems that it is always 
> copied to $MAVEN_HOME/plugins -- even if the plugin is already there.
> 
> Why is this?
> 
> This caused me some problems when running on a machine in 
> which I didn't 
> have write permissions to $MAVEN_HOME/plugins.  I sudo'd and 
> installed 
> the plugin manually, but then still received an IOException because I 
> couldn't write to the plugin's jar file.
> 
> Are there any workarounds for this?  If not, I'd consider 
> this a bug -- 
> do others agree?
> 
> Thanks!
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


Why are plugin deps always copied to $MAVEN_HOME/plugins?

2004-01-23 Thread __matthewHawthorne
If a dependency has plugin, it seems that it is always 
copied to $MAVEN_HOME/plugins -- even if the plugin is already there.

Why is this?

This caused me some problems when running on a machine in which I didn't 
have write permissions to $MAVEN_HOME/plugins.  I sudo'd and installed 
the plugin manually, but then still received an IOException because I 
couldn't write to the plugin's jar file.

Are there any workarounds for this?  If not, I'd consider this a bug -- 
do others agree?

Thanks!

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