I am doing something like this using dependency:unpack-dependencies at the generate-resources phase. This way I don't have to think about a jar of jars or classpath.
-----Original Message----- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: Monday, February 02, 2009 12:19 PM To: Maven Users List Subject: [SPAM] RE: Maven deploy project on a server different from remote repo server Importance: Low You could use the assembly plugin to produce a bundle with the dependencies. Or you could patch something together with dependency:copy-dependencies and dependency:build-classpath -----Original Message----- From: Qureshi,Shahzad [Ontario] [mailto:shahzad.qure...@ec.gc.ca] Sent: Monday, February 02, 2009 11:26 AM To: users@maven.apache.org Subject: Maven deploy project on a server different from remote repo server Hi all, Here is the situation. Our internal remote repository is on server1 and my application that will require some of the jars sitting on the remote repo is on server2. Now my application is in jar format (created using maven) and is used by a web coldfusion based application. Now, do I simply figure out which dependencies my app requires and manually put them somewhere on server2 and use the classpath way of doing things to run this app or is there a better way to do this using Maven? I have been using Maven for a few months now and I understand how it works but I am not sure what to do in this deployment scenario that I mentioned above Any insights will be appreciated. Thank you Shahzad Qureshi Systems Analyst/Programmer Applications Directorate, CIOB Environment Canada shahzad.qure...@ec.gc.ca --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
