[ https://issues.apache.org/jira/browse/KARAF-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985274#comment-14985274
]
Jean-Baptiste Onofré edited comment on KARAF-4082 at 11/2/15 2:20 PM:
----------------------------------------------------------------------
The assembly goal works fine: the system folder is populated even if the dependency flagged
bundles.
For instance, I created a test pom.xml containing:
{code}
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>assembly</goal>
</goals>
<configuration>
<installedFeatures>
<feature>aries-annotation</feature>
</installedFeatures>
<bootFeatures/>
<startupFeatures/>
</configuration>
</execution>
{/code}
The aries-annotation feature contains dependency bundles (like common-jexl, etc), and I can
see those bundles in the generated system folder.
Now, I'm testing with the add-features-to-repo goal.
was (Author: jbonofre):
The assembly goal works fine: the system folder is populated even if the dependency flagged
bundles.
For instance, I created a test pom.xml containing:
[code]
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>assembly</goal>
</goals>
<configuration>
<installedFeatures>
<feature>aries-annotation</feature>
</installedFeatures>
<bootFeatures/>
<startupFeatures/>
</configuration>
</execution>
[/code]
The aries-annotation feature contains dependency bundles (like common-jexl, etc), and I can
see those bundles in the generated system folder.
Now, I'm testing with the add-features-to-repo goal.
> .kar file generated by karaf-maven-plugin does not contain all jars (no offline support)
> ----------------------------------------------------------------------------------------
>
> Key: KARAF-4082
> URL: https://issues.apache.org/jira/browse/KARAF-4082
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-tooling
> Affects Versions: 4.0.2
> Reporter: Robert Weiser
> Assignee: Jean-Baptiste Onofré
>
> The {{karaf-maven-plugin}} only adds the bundle/jar files to the repository that have
been included using:
> {code}
> <bundle start-level="30"/>
> {code}
> The following definition types are not supported:
> {code}
> <bundle start-level="30" dependency="true">
> {code}
> or
> {code}
> <conditional>
> <condition>deployer</condition>
> <bundle start-level="30">mvn:org.apache.karaf.deployer/org.apache.karaf.deployer.spring/4.0.2</bundle>
> </conditional>
> {code}
> ...this is not a problem if the machine is granted internet access - if not the .kar
archive cannot be installed - it is not "self-contained".
> The described behaviour can be tested if configuring the file {{org.ops4j.pax.url.mvn.cfg}}
the following way:
> {code}
> org.ops4j.pax.url.mvn.localRepository=file:${karaf.home}/${karaf.default.repository}
> org.ops4j.pax.url.mvn.useFallbackRepositories=false
> org.ops4j.pax.url.mvn.defaultRepositories=\
> file:${karaf.home}/${karaf.default.repository}@id=system.repository@snapshots, \
> file:${karaf.data}/kar@id=kar.repository@multi@snapshots, \
> file:${karaf.base}/${karaf.default.repository}@id=child.system.repository@snapshots
> org.ops4j.pax.url.mvn.repositories=
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
|