geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rodrigo S. de Castro (JIRA)" <>
Subject [jira] Commented: (GERONIMO-234) Build fails when maven/plugins is not writable
Date Wed, 24 Nov 2004 14:01:23 GMT
     [ ]
Rodrigo S. de Castro commented on GERONIMO-234:

I checked Maven's code and it seems to have an inconsistent behaviour between the plugin:install
and plugin:install-now, since the former install plugin in the global dir and the latter in
the user dir. I submitted a bug to Maven Plugin Pluing, along with a very simple patch to
fix that, allowing Geronimo to install the plugin without problems. Let's wait and check if
the analysis is confirmed.

You may check this issue here:

> Build fails when maven/plugins is not writable
> ----------------------------------------------
>          Key: GERONIMO-234
>          URL:
>      Project: Apache Geronimo
>         Type: Improvement
>   Components: buildsystem
>     Versions: 1.0-M1
>  Environment: Linux [Debian | SuSE ], Maven RC1, Geronimo HEAD
>     Reporter: Bernd Fondermann
>     Assignee: Dain Sundstrom
>     Priority: Minor

> 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.
> 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
> 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?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message