Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
GoogleCodeExporter opened this issue Jul 7, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

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
Copy link
Author

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 [email protected] on 15 Nov 2014 at 1:00

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant