Re: Upload 3rd party jars retaining original names

2014-07-24 Thread Hilton Wichwski Silva
Maybe this help http://maven.apache.org/plugins/maven-dependency-plugin/copy-mojo.html 2014-07-24 8:20 GMT-03:00 David Evans da...@evans6.me.uk: Is it possible to put a bunch of 3rd party jars into a Maven repository so that they can be accessed by a project using their original names? I am

Re: Upload 3rd party jars retaining original names

2014-07-24 Thread Anders Hammar
The name of artifacts in a Maven repo is not possible to specify yourself. As you've noticed, they are called artifactId-version (and you can also have a classifier). So no, you cannot give them their original name if that is different from that naming scheme. /Anders On Thu, Jul 24, 2014 at

Re: Upload 3rd party jars retaining original names

2014-07-24 Thread Karl Heinz Marbaise
Hi David, Is it possible to put a bunch of 3rd party jars into a Maven repository so that they can be accessed by a project using their original names? What do you mean by original names? As they were in Ant? More or simple answer to this is no, cause Maven has it's rules how artifacts are

Re: Upload 3rd party jars retaining original names

2014-07-24 Thread David Evans
Thanks all. It seems that what I want to do doesn't fit naturally into the Maven way of things. Using the copy plugin I can see how I might possibly unpack elements and modify my Eclipse classpath in flight but part of the problem with my existing Ant deployment is that I've extended it to do

Re: Upload 3rd party jars retaining original names

2014-07-24 Thread Ron Wheeler
http://maven.apache.org/articles.html There are a number of books (free and for purchase) and articles that might help you get up to speed very quickly and give you some ideas about Best Practices We all use 3rd party jars (70+ in one of our projects) and Maven makes this easy. You declare

RE: Upload 3rd party jars retaining original names

2014-07-24 Thread cody.a.fyler
To: users@maven.apache.org Subject: Re: Upload 3rd party jars retaining original names Thanks all. It seems that what I want to do doesn't fit naturally into the Maven way of things. Using the copy plugin I can see how I might possibly unpack elements and modify my Eclipse classpath in flight

Re: Upload 3rd party jars retaining original names

2014-07-24 Thread Ron Wheeler
On 24/07/2014 8:57 AM, David Evans wrote: Thanks all. It seems that what I want to do doesn't fit naturally into the Maven way of things. Using the copy plugin I can see how I might possibly unpack elements and modify my Eclipse classpath in flight but part of the problem with my existing Ant

RE: Upload 3rd party jars retaining original names

2014-07-24 Thread Martin Gainty
From: cody.a.fy...@wellsfargo.com To: users@maven.apache.org Subject: RE: Upload 3rd party jars retaining original names Date: Thu, 24 Jul 2014 13:06:11 + If you're using ant, why not also use Ivy? Then you can make use of the maven standard named artifacts. MGCody...how would

Re: Upload 3rd party jars retaining original names

2014-07-24 Thread Curtis Rueden
Hi David, * I'll carry on with the libraries in my [Perforce] SCM. * I can map them to a project folder as I do now (similar to sources, resources, etc). See Stephen Connelly's blog post on dealing with non-Maven JARs: