Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#27252 - [maven] Do not set M2_HOME
Attached to Project:
Community Packages
Opened by Julien Nicoulaud (nicoulaj) - Friday, 25 November 2011, 17:40 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 01 December 2011, 13:47 GMT
Opened by Julien Nicoulaud (nicoulaj) - Friday, 25 November 2011, 17:40 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 01 December 2011, 13:47 GMT
|
DetailsDescription:
The package installs a script at /etc/profile.d/maven.sh that exports the M2_HOME environment variable. This variable is not needed for Maven to work properly and causes the package to conflict with other standalone installations/AUR packages of Maven 2. Additional info: * package version: 3.0.3 Steps to reproduce: Download and extract a Maven 2 tar.gz, execute bin/mvn, and a Java stack trace appears, because it tries to use M2_HOME from the environment. |
This task depends upon