[
https://issues.apache.org/jira/browse/SLING-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-11877.
------------------------------------
Resolution: Fixed
https://github.com/apache/sling-org-apache-sling-testing-sling-mock/commit/97792b3703e246d2ac3f3bc6ba41ef20a18751e8
after thinking over it the risk for using the automatic snapshot version
resolving and not being aware of this issue is probably bigger and creates more
follow-up confusion than the risk for forgetting to update two artifact
dependencies in case of osgi-mock dependency update.
so i eliminated the usage of version properties here altogether, and moved the
block with the related dependency definitions to the top of the parent POM.
> 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)
