The following issue has been updated:
Updater: Dain Sundstrom (mailto:[EMAIL PROTECTED])
Date: Wed, 8 Sep 2004 8:47 PM
Changes:
description changed from 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?
to 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?
environment changed from Linux [Debian | SuSE ], Maven RC1,
Geronimo HEAD
to Linux [Debian | SuSE ], Maven RC1, Geronimo HEAD
Version changed to 1.0-M1
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/GERONIMO-234?page=history
---------------------------------------------------------------------
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
Versions:
1.0-M1
Assignee: Dain Sundstrom
Reporter: Bernd Fondermann
Created: Sat, 15 May 2004 2:34 AM
Updated: Wed, 8 Sep 2004 8:47 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
