You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Andreas Pieber (JIRA)" <ji...@apache.org> on 2011/01/10 16:06:46 UTC
[jira] Created: (KARAF-365) Merge .kar files in
features-maven-plugin during "add-features-to-repo" goal
Merge .kar files in features-maven-plugin during "add-features-to-repo" goal
----------------------------------------------------------------------------
Key: KARAF-365
URL: https://issues.apache.org/jira/browse/KARAF-365
Project: Karaf
Issue Type: New Feature
Components: tooling
Reporter: Andreas Pieber
Priority: Minor
What I can think of there is to extend the add-feature-to-repo goal to something like:
{code}
<plugin>
<groupId>org.apache.karaf.tooling</groupId>
<artifactId>features-maven-plugin</artifactId>
<version>${karaf.version}</version>
<executions>
<execution>
<id>add-features-to-repo</id>
<phase>generate-resources</phase>
<goals>
<goal>add-features-to-repo</goal>
</goals>
<configuration>
<descriptors>
DESCRIPTORS
</descriptors>
<features>
FEATURES
</features>
<kars>
KARS
</kars>
<repository>target/features-repo</repository>
<failOnArtifactResolutionError>true</failOnArtifactResolutionError>
</configuration>
</execution>
</executions>
</plugin>
{code}
.kar files could be installed via maven but basically nothing more than merging them into the "repository" happens. This should do it for now, should be simple to implement but allow an additional abstraction layer since entire packages could be used without looking at the features file at this place at all.
I'm not sure by now how useful this will be since you can do the same via the feature file (which is anyhow required to build a kar file). But at least it would assist to make .kar to the default packaging for karaf features.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] [Commented] (KARAF-365) Merge .kar files in
features-maven-plugin during "add-features-to-repo" goal
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063256#comment-13063256 ]
Jean-Baptiste Onofré commented on KARAF-365:
--------------------------------------------
I think it's already more or less achieve on trunk. We have to take a deeper look to perform a kind of gap analyze.
> Merge .kar files in features-maven-plugin during "add-features-to-repo" goal
> ----------------------------------------------------------------------------
>
> Key: KARAF-365
> URL: https://issues.apache.org/jira/browse/KARAF-365
> Project: Karaf
> Issue Type: New Feature
> Components: tooling
> Reporter: Andreas Pieber
> Priority: Minor
>
> What I can think of there is to extend the add-feature-to-repo goal to something like:
> {code}
> <plugin>
> <groupId>org.apache.karaf.tooling</groupId>
> <artifactId>features-maven-plugin</artifactId>
> <version>${karaf.version}</version>
> <executions>
> <execution>
> <id>add-features-to-repo</id>
> <phase>generate-resources</phase>
> <goals>
> <goal>add-features-to-repo</goal>
> </goals>
> <configuration>
> <descriptors>
> DESCRIPTORS
> </descriptors>
> <features>
> FEATURES
> </features>
> <kars>
> KARS
> </kars>
> <repository>target/features-repo</repository>
> <failOnArtifactResolutionError>true</failOnArtifactResolutionError>
> </configuration>
> </execution>
> </executions>
> </plugin>
> {code}
> .kar files could be installed via maven but basically nothing more than merging them into the "repository" happens. This should do it for now, should be simple to implement but allow an additional abstraction layer since entire packages could be used without looking at the features file at this place at all.
> I'm not sure by now how useful this will be since you can do the same via the feature file (which is anyhow required to build a kar file). But at least it would assist to make .kar to the default packaging for karaf features.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-365) Merge .kar files in
features-maven-plugin during "add-features-to-repo" goal
Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-365:
---------------------------------------
Fix Version/s: 3.1.0
3.0.0
> Merge .kar files in features-maven-plugin during "add-features-to-repo" goal
> ----------------------------------------------------------------------------
>
> Key: KARAF-365
> URL: https://issues.apache.org/jira/browse/KARAF-365
> Project: Karaf
> Issue Type: New Feature
> Components: tooling
> Reporter: Andreas Pieber
> Priority: Minor
> Fix For: 3.0.0, 3.1.0
>
>
> What I can think of there is to extend the add-feature-to-repo goal to something like:
> {code}
> <plugin>
> <groupId>org.apache.karaf.tooling</groupId>
> <artifactId>features-maven-plugin</artifactId>
> <version>${karaf.version}</version>
> <executions>
> <execution>
> <id>add-features-to-repo</id>
> <phase>generate-resources</phase>
> <goals>
> <goal>add-features-to-repo</goal>
> </goals>
> <configuration>
> <descriptors>
> DESCRIPTORS
> </descriptors>
> <features>
> FEATURES
> </features>
> <kars>
> KARS
> </kars>
> <repository>target/features-repo</repository>
> <failOnArtifactResolutionError>true</failOnArtifactResolutionError>
> </configuration>
> </execution>
> </executions>
> </plugin>
> {code}
> .kar files could be installed via maven but basically nothing more than merging them into the "repository" happens. This should do it for now, should be simple to implement but allow an additional abstraction layer since entire packages could be used without looking at the features file at this place at all.
> I'm not sure by now how useful this will be since you can do the same via the feature file (which is anyhow required to build a kar file). But at least it would assist to make .kar to the default packaging for karaf features.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (KARAF-365) Merge .kar files in
features-maven-plugin during "add-features-to-repo" goal
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006226#comment-13006226 ]
David Jencks commented on KARAF-365:
------------------------------------
Can you take a look at the karaf-assembly packaging? I think it does something like this in a much more convenient way.
I'm hoping to get an example karaf-assembly (although it will need to use the mojos separately) into the karaf build soon, but there is currently an example at
https://svn.apache.org/repos/asf/geronimo/sandbox/djencks/txmanager
> Merge .kar files in features-maven-plugin during "add-features-to-repo" goal
> ----------------------------------------------------------------------------
>
> Key: KARAF-365
> URL: https://issues.apache.org/jira/browse/KARAF-365
> Project: Karaf
> Issue Type: New Feature
> Components: tooling
> Reporter: Andreas Pieber
> Priority: Minor
>
> What I can think of there is to extend the add-feature-to-repo goal to something like:
> {code}
> <plugin>
> <groupId>org.apache.karaf.tooling</groupId>
> <artifactId>features-maven-plugin</artifactId>
> <version>${karaf.version}</version>
> <executions>
> <execution>
> <id>add-features-to-repo</id>
> <phase>generate-resources</phase>
> <goals>
> <goal>add-features-to-repo</goal>
> </goals>
> <configuration>
> <descriptors>
> DESCRIPTORS
> </descriptors>
> <features>
> FEATURES
> </features>
> <kars>
> KARS
> </kars>
> <repository>target/features-repo</repository>
> <failOnArtifactResolutionError>true</failOnArtifactResolutionError>
> </configuration>
> </execution>
> </executions>
> </plugin>
> {code}
> .kar files could be installed via maven but basically nothing more than merging them into the "repository" happens. This should do it for now, should be simple to implement but allow an additional abstraction layer since entire packages could be used without looking at the features file at this place at all.
> I'm not sure by now how useful this will be since you can do the same via the feature file (which is anyhow required to build a kar file). But at least it would assist to make .kar to the default packaging for karaf features.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-365) Merge .kar files in
features-maven-plugin during "add-features-to-repo" goal
Posted by "Jamie goodyear (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear updated KARAF-365:
---------------------------------
Fix Version/s: (was: 3.0.0)
> Merge .kar files in features-maven-plugin during "add-features-to-repo" goal
> ----------------------------------------------------------------------------
>
> Key: KARAF-365
> URL: https://issues.apache.org/jira/browse/KARAF-365
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-tooling
> Reporter: Andreas Pieber
> Priority: Minor
> Fix For: 3.1.0
>
>
> What I can think of there is to extend the add-feature-to-repo goal to something like:
> {code}
> <plugin>
> <groupId>org.apache.karaf.tooling</groupId>
> <artifactId>features-maven-plugin</artifactId>
> <version>${karaf.version}</version>
> <executions>
> <execution>
> <id>add-features-to-repo</id>
> <phase>generate-resources</phase>
> <goals>
> <goal>add-features-to-repo</goal>
> </goals>
> <configuration>
> <descriptors>
> DESCRIPTORS
> </descriptors>
> <features>
> FEATURES
> </features>
> <kars>
> KARS
> </kars>
> <repository>target/features-repo</repository>
> <failOnArtifactResolutionError>true</failOnArtifactResolutionError>
> </configuration>
> </execution>
> </executions>
> </plugin>
> {code}
> .kar files could be installed via maven but basically nothing more than merging them into the "repository" happens. This should do it for now, should be simple to implement but allow an additional abstraction layer since entire packages could be used without looking at the features file at this place at all.
> I'm not sure by now how useful this will be since you can do the same via the feature file (which is anyhow required to build a kar file). But at least it would assist to make .kar to the default packaging for karaf features.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira