Exception on first run...
See original GitHub issueProblem with first run… I am getting an exception shown below. Any help would be appreciated.
connected to the server.
X
Hello ! This is the beta version of POM Explorer ...
Have fun !
The official repository is here : https://github.com/ltearno/pom-explorer
Creating your session
Session created and registered. It has been attached to your profile
Analyzing the default directory
X
analyze directory d:\sigdev\dst-utils
Analyzing directory 'd:\sigdev\dst-utils'...
possible options: verbose, nofetch, offline, profiles
analyzing 'd:\sigdev\dst-utils'
Pom Analysis ready!
adding directory 'd:\sigdev\dst-utils'
found 10 pom files
loading pom files
loaded 10 projects
completing loaded projects
Error when interpreting command 'analyze directory d:\sigdev\dst-utils'
Command class : AnalyzeCommand
Command method : directory
Argument : class: fr.lteconsulting.pomexplorer.commands.CommandOptions toString : fr.lteconsulting.pomexplorer.commands.CommandOptions@c64dced
Argument : class: fr.lteconsulting.pomexplorer.Client toString : fr.lteconsulting.pomexplorer.Client@275f17e6
Argument : class: fr.lteconsulting.pomexplorer.ApplicationSession toString : fr.lteconsulting.pomexplorer.ApplicationSession@6afa0755
Argument : class: fr.lteconsulting.pomexplorer.AppFactory$2 toString : fr.lteconsulting.pomexplorer.AppFactory$2@4ad78fac
Argument : class: java.lang.String toString : d:\sigdev\dst-utils
org.jboss.shrinkwrap.resolver.api.Invokable$InvocationException: Unable to invoke onlyOne([Ljava.lang.Class;@434c683e) on object org.jboss.shrinkwrap.resolver.spi.loader.ServiceRegistry with parameters [Ljava.lang.Object;@14000b2c
org.jboss.shrinkwrap.resolver.api.Invokable.invokeMethod(Invokable.java:108)
org.jboss.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:91)
org.jboss.shrinkwrap.resolver.api.ResolverSystemFactory.createFromUserView(ResolverSystemFactory.java:53)
org.jboss.shrinkwrap.resolver.api.Resolvers.use(Resolvers.java:68)
org.jboss.shrinkwrap.resolver.api.maven.Maven.resolver(Maven.java:36)
fr.lteconsulting.pomexplorer.MavenResolver.init(MavenResolver.java:51)
fr.lteconsulting.pomexplorer.Session.mavenResolver(Session.java:51)
fr.lteconsulting.pomexplorer.DefaultPomFileLoader.loadPomFileForGav(DefaultPomFileLoader.java:26)
fr.lteconsulting.pomexplorer.PomAnalysis.loadAndCheckProject(PomAnalysis.java:373)
fr.lteconsulting.pomexplorer.PomAnalysis.processProjectForCompleteness(PomAnalysis.java:334)
fr.lteconsulting.pomexplorer.PomAnalysis.completeLoadedProjects(PomAnalysis.java:228)
fr.lteconsulting.pomexplorer.PomAnalysis.runFullRecursiveAnalysis(PomAnalysis.java:71)
fr.lteconsulting.pomexplorer.commands.AnalyzeCommand.directory(AnalyzeCommand.java:29)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:498)
fr.lteconsulting.pomexplorer.commands.Commands.takeCommand(Commands.java:251)
fr.lteconsulting.pomexplorer.AppFactory$1.onWebsocketMessage(AppFactory.java:169)
fr.lteconsulting.pomexplorer.webserver.WebServer$2$1.lambda$onFullTextMessage$0(WebServer.java:145)
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
java.lang.Thread.run(Thread.java:745)
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Understanding Exceptions while debugging with Visual Studio
All exceptions start as first chance exceptions. The debugger gets notified every time an exception is thrown.
Read more >What is a "first chance exception"? - Stack Overflow
It's a debugging concept. Basically exceptions are thrown to the debugger first and then to the actual program where if it isn't handled...
Read more >5.15. Breaking on a First Chance Exception - O'Reilly
Click the OK button and then run your application. Any time the application throws the type of error you selected in the Exceptions...
Read more >ApexMocks - throw exception on 1st call but not on second
twice and the first time you call it, you want an exception to be thrown but the second time, you want no exception...
Read more >Remove exception during first run in p:queue-work - Drupal
Remove exception during first run in p:queue-work. Closed (fixed). Project: Purge. Version: 8.x-3.x-dev. Component: Code. Priority:.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just investigated a bit more your stack trace.
The problem comes from ShrinkWrap which is a 3rd party lib I use to link to the Maven system. The library seems to have difficulties to initialize.
This might be due to it not finding your maven configuration file.
Can you please type the following line before entering the
analyze directory d:\sigdev\dst-utils
command (and replace PATH_TO_MAVEN_SETTINGS with the correct path) :session mavenSettingsFilePath C:\PATH_TO_MAVEN_SETTINGS\settings.xml
I suspect that ShrinkWrap does not find your configuration but not 100% sure.
Meanwhile I have added some more logging when an exception occurs. So could you please pull the latest changes from the master branch, compile it again and run it again, and send me the stack trace (it should this time include root cause exceptions).
Thanks
Clever. I will look around the documented purpose of this file. If possible, add a message in pom explorer for other users.
Le mer. 2 août 2017 à 17:06, Steve Horne notifications@github.com a écrit :