search

tony1223 / run-jetty-run

Automatically exported from code.google.com/p/run-jetty-run
0 stars 0 forks source link

rjr doesn't update classpath #87

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When the POMs of other projects change, the classpath of RJR doesn't update.

How can I force it to recalculate the classpath?

I'm using WTP 3.7.1 (lastest from Indigo), m2e 1.0.100, RJR 1.3, Maven 3.0.3.

Original issue reported on code.google.com by adigu...@gmail.com on 7 Oct 2011 at 4:08

GoogleCodeExporter commented 9 years ago 
I found a file in workspace/.metadata/.plugins/runjettyrun/ and deleted it but 
the classpath is still wrong.

I can see that the classpath is correct when using mvn dependency:tree or with 
the dependency view in the POM editor of m2e. But it's broken when I look at 
the output of RJR in the console ("ProjectClassLoader: ...")

Original comment by adigu...@gmail.com on 7 Oct 2011 at 4:11

GoogleCodeExporter commented 9 years ago 
The issue went away after rebooting my PC but I'm wary what will happen when I 
change the parent POMs next time.

Is the "Maven Integration for WTP" plugin necessary to keep the classpath 
current?

Original comment by adigu...@gmail.com on 10 Oct 2011 at 9:42

GoogleCodeExporter commented 9 years ago 
It should be as same as your project classpath , 
and also add the jars in WEB-INF/libs and WEB-INF/classes . 

I haven't test on 3.7.1 so far , if you find this next time , 
would you mind also check the project classpath and see if the jar files is 
correct?

We are not caching the classpath , we generated a new classpath every time when 
you launch it.

The reason for us to keep a classpath file is passing the classpath to 
Bootstrap by file , since there's length limit for command line . (Reference 
Issue 48 . )

Let me know if this keep happening , I will review this then.

Original comment by tonylovejava on 14 Nov 2011 at 10:08

GoogleCodeExporter commented 9 years ago 
I'll wait for a fix to issue 88 because that would help to track down the 
problem.

Original comment by adigu...@gmail.com on 22 Nov 2011 at 1:44

GoogleCodeExporter commented 9 years ago 
I believe this one is related to Issue 102.

Original comment by tonylovejava on 13 Dec 2011 at 2:22

GoogleCodeExporter commented 9 years ago 
Because we didn't get more details in past two month, close this first.

If there's any new details with this issue, 
it's still very welcome to reopen this or create a new issue.

Original comment by tonylovejava on 19 Feb 2012 at 4:42