You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2017/03/20 15:14:41 UTC

[jira] [Commented] (SLING-6675) Sling parent pom 30 breaks o.a.s.engine bundle

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

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

Reverted to parent pom 29 in revision 1787792, and also changed launchpad/builder to use the o.a.s.engine snapshot to expose the issue.

> Sling parent pom 30 breaks o.a.s.engine bundle
> ----------------------------------------------
>
>                 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)