[ 
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

        

Reply via email to