Thanks you Stephen, I was afraid that is what it comes down to :(. --Kurt
On 6/17/11 11:25 AM, Stephen Connolly wrote:
I would do two different artifactId's... one for jax-ws-2.1 and the other
for jax-ws-2.2
They need to be separate projects as they have different dependencies.
Behind the scenes you might have a third module which contains just the
source and you package up that source and unpack it for the two modules...
or you could get away with m-shade-p producing an uber-jar
On 17 June 2011 16:21, Kurt T Stam<[email protected]> wrote:
Hi maven users,
On the jUDDI project we have a need to support compiling against 2
different version of the jax-ws spec (2.1 and 2.2). How do we go about this?
We can make profiles with different classifiers but some people argue for 1
build
artifact for each module, and this way we'd be producing 2, by running the
module twice with profiles (producing different jars with different
classification). BTW we ran into issues with this solution where the meta
data gets out sync during deploying to the repo.
This must be something other people have solved before. Any help would be
greatly appreciated.
Best regards,
--Kurt
Kurt Stam
------------------------------**------------------------------**---------
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.org<[email protected]>
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
