[
https://issues.apache.org/jira/browse/SLING-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974327#comment-14974327
]
Stefan Egli commented on SLING-5196:
------------------------------------
Can we live with using maven-bundle-plugin 2.5.3 for now, or is there an urgent
need to have 3.0.0? or in other words: can this ticket be closed leaving it at
2.5.3?
> 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.2.0, 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)
