Runtime classpath problem with maven dependencies #925

Activity

1. dmarrazzo commented on May 18, 2019

   

   dmarrazzo

   on May 18, 2019

   Author

   More actions

   Hi @fbricon
   is it the right place for this issue?
   Thank you
2. dmarrazzo commented on May 18, 2019

   

   dmarrazzo

   on May 18, 2019

   Author

   More actions

   I've noticed this behavior:

   • when I run vscode inside the project (kie-client) it works nicely!
   • when I run vscode in the parent folder (that contains other projects and kie-client), It has the problem.

   In order to debug, I've added those lines at the beginning of the main:

           try {
               Class.forName("org.drools.compiler.commons.jci.readers.ResourceReader");
           } catch (ClassNotFoundException e) {
               e.printStackTrace();
           }
           ClassLoader cl = EmbedMain.class.getClassLoader();
   
           URL[] urls = ((URLClassLoader) cl).getURLs();
   
           for (URL url : urls) {
               System.out.println(url.getFile());
           }

   The output (attached) shows that the classpath is significantly different:

   parent.txt

   inner.txt
3. fbricon commented on May 18, 2019

   

   fbricon

   on May 18, 2019

   Collaborator

   More actions

   vscode-java is not providing the Java running facilities in VS Code. That would be https://github.com/Microsoft/vscode-java-debug. Now it seems you're running mvn directly, so that's probably not even vscode's issue. You should see the exact same results when running in a terminal.
   I won't be able to look at this issue until the next few days, but maybe someone else can help you investigate in the meantime.
4. fbricon

   added

   bug

   Maven

   on May 18, 2019
5. dmarrazzo commented on May 18, 2019

   

   dmarrazzo

   on May 18, 2019

   Author

   More actions

   Hi @fbricon thank you for the prompt reply, I've open the same issue in vscode-java-debug.
   BTW, the execution in maven command line was there just for comparison.
   Now it's not more relevant since the same vscode has 2 different behaviour depending on the workspace root.
6. dmarrazzo commented on May 23, 2019

   

   dmarrazzo

   on May 23, 2019

   Author

   More actions

   It's a bug of vscode-java-debug, so I'm closing here.
   I'm looking forward to see the resolution! Thank you
7. dmarrazzo

   closed this as completedon May 23, 2019