|
I
don't understand why it's acceptable to have a tool environment that allows
people to check in broken code. It's certainly not acceptable to me that I
could compile in both our provided development environments, run the full set of
unit tests, and still check in broken code.
When
you say you don't want to "require all developers to
always have also the java 1.4 environment at hand" it
was my understanding that we already explicity require this. How else does
one develop and test for a Java 1.4 environment as required by section 3.3 of
the cookbook? Are we saying that the rationale for not checking in broken
code as outlined in section 7.2 no longer applies?
Tom
Hello
Tom!
It was probably me
that removed the java 1.4 libraries from the Eclipse environment. I had some
problems with it and didn’t understand why we explicitly specified the
libraries.
I don’t think that
this is a serious problem. Not serious enough to require all developers to
always have also the java 1.4 environment at hand. I hope that having everyone
running their favorite version of JDK glancing at the nightly build, and some
extra checks before every release would be
enough.
For me, as you
understand from above, the big problem is that the nightly build doesn’t give
information that the build failed at a glance. I will have to fix
that.
/Linus
From: Tom
Morris [mailto:tfmorris@xxxxxxxxx]
Sent: den 31 oktober 2006
21:30
To: dev@xxxxxxxxxxxxxxxxxx
Subject: [argouml-dev] Project compiler
settings (was The plan for the 0.23.3
release)
I've fixed this
problem, but the fact that it occurred points out a shortcoming in both our
Eclipse and Ant build environments.
For Eclipse, we
specify the compiler versions, but not the Java libraries to compile against,
so a change in the developer's workspace settings will affect ArgoUML
builds. I believe I had library versions specified at some time in the
Eclipse project settings, but they got removed (not sure whether it was
intentional or not). If everyone has upgraded to Eclipse 3.2, I'd like
to see us have all Eclipse project definitions specify the J2SE-1.4 execution
environment. There's a little background about this new feature here http://www.developer.com/java/ent/article.php/3639021
For Ant, we rely on
the libraries pointed to by JAVA_HOME, so changes to this in the system
environment can affect ArgoUML builds. We don't set this explicitly, nor
do we check to make sure that it points to Java 1.4 libraries. Since I
have multiple Java development environments, I guess I'll just hardwire my
build scripts to reset JAVA_HOME to point to a Java 1.4
installation.
|
