Am 15.06.15 um 15:18 schrieb Bertrand Delacretaz:
> On Mon, Jun 15, 2015 at 3:12 PM, Carsten Ziegeler <[email protected]>
> wrote:
>> Your packaging is slingfeature, so this in the main artifact - in maven
>> you usually don't use a classifier for the main artifact..
>
> Ah ok, thanks - the problem is that Crankstart needs to know that that
> artifact is a slingfeature, based on its Maven coordinates, what's the
> best way to do that?
>
> Other utilities working with provisioning model artifacts might have
> the same requirement - you get a bunch of Maven artifact URLs and need
> to sort them out into bundles, Sling provisioning models, etc.
>
Yes, that's what the type is used for, so in your model you have
{groupId}/{artifactId}/{version}/slingfeature
This is what the slingstart maven plugin is searching for.
It also handles
{groupId}/{artifactId}/{version}/slingstart
As the main artifact for a slingstart is the jar, the maven plugin
automatically sets the classifier to "slingfeature" in this case.
Makes it very easier to use in the provisioning model.
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
