sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-7302) slingstart-maven-plugin: Also consider the project's version itself in the PomArtifactVersionResolver
Date Wed, 13 Dec 2017 08:43:00 GMT

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

Konrad Windszus commented on SLING-7302:
----------------------------------------

Merged PR in https://github.com/apache/sling-slingstart-maven-plugin/commit/edb2a7a2f47f4e8a1d03a888cc52a1342094ae61.

> slingstart-maven-plugin: Also consider the project's version itself in the PomArtifactVersionResolver
> -----------------------------------------------------------------------------------------------------
>
>                 Key: SLING-7302
>                 URL: https://issues.apache.org/jira/browse/SLING-7302
>             Project: Sling
>          Issue Type: Improvement
>          Components: Maven Plugins and Archetypes
>    Affects Versions: Slingstart Maven Plugin 1.7.10
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>             Fix For: Slingstart Maven Plugin 1.7.12
>
>
> In the context of using provisioning models with ITs it is often useful to package the
current bundle into the launchpad. Currently the parameter {{usePomDependencies}} does not
help though to make it possible to not duplicate the current maven module's version in the
model file again, as the {{PomArtifactVersionResolver}} only considers versions being set
explicitly either in project dependencies or in the dependencyManagement. I propose to also
evaluate the current maven project's version.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message