eclipse - jboss forge cannot setup plugins -


i wanna create jboss forge plugin have massive problems running forge...

when start forge inside eclipse or command prompt takes quite long time , huge exception. (see bottom)

then when create plugin project , wanna setup plugins api. forge freezes 1 minute , gives me exception

wrote <pathtoworkspace>/pluginforge/pom.xml ***error*** exception encountered: null (type "set verbose true" enable stack traces) 

after pom.xml broken dependency regarding jboss-javaee-6.0

reinstalling jboss developer tools didn't either. cmd prompt , eclipse integration producing same issues.. have no idea do...already wasting hours on this... can .

startup-exception:

error during poststartup event java.lang.nullpointerexception     @ java.lang.string.contains(string.java:2076)     @ org.apache.maven.model.building.defaultmodelbuilder.containscoordinates(defaultmodelbuilder.java:1047)     @ org.apache.maven.model.building.defaultmodelbuilder.importdependencymanagement(defaultmodelbuilder.java:948)     @ org.apache.maven.model.building.defaultmodelbuilder.build(defaultmodelbuilder.java:403)     @ org.apache.maven.model.building.defaultmodelbuilder.build(defaultmodelbuilder.java:374)     @ org.apache.maven.model.building.defaultmodelbuilder.build(defaultmodelbuilder.java:365)     @ org.apache.maven.model.building.defaultmodelbuilder.build(defaultmodelbuilder.java:232)     @ org.apache.maven.project.defaultprojectbuilder.build(defaultprojectbuilder.java:141)     @ org.apache.maven.project.defaultprojectbuilder.build(defaultprojectbuilder.java:102)     @ org.jboss.forge.maven.facets.mavencorefacetimpl.getpartialprojectbuildingresult(mavencorefacetimpl.java:86)     @ org.jboss.forge.maven.facets.mavencorefacetimpl.resolveproperties(mavencorefacetimpl.java:304)     @ org.jboss.forge.maven.facets.mavendependencyfacet.resolveproperties(mavendependencyfacet.java:393)     @ org.jboss.forge.maven.facets.mavendependencyfacet.haseffectivedependency(mavendependencyfacet.java:171)     @ org.jboss.forge.spec.javaee.basejavaeefacet.isinstalled(basejavaeefacet.java:64)     @ org.jboss.forge.spec.javaee.cdi.cdifacetimpl.isinstalled(cdifacetimpl.java:51)     @ org.jboss.forge.project.baseproject.registerfacet(baseproject.java:153)     @ org.jboss.forge.project.services.projectfactory.registersinglefacet(projectfactory.java:208)     @ org.jboss.forge.project.services.projectfactory.registersinglefacet(projectfactory.java:186)     @ org.jboss.forge.project.services.projectfactory.registerfacets(projectfactory.java:178)     @ org.jboss.forge.project.services.projectfactory.findprojectrecursively(projectfactory.java:117)     @ org.jboss.forge.shell.project.projectinitializer.doinit(projectinitializer.java:92)     @ sun.reflect.nativemethodaccessorimpl.invoke0(native method)     @ sun.reflect.nativemethodaccessorimpl.invoke(nativemethodaccessorimpl.java:57)     @ sun.reflect.delegatingmethodaccessorimpl.invoke(delegatingmethodaccessorimpl.java:43)     @ java.lang.reflect.method.invoke(method.java:601)     @ org.jboss.weld.util.reflection.securereflections$13.work(securereflections.java:305)     @ org.jboss.weld.util.reflection.securereflectionaccess.run(securereflectionaccess.java:54)     @ org.jboss.weld.util.reflection.securereflectionaccess.runasinvocation(securereflectionaccess.java:163)     @ org.jboss.weld.util.reflection.securereflections.invoke(securereflections.java:299)     @ org.jboss.weld.introspector.jlr.weldmethodimpl.invokeoninstance(weldmethodimpl.java:188)     @ org.jboss.weld.introspector.forwardingweldmethod.invokeoninstance(forwardingweldmethod.java:59)     @ org.jboss.weld.injection.methodinjectionpoint.invokeoninstancewithspecialvalue(methodinjectionpoint.java:198)     @ org.jboss.weld.event.observermethodimpl.sendevent(observermethodimpl.java:282)     @ org.jboss.weld.event.observermethodimpl.sendevent(observermethodimpl.java:265)     @ org.jboss.weld.event.observermethodimpl.notify(observermethodimpl.java:234)     @ org.jboss.weld.manager.beanmanagerimpl.notifyobservers(beanmanagerimpl.java:635)     @ org.jboss.weld.manager.beanmanagerimpl.fireevent(beanmanagerimpl.java:628)     @ org.jboss.weld.event.eventimpl.fire(eventimpl.java:75)     @ org.jboss.forge.shell.project.projectinitializer.poststartuptrigger(projectinitializer.java:45)     @ sun.reflect.nativemethodaccessorimpl.invoke0(native method)     @ sun.reflect.nativemethodaccessorimpl.invoke(nativemethodaccessorimpl.java:57)     @ sun.reflect.delegatingmethodaccessorimpl.invoke(delegatingmethodaccessorimpl.java:43)     @ java.lang.reflect.method.invoke(method.java:601)     @ org.jboss.weld.util.reflection.securereflections$13.work(securereflections.java:305)     @ org.jboss.weld.util.reflection.securereflectionaccess.run(securereflectionaccess.java:54)     @ org.jboss.weld.util.reflection.securereflectionaccess.runasinvocation(securereflectionaccess.java:163) 

a late answer, hope helps else has run this. looks had problems maven dependency resolution. either failed, or sloe, or dependencies being downloaded timed out.

when change project context in forge, i.e. cd project directory, or when run command modifies project's dependency hierarchy, forge attempt partial or full maven build. 1 of aspects of build dependency resolution process attempts ensure dependencies required activating forge facets available in local maven repository.

with forge 1.4.0+ (especially upcoming 1.4.1) release, shell should output warnings in area, should there failure in dependency resolution @ point.

as tip, better operate maven repository manager nexus or artifactory heavily reduce possibility of slow artifact downloads or timeouts.


Comments

Popular posts from this blog

python - How to create a legend for 3D bar in matplotlib? -

java - Multi-Label Document Classification -

php - Dynamic url re-writing using htaccess -