hmm, those inconsistencies were newly introduced with the latest version. although the one has "provided" scope and the other "test" scope, it has effect on the package version selected by the bnd plugin for depending on the service user mapper dependency. it seems to have picked automatically the newer version which may be fine.
i'm +0 on it, problem is not serious enough to block the release, but publishing POMs with inconsistencies to maven central is bad practice. stefan >-----Original Message----- >From: Stefan Egli <stefane...@apache.org> >Sent: Tuesday, April 13, 2021 12:01 PM >To: dev@sling.apache.org >Subject: Re: [VOTE] Release Apache Sling Event Support 4.2.16 > >Hi Stefan, > >Good point, I created SLING-10300 to follow up. > >What's your vote for 4.2.16? > >Cheers, >Stefan > >On 12.04.21 22:41, Stefan Seifert wrote: >> the dependencies defined for the project are inconsistent - as reported >by maven: >> >> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' >must be unique: org.apache.sling:org.apache.sling.serviceusermapper:jar -> >version 1.2.0 vs 1.4.6 @ line 357, column 21 >> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' >must be unique: org.apache.felix:org.apache.felix.framework:jar -> version >5.6.2 vs 6.0.3 @ line 377, column 21 >> >> >> stefan >>
