[
https://issues.apache.org/jira/browse/SLING-8034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655015#comment-16655015
]
ASF GitHub Bot commented on SLING-8034:
---------------------------------------
simonetripodi commented on issue #12: SLING-8034 - SlingStart-m-p and
SlingFeature-m-p packagetype clash
URL:
https://github.com/apache/sling-slingfeature-maven-plugin/pull/12#issuecomment-430956650
@bosschaert updated, but I would like to have a better test on a wider
project: while all tests pass on build, looks like some "old" `slingfeature`
are now resolved as `txt`... could you wait me a little, please, before merging
the modifications? TIA! :)
----------------------------------------------------------------
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]
> SlingStart-m-p and SlingFeature-m-p packagetype clash
> -----------------------------------------------------
>
> Key: SLING-8034
> URL: https://issues.apache.org/jira/browse/SLING-8034
> Project: Sling
> Issue Type: Improvement
> Components: Maven Plugins and Archetypes
> Reporter: Simone Tripodi
> Assignee: David Bosschaert
> Priority: Major
>
> Both MOJOs use the same _slingfeature_ package type - SlingStart-m-p should
> keep the defined package type while SlingFeature-m-p's should be changed,
> i.e. {{slingosgifeature}}.
> PR is coming
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
