[
https://issues.apache.org/jira/browse/SLING-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722755#comment-17722755
]
Stefan Seifert commented on SLING-11877:
----------------------------------------
https://github.com/apache/sling-org-apache-sling-testing-sling-mock/commit/ca5de3f8f5134f90e2c87193e9befa211460424d
restructured the usage of the version propeties so that they are only
references inside the parent POM. unfortunately maven-release-plugin still does
not update them correctly on auto-resolving of dependencies via the
maven-release-plugin, so that features should not be used when releasing
sling-mock. we could eliminate that version properties completely, but at least
for osgi-mock we reference two artifacts from osgi-mock, and it might be
forgotten to update both of them.
> sling-mock: Manage References in a more release-friendly way
> ------------------------------------------------------------
>
> Key: SLING-11877
> URL: https://issues.apache.org/jira/browse/SLING-11877
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: Testing Sling Mock 3.4.8
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Testing Sling Mock 3.4.10
>
>
> the last release 3.4.8 or sling-mock contained SNAPSHOT references in the
> properties that define them in the parent POM:
> https://repo1.maven.org/maven2/org/apache/sling/org.apache.sling.testing.sling-mock.parent/3.4.8/org.apache.sling.testing.sling-mock.parent-3.4.8.pom
> but the actual references in the other modules do no longer use that
> properties, so from a maven-perspective the version are fine. it seems those
> property references are removed automatically by the release plugin, we
> should change the notation in a way that is compatible with automatic updates
> by the release plugin.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
