[
http://jira.codehaus.org/browse/MRM-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103735
]
Brett Porter commented on MRM-430:
----------------------------------
note on the "read" end of this behaviour, it should read both, and merge the
results, taking ~/.m2/archiva.xml as the priority. This should already be
achieved by the registry mechanism.
> Archiva always writes to ~/.m2/archiva.xml
> ------------------------------------------
>
> Key: MRM-430
> URL: http://jira.codehaus.org/browse/MRM-430
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-alpha-2
> Reporter: Wendy Smoak
> Fix For: 1.0-beta-1
>
>
> From http://maven.apache.org/archiva/guides/configuration.html :
> "When Archiva saves it's configuration, all configuration is stored to
> a single file. The file chosen is by the following rules:
> * If ~/.m2/archiva.xml exists, it is saved there
> * Otherwise, it is saved to $ARCHIVA_BASE/conf/archiva.xml,
> regardless of whether it previously existed. "
> The latest code (r553963) always writes to ~/.m2/archiva.xml, even if it did
> not exist, and completely ignores $ARCHIVA_BASE/conf/archiva.xml.
> Related thread:
> http://www.nabble.com/Archiva-now-always-writes-to-%7E-.m2-archiva.xml-t4053580.html
--
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
