Sorry, I forgot to include that you need to do either of these two:
1. Grant the repository observer role for your repo to user 'guest', OR
2. Create a user in Archiva and assign it with the repository observer role
for your repo, then set this in your settings.xml as well:
server
Thanks for the quick reply,
but maybe this is not what i want.
as far as i know, the svn repository access is configured in the scm /
section.
I want to acces a subversion source repository not a maven artifact
repository.
So i configured something like the following to access the server's
I'm getting this error unable to find project model when I browse down
to a particular module, even though the POM and metadata are there, and
I've force the database to rescan. What's going on and and how do I
need to fix it?
TIA,
Carlton
-
I have just upgraded to Archiva 1.0.1 I think (deployed as a war file on
tomcat), and wanted to confirm the upgrade had worked, but cannot find any
references to the version in the logs or on the pages.
In the logs I get the alpaca ASCII art as shown:
2008-02-06 14:36:32,742 [main] INFO
On Feb 6, 2008 7:44 AM, Ben Lidgey [EMAIL PROTECTED] wrote:
I have just upgraded to Archiva 1.0.1 I think (deployed as a war file on
tomcat), and wanted to confirm the upgrade had worked, but
cannot find any references to the version in the logs or on the pages.
In the logs I get the alpaca
