[
https://issues.apache.org/jira/browse/SLING-8038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656360#comment-16656360
]
ASF GitHub Bot commented on SLING-8038:
---------------------------------------
cziegeler commented on issue #13: SLING-8038 - Allow the Repository MOJO
specify including features from CLI
URL:
https://github.com/apache/sling-slingfeature-maven-plugin/pull/13#issuecomment-431268901
It's a little bit hard to follow what exactly has changed. Maybe you could
redo the patch without moving code out of the existing class first. We can
later on then rename this class to AbstractXYZ
The new mojo should not be bound to any lifecycle phase, otherwise it's not
usable outside of a maven project.
In addition the only parameter it should get are mvn coordinates for the
feature, no includes, no directory etc.
The mvn coordinates can be parsed with the existing code in ArtifactId
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Allow the Repository MOJO specify including features from CLI
> -------------------------------------------------------------
>
> Key: SLING-8038
> URL: https://issues.apache.org/jira/browse/SLING-8038
> Project: Sling
> Issue Type: Improvement
> Reporter: Simone Tripodi
> Priority: Major
>
> The is a need of creating a standalone Repository, the {{RepositoryMojo}}
> does already that job, BUT requirement is having a tool which can be easily
> invoked from CLI (where the
> {{org.apache.sling.feature.maven.mojos.DependencyLifecycleParticipant}} is
> not invoked due to the fact that plugin extensions could not be enabled).
> PS is coming
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
