On 23/10/2007, at 11:09 AM, Joakim Erdfelt wrote:
I use -Dappserver.base=/path/to/other-install, but only when I
need to test the other data. Do you need to test a large
repository every time you test the webapp?
This doesn't work.
It loads both files resulting in a "Configuration can not be saved
when it is loaded from two sources" error when loaded this way ...
[archiva-webapp]$ mvn -Dappserver.base=$HOME/java/archiva clean
jetty:run
The $HOME/java/archiva directory has a conf, log, and repos,
subdirectory.
The $HOME/java/archiva/conf/archiva.xml file contains my desired
configuration.
This is when you have ~/.m2/archiva.xml that contains repositories
too, since the current logic is to merge them.
I would document that (unless you know what you are doing), it would
be better to use one or the other. It's not realistic for that to be
~/.m2/archiva.xml in a development environment since there can be
only one. I suggest this is the best way to address it right now -
through documentation.
You can also see my extensive comments in
DefaultArchivaConfiguration's javadoc (I think they still apply,
though I'm not sure since you made a lot of changes in there - it
appears since the tests still hold they would).
Cheers,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
