Jason, maven-proxy has not be actively developed for approximately 18 months now (at least JIRA has not been touched since then). There does not appear to be a way to start maven-proxy as a windows service. It has a webapp version (so you could run tomcat/jetty as a service) but it does not support configuration?!?!
I would be a little hesitant to use maven-proxy due to these issues. mike -----Original Message----- From: Jason Dillon [mailto:[EMAIL PROTECTED] Sent: Friday, September 23, 2005 1:29 PM To: Maven Users List Subject: RE: How are SNAPSHOT dependency downloads handled? The default config props are documented quite well. http://maven-proxy.codehaus.org Should be trivial to get the standalone version up and configured ;-) Then just use it as your single maven.repo.remote. Cheers, --jason > -----Original Message----- > From: KC Baltz [mailto:[EMAIL PROTECTED] > Sent: Friday, September 23, 2005 11:22 AM > To: Maven Users List > Subject: RE: How are SNAPSHOT dependency downloads handled? > > I'll look into that. Is there a good pointer to documentation or a sample > config you can get me started with? > > K.C. > > -----Original Message----- > From: Jason Dillon [mailto:[EMAIL PROTECTED] > Sent: Friday, September 23, 2005 11:18 AM > To: Maven Users List > Subject: RE: How are SNAPSHOT dependency downloads handled? > > > The first repository might not have the latest snapshot... though in > your case it probably would. But in general all repos have to be > searched for the latest. > > I would personally recommend setting up Maven-Proxy to handle your local > repository needs as well as for your remote repositories. As if you use > SNAPSHOT internally this will speed things up dramatically since only > one repo needs to be checked from the client's perspective, and the > proxy will cache failures from remote repos so it doesn't keep checking > each remote for an artifact that does not exist. > > --jason > > > > -----Original Message----- > > From: KC Baltz [mailto:[EMAIL PROTECTED] > > Sent: Friday, September 23, 2005 11:11 AM > > To: Maven Users List (E-mail) > > Subject: How are SNAPSHOT dependency downloads handled? > > > > [Using Maven 1.1-beta-2] > > I'm trying to use SNAPSHOT to get the latest version of an internally > > developed JAR from our in-house remote repository . It appears to > work > > (I.e. I do end up with the latest version), but not without dumping a > > number of errors to the screen about how it can't find my jar at > maven- > > plugins.sourceforge.net. I have the following in my personal > > build.properties: > > > > > maven.repo.remote=file:///export/home/kcbaltz/testRepo,http://www.ibibli > o. > > > org/maven/,http://maven-plugins.sf.net/maven,http://www.codeczar.com/mav > en > > > > I would assume that if it found the SNAPSHOT in the testRepo > repository, > > it wouldn't search the rest. Is that a correct assumption? The error > > messages are below: > > > > > > > > Attempting to download copart-core-1.0-SNAPSHOT.jar. > > Error getting URI host > > org.apache.commons.httpclient.HttpException: Redirect from host maven- > > plugins.sf.net to maven-plugins.sourceforge.net is not supported > > at > > > org.apache.commons.httpclient.HttpMethodBase.checkValidRedirect(HttpMeth > od > > Base.java:1237) > > at > > > org.apache.commons.httpclient.HttpMethodBase.processRedirectResponse(Htt > pM > > ethodBase.java:1185) > > at > > > org.apache.commons.httpclient.HttpMethodBase.isRetryNeeded(HttpMethodBas > e. > > java:967) > > at > > > org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java > :1 > > 089) > > at > > > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:6 > 43 > > ) > > at > > > org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:4 > 97 > > ) > > at > > > org.apache.maven.wagon.providers.http.HttpWagon.get(HttpWagon.java:287) > > at > > > org.apache.maven.wagon.providers.http.HttpWagon.getIfNewer(HttpWagon.jav > a: > > 234) > > at > > > org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact(Depend > en > > cyVerifier.java:391) > > at > > > org.apache.maven.verifier.DependencyVerifier.getDependencies(DependencyV > er > > ifier.java:291) > > at > > > org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(Depende > nc > > yVerifier.java:182) > > at > > > org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.j > av > > a:99) > > at > > org.apache.maven.project.Project.verifyDependencies(Project.java:569) > > at > > > org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:663 > ) > > at > > org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) > > at org.apache.maven.cli.App.doMain(App.java:511) > > at org.apache.maven.cli.App.main(App.java:1258) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav > a: > > 39) > > at > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > Im > > pl.java:25) > > at java.lang.reflect.Method.invoke(Method.java:585) > > at com.werken.forehead.Forehead.run(Forehead.java:551) > > at com.werken.forehead.Forehead.main(Forehead.java:581) > > Invalid Redirect URI from: http://maven- > > plugins.sf.net:80/maven//copart/jars/copart-core-1.0-SNAPSHOT.jar to: > > > http://maven-plugins.sourceforge.net/maven//copart/jars/copart-core-1.0- > > SNAPSHOT.jar > > Error retrieving artifact from [http://maven-plugins.sf.net/maven]: > > org.apache.maven.wagon.TransferFailedException: Failed to trasfer > file: > > http://maven-plugins.sf.net/maven//copart/jars/copart-core-1.0- > > SNAPSHOT.jar. Return code is: 302 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
