[
https://issues.apache.org/jira/browse/SLING-5369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057856#comment-15057856
]
Oliver Lietz commented on SLING-5369:
-------------------------------------
[~bdelacretaz], [~joelrich] asked for releasing Commons Testing (SLING-5341). I
think we should keep the version of JUnit across Sling in sync, which means
updating {{parent}} to {{4.12}} also before doing a release of Commons Testing.
Is updating to {{4.12}} ok? Btw, the embedded JUnit causes havoc when running
Lauchpad ITs against Karaf (SLING-3821), see
[PAXEXAM-723|https://ops4j1.jira.com/browse/PAXEXAM-723].
> Update to JUnit 4.12
> --------------------
>
> Key: SLING-5369
> URL: https://issues.apache.org/jira/browse/SLING-5369
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: JUnit Core 1.0.14
> Reporter: Thierry Ygé
>
> Currently JUnit Core is based on JUnit 4.11, in SLING-5352, some improvement
> could benefit from the enhancement implemented in JUnit 4.12 related to
> possibility to combine both ClassRule and Rule annotation for a static field.
> That would be a great help to simplify the use case discussed in SLING-5352.
> simply update the version on the pom.xml would be sufficient.
> from 4.11
> {noformat}
> ...
> <properties>
> <junit.version>4.11</junit.version>
> <hamcrest.version>1.3</hamcrest.version>
> <jacoco.version>0.6.2.201302030002</jacoco.version>
> </properties>
> ...
> {noformat}
> to 4.12
> {noformat}
> ...
> <properties>
> <junit.version>4.12</junit.version>
> <hamcrest.version>1.3</hamcrest.version>
> <jacoco.version>0.6.2.201302030002</jacoco.version>
> </properties>
> ...
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
