archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <>
Subject Re: Archiva now always writes to ~/.m2/archiva.xml
Date Tue, 10 Jul 2007 13:37:03 GMT
Yeah, I had the same problem today trying to install it.

We need some integration tests on this functionality.

- Brett

On 10/07/2007, at 1:18 PM, Wendy Smoak wrote:

> From :
> "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.
> Did something change?  I'm fairly sure I used to be able to customize
> Archiva with conf/archiva.xml and keep everything out of my home
> directory.
> It's a bigger problem in a customized install of Archiva that has a
> different list of config files.  In that situation, it picks up the
> contents of the alternate config file, but always writes changes made
> through the web UI to ~/.m2/archiva.xml.  When you re-start Archiva,
> your changes are "lost" because they were not written to the correct
> file.
> I think it needs to work as described, and write to the conf directory
> in the absence of a ~/.m2/archiva.xml file.
> -- 
> Wendy

View raw message