Brett Thanks for all the replies I finally got it working using the standalone approach and separating out the install from the data, although the instructions on the web site are incomplete and in some places inaccurate for windows installs not sure about unix/linux that's my next task. The main issue is that the wrapper.conf file in the \bin\windows-x86-32 directory also needs editing, below are the changes I had to make.
#PG Changed this as it originally had set.default.PLEXUS_BASE=%PLEXUS_HOME% which means it ignores user set split install set.default.PLEXUS_BASE=%PLEXUS_BASE% # Java Additional Parameters #PG changes this from %PLEXUS_HOME% to %PLEXUS_BASE% as instructions say move all of the conf directory which is defined %PLEXUS_BASE% wrapper.java.additional.1=-Dclassworlds.conf="%PLEXUS_BASE%/conf/classworlds.conf" I think the other problems I was having were a few small typo's and database config issues as well as 2 small children and no sleep. Cheers Paul Brett Porter wrote: > > The id's on your managed repositories use '-', while your URLs use '_'. > > Do your archiva log files highlight the issue? > > Cheers, > Brett > > On 31/03/2008, Paul G <[EMAIL PROTECTED]> wrote: >> >> I have now deployed to tomcat 6 and still the same problem unable to >> deploy >> to Archiva. I have created a user called deployer and it has repository >> manager for the approriate repositories. >> Attached is the error aoutput from the Maven console and this is what I >> have >> in my files can anyone see the error? >> http://www.nabble.com/file/p16396030/mavenConsoleError.txt >> mavenConsoleError.txt >> >> Pom.xml >> <distributionManagement> >> <repository> >> <id>release</id> >> <name>Internal Release Repository</name> >> <url> >> >> dav:http://localhost:8080/archiva/repository/team_release >> </url> >> </repository> >> <snapshotRepository> >> <id>snapshot</id> >> <name>Internal Snapshot Repository</name> >> <url> >> >> dav:http://localhost:8080/archiva/repository/team_snapshot >> </url> >> </snapshotRepository> >> </distributionManagement> >> >> Settings.xml >> <servers> >> <server> >> <id>release</id> >> <username>deployer</username> >> <password>password1234</password> >> </server> >> <server> >> <id>snapshot</id> >> <username>deployer</username> >> <password>password1234</password> >> </server> >> </servers> >> >> Archiva.xml >> <managedRepository> >> >> >> <location>C:\DevTools\Archiva_Base\data\repositories\team_release</location> >> <id>team-release</id> >> <name>Innovation Engineering release repository</name> >> </managedRepository> >> <managedRepository> >> >> >> <location>C:\DevTools\Archiva_Base\data\repositories\team_snapshot</location> >> <releases>false</releases> >> <snapshots>true</snapshots> >> <deleteReleasedSnapshots>true</deleteReleasedSnapshots> >> <id>team-snapshot</id> >> <name>Innovation Engineering snapshot repository</name> >> </managedRepository> >> >> >> >> -- >> View this message in context: >> http://www.nabble.com/Deploying-Artifact-with-Dav-problem-Part2-tp16396030p16396030.html >> Sent from the archiva-users mailing list archive at Nabble.com. >> >> > > > -- > Brett Porter > Blog: http://blogs.exist.com/bporter/ > > -- View this message in context: http://www.nabble.com/Deploying-Artifact-with-Dav-problem-Part2-tp16396030p16445074.html Sent from the archiva-users mailing list archive at Nabble.com.
