search

mbonaci / run-jetty-run

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

Does not resolve artifacts/classpath properly in a multi module maven project #186

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Does not resolve artifacts/classpath properly in a multi module maven project 

What is the expected output? What do you see instead?
Multi module maven project brings artifacts from other dependent projects also 
whereas maven nicely excludes/resolves artifacts from dependent projects, i.e., 
current project gets preference on which artifact to choose. How can we fix 
this classpath issue in case of multi module projects in Eclipse?

What steps will reproduce the problem?
1. Setup a multi module maven project
2. Make sure there are common artifacts that current project overrides from the 
dependent project
3. Run Jetty Run this project

What Eclipse version are you using ?
4.3, 4.4

What Run-Jetty-Run version are you using?
latest

What OS are you using ? 32bit or 64 bit?
64 bit

Please provide any additional information below.

Original issue reported on code.google.com by krishna81m on 21 Oct 2014 at 4:01

GoogleCodeExporter commented 9 years ago 
you may refer to this issue which provides a patch - 
https://code.google.com/p/run-jetty-run/issues/detail?id=187

Original comment by jumperc...@gmail.com on 15 Nov 2014 at 1:00