1. Felix
  2. FELIX-3358

Enhance the maven-scr-plugin to be compatible with recent Maven/Eclipse integrations


    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: maven-scr-plugin-1.8.0
    • Fix Version/s: maven-scr-plugin-1.9.0
    • Component/s: SCR Tooling
    • Labels:
    • Environment:
      Eclipse Indigo or newer


      With the recent changes brought to the Maven Eclipse integration, any unknown [0] 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 [1] 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 [2] .

      The maven-scr-plugin should take advantage of these new APIs to allow seamless integration with Eclipse.

      [0]: http://wiki.eclipse.org/M2E_plugin_execution_not_covered
      [1]: http://wiki.eclipse.org/M2E/Extension_Development
      [2]: http://wiki.eclipse.org/M2E_compatible_maven_plugins

        Issue Links

        There are no Sub-Tasks for this issue.


          Robert Munteanu created issue -
          Felix Meschberger made changes -
          Field Original Value New Value
          Link This issue relates to SLING-2423 [ SLING-2423 ]
          Timo Naroska made changes -
          Attachment m2e-lifecycle-mapping.diff [ 12541381 ]
          Carsten Ziegeler made changes -
          Affects Version/s maven-scr-plugin-1.8.0 [ 12319049 ]
          Carsten Ziegeler made changes -
          Fix Version/s maven-scr-plugin-1.8.2 [ 12322945 ]
          rmuntean made changes -
          Attachment FELIX-3358-BuildContext-message-reporting.txt [ 12543419 ]
          rmuntean made changes -
          rmuntean made changes -
          Comment [ 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

          rmuntean made changes -
          Attachment FELIX-3358-BuildContext-message-reporting.txt [ 12543419 ]
          Carsten Ziegeler made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Assignee Carsten Ziegeler [ cziegeler ]
          Resolution Fixed [ 1 ]
          Carsten Ziegeler made changes -
          Status Resolved [ 5 ] Closed [ 6 ]


            • Assignee:
              Carsten Ziegeler
              Robert Munteanu
            • Votes:
              2 Vote for this issue
              4 Start watching this issue


              • Created: