Mark Struberg wrote:
> Hi Jörg!
>
>> Typically you will set scope "test" for
>> this artifact in your depMgmnt section ...
>
> Yup, but this means that the version has to be set twice.
> Also I'm not sure if the maven-release-plugin can handle 2
> dependencyManagement entries for the same module
Von: Brian E. Fox
> Betreff: RE: dependencyManagement do not work for attached artifacts
> An: "Maven Users List"
> Datum: Samstag, 17. Januar 2009, 19:33
> Specify another dependencyManagement and specify the
> classifier "tests" and it will work. Classifier
Specify another dependencyManagement and specify the classifier "tests" and it
will work. Classifier is part of the coordinates and if you skip it, it's
assumed to be null. If you want to keep both entries in sync, then define a
property for the version.
-Original Message-
From: Mark St
ly.
Has anyone tried releasing such a scenario yet?
txs and LieGrue,
strub
--- Jörg Schaible schrieb am Sa, 17.1.2009:
> Von: Jörg Schaible
> Betreff: Re: dependencyManagement do not work for attached artifacts
> An: users@maven.apache.org
> Datum: Samstag, 17. Januar 2009, 15:53
Mark Struberg wrote:
> Hi!
>
> I'm not sure if this behaviour is by design or a bug.
>
> The situation:
>
> I have 2 modules in my project
>
> 1.) openwebbeans-impl
> 2.) openwebbeans-tck (there is a reason for having this in a separate
> module currently)
>
> The impl contains test code (e.g
