[
https://issues.apache.org/jira/browse/SLING-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807813#comment-13807813
]
Robert Munteanu commented on SLING-3209:
----------------------------------------
What I can think of is inspecting the MANIFEST.MF and looking for a
Service-Component header . If that header exists, ensure that it matches
something in the project output directory. Of course, things can get hairy if
we have a header which is {{OSGI-INF/*.xml}} .
I'm not sure that this is 100% correct, but that's what we can do and is
pretty much agnostic to how the application is assembled. This can be only one
of the pre-deployment rules that we have, as I think there is more to be done
in the future.
> Deploying files via "Install bundles directly from local directory" does not
> work properly
> ------------------------------------------------------------------------------------------
>
> Key: SLING-3209
> URL: https://issues.apache.org/jira/browse/SLING-3209
> Project: Sling
> Issue Type: Bug
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.0.0
> Reporter: Maciej Matuszewski
> Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> If you specify how to install artifacts to the launchpad instance as Install
> bundles directly from local directory, application crushes. This is caused by
> not sending all required data e.g. OSGI-INF content.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
