Michael Wechner wrote:
Andreas Hartmann wrote:
Jörn Nettingsmeier wrote:
[...]
btw, why do we ship class files in svn?
because these classes are considered as tools. Do you want to ship Lenya
with the ant java sources and first build ant?!
ok, that's an argument, but it gets absurd pretty quick.
in the c world, it would in fact be totally inconceivable to have the
make and autotools binaries in a cvs. (although in tarballs it's common
to include auto*-generated scripts as a courtesy to users - that's fine
by me.)
i'm sure you have very good reasons for shipping ant, but that should be
an exception and ease-of-use hack, not an argument for binaries in a svn
tree. i'm not even sure i like the abundance of jar files, but i must
confess having all those as svn externals would become unwieldy. it's a
trade-off.
in any case, building those ant tasks takes only a few seconds and
requires no configuration, i.e. it can't possibly go wrong.
and having as few generated files as possible in the repo is certainly a
good idea.
not if they are considered tools, whereas I agree that one should
separate the build process from the build process
of the tools. See for instance the tools/config.
Can we please put back these classes such that Lenya can be built again
with Java 1.4?
if i understand the issue correctly, the classes are there, but whenever
some committer with java 1.5 commits and forgets to exclude them, they
will be in a bytecode version that is not backwards-compatible to 1.4.
and that is definitely a strong argument towards getting rid of those
class files. all we need to do is add compile-build-tasks to the "all"
target. there doesn't even have to be an extra build step for trunk users.
jörn
--
"Open source takes the bullshit out of software."
- Charles Ferguson on TechnologyReview.com
--
Jörn Nettingsmeier, EDV-Administrator
Institut für Politikwissenschaft
Universität Duisburg-Essen, Standort Duisburg
Mail: [EMAIL PROTECTED], Telefon: 0203/379-2736
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
