Add missing M2E lifecycle mappings metadata 48/65548/1
authorMichael Vorburger <vorburger@redhat.com>
Wed, 15 Nov 2017 15:02:50 +0000 (16:02 +0100)
committerMichael Vorburger <vorburger@redhat.com>
Wed, 15 Nov 2017 15:04:07 +0000 (16:04 +0100)
commit49a04de83ce9ad7feac6b2fe87acf26ef1295280
tree8f51ebe7232c65a7fe13babca5f885d197ee6270
parent02c0bf523dd17d38660430c69c04ad8e7531f64e
Add missing M2E lifecycle mappings metadata

* Ignore for the karaf-maven-plugin

This change does intentionally NOT include a lifecycle mapping for the
(new) spotbugs-maven-plugin, because that's one which we do NOT want to
just IGNORE, but have to configure; re. that one, please watch
https://github.com/m2e-code-quality/m2e-code-quality/issues/110

FTR: Originally I started putting these (only) into
opendaylight-eclipse-setup, because "such Eclipse specifics should not
be in our POM", but today on IRC rovarga opined that "it should 'just
work' even if one doesn't want to use your opendaylight-eclipse-setup"
but why? its great!] so putting there here now - meaning we have a bit
of a mix now, but I guess this isn't the end of the world.

see https://github.com/vorburger/opendaylight-eclipse-setup#how-to-add-additional-m2e-lifecycle-mapping

Change-Id: I3498cc5f3af7481cd83b4f7f69045d19668fd1da
Signed-off-by: Michael Vorburger <vorburger@redhat.com>
feature-repo-parent/pom.xml
untested-single-feature-parent/pom.xml