Return-Path: 
 <issues-return-1159-apmail-karaf-issues-archive=karaf.apache.org@karaf.apache.org>
Delivered-To: apmail-karaf-issues-archive@minotaur.apache.org
Received: (qmail 55841 invoked from network); 8 Dec 2010 06:45:29 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 8 Dec 2010 06:45:29 -0000
Received: (qmail 3026 invoked by uid 500); 8 Dec 2010 06:45:28 -0000
Delivered-To: apmail-karaf-issues-archive@karaf.apache.org
Received: (qmail 2992 invoked by uid 500); 8 Dec 2010 06:45:27 -0000
Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@karaf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@karaf.apache.org>
List-Post: <mailto:issues@karaf.apache.org>
List-Id: <issues.karaf.apache.org>
Reply-To: issues@karaf.apache.org
Delivered-To: mailing list issues@karaf.apache.org
Received: (qmail 2980 invoked by uid 99); 8 Dec 2010 06:45:26 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Dec 2010 06:45:26 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Dec 2010 06:45:24 +0000
Received: from thor (localhost [127.0.0.1])
	by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oB86j2p0012124
	for <issues@karaf.apache.org>; Wed, 8 Dec 2010 06:45:02 GMT
Message-ID: <33270948.10921291790702355.JavaMail.jira@thor>
Date: Wed, 8 Dec 2010 01:45:02 -0500 (EST)
From: "Andreas Pieber (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Subject: [jira] Commented: (KARAF-165) A better 'feature-assembly' plugin
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Andreas Pieber commented on KARAF-165:
--------------------------------------

ok, the name of this issue is quite general but the specific request is already fixed, isn't it?

> A better 'feature-assembly' plugin
> ----------------------------------
>
>                 Key: KARAF-165
>                 URL: https://issues.apache.org/jira/browse/KARAF-165
>             Project: Karaf
>          Issue Type: New Feature
>    Affects Versions: 2.1.0
>            Reporter: Adrian Trenaman
>            Assignee: Adrian Trenaman
>
> Create an improved Maven feature-assembly plugin. Right now, to make a feature I've got to add almost a hundred lines of Maven verbage to my pom.xml in order to assemble a feature. I've got to use the attach-artifact goal of the org.codehaus.mojo/build-helper-maven-plugin to deploy my features file into Maven. I've got to use the add-features-to-repo goal from the org.apache.karaf.tooling/features-maven-plugin to suck down all the dependent bundles. I've got to a whole load of other stuff to perform the packaging to .tar.gz and .zip. The problem here is that I'm using a whole load of generic plugins to do a very specific job, and I'm having to tell the plugins what to do instead of telling them what I want done. I'd prefer to have a single more declarative plugin to do this. It might look like this:  
> {code:xml}
> 			<plugin>
> 				<groupId>org.apache.karaf.tooling</groupId>
> 				<artifactId>feature-assembly-plugin</artifactId>
> 				<version>2.2.0</version>
> 				<executions>
> 					<execution>
> 						<id>create-repo</id>
> 						<phase>generate-resources</phase>
> 						<goals>
> 							<goal>create-repo</goal>
> 						</goals>
> 						<configuration>
> 							<!-- Specify the feature file to use. -->
> 							<featureFile>file:${basedir}/target/classes/features.xml</featureFile>
> 	
> 							<!-- Specify what features to include. This is actually optional: if no features
> 								are specified, then include all features in the file by default. --> 
> 							<features>
> 								<feature>feature-a</feature>
> 							</features>
> 						</configuration>
> 					</execution>
> 				</executions>
> 			</plugin>
> {code}
> The plugin should produce a .tar.gz and .zip file, containing the feature descriptor (and all dependent descriptors) and all bundles (and dependent bundles)in a Maven-style directory, similar to the system/ directory currently used in Karaf. Note that this plugin doesn't need you to list out all the feature repositories / descriptors that your feature file may transitively include - it will detect these dependencies at runtime and work out the details.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.