Hi,
moving this code out of the DependencyLifecycleParticipant will break
some functionality. A DependencyLifecycleParticipant is run *before* any
mojos and allwos to add dependencies to projects. We use this to add the
artifacts from the feature files as dependencies to the maven project in
order to use mavens dependency mechanism. For example this allows to use
mavens mechanism to check for updates of artifacts etc.
If we speak about the converter, I guess the problem is that the
converter runs too late. So maybe we should rather fix that?
Regards
Carsten
Andreas Schaefer 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 <[email protected]> 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
--
Carsten Ziegeler
Adobe Research Switzerland
[email protected]
