[ https://issues.apache.org/jira/browse/SLING-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974245#comment-14974245 ]
Stefan Egli commented on SLING-5196: ------------------------------------ [~cziegeler], using 3.0.0 it explicitly puts the {{[2.6,3)}} dependency: {code} Import-Package: javax.crypto,javax.crypto.spec,javax.servlet;version="[2 .6,3)",javax.servlet.http;version="[2.6,3)",org.apache.commons.codec.bi nary;version="[1.6,2)" ..... {code} while using 2.5.2 it leaves out the version criteria: {code} Import-Package: javax.crypto,javax.crypto.spec,javax.servlet,javax.servl et.http,org.apache.commons.codec.binary {code} > missing dependency when using maven-bundle-plugin 3.0.0 in discovery.base > ------------------------------------------------------------------------- > > Key: SLING-5196 > URL: https://issues.apache.org/jira/browse/SLING-5196 > Project: Sling > Issue Type: Bug > Components: Extensions > Reporter: Stefan Egli > Assignee: Stefan Egli > Fix For: Discovery Impl 1.1.10, Discovery Base 1.0.0 > > > When using the default maven-bundle-plugin version inherited from parent (25 > atm), which is 3.0.0, then the following dependencies cannot be resolved in > AEM 5.6.1: > {code} > javax.servlet,version=[2.6,3) -- Cannot be resolved > javax.servlet.http,version=[2.6,3) -- Cannot be resolved > org.apache.commons.codec.binary,version=[1.6,2) -- Cannot be resolved > {code} > thus switching back to 2.5.3 for discovery.base to remain > backwards-compatibility -- This message was sent by Atlassian JIRA (v6.3.4#6332)