This keeps coming up, over and over and over. e.g: http://maven.40175.n5.nabble.com/Meta-information-about-dependencies-in-a-pom-td4971927.html
The maven 'answer' seems to amount to 'hard cheese, you must re-specify each and every one of your dependencies again in your plugin config'. And then pointing to the configuration horror that is the assembly plugin, and completely ignoring the duplication of, like, every single dependency in your use-case. And if your language has scopes other than the burnt-in ones in maven, double-hard cheese with a cherry on top - welcome to screenfuls of warnings and a non-working transitive dependency mechanism. Despite the fact you're already paying the XML tax (so each dependency takes 5 lines in your POM file, compared to single lines in other tools), *and* the fact that XML has a well-defined capability with namespaces to compatibly extend the data (and have those extensions easy to strip out), maven refuses to contemplate this, it seems. How about <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:karaf="maven:plugin:com.apache:karaf" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd";> .... <dependency> <groupId>com.example</groupId> <artifactId>bundle</artifactId> <version>1.0.1</version> <karaf:osgiStartLevel>99</karaf:osgiStartLevel> <karaf:bootInstall>true</karaf:bootInstall> </dependency> On Thu, Apr 4, 2013 at 2:57 PM, Andrei Pozolotin <[email protected] > wrote: > 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> > > in lieu of these, karaf-maven-plugin is trying to encode this > information via <scope> > > https://github.com/apache/karaf/blob/trunk/tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/features/InstallKarsMojo.java#L215 > > which contradicts the dependency resolution rules and really does not work. > > hence my request to "relax". is there any other ways to address this need? > > Andrei > > -------- Original Message -------- > Subject: Re: [VOTE] Apache 3.1.0-alpha-1 > From: Hervé BOUTEMY <[email protected]> > To: Maven Developers List <[email protected]> > Date: Thu 04 Apr 2013 01:21:32 AM CDT > > AFAIK, there is nothing "relaxed" from Mven 3.0.x planned > > > > But I don't really understand your case (and miss time to investigate in > > Karaf). > > Can you give us a pointer to SCM, or paste such a dependency "with custom > > tags"? > > > > Regards, > > > > Hervé > > > > Le mercredi 3 avril 2013 08:51:01 Andrei Pozolotin a écrit : > >> I am curious if 3.1.0 will be more relaxed with custom tags inside > >> <dependency>? > >> > >> Use case: karaf-maven-plugin uses bizarre conventions > >> on how to map from <scope> into osgi bundle properties (like start > level) > >> because there is no way to have a custom tag in <dependency> and express > >> this requirement. > >> > >> -------- Original Message -------- > >> Subject: Re: [VOTE] Apache 3.1.0-alpha-1 > >> From: Jason van Zyl <[email protected]> > >> To: Maven Developers List <[email protected]> > >> Date: Tue 02 Apr 2013 12:04:18 PM CDT > >> > >>> Thanks. > >>> > >>> On Apr 2, 2013, at 1:00 PM, Hervé BOUTEMY <[email protected]> > wrote: > >>>> Staged documentation: http://maven.apache.org/ref/3.1.0-alpha-1/ > >>>> > >>>> Regards, > >>>> > >>>> Hervé > >>>> > >>>> Le lundi 1 avril 2013 08:12:09 Jason van Zyl a écrit : > >>>>> Here are the release bits for 3.1.0-alpha-1: > >>>>> > >>>>> Release notes: > >>>>> > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&versio > >>>>> n=18 967 > >>>>> > >>>>> Staging repository: > >>>>> https://repository.apache.org/content/repositories/maven-042/ > >>>>> > >>>>> Staged distribution: > >>>>> > https://repository.apache.org/content/repositories/maven-042/org/apache/ > >>>>> mave n/apache-maven/3.1.0-alpha-1/ > >>>>> > >>>>> Anyone trying this in advance should know that the Site, Dependency, > and > >>>>> Shade plugin are not going to work. We are aware of this and those > >>>>> responsible for those plugins are looking into it. > >>>>> > >>>>> Thanks, > >>>>> > >>>>> Jason > >>>>> > >>>>> ---------------------------------------------------------- > >>>>> Jason van Zyl > >>>>> Founder & CTO, Sonatype > >>>>> Founder, Apache Maven > >>>>> http://twitter.com/jvanzyl > >>>>> --------------------------------------------------------- > >>>>> > >>>>> We know what we are, but know not what we may be. > >>>>> > >>>>> -- Shakespeare > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: [email protected] > >>>> For additional commands, e-mail: [email protected] > >>> Thanks, > >>> > >>> Jason > >>> > >>> ---------------------------------------------------------- > >>> Jason van Zyl > >>> Founder & CTO, Sonatype > >>> Founder, Apache Maven > >>> http://twitter.com/jvanzyl > >>> --------------------------------------------------------- > >>> > >>> What matters is not ideas, but the people who have them. Good people > can > >>> fix bad ideas, but good ideas can't save bad people.> > >>> -- Paul Graham > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > . > > > >
