[jira] Commented: (GERONIMO-234) Build fails when maven/plugins is not writable

[de...@geronimo.apache.org]

The following comment has been added to this issue:

     Author: Dain Sundstrom
    Created: Wed, 8 Sep 2004 12:52 PM
       Body:
This can not be fixed until maven allows plugins to be installed on a per user basis.  Right not maven assumes each user has a private install of maven.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/GERONIMO-234?page=comments#action_52984

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-234

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: GERONIMO-234
    Summary: Build fails when maven/plugins is not writable
       Type: Improvement

     Status: Open
   Priority: Minor

    Project: Apache Geronimo
 Components: 
             buildsystem

   Assignee: Dain Sundstrom
   Reporter: Bernd Fondermann

    Created: Sat, 15 May 2004 2:34 AM
    Updated: Wed, 8 Sep 2004 12:52 PM
Environment: Linux [Debian | SuSE ], Maven RC1, Geronimo HEAD


Description:
When building by invoking 'maven' the build fails with the following error message when the maven plugin directory is not writable:

+----------------------------------------
| Executing (default): Geronimo :: Deployment
| Memory: 34M/43M
+----------------------------------------
Attempting to download geronimo-xmlbeans-plugin-1.0-SNAPSHOT.jar.
Attempting to download geronimo-kernel-1.0-SNAPSHOT.jar.
Attempting to download geronimo-common-1.0-SNAPSHOT.jar.
Attempting to download geronimo-system-1.0-SNAPSHOT.jar.

BUILD FAILED
File...... file:/home/username/apache/incubator-geronimo/
Element... maven:reactor
Line...... 180
Column.... 27
/usr/local/maven-1.0-rc1/plugins/geronimo-xmlbeans-plugin-1.0-SNAPSHOT.jar (Permission denied)

The immediate fix is to make plugins folder writable.

I don't like any project modifying their sibbling projects... couldn't this also lead to unexpected results in a multi-user environment where maven is shared among users?




---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira