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

Konrad Windszus edited comment on SLING-5648 at 11/30/18 11:36 AM:
-------------------------------------------------------------------

For  me with Eclipse 2018-09 (4.9.0) the copy mechanism for Manifest and 
Component descriptors does not work reliably. Very often the folder 
{{META-INF}} and {{OSGI-INF}} in the project's root are just plain empty 
(although in {{target/classes}} both folder are there and not empty. Could not 
find any related log entry though. Sometimes it works, other times it doesn't. 
[~rombert] Did you notice a similar thing? E.g. when freshly importing those 
projects in Eclipse?
Could be related to a timing issue, but in general bnd-maven-plugin should 
execute in phase {{process-classes}} while 
{{maven-resource-plugin:copy-resources}} is configured to run in phase 
{{process-test-resources}}.

Update: One more observation, in case this happens the folder META-INF and 
OSGI-INF is shortly filled with the correct files but they are afterwards 
removed by some step. So it definitely is some step after 
{{maven-resource-plugin:copy-resources}} responsible for that behaviour. Might 
be even outside the Maven Build...


was (Author: kwin):
For  me with Eclipse 2018-09 (4.9.0) the copy mechanism for Manifest and 
Component descriptors does not work reliably. Very often the folder 
{{META-INF}} and {{OSGI-INF}} in the project's root are just plain empty 
(although in {{target/classes}} both folder are there and not empty. Could not 
find any related log entry though. Sometimes it works, other times it doesn't. 
[~rombert] Did you notice a similar thing? E.g. when freshly importing those 
projects in Eclipse?
Could be related to a timing issue, but in general bnd-maven-plugin should 
execute in phase {{process-classes}} while 
{{maven-resource-plugin:copy-resources}} is configured to run in phase 
{{process-test-resources}}.

> Make Non-Eclipse Module regular Maven Packages
> ----------------------------------------------
>
>                 Key: SLING-5648
>                 URL: https://issues.apache.org/jira/browse/SLING-5648
>             Project: Sling
>          Issue Type: Improvement
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.10
>            Reporter: Andreas Schaefer
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Sling Eclipse IDE 1.2.4
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Non Eclipse modules like api, artifacts, imll-resource, impl-vlt should be 
> regular Maven packages (jar) instead of eclipse plugins (eclipse-plugin) to 
> support development of it by other IDEs like IntelliJ IDEA.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to