Hello Maven community,

Why does Maven (3.0.3) resolve test scoped dependencies when tests
compilation and execution is skipped via maven.test.skip system property?

I'm trying to achieve this by defining a profile with all test scope
dependencies declared in it only. Profile is activated when maven.test.skip
system property is not defined. Would be more precise if I could specify
activation to be when that property is not defined or is set to false but
that doesn't seem to be possible (no compound expressions in single
property, no multiple properties in single activation) or am I missing
something?

Kind regards,
Stevo.

Reply via email to