[forge-dev] Forge project for Github Issue #31 - Unable to install arquillian plugin in Forge 1.3.3.FINAL

Vineet Reynolds Pereira vpereira at redhat.com
Sun Aug 25 04:10:37 EDT 2013 

Hi David,

  I'd like to know if you're willing to try out a custom build of Forge that would help report more useful information about the failure. I'm tracking this issue now as FORGE-1133 <https://issues.jboss.org/browse/FORGE-1133>. I managed to reproduce this by forcing Maven central to point to an invalid location (not likely in your case but representative). This ended up in several resolution failures that were not reported in the Shell exhibiting the same behavior that you've reported.

  The build we can provide will report any dependency resolution failures, and we could then determine whether something is amiss in Forge or whether this issue is due to some other factor. Do let me know if you want a build prepared, or whether you could build Forge yourself.

Thanks,
Vineet

PS: I've attached a sample of the shell outputs that you're likely to see in various scenarios.

----- Original Message -----
> From: "Vineet Reynolds Pereira" <vpereira at redhat.com>
> To: "forge-dev List" <forge-dev at lists.jboss.org>
> Sent: Saturday, August 24, 2013 9:04:06 PM
> Subject: Re: [forge-dev] Forge project for Github Issue #31 - Unable to install arquillian plugin in Forge
> 1.3.3.FINAL
> 
> 
> Hi David,
> 
>    Thanks for those inputs.
> 
>    I was able to reproduce this exactly once and (quite unfortunately) I do
>    not the exact reason of what caused it (maybe a corrupt artifact in .m2
>    or a timeout in dependency resolution), but it's all down to a failure in
>    Maven dependency resolution for the plugin project.
> 
>    Let me know if it is feasible for you to delete your .m2 repo and retry
>    installation of the Arquillian plugin. If that helps, we just need to
>    improve the error reporting behavior in Forge and terminate the
>    installation. Otherwise we might need to do a debugging session to see
>    what artifacts have failed resolution in your environment, and
>  1. maybe fix Forge to ensure that they dont fail resolution (if that can be
>  done in Forge)
>  2. or provide you with a workaround so you can add entries to your
>  settings.xml to ensure that dependency resolution does not fail. You could
>  also see if this is the case by cloning the arquillian-plugin project from
>  https://github.com/forge/plugin-arquillian and running 'mvn clean compile'
>  on the downloaded project.
> 
> Thanks,
> Vineet
> 
> ----- Original Message -----
> > From: "David Beer" <david.m.beer at gmail.com>
> > To: "forge-dev List" <forge-dev at lists.jboss.org>
> > Sent: Saturday, August 24, 2013 8:48:40 PM
> > Subject: Re: [forge-dev] Forge project for Github Issue #31 - Unable to
> > install arquillian plugin in Forge
> > 1.3.3.FINAL
> > 
> > Hi Vineet
> > 
> > Yes our settings file overwrites those values and retrieves all artifacts
> > from our maven repository, which based on a cloud server for access by
> > different people and services. The password protection is needed for the
> > repository to stop access to company wide artifacts libraries and demo
> > applications etc.
> > 
> > If there is anything else I can help with please let me know.
> > 
> > Thanks
> > 
> > David
> > 
> > 
> > On 23 August 2013 22:16, Vineet Reynolds Pereira < vpereira at redhat.com >
> > wrote:
> > 
> > 
> > 
> > Hi David
> > 
> > The settings.xml file looks interesting, and I'll take a deeper look at the
> > scenarios possible. One of them includes overriding Maven central, and the
> > other is password protected access to the repository.
> > 
> > About running the 'install-plugin' command from a empty directory, I
> > believe
> > this had nothing to do with cleaning out the .forge directory, although
> > that
> > does help sometimes. The issue here is that of Forge not recognizing the
> > plugin project and using the existing Maven project in the current
> > directory
> > from where you run the 'forge install-plugin arquillian' command. Running
> > this command from an empty directory, will still attempt to install the
> > plugin without requiring a change in the project context. This is only
> > proposed as a workaround until we determine what is wrong and/or fix this
> > in
> > Forge.
> > 
> > Thanks,
> > Vineet
> > 
> > ----- Original Message -----
> > > From: "David Beer" < david.m.beer at gmail.com >
> > > To: "forge-dev List" < forge-dev at lists.jboss.org >
> > > Sent: Saturday, August 24, 2013 12:17:45 AM
> > > Subject: Re: [forge-dev] Forge project for Github Issue #31 - Unable to
> > > install arquillian plugin in Forge
> > > 1.3.3.FINAL
> > > 
> > > Hi All
> > > 
> > > Thanks for the suggestions. I am not behind a proxy I connect direct to
> > > the
> > > LAN which connects to the router/internet. @Lincoln I tried the install
> > > in
> > > my home directory and set the JAVA_HOME setting and get the same result.
> > > I
> > > cleared out my .forge directory as well and still get the same error, I
> > > have
> > > also set the M2_HOME variable and added it to my path. I have two
> > > profiles
> > > in my settings file (attached) one is active by default the other is not
> > > and
> > > is used simply as a backup. I tried a the steps in the issue except for
> > > setting a proxy as I am not behind one.
> > > 
> > > Hope this all helps.
> > > 
> > > Thanks
> > > 
> > > David
> > > 
> > > 
> > > On 23 August 2013 18:19, Vineet Reynolds Pereira < vpereira at redhat.com >
> > > wrote:
> > > 
> > > 
> > > 
> > > And to follow up on more advice, there is some configuration to perform,
> > > should you be behind a proxy:
> > > http://forge.jboss.org/docs/using/configure-proxy.html
> > > 
> > > This is kind of necessary since we ran into a similar issue a few months
> > > back: https://issues.jboss.org/browse/FORGE-761 . Going by this earlier
> > > issue, it would help use if you can tell us more about any profiles that
> > > are
> > > active by default, in your maven settings.xml file.
> > > 
> > > Thanks,
> > > Vineet
> > > 
> > > ----- Original Message -----
> > > > From: "Vineet Reynolds Pereira" < vpereira at redhat.com >
> > > > To: "forge-dev List" < forge-dev at lists.jboss.org >
> > > > Sent: Friday, August 23, 2013 10:22:35 PM
> > > > Subject: Re: [forge-dev] Forge project for Github Issue #31 - Unable to
> > > > install arquillian plugin in Forge
> > > > 1.3.3.FINAL
> > > > 
> > > > 
> > > > David,
> > > > 
> > > > Doing what Lincoln suggested would help us determine if there is a
> > > > problem
> > > > with dependency resolution in Forge in your environment. There was a
> > > > few
> > > > improvements and fixes in this area in earlier releases, and one might
> > > > have slipped past us.
> > > > 
> > > > Vineet
> > > > 
> > > > ----- Original Message -----
> > > > > From: "Lincoln Baxter, III" < lincolnbaxter at gmail.com >
> > > > > To: "forge-dev List" < forge-dev at lists.jboss.org >
> > > > > Sent: Friday, August 23, 2013 9:40:21 PM
> > > > > Subject: Re: [forge-dev] Forge project for Github Issue #31 - Unable
> > > > > to
> > > > > install arquillian plugin in Forge
> > > > > 1.3.3.FINAL
> > > > > 
> > > > > Hey David,
> > > > > 
> > > > > Could you try running the install command from an empty directory?
> > > > > 
> > > > > Thanks,
> > > > > Lincoln
> > > > > 
> > > > > 
> > > > > On Fri, Aug 23, 2013 at 11:13 AM, David Beer < david.m.beer at gmail.com
> > > > > >
> > > > > wrote:
> > > > > 
> > > > > 
> > > > > 
> > > > > 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 [
> > > > > https://raw.github.com/forge/plugin-repository/master/repository.yaml
> > > > > ].
> > > > > ..
> > > > > 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 at 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/content/org/jboss/forge/forge-distribution/1.4.0.Final/forge-distribution-1.4.0.Final.zip
> > > > > 
> > > > > ----- Original Message -----
> > > > > > From: "David Beer" < david.m.beer at gmail.com >
> > > > > > To: "forge-dev List" < forge-dev at 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 at 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 at redhat.com >
> > > > > > > To: "forge-dev List" < forge-dev at 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 at gmail.com >
> > > > > > > > To: forge-dev at 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 at lists.jboss.org
> > > > > > > > https://lists.jboss.org/mailman/listinfo/forge-dev
> > > > > > > _______________________________________________
> > > > > > > forge-dev mailing list
> > > > > > > forge-dev at lists.jboss.org
> > > > > > > https://lists.jboss.org/mailman/listinfo/forge-dev
> > > > > > > 
> > > > > > _______________________________________________
> > > > > > forge-dev mailing list
> > > > > > forge-dev at lists.jboss.org
> > > > > > https://lists.jboss.org/mailman/listinfo/forge-dev
> > > > > > 
> > > > > > 
> > > > > > _______________________________________________
> > > > > > forge-dev mailing list
> > > > > > forge-dev at lists.jboss.org
> > > > > > https://lists.jboss.org/mailman/listinfo/forge-dev
> > > > > _______________________________________________
> > > > > forge-dev mailing list
> > > > > forge-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/forge-dev
> > > > > 
> > > > > 
> > > > > _______________________________________________
> > > > > forge-dev mailing list
> > > > > forge-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/forge-dev
> > > > > 
> > > > > 
> > > > > 
> > > > > --
> > > > > Lincoln Baxter, III
> > > > > http://ocpsoft.org
> > > > > "Simpler is better."
> > > > > 
> > > > > _______________________________________________
> > > > > forge-dev mailing list
> > > > > forge-dev at lists.jboss.org
> > > > > https://lists.jboss.org/mailman/listinfo/forge-dev
> > > > _______________________________________________
> > > > forge-dev mailing list
> > > > forge-dev at lists.jboss.org
> > > > https://lists.jboss.org/mailman/listinfo/forge-dev
> > > > 
> > > _______________________________________________
> > > forge-dev mailing list
> > > forge-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/forge-dev
> > > 
> > > 
> > > _______________________________________________
> > > forge-dev mailing list
> > > forge-dev at lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/forge-dev
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
> > 
> > 
> > _______________________________________________
> > forge-dev mailing list
> > forge-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/forge-dev
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev
> 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ShellOutput.txt
Url: http://lists.jboss.org/pipermail/forge-dev/attachments/20130825/10b91ecd/attachment-0001.txt

More information about the forge-dev mailing list