[jira] [Updated] (KARAF-424) Maven packaging for feature, kar, karaf-assembly; mojos based on geronimo server assemblies

["Jamie goodyear (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KARAF-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jamie goodyear updated KARAF-424:
---------------------------------

    Fix Version/s:     (was: 3.0.0)
                   3.1.0

I've bumped out this issue to 3.1.0 - some of the sub issues may be able to be included in 3.0.0.
                
> Maven packaging for feature, kar, karaf-assembly; mojos based on geronimo server assemblies
> -------------------------------------------------------------------------------------------
>
>                 Key: KARAF-424
>                 URL: https://issues.apache.org/jira/browse/KARAF-424
>             Project: Karaf
>          Issue Type: New Feature
>          Components: karaf-tooling
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.1.0
>
>
> This overlaps with quite a few other jiras.
> This work adds mojos for:
> feature xml generation with one feature per maven project, following the appropriately scoped maven dependencies.  This is very different from the existing feature.xml generation which has apparently not proved useful. We stop following transitive dependencies when we reach another maven dependency that's a feature.
> kar assembly including the feature.xml file as above, maven dependencies, and resources.
> Server assembly which installs the kars listed in the pom; kar installation uses the existing kar deployer
> server archiving which packs up the assembled server into tar.gz and zip files
> and also maven packagings for these.  
> In addition there's a framework kar that includes the basic file structure for a karaf server and the stuff that isn't in the local-repo and a sample server assembly that just has the framework in it.

--
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