Hi Andrei,
Andrei Pozolotin wrote:
> *Wayne*
>
> 1) in this case "I choose madness" :-)
>
> 2) here is my request:
> please provide an option to modello or whoever is enforcing strict
> xml model in maven
> to relax the rules, so people can use maven they way it fits them,
> while enforcing the rules by default.
Then why don't you use custom properties that follow simple naming
conventions? Just run in your mojo through the list of (resolved)
dependencies and look if an appropriate custom property has been defined:
<dependencies>
...
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
</dependency>
<dependency>
<groupId>com.example</groupId>
<artifactId>bundle</artifactId>
<version>1.0.1</version>
<classifier>features</classifier>
<type>xml</type>
</dependency>
...
</dependencies>
...
<properties>
...
<karaf.com.example.bundle.osgiStartLevel>99</karaf.com.example.bundle.osgiStartLevel>
<karaf.com.example.bundle.features.bootInstall>true</karaf.com.example.bundle.features.bootInstall>
...
</properties>
Obvious naming convention: karaf.groupId.artifactId[.classifier].variable
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
