Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Wed, 11 May 2011 22:48:48 +0000 (UTC)
From: "David Jencks (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: 
 <423494747.5230.1305154128048.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <30463790.259271296199063634.JavaMail.jira@thor>
Subject: [jira] [Commented] (KARAF-424) Maven packaging for feature, kar,
 karaf-assembly; mojos based on geronimo server assemblies
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=13032148#comment-13032148 ] 

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

There's something odd about aethers handling of "provided" scope dependencies.  The javadoc implies that 

            CollectRequest collectRequest = new CollectRequest(new Dependency(artifact, "compile"), null, projectRepos);
            DefaultRepositorySystemSession session = new DefaultRepositorySystemSession(repoSession);

will act like maven and the direct provided scope dependencies of the supplied artifact will be included in the result, but they are not.  For geronimo use of the DependencyHelper I need them to be.  In karaf we should look into this further.


> 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
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira