[
https://issues.apache.org/jira/browse/SLING-8541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894051#comment-16894051
]
Andreas Schaefer commented on SLING-8541:
-----------------------------------------
Not sure I want another folder to deal with.
I uploaded a solution in my branch of
[https://github.com/apache/sling-slingfeature-maven-plugin/tree/merge-cpconverter-plugin.]
This moved the code into the ProjectHelper which will do the checks. Then I
created an abstract base mojo that all mojos here implement and in there
provide a method to check the project if a re-parsing is needed. It also checks
if the execution order is correct. If a FM generation Mojo is called after a
Handling Mojo (aggregate, attach etc) is executed then it throws an exception.
I tried to put the Environment instance onto the Maven Project but that fails
because of class loading issues between the DLP and the Mojo execute() method.
Let me know if that works for you.
> slingfeature-maven-plugin should allow for generated feature model files
> ------------------------------------------------------------------------
>
> Key: SLING-8541
> URL: https://issues.apache.org/jira/browse/SLING-8541
> Project: Sling
> Issue Type: New Feature
> Components: Feature Model
> Affects Versions: slingfeature-maven-plugin 1.0.4
> Reporter: Andreas Schaefer
> Priority: Major
> Fix For: slingfeature-maven-plugin 1.0.6
>
>
> The Sling Feature Maven Plugin is checking that the feature model folder is
> containing feature model files when the plugin is started.
> This fails when the FM are generated prior to the execution of the Sling
> Feature Maven Plugin. This check should be either made optional or moved
> prior to the actual execution of the Plugin's goal.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
