[ 
https://issues.apache.org/jira/browse/SLING-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14239201#comment-14239201
 ] 

Konrad Windszus commented on SLING-4226:
----------------------------------------

{quote}
when i run the IT with 8-SNAPSHOT i make sure that models api and impl are 
compiled and installed to my lokal maven repo, and then clean and install the 
integration test. then the lastest api and impl bundles are deployed together 
with 8-SNAPSHOT launchpad and all runs as expected.
{quote}
This is not enough. You have to compile the launchpad on your own, because that 
one contains the models api and models impl already.
Can you reproduce the problem with the attached patch?

> Wrong wiring of the bundle Models Impl in the Models IT
> -------------------------------------------------------
>
>                 Key: SLING-4226
>                 URL: https://issues.apache.org/jira/browse/SLING-4226
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Sling Models Implementation 1.1.0
>            Reporter: Konrad Windszus
>         Attachments: SLING-4226.patch
>
>
> The Sling Models IT deploys a new version of Sling Models API and Sling 
> Models Impl. The Sling Launchpad 8-SNAPSHOT already contains those bundles in 
> the version 1.1.1-SNAPSHOT.
> After the deployment of the newer Models bundles the Sling Models Impl bundle 
> is connected to both the old and the new API bundle.
> To reproduce just apply the attached patch to the Sling Models IT, run {{mvn 
> install}} on that module and open Models Impl Bundle in the Felix Webconsole.
> Now the imported packages section looks like
> {code}
> javax.annotation,version=0.0.0.1_007_JavaSE from org.apache.felix.framework 
> (0)
> javax.inject,version=0.0.0 from org.apache.sling.models.api (117)
> javax.servlet,version=2.6.0 from org.apache.felix.http.servlet-api (24)
> javax.servlet,version=3.0.0 from org.apache.felix.http.servlet-api (24)
> javax.servlet.http,version=2.6.0 from org.apache.felix.http.servlet-api (24)
> javax.servlet.http,version=3.0.0 from org.apache.felix.http.servlet-api (24)
> org.apache.commons.collections.comparators,version=3.2.1 from 
> org.apache.commons.collections (60)
> org.apache.commons.collections.keyvalue,version=3.2.1 from 
> org.apache.commons.collections (60)
> org.apache.commons.collections.list,version=3.2.1 from 
> org.apache.commons.collections (60)
> org.apache.commons.collections.set,version=3.2.1 from 
> org.apache.commons.collections (60)
> org.apache.commons.lang,version=2.6.0 from org.apache.commons.lang (64)
> org.apache.commons.logging,version=1.1.1 from jcl.over.slf4j (1)
> org.apache.sling.api,version=2.3.0 from org.apache.sling.api (71)
> org.apache.sling.api.adapter,version=2.2.0 from org.apache.sling.api (71)
> org.apache.sling.api.resource,version=2.6.0 from org.apache.sling.api (71)
> org.apache.sling.api.scripting,version=2.1.0 from org.apache.sling.api (71)
> org.apache.sling.commons.osgi,version=2.2.0 from 
> org.apache.sling.commons.osgi (78)
> org.apache.sling.models.annotations,version=1.2.0 from 
> org.apache.sling.models.api (117)
> org.apache.sling.models.annotations.injectorspecific,version=1.1.0 from 
> org.apache.sling.models.api (117)
> org.apache.sling.models.factory,version=1.0.0 from 
> org.apache.sling.models.api (114)
> org.apache.sling.models.spi,version=1.0.2 from org.apache.sling.models.api 
> (114)
> org.apache.sling.models.spi.injectorspecific,version=1.1.0 from 
> org.apache.sling.models.api (117)
> org.osgi.framework,version=1.7.0 from org.apache.felix.framework (0)
> org.osgi.service.component,version=1.2.1 from org.apache.felix.scr (40)
> org.slf4j,version=1.7.6 from slf4j.api (15)
> {code}
> You see that both the old (114) and the new version (117) of sling.models.api 
> is bound.
> Due to bug SLING-3819 I updated the dependency of the testing tools to 
> 1.0.9-SNAPSHOT. Compare also with 
> http://www.mail-archive.com/[email protected]/msg40336.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to