Hi,
soory for the late answer.
Now I try it with a new workspace and new checkout and all works fine.
I have no idea, war was the problem.
Greetings
Heiko
Am 08.07.2013 19:34, schrieb Fred Bricon:
I've done quite a bit of offline testing for JBoss Tools the last few
weeks and didn't see any issue.
Your stacktrace indicates your lifecycle mapping is missinga version
range. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=347602
2013/7/8 Igor Fedorenko <i...@ifedorenko.com <mailto:i...@ifedorenko.com>>
This is a bug, please submit new bugreport in m2e bugzilla and provide
small standalone example and exact steps to reproduce it. Since
working
offline is relatively niche usecase, please consider contributing a
quality patch to fix the problem.
--
Regards,
Igor
On 2013-07-08 8:48 PM, Heiko wrote:
Hi,
due to security constraints, we must carry out our development
without
direct internet connections.
In the past I used Juno Eclipse SR2 with m2e 1.3and Tycho 0.16
- 0.18.
All necessary data were available on Nexus or a p2 repositories.
With the update to Eclipse Kepler and m2e 1.4 but now I have
serious
internal errosr when I try toupdate / refresh my maven / tycho
projects.
Stack Trace:
Error
Mon Jul 08 15:33:06 CEST 2013
Errors running builder 'Maven Project Builder' on project
'foo.bar'.
java.lang.NullPointerException
at
org.eclipse.m2e.core.internal.lifecyclemapping.SimpleMappingMetadataSource.getPluginExecutionMetadata(SimpleMappingMetadataSource.java:71)
at
org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory.calculateEffectiveLifecycleMappingMetadata0(LifecycleMappingFactory.java:512)
at
org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory.calculateEffectiveLifecycleMappingMetadata(LifecycleMappingFactory.java:454)
at
org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory.calculateEffectiveLifecycleMappingMetadata(LifecycleMappingFactory.java:244)
at
org.eclipse.m2e.core.internal.lifecyclemapping.LifecycleMappingFactory.calculateLifecycleMapping(LifecycleMappingFactory.java:176)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupLifecycleMapping(ProjectRegistryManager.java:547)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refreshPhase2(ProjectRegistryManager.java:474)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$3.call(ProjectRegistryManager.java:453)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager$3.call(ProjectRegistryManager.java:1)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:457)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:334)
at
org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:287)
at
org.eclipse.m2e.core.internal.project.registry.MavenProjectManager.refresh(MavenProjectManager.java:67)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder.getProjectFacade(MavenBuilder.java:216)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$1.call(MavenBuilder.java:91)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder$1.call(MavenBuilder.java:1)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
at
org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:89)
at
org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1305)
at
org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:89)
at
org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726)
at
org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at
org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at
org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at
org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at
org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at
org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at
org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at
org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
A similar demo project (pom same configuration) with active
Internet
connection works without problems.
M2e still needs certain data at runtime from maven / p2
repositories?
Or what could be raise this error?
Thanks in advance
Heiko
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org <mailto:m2e-users@eclipse.org>
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org <mailto:m2e-users@eclipse.org>
https://dev.eclipse.org/mailman/listinfo/m2e-users
--
"Have you tried turning it off and on again" - The IT Crowd
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/m2e-users
