karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Moquin (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KARAF-2127) Create a KAR artifact for the Cellar features
Date Fri, 18 Jan 2013 14:10:13 GMT
Ryan Moquin created KARAF-2127:

             Summary: Create a KAR artifact for the Cellar features
                 Key: KARAF-2127
                 URL: https://issues.apache.org/jira/browse/KARAF-2127
             Project: Karaf
          Issue Type: Improvement
          Components: cellar-core
    Affects Versions: cellar-3.0.0
         Environment: Windows 8 64-bit
            Reporter: Ryan Moquin

When I was trying to build a custom Karaf distribution that includes Cellar already installed
to eliminate having to manually install it, I ran into a lot of trouble.  Basically it boiled
down to the fact that no matter what I did, the configfile entries in the features xml were
not getting added to the /etc of the distribution.  The karaf-maven-plugin is supposed to
add them, but I don't think it still does in all situations.  Anyhow, the way I had to work
around it was to use the karaf-maven-plugin to create a kar file in the assembly sub-project.
 I also had to move and rename the configuration files otherwise they are not added to the
kar file in the proper location so that they'll install correctly.  Check out this commit
in my repo to see what I did and decide if you want to do the same thing or if there is a
way to achieve the same thing but in a more preferred way (or if it is a karaf-maven-plugin,
then fixing that).  I tried to make a pull request, but I kept goofing on making a branch
that merged in only certain related changes.  The only other thing in this commit is related
to the previous bug I filed, so just ignore those:


You only really need to look at anything in the assembly project that changed, which are mostly
just the renamed resources.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message