You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2011/01/28 08:17:43 UTC

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

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.


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

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guillaume Nodet updated KARAF-424:
----------------------------------

    Affects Version/s:     (was: 2.2.0)
        Fix Version/s:     (was: 2.2.0)
                       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: 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

        

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

Posted by "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

        

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

Posted by "Andreas Pieber (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Pieber updated KARAF-424:
---------------------------------

    Fix Version/s:     (was: 3.1.0)
                   3.0.0

moved again to 3.0.0 as "representation" of the "profile issue

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

        

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

Posted by "David Jencks (JIRA)" <ji...@apache.org>.
    [ 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

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

Posted by "David Jencks (JIRA)" <ji...@apache.org>.
    [ 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.


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

Posted by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/KARAF-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofré updated KARAF-424:
---------------------------------------

    Fix Version/s:     (was: 3.0.0)
                   3.1.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: 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira