Hi, A question I'm sure have been on the mailing-lists before (but I could not find it) regarding how to handle 3rd party JARs:
I am using some 3rd party JARs which does not exsist in the global Maven2 repository ( http://repo1.maven.org/maven2/). I've found some references on the web to using "mvn install:install-file" or "mvn deploy:deploy-file" to add these jars to my repository. The "mvn install:install-file" works OK to install in my local repository, but when I try installing to our company-wide repository using "mvn deploy:deploy-file" and an FTP-URL, I get an error about missing Wagon for FTP. Ideally, I would have liked to set up a Maven2 project holding the JAR in question (almost as a source), setting up all I need (groupID, artifactID, version etc.) in the project pom, and then do "mvn deploy" on the project, resulting in the correct JAR beeing deployed to our thirdparty repository. Whenever the thirdparty library changes (new version released etc.), I could download the new Jar, updated the version in my pom, and do a mvn deploy. This would mean a maven2 project with no source (java source). Would this work, and if so, how should I set up such a project ? ..or am I totally on the wrong path here ? Regards Arne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
