I think we have this planned for 2.1. I know it's been discussed before.
-----Original Message-----
From: Christian Gruber [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 24, 2007 7:13 PM
To: Maven Developers List
Subject: thought about a change to compile scope.
Hey.
I was thinking about the best-practice (I hate that word) of
including all direct dependencies in a pom even if you would get the
code transitively (in case transitive relationships are changed
behind the scenes). This makes sense, but it makes me wonder if the
compile phase shouldn't only import dependencies non-transitively. I
think that, because the compiler may not need to link in all classes
ultimately required at runtime, it would effectively enforce this
best-practice. Transitivity would be then for runtime scope which is
obviously used in packaging or deploying.
One possible problem would be with the m2eclipse plugin which (at
present) really does need to use transitive dependencies, but I think
it might actually ignore scope, since eclipse has no such concept and
I've seen all classes already there (including provided, test, etc.).
Thoughts? Flaws in thinking?
Christian.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
