Hi Vineet
I get the same error with 1.4.0, stack trace below.
[arquillian-demo] arquillian-demo $ forge install-plugin arquillian
Connecting to remote repository [
.
connected!
***INFO*** Preparing to install plugin: arquillian
***INFO*** Checking out plugin source files to
[/tmp/forgetemp8106787201439169702] via 'git'
***INFO*** Switching to branch/tag [refs/heads/1.0.6.Final]
***INFO*** Project found
***INFO*** Name: arquillian-plugin
***INFO*** Version: 1.0.0-SNAPSHOT
***INFO*** Type: Java Application
? The project does not appear to be a Forge Plugin Project, install
anyway? [y/N] y
***INFO*** Project found
***INFO*** Name: arquillian-demo
***INFO*** Version: 1.0.0-SNAPSHOT
***INFO*** Type: Java Application
***INFO*** Cleaning up temp workspace [/tmp/forgetemp8106787201439169702]
Wrote
/home/dbeer/.forge/httpsrawgithubcomforgepluginrepositorymasterrepositoryyaml.yaml
Deleted /tmp/forgetemp8106787201439169702
***ERROR*** Exception encountered: (type "set VERBOSE false" to disable
stack traces)
java.lang.NullPointerException
at
org.jboss.forge.shell.plugins.builtin.ForgePlugin.buildFromCurrentProject(ForgePlugin.java:625)
at
org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromGit(ForgePlugin.java:414)
at
org.jboss.forge.shell.plugins.builtin.ForgePlugin.installFromIndex(ForgePlugin.java:233)
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:606)
at org.jboss.forge.shell.command.Execution.perform(Execution.java:160)
at
org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109)
at
org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
at
org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:795)
at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:818)
at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:608)
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:606)
at
org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
at
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
at
org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)
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:606)
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:622)
at
org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)
at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:186)
at java.lang.Thread.run(Thread.java:724)
Maven is able to resolve artifacts outside of forge. I have also attached
my home .forge directory contents as a zip file.
Thanks
David
On 23 August 2013 12:02, Vineet Reynolds Pereira <vpereira(a)redhat.com>wrote:
Hi David,
Before we proceed with a debugging session, I'd like to know if you
continue to face this on Forge 1.4.0 [1] that was just released, since any
bug fix would be issued against this or a later release.
About the Maven repo, I cannot rule it out entirely. But it is a
possibility - I could think of possible failures to resolve dependencies in
the Arquillian plugin via this Maven repo, that are not propagated
correctly to Forge. I'll investigate this area a bit more in depth. If this
turns out to be true, it could be worked around via the Maven settings.xml
file, or by changing the Maven repo/mirror config.
Vineet
[1]:
https://repository.jboss.org/nexus/service/local/repositories/releases/co...
----- Original Message -----
> From: "David Beer" <david.m.beer(a)gmail.com>
> To: "forge-dev List" <forge-dev(a)lists.jboss.org>
> Sent: Friday, August 23, 2013 4:04:02 PM
> Subject: Re: [forge-dev] Forge project for Github Issue #31 - Unable to
install arquillian plugin in Forge
> 1.3.3.FINAL
>
> Hi Vineet
>
> Thanks for checking this. I wonder if this is t do with maven as we use a
> company specific maven repo that requires authentication. I am happy to
set
> up a debug session and to see if that can help. I appreciate peoples
help on
> this.
>
>
> On 23 August 2013 09:01, Vineet Reynolds Pereira < vpereira(a)redhat.com >
> wrote:
>
>
>
> I couldn't reproduce this issue on Java 7 u25 as well. On Linux Mint, if
that
> makes a difference. I think a debugging session might help.
>
> Vineet
>
>
> ----- Original Message -----
> > From: "Vineet Reynolds Pereira" < vpereira(a)redhat.com >
> > To: "forge-dev List" < forge-dev(a)lists.jboss.org >
> > Sent: Thursday, August 22, 2013 12:42:57 AM
> > Subject: Re: [forge-dev] Forge project for Github Issue #31 - Unable to
> > install arquillian plugin in Forge
> > 1.3.3.FINAL
> >
> >
> > I just took a look at this. Not able to reproduce this again,
surprisingly.
> > We could rule out the existing project from where the command is
launched,
> > as a cause.
> >
> > And going by the expected behavior, I suspect the bug to be due to
Weld,
> > the
> > version of the JVM used, or some behavior in Weld+JVM that we didnt
account
> > for.
> >
> > Vineet
> >
> > ----- Original Message -----
> > > From: "David Beer" < david.m.beer(a)gmail.com >
> > > To: forge-dev(a)lists.jboss.org
> > > Sent: Thursday, August 22, 2013 12:25:56 AM
> > > Subject: [forge-dev] Forge project for Github Issue #31 - Unable to
> > > install
> > > arquillian plugin in Forge 1.3.3.FINAL
> > >
> > > Hi All
> > >
> > > As requested by @lincolnthree attached is a zip of my project. I am
> > > simply
> > > trying to follow the arquillian guide
> > >
http://arquillian.org/guides/get_started_faster_with_forge/
> > >
> > > Thanks
> > >
> > > David
> > >
> > > _______________________________________________
> > > forge-dev mailing list
> > > forge-dev(a)lists.jboss.org
> > >
https://lists.jboss.org/mailman/listinfo/forge-dev
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/forge-dev
> >
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/forge-dev
>
>
> _______________________________________________
> forge-dev mailing list
> forge-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev