RE: Archiva Proxy connectors user credentials
I felt a little embarrassed since the answer was almost right in front of me. Here it is. When you create remote repository you can provide user name and password to connect to it, NOT in proxy connectors section ( where I was looking originally ) Cheers Andrei From: Daniel King [EMAIL PROTECTED] To: archiva-users@maven.apache.org Date: 04/23/2008 02:02 PM Subject: RE: Archiva Proxy connectors user credentials It always nice to *POST* answers to your question even if you answer them yourself. You never know when someone else might be trying the same thing. In this case your post is a dead rabbit hole for them. Thanks, Daniel King Vurv The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify me immediately by replying to the message and deleting it from your computer. Thank you. -Original Message- From: Andrei Vojakine [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 23, 2008 4:53 PM To: archiva-users@maven.apache.org Subject: Re: Archiva Proxy connectors user credentials Sorry folks... scratch that I found the answer Andrei From: Andrei Vojakine/CanWest/[EMAIL PROTECTED] To: archiva-users@maven.apache.org Date: 04/23/2008 01:52 PM Subject: Archiva Proxy connectors user credentials Hi all I was wondering if it is possible to provide user credentials for Archiva proxy connector. Here is the scenario. We have two Archiva installations; the primary one is secured with user names and password , that secondary one is at the remote location meant to serve as proxy to the primary one. How can I provide user name and password on the secondary one to login to the primary location? Thank you Andrei
retention policy on release repository
Hi all I was wondering if it is possible to set up retention policy on release repository? For instance lets suppose a group of developers always produces 95 versions of the product during 123 days and I want to keep only last 20 not older than 20 days. Is it possible to do it on releases? or I have to write my own external script ( or Archiva plugin ) and cron it? Thank you Andrei
Re: 1.0 to 1.0.2 webapp upgrade fails
) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Caused by: SQL Exception: Failed to start database '/opt/proxy/apache-tomcat-5.5.25/archiva/users', see the next exception for details. at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.newEmbedSQLException(Unknown Source) at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection.init(Unknown Source) at org.apache.derby.impl.jdbc.EmbedConnection30.init(Unknown Source) at org.apache.derby.jdbc.Driver30.getNewEmbedConnection(Unknown Source) at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source) at org.apache.tomcat.dbcp.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38) at org.apache.tomcat.dbcp.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:1247) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1221) ... 86 more CUT HERE -- ... 86 more it's how it was reported. Andrei From: Brett Porter [EMAIL PROTECTED] To: archiva-users@maven.apache.org Date: 04/14/2008 07:06 PM Subject: Re: 1.0 to 1.0.2 webapp upgrade fails is there a later exception that gives a better hint? Maybe they were locked and the lockfile needs to be removed? On 15/04/2008, Andrei Vojakine [EMAIL PROTECTED] wrote: Hi all I am having problems with upgrading 1.0 to 1.02. I have webapp installation on tomcat 5.5.25 it was installed as described here : http://cwiki.apache.org/confluence/display/ARCHIVA/Archiva+on+Tomcat with Derby 10.1.3.1 now I am trying to upgrade archive to 1.0.2 for the upgrade I found only this: http://www.mail-archive.com/archiva-users@maven.apache.org/msg00232.html but it doesn't work. Every time I try stating Catalina with existing Derby databases I get this error: 2008-04-14 16:32:07,484 [main] WARN net.sf.ehcache.config.ConfigurationFactory - No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: jar:file:/opt/proxy/apache-tomcat-5.5.25/webapps/archiva/WEB-INF/lib/ehcache-1.3.0.jar!/ehcache-failsafe.xml 2008-04-14 16:32:08,200 [main] ERROR JPOX.RDBMS.Schema - Failed initialising database. Please check that your database JDBC driver is accessible, and the database URL and username/password are correct. Exception : Cannot create PoolableConnectionFactory (Failed to start database '/opt/proxy/apache-tomcat-5.5.25/archiva/users', see the next exception for details.) org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Failed to start database '/opt/proxy/apache-tomcat-5.5.25/archiva/users', see the next exception for details.) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1225) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880) at org.jpox.util.FailoverUtils.getConnection(FailoverUtils.java:51) at org.jpox.store.rdbms.RDBMSManager.init(RDBMSManager.java:244) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.jpox.util.ClassUtils.newInstance(ClassUtils.java:73) etc If I remove my user and archiva databases it starts up
Re: 1.0 to 1.0.2 webapp upgrade fails
I got it thanks for the tip Brett! after you stop Catalina and replace the war file remove db.lck and dbex.lck files from your database's directories. Andrei From: Brett Porter [EMAIL PROTECTED] To: archiva-users@maven.apache.org Date: 04/14/2008 07:06 PM Subject: Re: 1.0 to 1.0.2 webapp upgrade fails is there a later exception that gives a better hint? Maybe they were locked and the lockfile needs to be removed? On 15/04/2008, Andrei Vojakine [EMAIL PROTECTED] wrote: Hi all I am having problems with upgrading 1.0 to 1.02. I have webapp installation on tomcat 5.5.25 it was installed as described here : http://cwiki.apache.org/confluence/display/ARCHIVA/Archiva+on+Tomcat with Derby 10.1.3.1 now I am trying to upgrade archive to 1.0.2 for the upgrade I found only this: http://www.mail-archive.com/archiva-users@maven.apache.org/msg00232.html but it doesn't work. Every time I try stating Catalina with existing Derby databases I get this error: 2008-04-14 16:32:07,484 [main] WARN net.sf.ehcache.config.ConfigurationFactory - No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: jar:file:/opt/proxy/apache-tomcat-5.5.25/webapps/archiva/WEB-INF/lib/ehcache-1.3.0.jar!/ehcache-failsafe.xml 2008-04-14 16:32:08,200 [main] ERROR JPOX.RDBMS.Schema - Failed initialising database. Please check that your database JDBC driver is accessible, and the database URL and username/password are correct. Exception : Cannot create PoolableConnectionFactory (Failed to start database '/opt/proxy/apache-tomcat-5.5.25/archiva/users', see the next exception for details.) org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Failed to start database '/opt/proxy/apache-tomcat-5.5.25/archiva/users', see the next exception for details.) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1225) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880) at org.jpox.util.FailoverUtils.getConnection(FailoverUtils.java:51) at org.jpox.store.rdbms.RDBMSManager.init(RDBMSManager.java:244) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.jpox.util.ClassUtils.newInstance(ClassUtils.java:73) etc If I remove my user and archiva databases it starts up , but offcourse I have no users and no indexes. I am stuck. How can I upgrade existing Archiva 1.0 webapp installation with Derby as a database w/o starting user database from scratch? Thank you Andrei -- Brett Porter Blog: http://blogs.exist.com/bporter/
1.0 to 1.0.2 webapp upgrade fails
Hi all I am having problems with upgrading 1.0 to 1.02. I have webapp installation on tomcat 5.5.25 it was installed as described here : http://cwiki.apache.org/confluence/display/ARCHIVA/Archiva+on+Tomcat with Derby 10.1.3.1 now I am trying to upgrade archive to 1.0.2 for the upgrade I found only this: http://www.mail-archive.com/archiva-users@maven.apache.org/msg00232.html but it doesn't work. Every time I try stating Catalina with existing Derby databases I get this error: 2008-04-14 16:32:07,484 [main] WARN net.sf.ehcache.config.ConfigurationFactory - No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: jar:file:/opt/proxy/apache-tomcat-5.5.25/webapps/archiva/WEB-INF/lib/ehcache-1.3.0.jar!/ehcache-failsafe.xml 2008-04-14 16:32:08,200 [main] ERROR JPOX.RDBMS.Schema - Failed initialising database. Please check that your database JDBC driver is accessible, and the database URL and username/password are correct. Exception : Cannot create PoolableConnectionFactory (Failed to start database '/opt/proxy/apache-tomcat-5.5.25/archiva/users', see the next exception for details.) org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Failed to start database '/opt/proxy/apache-tomcat-5.5.25/archiva/users', see the next exception for details.) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1225) at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880) at org.jpox.util.FailoverUtils.getConnection(FailoverUtils.java:51) at org.jpox.store.rdbms.RDBMSManager.init(RDBMSManager.java:244) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.jpox.util.ClassUtils.newInstance(ClassUtils.java:73) etc If I remove my user and archiva databases it starts up , but offcourse I have no users and no indexes. I am stuck. How can I upgrade existing Archiva 1.0 webapp installation with Derby as a database w/o starting user database from scratch? Thank you Andrei
