Re: uploading jars to a internal repository using mvn deploy
I think the purpose of http://proximity.abstracthorizon.org/ Proximity is to do just that - act as a mirror and be an inhouse repository? Have I got it wrong? Owen Jacobson-2 wrote: On 28-Sep-07, at 1:10 AM, owen_moony wrote: I have just created an internal maven repository using proximity (http://proximity.abstracthorizon.org). Everything is great, its acting as a proxy and getting the jars from the internet and caching them - brilliant! My only question is how do I upload my own jars created by me? Upload them to a bog-standard maven repository using, for example, scp or webdav. Maven repos are just directory trees of a known structure. Is there an easier way to create an internal repository (forget proximity), so that you can use the mvn deploy command and get the thing to act as a proxy and cache to the internet jars? Maintain your in-house repository in parallel to your mirror, rather than trying to use one repo for both tasks. Cheers, Owen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/uploading-jars-to-a-internal-repository-using-%22mvn-deploy%22-tf4533027s177.html#a12993245 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: uploading jars to a internal repository using mvn deploy
cstamas wrote: you could try to use WebDAV (confgure it as build extension in mvn 2.0.7) and point the repo URL to address: http://devserver1:/px-webapp/dav/inhouse Thank you so much for that suggestion!! it got me that little closer to the answer, which seems to be (notice the 'dav:http://' rather than just 'http://'): distributionManagement repository iddeployserver/id urldav:http://devserver1:9990/px-webapp/dav/inhouse/url /repository /distributionManagement Although, i managed to do the same thing using: urlscpexe://192.168.0.157/home/owen/proximity/inhouse.snapshot/storage/url and having a http://maven.apache.org/ref/current/maven-settings/settings.html#class_server server defined in my setting.xml with the location of my public key (NOTE: password would not work in this server tag when doing a deploy, i think its a bug). But using scp is a pain, because you have to create scp accounts and keys etc. The only thing is, for some strange reason, the dav seems to take a lot longer - like 2min instead of scp, which takes a few seconds to deploy the jars to the company repository. And for those who have stumbled over this looking for help, to use the distributionManagement tag mentioned above, you will need to also add to the pom.xml the following: build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-ssh-external/artifactId version1.0-alpha-5/version /extension extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions /build Thanks, Owen. -- View this message in context: http://www.nabble.com/uploading-jars-to-a-internal-repository-using-%22mvn-deploy%22-tf4533027s177.html#a12992552 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: uploading jars to a internal repository using mvn deploy
Hello, you could try to use WebDAV (confgure it as build extension in mvn 2.0.7) and point the repo URL to address: http://devserver1:/px-webapp/dav/inhouse Hope helps, ~t~ On 9/28/07, owen_moony [EMAIL PROTECTED] wrote: distributionManagement repository idinhouse/id urlhttp://devserver1:/px-webapp/repository/inhouse/url /repository /distributionManagement - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: uploading jars to a internal repository using mvn deploy
On 28-Sep-07, at 1:10 AM, owen_moony wrote: I have just created an internal maven repository using proximity (http://proximity.abstracthorizon.org). Everything is great, its acting as a proxy and getting the jars from the internet and caching them - brilliant! My only question is how do I upload my own jars created by me? Upload them to a bog-standard maven repository using, for example, scp or webdav. Maven repos are just directory trees of a known structure. Is there an easier way to create an internal repository (forget proximity), so that you can use the mvn deploy command and get the thing to act as a proxy and cache to the internet jars? Maintain your in-house repository in parallel to your mirror, rather than trying to use one repo for both tasks. Cheers, Owen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
