You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/11/01 15:15:00 UTC

[jira] [Commented] (SLING-8034) SlingStart-m-p and SlingFeature-m-p packagetype clash

    [ https://issues.apache.org/jira/browse/SLING-8034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16671730#comment-16671730 ] 

ASF GitHub Bot commented on SLING-8034:
---------------------------------------

bosschaert closed pull request #12: SLING-8034 - SlingStart-m-p and SlingFeature-m-p packagetype clash
URL: https://github.com/apache/sling-slingfeature-maven-plugin/pull/12
 
 
   

----------------------------------------------------------------
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:
users@infra.apache.org


> 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
>             Fix For: slingfeature-maven-plugin 1.0.0
>
>
> 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)