[
https://issues.apache.org/jira/browse/SLING-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15602373#comment-15602373
]
Konrad Windszus commented on SLING-4031:
----------------------------------------
Although not explicitly checked, there are some implicit checks for the m2e
project importers for bundles which should assure that the pom.xml is properly
configured (committed with SLING-6112).
The question is whether we need something in addition to support non-Maven
projects and whether there should be an explicit check for the MANIFEST.MF. For
the latter we need to leverage the right trigger for that (after the build was
successful). This is not supported through the WST Validation framework AFAIK,
because this is only triggered when an individual file has been touched (not
necessarily after the build finished).
> Missing MANIFEST.MF should be a validation error
> ------------------------------------------------
>
> Key: SLING-4031
> URL: https://issues.apache.org/jira/browse/SLING-4031
> Project: Sling
> Issue Type: Test
> Components: IDE
> Affects Versions: Sling Eclipse IDE 1.0.2
> Reporter: Robert Munteanu
> Priority: Minor
> Fix For: Sling Eclipse IDE 1.1.2
>
>
> I just noticed a warning on the Sling console when a bundle was rebuilt
> {quote}[October 11, 2014 2:09:53 AM EEST] InstallBundle ->
> /home/ADOBENET/rmuntean/Downloads/import/myproject/components/target/classes
> : Project P/myproject.components does not have a META-INF/MANIFEST.MF (yet) -
> not publishing this time (0 ms)
> {quote}
> This should be a validation error and block publishing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
