[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-dev] creating org.eclipse.m2e:lifecycle-mapping:pom:1.0.0 in central to avoid MPIR reporting failure
|
wow, nice use of directives: I didn't see that feature
this would solve the issue, and would also be more convenient than the
lifecycle-mapping trick: I'm definitely buying this!
thank you Igor
Le lundi 5 novembre 2018, 00:28:38 CET Igor Fedorenko a écrit :
> Have you tried using <?m2e ...?> [1]? It can't be used in all cases, but I
> find it far more convenient to use when I can.
>
> [1] http://www.eclipse.org/m2e/documentation/release-notes-17.html
>
> > Hi,
> >
> > Recently, org.eclipse.m2e:lifecycle-mapping was added to Maven's parent
> > pom to better manage some plugins in m2e: see MPOM-201 [1]
> > Since then, when doing a plugin management report during documentation
> > generation, we get a failure to download org.eclipse.m2e:lifecycle-
> > mapping:pom:1.0.0
> > I created MPIR-375 [2] to add a new feature to the report plugin to ignore
> > some plugins like this one: this is one option at report level to
> > workaround the issue.
> >
> > But while thinking at it, it would be IMHO easy for m2e to push a basic
> > pom to that coordinate and would avoid to add a new configuration in
> > every user's pom.xml: is it feasible, please?
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://issues.apache.org/jira/browse/MPOM-201
> >
> > [2] https://issues.apache.org/jira/projects/MPIR/issues/MPIR-375
> >
> >
> > _______________________________________________
> > m2e-dev mailing list
> > m2e-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe
> > from this list, visit
> > https://www.eclipse.org/mailman/listinfo/m2e-dev
>
> _______________________________________________
> m2e-dev mailing list
> m2e-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev
