[
https://issues.apache.org/jira/browse/KARAF-3597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14369448#comment-14369448
]
Damian ONeill commented on KARAF-3597:
--------------------------------------
Thanks.
Yes we use runtime scope extensively throughout our maven build system. We
have a multimodule build with ~70 children. We enforce strict versioning
against each of the children by ensuring that mvn dependency:analyze raises no
issues. This therefore mandates defining the correct runtime jar files (and
version) for each of the child poms.
I'm currently looking at taking our Gateway SDK (resource adapter) and osgi
enabling it for deployment in karaf. For the SDK it contains ~120 transitive
jars, so clearly automating the feature description is very desirable from a
maintenance perspective.
Ideally I'd like to be able to update our dependency management section with
new versions (when needed) and have the build system generate the appropriate
new feature in the assembly.
Hope this helps.
> features-generate-descriptor ignoring runtime dependencies
> ----------------------------------------------------------
>
> Key: KARAF-3597
> URL: https://issues.apache.org/jira/browse/KARAF-3597
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 3.0.3
> Environment: Apache Maven 3.2.5
> (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T17:29:23+00:00)
> Maven home: /usr/local/Cellar/maven/3.2.5/libexec
> Java version: 1.7.0_67, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.10.2", arch: "x86_64", family: "mac"
> Reporter: Damian ONeill
> Assignee: Jean-Baptiste Onofré
> Labels: features-generate-descriptor
> Attachments: pom.xml
>
>
> When running the following command
> $ mvn -U karaf:features-generate-descriptor
> The generated feature.xml file does not contain any bundle definitions for
> dependencies defined with scope runtime.
> For e.g.
> <dependencies>
> <dependency>
> <groupId>javax.xml.bind</groupId>
> <artifactId>jaxb-api</artifactId>
> </dependency>
> <dependency>
> <groupId>com.sun.xml.bind</groupId>
> <artifactId>jaxb-impl</artifactId>
> <scope>runtime</scope>
> </dependency>
> <dependency>
> <groupId>org.jvnet.jaxb2_commons</groupId>
> <artifactId>jaxb2-basics-runtime</artifactId>
> </dependency>
> </dependencies>
> results in
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <features xmlns="http://karaf.apache.org/xmlns/features/v1.2.1";
> name="resourcesModel">
> <feature name="resourcesModel" version="6.0-SNAPSHOT"
> description="resourcesModel">
> <details>9001 is the proNX brand name for the EMS Core.</details>
> <bundle>wrap:mvn:javax.xml.bind/jaxb-api/2.1</bundle>
> <bundle>wrap:mvn:javax.xml.stream/stax-api/1.0-2</bundle>
> <bundle>wrap:mvn:javax.activation/activation/1.1</bundle>
>
> <bundle>mvn:org.jvnet.jaxb2_commons/jaxb2-basics-runtime/0.6.4</bundle>
> </feature>
> </features>
> Note no bundle definition for jaxb-impl defined with runtime scope above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
