[ 
https://issues.apache.org/jira/browse/SLING-11877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert updated SLING-11877:
-----------------------------------
    Description: 
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.

  was:
update to latest JCR Mock and OSGi Mock dependency.

normally we do not create issues for just updating this dependency - but the 
last release 3.4.8 or sling-mock accidentally contained SNAPSHOT references to 
those dependencies, so we create this issue for documentation purposes.

        Summary: sling-mock: Manage References in a more release-friendly way  
(was: sling-mock: Update to last JCR Mock and OSGi Mock)

> 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)

Reply via email to