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": http://developer-blog.cloudbees.com/2013/03/playing-trade-offs-with-maven.html Hopefully that will give you some ideas of good (and bad) ways of handling your needs here. -Curtis On Thu, Jul 24, 2014 at 7:57 AM, David Evans <[email protected]> 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 deployment is that I've extended it to do the "possible", not > necessarily considering the "sensible", so I'll not go down that route. > Yet. > > It's a shame that I can't store the external jars in the Maven repository > and treat them ) as "versioned foreign artifacts" because having Maven > manage them in this way would be brilliant. > > Here's what I'm going to try instead: > > * 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). > > * if I understand this part of Maven dependepencies correctly, I can create > a parent dependendency that depends on an individual system-scope > dependency > for each of the libraries. This will hopefully get them all onto my Maven > project classpath without too much fuss. > > * use "assembly" to include the jars in my final deployment. > > Does this seem the natural and sensible way to manage external jars with > Maven? > > Thanks > > David > > > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Upload-3rd-party-jars-retaining-original-names-tp5800921p5800925.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
