[FELIX-2948] scr-maven-plugin fails with org.maven.ide.eclipse plugin (exploded bundle)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: maven-scr-plugin-1.7.0, scr ant task 1.1.0, scr generator 1.1.0
• Fix Version/s: maven-scr-plugin-1.7.2, scr ant task 1.1.2, scr generator 1.1.2
• Component/s: SCR Tooling
• Assignee: Carsten Ziegeler
• Reporter: Andrei Pozolotin
• Created: 13/May/11 00:19
• Updated: 28/Jul/11 08:54
• Resolved: 19/May/11 06:00

Description

scr-maven-plugin fails with org.maven.ide.eclipse plugin (exploded bundle)

1) when you run scr-maven-plugin in the eclipse ide with m2e plugin
then it seems at first to work fine:

a) import this project in the eclipse with help of m2e:
https://github.com/carrot-garden/carrot-bugger/tree/master/carrot-bug-scr-maven-plugin-001

b) and run "eclipse -> project -> clean"; it produces this success log:
https://github.com/carrot-garden/carrot-bugger/blob/master/carrot-bug-scr-maven-plugin-001/doc-inf/build-m2e.log

2) but when your try

a) a second project which depends on first:
https://github.com/carrot-garden/carrot-bugger/tree/master/carrot-bug-scr-maven-plugin-002

b) then "eclipse -> project -> clean" now produces the following failure log:
https://github.com/carrot-garden/carrot-bugger/blob/master/carrot-bug-scr-maven-plugin-002/doc-inf/build-m2e.log

3) this is because scr-maven-plugin expects dependency to be in the jar form
but m2e instead (and appropriately) provides a path to the exploded bundle in the ./target/classes
of the dependency project (if it is a workspace project);

4) the workaround is to disable workspace project resolution in m2e
but this impedes development speed considerably