Hi
I committed my changes to sling-slingfeature-maven-plugin branch:
merge-cpconverter-plugin.
With these changes I was able to convert Sling Starter Provisioning and
Headwire’s Peregrine Content Packages into a feature launcher system in one
maven built step (mvn clean install) and launch it successfully.
There are still a few things I need to iron out but this is a good starting
point I think.
Cheers - Andy Schaefer
> On Jul 16, 2019, at 4:36 PM, Andreas Schaefer <schaef...@me.com.INVALID>
> wrote:
>
> Hi
>
> I found a solution by moving the code into the Mojos. The entire code is now
> here:
>
> AbstractFeatureMojo.prepareProject()
>
> And all Mojos interested can call them at the beginning of the execute()
> method.
>
> This way my Mojo can work w/o any features present and w/o having issues
> during the different phases and goals.
>
> Let me know if that is an acceptable solution.
>
> Cheers - Andy Schaefer
>
>> On Jul 16, 2019, at 7:50 AM, Andreas Schaefer <schaef...@me.com.INVALID>
>> wrote:
>>
>> Hi Simone
>>
>> I ran into a snafu with the Sling Feature Maven Plugin. This plugin is doing
>> a blank check during the initialization phase which is causing headaches for
>> the CP Converter goal.
>>
>> There are various issues but the most glaring is the fact that when I use
>> placeholders in the FM id like "${project.groupId}” then it will fail to
>> even clean the project with ‘mvn clean’ or when there is no feature at all.
>>
>> Can we either disable these tests or move them in the respective Mojos
>> (phase) ?
>>
>> Cheers - Andy Schaefer
>
