With the recent changes brought to the Maven Eclipse integration, any unknown  plugins are flagged as problematic and an error is reported in the pom.xml . Typically this is solved by writing a thin integration layer between the Eclipse integration and the Maven plugin  or by instructing Eclipse to ignore some plugin executions.
The new 1.1 version of the m2eclipse plugin will allow a Maven plugin ( with no links to Eclipse plugin development ) to use an enhanced API to become compatible out of the box with the Eclipse integration  .
The maven-scr-plugin should take advantage of these new APIs to allow seamless integration with Eclipse.
|Affects Version/s||maven-scr-plugin-1.8.0 [ 12319049 ]|
|Fix Version/s||maven-scr-plugin-1.8.2 [ 12322945 ]|
|Attachment||FELIX-3358-BuildContext-message-reporting.txt [ 12543419 ]|
|Attachment||FELIX-3358-BuildContext-message-reporting.txt [ 12543420 ]|
[ I've adapted the current MavenLog to use the BuildContext whenever an error is reported with a possible source location. This work in the following manner:
The error/warning is logged with a specific format, e.g.
[WARNING] /home/rmuntean/w/workspace/bundle-sample/src/main/java/rmuntean/bundle_sample/ComplexDSComponent.java [0:0]: @Component : Lifecycle method deactivate has wrong number of arguments
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Assignee||Carsten Ziegeler [ cziegeler ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|