You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Andreas Schaefer (JIRA)" <ji...@apache.org> on 2019/08/15 18:02:00 UTC
[jira] [Commented] (SLING-8630) Converter must not replace existing
POM files
[ https://issues.apache.org/jira/browse/SLING-8630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908363#comment-16908363 ]
Andreas Schaefer commented on SLING-8630:
-----------------------------------------
Created PR for the change in the CP Converter: https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/16
> Converter must not replace existing POM files
> ---------------------------------------------
>
> Key: SLING-8630
> URL: https://issues.apache.org/jira/browse/SLING-8630
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
> Reporter: Andreas Schaefer
> Assignee: Andreas Schaefer
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When the output folder for the converted feature is set to the local Maven repo (~/.m2/repository) then an existing POM is overwritten by the converter with the generated one. This can and will change the behavior of Maven for other projects. So, if a POM file exists then it should not be replaced and even if the existing POM is the generated it is not necessary as this file should not change otherwise the POM will be placed somewhere else.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)