Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] NPE on import existing maven projects
I'm pretty sure now it's this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=367870.
About to try the described workaround...

Craig

On Tue, Apr 24, 2012 at 2:48 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
versionRange?

--
Regards,
Igor


On 12-04-24 1:47 PM, Craig Foote wrote:
Thanks Igor. I'm a noob at this, what elements in the pom would that
involve?

Craig

On Tue, Apr 24, 2012 at 12:35 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> wrote:

   If I were to guess, the failing project's pom has incomplete lifecycle
   mapping configuration.

   --
   Regards,
   Igor


   On 12-04-23 12:56 PM, Craig Foote wrote:

       I'm using eclipse_3.7.2 with m2eclipse_1.0.200 and I'm getting a
       NullPointerException when running Project > Clean then Build on
       a set of
       projects I checked out as Maven projects:

       Errors running builder 'Maven Project Builder' on project '[my
       project]'.

       java.lang.NullPointerException
       at
       org.eclipse.m2core.internal.__lifecyclemapping.model.__PluginExecutionFilter.match(__PluginExecutionFilter.java:__304)
       at
       org.eclipse.m2core.internal.__lifecyclemapping.__SimpleMappingMetaDataSource.__getPluginExecutionMetaData(__SimpleMappingMetaDataSource.__java:71)
       at
       org.eclipse.m2core.internal.__lifecyclemapping.__LifecycleMappingFactory.__calculateEffectiveLifecycleMap__ping(LifecycleMappingFactory.__java:294)
       at
       org.eclipse.m2core.internal.__lifecyclemapping.__LifecycleMappingFactory.__calculateEffectiveLifecycleMap__ping(LifecycleMappingFactory.__java:208)
       at
       org.eclipse.m2core.internal.__lifecyclemapping.__LifecycleMappingFactory.__calculateLifecycleMapping(__LifecycleMappingFactory.java:__159)
       at
       org.eclipse.m2core.internal.__project.registry.__ProjectRegistryManager.__setupLifecycleMapping(__LifecycleMappingFactory.java:__526)
       [snip]
       at
       org.eclipse.m2core.internal.__project.registry.__ProjectRegistryManager.__refresh(MavenProjectManager.__java:58)
       [snip]
       at
       org.eclipse.m2core.internal.__builder.MavenBuilder.build(__MavenBuilder.java:20)

       [snip]

       It identifies a single project which, like several other
       seemingly fine
       projects, uses the org-apache-felix:maven-bundle-__plugin_2.1.0 to

       generate its MANIFEST.MF.

       It doesn't seem to affect the maven build but it is annoying and
       prevents checking out projects into a Working Set.

       Unfortunately I need to stick with the versions I have and
       cannot run
       milestones.

       Anyone have any ideas?

       Thanks,
       Craig



       _________________________________________________
       m2e-users mailing list
       m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
       https://dev.eclipse.org/__mailman/listinfo/m2e-users
       <https://dev.eclipse.org/mailman/listinfo/m2e-users>

   _________________________________________________
   m2e-users mailing list
   m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
   https://dev.eclipse.org/__mailman/listinfo/m2e-users

   <https://dev.eclipse.org/mailman/listinfo/m2e-users>




_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

Back to the top