(1) I cannot take care of in my application since I don't know where to get the dependencies from. The idea behind Maven and Class-Path is that the user doesn't need to care about.

(2) Why not just correcting the Class-Path in the JAR or the pom.xml? As you put the the project in the project, you are responsible for doing it correctly. What sense does it make to have jar and pom.xml found in the repo that in fact are not in sync and cannot be used at all?

Markus

Carlos Sanchez schrieb:

We don't build the jars, we just put them in the repo. If they build
agains a jar that being the same has a different name we can't do
anything about it. You are the one that in your application have to
take care of it.


begin:vcard
fn:Markus KARG
n:KARG;Markus
org:QUIPSY QUALITY GmbH;Entwicklung / R & D
adr:;;Stuttgarter Strasse 23;Pforzheim;Baden-Wuerttemberg;75179;Bundesrepublik Deutschland
email;internet:[EMAIL PROTECTED]
title:Staatl. gepr. Inf.
tel;work:+49-7231-9189-52
tel;fax:+49-7231-9189-59
note:QUIPSY(R) Entwicklung / R & D
x-mozilla-html:TRUE
url:http://www.quipsy.de
version:2.1
end:vcard

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to