jboss forge无法安装插件

Question

我想创建一个jboss forge插件，但我在运行forge时遇到了巨大的问题……

当我在Eclipse中或从命令提示符启动forge时，需要相当长的时间，然后我总是得到这个巨大的异常。(见下图)

然后，当我创建我的插件项目并想要设置插件API时。Forge冻结了大约1分钟，然后给出了这个异常

Wrote <pathtoworkspace>/pluginforge/pom.xml
***ERROR*** Exception encountered: null (type "set VERBOSE true" to enable stack traces)

在那之后，我的pom.xml就因为依赖jboss-javaee-6.0而中断了。

重新安装jboss开发工具也无济于事。cmd提示和eclipse集成产生了相同的问题..我不知道怎么do...already浪费时间在这上面...希望有人能帮上忙。

启动-异常：

Error during PostStartup event
java.lang.NullPointerException
    at java.lang.String.contains(String.java:2076)
    at org.apache.maven.model.building.DefaultModelBuilder.containsCoordinates(DefaultModelBuilder.java:1047)
    at org.apache.maven.model.building.DefaultModelBuilder.importDependencyManagement(DefaultModelBuilder.java:948)
    at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:403)
    at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:374)
    at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:365)
    at org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:232)
    at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:141)
    at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:102)
    at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:86)
    at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:304)
    at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:393)
    at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:171)
    at org.jboss.forge.spec.javaee.BaseJavaEEFacet.isInstalled(BaseJavaEEFacet.java:64)
    at org.jboss.forge.spec.javaee.cdi.CDIFacetImpl.isInstalled(CDIFacetImpl.java:51)
    at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153)
    at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208)
    at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186)
    at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178)
    at org.jboss.forge.project.services.ProjectFactory.findProjectRecursively(ProjectFactory.java:117)
    at org.jboss.forge.shell.project.ProjectInitializer.doInit(ProjectInitializer.java:92)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
    at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
    at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
    at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
    at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
    at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
    at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
    at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
    at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
    at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
    at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
    at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628)
    at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75)
    at org.jboss.forge.shell.project.ProjectInitializer.postStartupTrigger(ProjectInitializer.java:45)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:601)
    at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
    at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
    at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)

Answer 1

这是一个非常晚的答案，但我希望这对遇到这种情况的其他人有所帮助。这看起来像是你在Maven依赖解析上有问题。可能是失败，或者是sloe，或者依赖项正在下载但超时。

当您在Forge中更改项目上下文时，例如，当您cd到项目目录中时，或者当您运行修改项目依赖层次结构的命令时，Forge将尝试部分或完整的Maven构建。此构建的一个方面是依赖项解析过程，该过程试图确保任何依赖项，尤其是激活Forge facet所需的依赖项在本地Maven存储库中都可用。

在Forge 1.4.0+ (特别是即将发布的1.4.1)版本中，如果在任何时候依赖项解析出现故障，shell都应该输出这方面的任何警告。

作为提示，最好使用像Nexus或Artifactory这样的Maven存储库管理器，这将大大减少缓慢的工件下载或超时的可能性。