[
http://jira.codehaus.org/browse/MRM-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108285
]
Joakim Erdfelt commented on MRM-501:
------------------------------------
You will notice that many components, libs, and build tools that archiva uses
require the existence of a valid ${user.home} directory.
The configuration pieces are intentionally designed to only write to the last
successfully located archiva.xml that exists on a local filesystem.
current order:
# embedded archiva.xml (found in jar files)
# $\{appserver.base}/conf/archiva.xml
# $\{user.home}/.m2/archiva.xml
One solution I see to this, is to prevent editing of the configuration if you
are running in an environment where ...
* ${user.home}/.m2/archiva.xml does not exist, or cannot exist.
* ${appserver.base}/conf/archiva.xml does not exist.
In this scenario, we would need to disable the admin screens and then tell the
admin the reason for the disabled admin screens, and to either change the
environment, or create the ${appserver.base}/conf/archiva.xml
> Saving configuration fails through the webapp.
> ----------------------------------------------
>
> Key: MRM-501
> URL: http://jira.codehaus.org/browse/MRM-501
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.0-beta-2
> Environment: JDK-1.5.0
> Geronimo-2.0.1
> PostgreSQL-8.2.4
> Reporter: Aleksandr Tarutin
> Priority: Blocker
> Fix For: 1.0-beta-3
>
>
> When modifying Proxy Connector through the web UI the following error occured:
> {code}
> Unable to save configuration: Unable to create configuration file:
> /dev/null/.m2/archiva.xml (Not a directory)
> {code}
> Geronimo runs as a user without login and with home dir set to /dev/null.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
