[
https://issues.apache.org/jira/browse/SLING-6675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933331#comment-15933331
]
Oliver Lietz commented on SLING-6675:
-------------------------------------
We should have at least one IT per bundle to check if its services come up. I
did several full builds but didn't notice that Sling Engine was broken. Sorry
for that.
> 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)
