[
https://issues.apache.org/jira/browse/SLING-8197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735555#comment-16735555
]
Stefan Seifert commented on SLING-8197:
---------------------------------------
sorry, that was my fault for introducing this issue. i was under the false
assumption that the [Felix SCR bnd
plugin|http://repo1.maven.org/maven2/org/apache/felix/org.apache.felix.scr.bnd/]
was configured by default in the parent POM, should have checked that better.
bq. Do you think we should not only ban maven-scr-plugin but also the Felix SCR
Annotations dependencies in the newest parent?
i first thought let's add the Felix SCR bnd plugin to make upading to the
latest Parent POM easier. but as we have recently switched from
maven-bundle-plugin to bnd-maven-plugin and this involves some manual migration
for each project anyway it may be the best solution to also ban the Felix SCR
annotations to have a clean cut.
> Tenant Package 1.1.2 is missing OSGI-INF folder and the Tenant Provider /
> Manager services are not activated
> ------------------------------------------------------------------------------------------------------------
>
> Key: SLING-8197
> URL: https://issues.apache.org/jira/browse/SLING-8197
> Project: Sling
> Issue Type: Bug
> Components: Extensions
> Affects Versions: Tenant 1.1.2
> Reporter: Andreas Schaefer
> Assignee: Carsten Ziegeler
> Priority: Critical
> Fix For: Tenant 1.1.4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The version 1.1.2 released on 9/2 is missing the OSGI-INF folder when built
> due to the missing 'maven-scr-plugin' in the POM. This version was included
> into the AEM M3 build and so M3 is missing the tenant service (Tenant
> Provider / Manager).
> It would be great if 1.1.1 could be released so that the next Load contains a
> proper tenant package.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
