search

wjw465150 / run-jetty-run

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

Project classpath issue for WebApp classpath and Jetty classpath #114

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Adding a maven project as a custom classpath entry to either the WebApp 
classpath or the Jetty classpath only adds the class output folders to the 
classpath.

I would expect that the maven dependencies in the added project would be put on 
the classpath as well. In fact they are added to the visual classpath inside 
the RJR configuration GUI, but are not added to the classpath when running RJR.

Original issue reported on code.google.com by rthu...@gmail.com on 17 Feb 2012 at 9:42

GoogleCodeExporter commented 9 years ago 
I'm using eclipse 3.7.1, RJR 1.3.2, and 1.0.100.20110804.

Original comment by rthu...@gmail.com on 17 Feb 2012 at 9:44

GoogleCodeExporter commented 9 years ago 
After a closer look, the same happens with ordinary java projects. The exported 
libraries is not added to the RJR classpath, only the class folders of the 
added project.

Original comment by rthu...@gmail.com on 20 Feb 2012 at 6:28

GoogleCodeExporter commented 9 years ago 
I have confirmed that's a bug for custom classpath entry , 
the project is only getting included the output folder.

I will fix this soon.

Original comment by tonylovejava on 20 Feb 2012 at 3:05

GoogleCodeExporter commented 9 years ago

Original comment by tonylovejava on 20 Feb 2012 at 4:33

GoogleCodeExporter commented 9 years ago 
I found I didn't handle project classpath well in 1.3.2 ,
it's really very complicated job to build a classpath editor by myself. :-|

Hope we clear all the bugs of custom entries.

Fixed since 2012/02/21, will be 1.3.3 . Committed version r311 .

Original comment by tonylovejava on 20 Feb 2012 at 4:36