|
On 03/04/2016 05:11 PM, Max Rydahl
Andersen wrote:
I assume the order issue here is "just" about
wether one scope comes before another, not that individual
jars comes before and after ?
I don't know. That's why I'm asking for more details.
Examples of where order are an issue I can think
of where you use stifled api jars during compilation vs
api+impl jars during tests. If the tests jars don't "win"
during run then they will hit the api jars and break. This is
example from using standard oracle jsf api jars and use some
specific vendor jar for tests.
Ok. Do you know an example of such a project?
Currently, m2e would handle it by having the vendor jar classpath
"leaking" into the main source project while writing code. What I'm
trying to identify is what would be the impact of this case a user
perspective if we have 2 containers instead of a single one. I don't
know Maven in that level of details to figure it out by myself.
Question on wether its important or not ? It
is something JDT and m2e already do so I would say it would be a
step backwards if we come up with a design that makes it wrong
what order of jars there will be.
Define "it" ?
On the related bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=486035 , I also
suggested that if 2 classpath containers are a real problem for some
use-cases, we could let user choose whether to use 1 or multiple
containers when doing "Update Maven projects".
|
