Hi,
I found an interessting sentence at the User Guide.
32.6.1. Implicit transitive dependencies
... and the compile task uses all dependencies, not just the first level
dependencies.
That means, that normally the compile tasks should use only the first
level dependencies.
Is it a bug?
regards,
Mathias Kalb
Am 20.01.2011 14:00, schrieb Steinar Haugen:
This point is a good one.
Even if we're using transitive dependencies, we might want them to be
non-transitive at compile-time to make sure we get compile errors if
we're missing a first level dependency. When running tests, building
wars, etc. they should be transitive.
Is there a way to achieve this?
-Steinar
On Thu, Jan 20, 2011 at 12:58 PM, Mathias Kalb
<[email protected] <mailto:[email protected]>> wrote:
Hi,
maybe I am wrong, but i thought that only the tomahawk.jar will be
on the javac classpath.
The transitive dependencies are only needed at runtime (or at a WAR).
If a developer uses classes from common-lang it compiles without
declaring it as a first level dependency.
regards,
Mathias Kalb
Am 20.01.2011 12:43, schrieb Peter Niederwieser:
Not sure what you are trying to say. Declaring the first-level
dependencies
is the responsibility of the developer. Transitive dependency
management
cares about the rest.
Cheers,
Peter
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Steinar Haugen
Gausengate 12
3080 Holmestrand
Phone: +47 932 08 373
Email (p): [email protected] <mailto:[email protected]>
Email (w): [email protected]
<mailto:[email protected]>
Web: http://www.haugenconsulting.no
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
