We currently support only Maven 2 clients. Technically, it should not be too difficult to add Maven 1, but we never needed it since none of the organizations we used Artifactory with was using Maven 1 for managing enterprise builds. As for support for relocation, I would assume this logic is embedded into the Maven client itself, so there should be no problem here
nicolas de loof-2 wrote: > > Just a simple question about artifactory features : > Does it support BOTH maven1 style and maven2 style for artifact requests ? > > For example, if my repo has javax/servlet/servlet-api/2.3/servlet- > api-2.3.jar and I ask for > "/javax.servlet/jars/servlet-api-2.3.jar", do I get the expected jar ? > > If answer is "yes", will artifactiry handle maven2 meta-data for > relocation > ? If I request > "servletapi/jars/servletapi-2.3.jar" will it read the servletapi-2.3.pom > and > use <relocation> infos to return the relocated servlet-api-2.3.jar ? > > thanks. > > > 2007/3/6, Frederic Simon <[EMAIL PROTECTED]>: >> >> You just got into a maven extensions issue. >> Maven extensions needs to be in the maven local repository so they will >> be >> activated, not in the lib dir. >> >> I also did a mistake in my command it is -Dpackaging=jar not -Dtype=... >> >> The dav wagon is on repo1.maven.org. If you cannot access it deploy the >> jar >> (and check the embeded pom deployed should have dependencies) with >> artifactory web interface. >> If pom deployment fails, deploy the pom by itself. >> >> Then you can use artifactory as repository and maven should download and >> activate web-dav. If Artifactory is behind Apache (with mod_jk), you may >> get >> dav protocol errors. >> >> Good luck. >> >> On 3/6/07, Reinhard Nägele <[EMAIL PROTECTED]> wrote: >> > >> > Thanks for the quick reply. >> > >> > I still can't get web dav to work. I did exactly what you suggested. >> > Additionally I copied wagon-webdav-1.0-beta-2.jar and its dependencies >> to >> > maven's lib folder. >> > >> > ----------------------------------------------------- >> > [INFO] >> > >> ------------------------------------------------------------------------ >> > [ERROR] BUILD ERROR >> > [INFO] >> > >> ------------------------------------------------------------------------ >> > [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot >> find >> > wagon which supports the requested protocol: dav >> > >> > org/apache/commons/httpclient/URIException >> > >> > >> > Anything else I need to do? I am using Maven 2.0.5. >> > >> > However, I now managed to use HTTP upload: >> > >> > <distributionManagement> >> > <repository> >> > <id>artifactory-server</id> >> > <url>http://localhost:8080/artifactory/[EMAIL PROTECTED]</url> >> > </repository> >> > </distributionManagement> >> > >> > Still, I would love to be able to use web dav as well. Which way would >> be >> > better? What's the preferred/most reliable way to deploy to an >> Artifactory >> > repository? >> > >> > Thanks, >> > Reinhard >> > >> > >> > -----Original Message----- >> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On >> Behalf >> > Of Frederic Simon >> > Sent: Dienstag, 6. März 2007 15:01 >> > To: Maven Users List >> > Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository >> > >> > Hi, >> > Thanks for the comments, I will try to fix the doc, please review >> > http://www.jfrog.org/sites/artifactory/latest/install.html where we >> talk >> > about first admin user and system properties. >> > >> > For deploying you first local repository, we use the import from local >> > disk feature. You need to create a clean maven repo tree with the >> standard >> > groupId/artifactId/version/files on a disk accessible by Artifactory >> and >> > then go to the import page and set the root folder of the above tree. >> > >> > For web dav, me I'm using a dummy pom.xml that looks like: >> > <?xml version="1.0"?> >> > <project xmlns="http://maven.apache.org/POM/4.0.0"; >> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >> > http://maven.apache.org/maven-v4_0_0.xsd";> >> > <modelVersion>4.0.0</modelVersion> >> > <groupId>org.artifactory.deploy-test</groupId> >> > <artifactId>aye</artifactId> >> > <version>1.0-SNAPSHOT</version> >> > <packaging>jar</packaging> >> > >> > <distributionManagement> >> > <repository> >> > <id>artifactory-server</id> >> > <url>dav:http://localhost:8080/artifactory/[EMAIL PROTECTED] >> > </url> >> > </repository> >> > </distributionManagement> >> > >> > <build> >> > <extensions> >> > <extension> >> > <groupId>org.apache.maven.wagon</groupId> >> > <artifactId>wagon-webdav</artifactId> >> > <version>1.0-beta-2</version> >> > </extension> >> > </extensions> >> > </build> >> > </project> >> > >> > and from where this pom sits you can run: >> > mvn deploy:deploy-file -DrepositoryId=artifactoryServer >> > -Durl=dav:http://... >> > -Dfile=.. -DgroupId=... -DartifactId=... -Dversion=... -Dtype=... >> > -Dclassifier=... >> > >> > Hope it helps. >> > >> > On 3/6/07, Reinhard Nägele < [EMAIL PROTECTED]> wrote: >> > > >> > > >> > > This looks quite interesting, and I started to play around with it. >> > > The biggest problem is the poor documentation. With Jetty, you can >> > > quickly start it out of the box. Accessing the Web interface, you are >> > > then stuck with the login screen because the default credentials are >> > > not documented anywhere. I had to connect to the embedded Derby >> database >> > to find them out. >> > > >> > > I then moved on and tried to set it up on Tomcat. After fiddling yet >> > > for another while, I discovered it needs a system property to be >> > > present. I don't like that. Anyways, it seems to be running fine now. >> > > >> > > The next step where I need help is in deploying to a local >> repository. >> > > I tried both HTTP and DAV without success. Using HTTP, the artifact >> > > was uploaded and then yielded an HTTP 500 error, DAV didn't work >> > > because the wagon was not found, even though I installed it and >> > > followed all the tips I found for using WebDAV with Maven. >> > > >> > > I am stuck now and would appreciate further help. I'd like to repeat >> > > that the product does look promising. Chances are good that we may >> > > replace Maven Proxy with it once we get these problems sorted. And >> > > please enhance the docs! >> > > >> > > Thanks, >> > > Reinhard >> > > >> > > >> > > -----Original Message----- >> > > From: Yoav Landman [mailto:[EMAIL PROTECTED] >> > > Sent: Montag, 5. März 2007 07:14 >> > > To: users@maven.apache.org >> > > Subject: Re: [m2] [ANN] Artifactory - new Maven 2 proxy repository >> > > >> > > >> > > Well, Artifactory actually started out as a series as patches on >> > > m2proxy and ended in a complete rewrite of it. The extras that we did >> > > came from real world requirements. >> > > The old m2proxy might still answer your every need in your >> development >> > > environment, and that's fine. Artifactory is used today by a couple >> of >> > > very large distributed development environments and that's where it >> > > really makes a difference. It offers everything that m2proxy used to >> > > offer + enterprise features such as: >> > > - Ability to deploy a mesh of proxies, each site proxying another. >> > > - Enhanced security for controlling who can deploy/undeploy to where. >> > > - Multiple local repositories support with control on what can be >> > > deployed to each repo, either by include/exclude patterns or by >> > snapshot/releases. >> > > - Optional authenticated download of artifacts from local >> repositories >> > > - Web based deployment, including extraction a pom embedded in a >> > > deployed jar for a single transaction deployment of both jar and its >> > pom. >> > > - HTTP(s) or WebDav deployment >> > > - Advanced indexing >> > > - Much improved web UI >> > > There's a more detailed feature description at: >> > > http://www.jfrog.org/sites/artifactory/latest/introduction.html >> > > >> > > Yoav >> > > >> > > >> > > Kalle Korhonen-2 wrote: >> > > > >> > > > Interesting. To this date, there's at least maven-proxy ( >> > > > http://maven-proxy.codehaus.org/ ), Proximity ( >> > > > http://proximity.abstracthorizon.org/), Archiva ( >> > > > http://maven.apache.org/archiva/ ) and now, Artifactory, for more >> of >> > > > less the same purpose. They are all Apache2 type licensed. We still >> > > > use maven-proxy, and while it's only at version 0.2 and its >> > > > development has stopped, we haven't seen any issues with it. Are >> any >> > > > of these based on other's codebase or separate efforts and does >> > > > anybody have any idea what the practical differences between all >> > > > these are to the end user? >> > > > >> > > > Kalle >> > > > >> > > > On 3/4/07, Yoav Landman <[EMAIL PROTECTED]> wrote: >> > > >> >> > > >> >> > > >> Hi all, >> > > >> >> > > >> We would like to announce the immediate availability of >> > > >> Artifactory, a Maven >> > > >> 2 enterprise proxy. >> > > >> >> > > >> Artifactory offers advanced proxying, caching and security >> > > >> facilities to answer the needs of a robust, reproducible and >> > > >> independent build environment using Maven 2. >> > > >> It uses a JSR-170 Java Content Repository (JCR) for storage, which >> > > >> makes it extremely easy to manage searchable metadata, and provide >> > > >> extended features such as security, transacted operations, >> > > >> auditing, locking, etc. >> > > >> >> > > >> Artifactory is distributed under APLv2 at >> > > >> http://artifactory.sourceforge.net. >> > > >> It is currently available as a downloadable archive, that can be >> > > >> run out of the box (with default settings). An install script to >> > > >> run it as a Linux service is also provided. >> > > >> A (limited) guest live demo is available at >> > > >> http://www.jfrog.org/artifactory/ >> > > >> >> > > >> You are welcome to give it a go! >> > > >> >> > > >> Cheers, >> > > >> >> > > >> Yoav Landman, >> > > >> The Artifactory Team >> > > >> >> > > >> -- >> > > >> View this message in context: >> > > >> >> http://www.nabble.com/-ANN--Artifactory---new-Maven-2-proxy-reposit >> > > >> or >> > > >> y-tf3344299s177.html#a9301347 Sent from the Maven - Users mailing >> > > >> list archive at Nabble.com. >> > > >> >> > > >> >> > > >> >> ------------------------------------------------------------------- >> > > >> -- To unsubscribe, e-mail: [EMAIL PROTECTED] >> > > >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > >> >> > > >> >> > > > >> > > > >> > > >> > > -- >> > > View this message in context: >> > > >> http://www.nabble.com/-ANN--Artifactory---new-Maven-2-proxy-repository >> > > -tf3344299s177.html#a9305322 Sent from the Maven - Users mailing list >> > > archive at Nabble.com. >> > > >> > > >> > > --------------------------------------------------------------------- >> > > 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] >> > > >> > > >> > >> > >> > -- >> > ------------------------ >> > Frederic Simon - Senior Architect >> > AlphaCSP Israel >> > Malam Group >> > Phone: +972 3 5312388 * Fax: +972 3 5312512 Mobile: +972 54 954301 >> > 13 Gosh Etzion St.,Givat Shmuel 54030, Israel http://www.alphacsp.com/ >> > http://www.malam.com/ >> > ------------------------ >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> >> -- >> ------------------------ >> Frederic Simon - Senior Architect >> AlphaCSP Israel >> Malam Group >> Phone: +972 3 5312388 * Fax: +972 3 5312512 Mobile: +972 54 954301 >> 13 Gosh Etzion St.,Givat Shmuel 54030, Israel >> http://www.alphacsp.com/ http://www.malam.com/ >> ------------------------ >> > > -- View this message in context: http://www.nabble.com/-ANN--Artifactory---new-Maven-2-proxy-repository-tf3344299s177.html#a9340957 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
