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 stored in a repository.



I am developing against a 3rd party software package that includes about
a dozen supporting jar files. I am trying to upload these jars into a
Maven repository such that I can put a dependency in my development
project that puts all of the original jars on my classpath. I have
tried:

* insert jars individually (and as a collection) using Nexus console but
the stored jar is named {artifactId}-{version}
This is the rule as artifacts are stored in a repository...


* create jar projects with various source structures but, again, the
stored jar is named {artifactId}-{version}
The sources structure is not related to the naming rules, cause you should think about how would other consume those artifacts if they do not follow a naming rule...big example see Maven Central....


* create a jar project containing an assembly: I can make the 3rd party
jars visible with their original names but, yet again, they are put into
in a jar named {artifactId}-{version}.

Context is that I'm just beginning to try and replace historical
Ant/Eclipse projects with Maven/Eclipse. I've read through "Maven The
Definitive Guide" and Googled as much as I can but I'm at a stage where
I'm not even sure I'm asking sensible questions.  If there's a "how to"
document around (with worked examples rather than isolated XML
fragments) that would be great.  If I'm missing the point of Maven and
trying to implement an Ant concept that would be good to know too.

You have to follow the naming rule and change other projects to consume those artifacts with the appropriate naming rules....

Kind regards
Karl-Heinz Marbaise

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to