sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bertrand Delacretaz (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-6675) Sling parent pom 30 breaks o.a.s.engine bundle - empty SCR metadata
Date Mon, 20 Mar 2017 15:36:41 GMT

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

Bertrand Delacretaz commented on SLING-6675:
--------------------------------------------

SLING-6649 has a workaround but best would be to update the SlingMainServlet to the {{org.osgi}}
SCR annotations instead of the old {{org.apache.felix}} ones.

> Sling parent pom 30 breaks o.a.s.engine bundle - empty SCR metadata
> -------------------------------------------------------------------
>
>                 Key: SLING-6675
>                 URL: https://issues.apache.org/jira/browse/SLING-6675
>             Project: Sling
>          Issue Type: Bug
>          Components: Engine
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
>
> For now I'll revert the bundles/engine pom to use our parent pom 29 as with the current
version 30 the generated {{org.apache.sling.engine.impl.SlingMainServlet.xml}} is empty.
> The visible effects are Sling returning a 404 on all requests, as the SlingMainServlet
is not registered and the default OSGi HTTP service gets the request.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message