karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Pieber (JIRA)" <j...@apache.org>
Subject [jira] Created: (KARAF-365) Merge .kar files in features-maven-plugin during "add-features-to-repo" goal
Date Mon, 10 Jan 2011 15:06:46 GMT
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.


Mime
View raw message