That's not the same case : testng has many jars with various classifier,
depending on the jdk used to build it from sources. They all share the same
POM
A maven artifact with a classifier always has the same POM as the
no-classifier artifact.
You will need to create multiple VERSIONS on the jar
Yes, that's what I'm saying. This is how testng (and others) do it:
http://repo1.maven.org/maven2/org/testng/testng/5.5/
Wayne
On 10/23/07, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
> Do I understand it correctly that you saying that I need to create 2 upload
> bundles for swingx, one for jdk 1.5 a
Do I understand it correctly that you saying that I need to create 2 upload
bundles for swingx, one for jdk 1.5 and one for jdk 1.6?
They both will have the exact same code, only different dependencies?
regards,
Wim
2007/10/23, Wayne Fay <[EMAIL PROTECTED]>:
>
> Most people solve these kinds o
You would need the jars to have the associated classifier too...
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 23, 2007 3:11 PM
To: Maven Users List
Subject: Re: declare dependencies depending on jdk version
Most people solve these kinds of problems
Most people solve these kinds of problems by simply creating 2 (or
more) poms that have different classifiers to specify the difference,
eg:
swingx-1.0.pom
swingx-1.0-jdk4.pom
swingx-1.0-jdk5.pom
swingx-1.0-jdk6.pom
Wayne
On 10/23/07, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm looking
Hi,
I'm looking into putting swingx in the central repo. As they do not use
maven to build, I need to come up with a good pom. They have 3 dependencies.
Two of them are only needed when running under jdk 1.5. How can I declare
this in the pom.xml?
Suppose this is a part of the pom:
s
