You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/10/26 16:05:27 UTC
[jira] [Updated] (SLING-5196) missing dependency when using
maven-bundle-plugin 3.0.0 in discovery.base and discovery.impl
[ https://issues.apache.org/jira/browse/SLING-5196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Egli updated SLING-5196:
-------------------------------
Summary: missing dependency when using maven-bundle-plugin 3.0.0 in discovery.base and discovery.impl (was: missing dependency when using maven-bundle-plugin 3.0.0 in discovery.base)
> missing dependency when using maven-bundle-plugin 3.0.0 in discovery.base and discovery.impl
> --------------------------------------------------------------------------------------------
>
> 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)