[
https://issues.apache.org/jira/browse/FELIX-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033046#comment-13033046
]
Andrei Pozolotin commented on FELIX-2948:
-----------------------------------------
1) yes, the error message is similar to FELIX-2878
2) I updated both projects to latest snapshots
https://github.com/carrot-garden/carrot-bugger/blob/master/carrot-bug-scr-maven-plugin-001/pom.xml
https://github.com/carrot-garden/carrot-bugger/blob/master/carrot-bug-scr-maven-plugin-002/pom.xml
<groupId>org.apache.felix</groupId>
<artifactId>org.apache.felix.scr.annotations</artifactId>
<version>1.5.3-SNAPSHOT</version>
<groupId>org.apache.felix</groupId>
<artifactId>maven-scr-plugin</artifactId>
<version>1.7.1-SNAPSHOT</version>
<groupId>org.apache.felix</groupId>
<artifactId>maven-bundle-plugin</artifactId>
<version>2.3.5-SNAPSHOT</version>
3) I still have the same error on eclipse->clean invocation on project #2
5/13/11 8:56:17 AM CDT: [ERROR] Unable to get scrinfo from artifact at
/home/user1/Workspaces/github/carrot-bugger/carrot-bug-scr-maven-plugin-001/target/classes:0
5/13/11 8:56:17 AM CDT: Build errors for carrot-bug-scr-maven-plugin-002;
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.felix:maven-scr-plugin:1.7.1-SNAPSHOT:scr (scr) on project
carrot-bug-scr-maven-plugin-002: SCR Descriptor parsing had failures (see log)
4) the difference from FELIX-2878 is that here it is not a command line mvn
run, but rather an embedded maven 3.0.0-XXX invocation from m2e plugin (eclipse
maven builder) which does special class path substitutions for artifacts that
are local workspace projects (this is analogues to the way felix handles
"reference:file:" url for exploded bundles)
> scr-maven-plugin fails with org.maven.ide.eclipse plugin (exploded bundle)
> --------------------------------------------------------------------------
>
> Key: FELIX-2948
> URL: https://issues.apache.org/jira/browse/FELIX-2948
> Project: Felix
> Issue Type: Bug
> Components: Maven SCR Plugin
> Reporter: Andrei Pozolotin
>
> 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
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
