On Tue, Jun 16, 2015 at 11:39 AM, Carsten Ziegeler <[email protected]> wrote: > Am 16.06.15 um 11:19 schrieb Bertrand Delacretaz: >>... That doesn't work for my contrib/crankstart/test-model model - as you >> say it's the main artifact of that module so it's deployed without the >> "slingfeature" type or classifier, it's just a "txt" type artifact. > > That happens if you're not using Maven :) > > Maven has a mapping for slingfeature -> txt for the extension
Ah ok, defined in the last two <component> elements here, right? https://svn.apache.org/repos/asf/sling/trunk/tooling/maven/slingstart-maven-plugin/src/main/resources/META-INF/plexus/components.xml > ...I suggest you do the same mapping as maven does, it's really a simple > type mapping for two types (slingfeature and slingstart).... Considering all artifacts having the "txt" type as being of the "slingfeature" type? That would work. Considering all "jar" as being "slingstart" wouldn't work as the jar artifacts that Crankstart uses are supposed to be bundles, but I don't think I need that at the moment. -Bertrand
