Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@karaf.apache.org
Message-ID: <28335657.273321296248203997.JavaMail.jira@thor>
Date: Fri, 28 Jan 2011 15:56:43 -0500 (EST)
From: "David Jencks (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Subject: [jira] Commented: (KARAF-424) Maven packaging for feature, kar,
 karaf-assembly; mojos based on geronimo server assemblies
In-Reply-To: <30463790.259271296199063634.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/KARAF-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988225#action_12988225 ] 

David Jencks commented on KARAF-424:
------------------------------------

Previous work runs into the maven problem that you cant build a plugin for the first time if you use it in your build.  So I put (r1064869) the uses of kar and server-assembly packaging into a "full" profile.

To build:
mvn clean install
mvn clean install -Pfull

needs improvement...

> 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: tooling
>    Affects Versions: 2.2.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 2.2.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.
-
You can reply to this email to add a comment to the issue online.