Community Packages

Please read this before reporting a bug:

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#46011 - [maven] Suggested package improvements

Attached to Project: Community Packages
Opened by Johannes Ernst (jernst) - Tuesday, 18 August 2015, 20:48 GMT
Last edited by Sergej Pupykin (sergej) - Wednesday, 09 March 2016, 18:41 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


From the file list:


Should this be in /opt/maven/etc or some place like it instead? It isn't executable, and /etc/profile.d/ implies (just like the bin in the path) that opt/maven/bin could be in the $PATH.


Are those Windows scripts? Do we really need them on Arch?

[Personally, I'm not a fan of /opt, and methinks /opt/something/bin rather confuses than helps. That only some files there are symlinked from /usr/bin adds to the puzzle. But I settle for the first two items in this task.]
This task depends upon

Closed by  Sergej Pupykin (sergej)
Wednesday, 09 March 2016, 18:41 GMT
Reason for closing:  Upstream
Comment by Doug Newgard (Scimmia) - Tuesday, 18 August 2015, 21:23 GMT
I don't know about maven specifically, but /opt is usually used for programs that don't play well with others. Some of these will require a config file in the same dir as the executable (Windows style).
Comment by Sergej Pupykin (sergej) - Wednesday, 09 March 2016, 18:41 GMT
Maven expects m2.conf in bin/. You should report upstream asking FHS maven installation.