Michael:
re "classifiers or build qualiafiers" - these are not variations on
dependency
this is same dependency, but in different poms this dependency have
different custom property.
think of it like @Inject annotation in guice
Thank you,
Andrei
-------- Original Message --------
Subject: Re: [VOTE] Apache 3.1.0-alpha-1
From: Michael-O <[email protected]>
To: Maven Developers List <[email protected]>
Date: Thu 04 Apr 2013 11:08:01 AM CDT
> Am 2013-04-04 15:57, schrieb Andrei Pozolotin:
>> Hervé:
>>
>> thank you for taking the time to respond.
>>
>> issue at hand:
>>
>> karaf
>> http://karaf.apache.org/
>>
>> has features.xml, which are built from pom.xml
>> http://karaf.apache.org/manual/latest-2.3.x/users-guide/provisioning.html
>>
>>
>> what is missing from maven is the ability to communicate arbitrary
>> custom attributes
>> on per-dependency basis, such as:
>>
>> provide osgiStartLevel value, to specify to osgi runtime bundle start
>> level:
>> <dependency>
>> <groupId>com.example</groupId>
>> <artifactId>bundle</artifactId>
>> <version>1.0.1</version>
>> <osgiStartLevel>99</osgiStartLevel>
>> </dependency>
>>
>> or provide karafBootInstall flag, to specify that karaf runtime should
>> install this dependency at boot-time vs build-time:
>> <dependency>
>> <groupId>com.example</groupId>
>> <artifactId>bundle-feature</artifactId>
>> <version>1.0.1</version>
>> <classifier>features</classifier>
>> <type>xml</type>
>> <karafBootInstall>true</karafBootInstall>
>> </dependency>
>
> I think that variations of depenencies must go either in classifiers
> or build qualiafiers. If we start allow arbitrary elements in
> <dependency>, people will start to ask for custom elements in X.
> Therefore custom elements are allow in a plugin's <configuration> only.
>
> Michael
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
