Cannot be classifiers, as he needs different dependencies.
May also want to use tool chains rather than hard coding Jdk paths
On Monday, 23 July 2012, Ron Wheeler wrote:
> It sounds like you have 2 artifacts at the end.
>
> One that is compiled and built with 1.5 and will run under 1.5 JVM and
>
It sounds like you have 2 artifacts at the end.
One that is compiled and built with 1.5 and will run under 1.5 JVM and
probably under 1.6 JVM
One that is compiled and built with 1.6 and will not run under 1.5 JVM.
It seems that these are 2 different artifacts and should have different
Artifac
> Any idea what would be the best way to realize this?
Find a way to simplify things. You're doing too much stuff in one
module. Break it into 2 and maybe more.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
If those tests should always run, why have them in a profile??
On 23.07.2012 17:26, Andreas Riedel wrote:
> Hello users,
>
> I have the following problem:
>- One system must be compiled with two different JDK.
>- I have two test suites, one for smoke test, one for all.
>
> Base scenario:
Hello users,
I have the following problem:
- One system must be compiled with two different JDK.
- I have two test suites, one for smoke test, one for all.
Base scenario:
- Two profiles, 'SmokeTest' activate by default, 'All' activate by
switch -P.
- One additional profile with depend
