[m2e-users] SOLVED??: Re: problem with resolving custom build <extension

[mar@xxxxxxxxxx (Martin)]

Well I have deleted:

rm .metadata/.plugins/org.eclipse.m2e.jdt/*

once again and Eclipse restart made the error go away.

Though, the behaviour of the plugin is not very deterministic; not to
mention that buildhelper connetor to maven livecycle, when we use custom
plugins, maven profiles etc. has still some problems, but at least when
maven build is executed outside eclipse, Java errors are gone while some
Maven errors still appear.

m.

On Thu, Nov 17, 2011 at 07:49:58AM +0100, Martin wrote:
> Hi all,
>
> I have a quite large multi module project, that defines a build <extension>
> in parent pom.xml, ie:
>
> - - - -
>     <build>
>
>         <finalName>${project.name}-${project.version}</finalName>
>
>         <extensions>
>             <extension>
>                 <!--
>                     this module must be accessible from repository before compilation, in case of changes install it
>                     separately before first compilation of the project
>                 -->
>                 <groupId>cz.dain.ispop</groupId>
>                 <artifactId>build-tools</artifactId>
>                 <version>1.0-SNAPSHOT</version>
>             </extension>
>         </extensions>
>
>         <plugins>
>
>         ...
> - - - -
>
> I used eclipse 3.6+, now latest 3.7-sr1 with latest m2e plugin from market
> place.
>
> Right now I have 'Maven Problem' for each maven module:
>
> - - - -
> Project build error: Unresolveable build extension: Plugin
> cz.dain.ispop:build-tools:1.0-SNAPSHOT or one of its dependencies could not
> be resolved: Failed to collect dependencies for
> cz.dain.ispop:build-tools:jar:1.0-SNAPSHOT ()
> - - - -
>
> Needless to say, compilation from command line works (and have always
> worked as expected).
>
> Regardless if I deploy the module to my local ~/.m2, or to my remote maven
> repo, I can't get this away.
>
> From time to time during my Eclipce experience on current project, I have
> ecountered such an error, but I was able to make it go away doing some kind
> of rm in projects .metadata, creating new workspace, clean&build, etc.
> Though I never new the proper way ho to get rid of it, somehow I have
> always did.  Now nothings help.
>
> Please, have you got the same experience using maven build extensions?  Is
> there a way to get it working?
>
> Best Regards,
> martin.
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>