[
https://issues.apache.org/jira/browse/SLING-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus updated SLING-7302:
-----------------------------------
Description: 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. (was: In the context of
using 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 version
being set explicitly either in project dependencies or in the
dependencyManagement. I propose to in addition also evaluate the current maven
projects version.)
> 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)
