You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@asterixdb.apache.org by Taewoo Kim <wa...@gmail.com> on 2016/10/19 23:33:29 UTC
Eclipse - Plugin execution not covered by lifecycle configuration error
Hi all,
Since a few days ago, I have seen the following error. Has anyone seen this
error, too?
Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-dependency-plugin:2.10:*analyze-only*
(execution: default, phase: process-test-classes)
Best,
Taewoo
Re: Eclipse - Plugin execution not covered by lifecycle configuration error
Posted by Taewoo Kim <wa...@gmail.com>.
It looks like that there is no m2e connector for analyze-only plugin. I
think we need to add this plugin to the plugin management section of
pom.xml file so that this could be ignored on Eclipse only.
Best,
Taewoo
On Wed, Oct 19, 2016 at 5:06 PM, Taewoo Kim <wa...@gmail.com> wrote:
> Thanks Till. Let me check that.
>
> Best,
> Taewoo
>
> On Wed, Oct 19, 2016 at 4:45 PM, Till Westmann <ti...@apache.org> wrote:
>
>> Hi,
>>
>> I haven’t seen this (as I don’t use eclipse), but I can tell you where
>> it’s coming from. We’ve added the maven-dependency-plugin to validate
>> that the dependencies that are declared in the POM actually match what
>> it being used by the module. The build will fail if dependencies are
>> missing or if we declare dependencies that are not being used in the
>> module. The goal is to have precise dependency information to be able
>> to produce correct LICENSE/NOTICE files for our binary artifacts.
>>
>> I would guess that there's a way to integrate that plugin with the
>> eclipse build using m2e, but it's just a guess ...
>>
>> Maybe somebody else took a look at this and knows more?
>>
>> Cheers,
>> Till
>>
>> [1] http://www.eclipse.org/m2e/
>>
>> On 19 Oct 2016, at 16:33, Taewoo Kim wrote:
>>
>> > Hi all,
>> >
>> > Since a few days ago, I have seen the following error. Has anyone seen
>> this
>> > error, too?
>> >
>> > Plugin execution not covered by lifecycle configuration:
>> > org.apache.maven.plugins:maven-dependency-plugin:2.10:*analyze-only*
>> > (execution: default, phase: process-test-classes)
>> >
>> > Best,
>> > Taewoo
>>
>
>
Re: Eclipse - Plugin execution not covered by lifecycle configuration error
Posted by Taewoo Kim <wa...@gmail.com>.
Thanks Till. Let me check that.
Best,
Taewoo
On Wed, Oct 19, 2016 at 4:45 PM, Till Westmann <ti...@apache.org> wrote:
> Hi,
>
> I haven’t seen this (as I don’t use eclipse), but I can tell you where
> it’s coming from. We’ve added the maven-dependency-plugin to validate
> that the dependencies that are declared in the POM actually match what
> it being used by the module. The build will fail if dependencies are
> missing or if we declare dependencies that are not being used in the
> module. The goal is to have precise dependency information to be able
> to produce correct LICENSE/NOTICE files for our binary artifacts.
>
> I would guess that there's a way to integrate that plugin with the
> eclipse build using m2e, but it's just a guess ...
>
> Maybe somebody else took a look at this and knows more?
>
> Cheers,
> Till
>
> [1] http://www.eclipse.org/m2e/
>
> On 19 Oct 2016, at 16:33, Taewoo Kim wrote:
>
> > Hi all,
> >
> > Since a few days ago, I have seen the following error. Has anyone seen
> this
> > error, too?
> >
> > Plugin execution not covered by lifecycle configuration:
> > org.apache.maven.plugins:maven-dependency-plugin:2.10:*analyze-only*
> > (execution: default, phase: process-test-classes)
> >
> > Best,
> > Taewoo
>
Re: Eclipse - Plugin execution not covered by lifecycle configuration
error
Posted by Till Westmann <ti...@apache.org>.
Hi,
I haven\u2019t seen this (as I don\u2019t use eclipse), but I can tell you where
it\u2019s coming from. We\u2019ve added the maven-dependency-plugin to validate
that the dependencies that are declared in the POM actually match what
it being used by the module. The build will fail if dependencies are
missing or if we declare dependencies that are not being used in the
module. The goal is to have precise dependency information to be able
to produce correct LICENSE/NOTICE files for our binary artifacts.
I would guess that there's a way to integrate that plugin with the
eclipse build using m2e, but it's just a guess ...
Maybe somebody else took a look at this and knows more?
Cheers,
Till
[1] http://www.eclipse.org/m2e/
On 19 Oct 2016, at 16:33, Taewoo Kim wrote:
> Hi all,
>
> Since a few days ago, I have seen the following error. Has anyone seen this
> error, too?
>
> Plugin execution not covered by lifecycle configuration:
> org.apache.maven.plugins:maven-dependency-plugin:2.10:*analyze-only*
> (execution: default, phase: process-test-classes)
>
> Best,
> Taewoo