I would think a better way would be to specify the different artifacts
as dependencies only in different profiles.
You can then just activate the profile for the artifact you want, and
everything is self-contained in the pom
2008/10/11 Brett Porter <[EMAIL PROTECTED]>:
> mvn help:effective-* will show the profiles actually used.
>
> This seems like a very bad idea for build reproducibility however - I
> wouldn't recommend it.
>
> - Brett
>
> 2008/10/11 Lucie <[EMAIL PROTECTED]>:
>>
>> This is defined pom.xml:
>>
>> <dependency>
>> <groupId><groupId>
>> <artifcactId>${my.artifactId}</artifactId>
>> <vesion></version>
>> </dependency>
>>
>> I have a profile defined in profiles.xml to pass the ${my.artifactId} as a
>> property at build time.
>> This doesn't work - no value is passed. What may have caused to failed?
>>
>> Lucie
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Changing-dependency-in-pom.xml-using-profiles-tp19927738p19927738.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
