Re: Dependency resolution in Java builds
Markus Gessner wrote:
Having just begun working with Java, I of course cannot really
appreciate its merits, but it seems, that it would be impossible to
implement the needs of a lot of business oriented applications without
its standards (Java EE), and some frameworks do have a certain charme
(e.g., JAXB and Hibernate). Nevertheless, the build environment I
experience gives me the overall impression of a car, nicely fitted with
teak panels, a GPS system and a minibar, but which has to be cranked
every mile or so. Says a somewhat frustrated mind, who prefers the
tramway :-)
OH, come on! Really?
I've worked on some hairy large projects and smaller ones, too. The time to
build an application as affected by this issue is never a factor, unless you
have improperly factored the dependencies, and that would be a problem in any
language.
Java's dependencies, at least when using Ant (I agree Maven is a bitch), are
usually resolvable for incremental builds without issue. When they aren't,
it's because of the unique features of Java (it compiles taking
already-compiled libraries into account, sort of combining compilation and
linking if you're thinking C[++]-ishly). In those situations, you do a clean
build and wait an extra minute. Big effing deal!
If your clean builds take hours, that's not Java's fault, that's yours.
--
Lew
Ceci n'est pas une fen??tre.
..___________.
|###] | [###|
|##/ | *\##|
|#/ * | \#|
|#----|----#|
|| | * ||
|o * | o|
|_____|_____|
|===========|