On 9 Jun 07, at 5:56 AM 9 Jun 07, Dennis Lundberg wrote:
Sure. I think I've found out why the process stopped after the
files had been unzipped on the server. It turns out that we are
using OS-dependent file separators in the rename script. Here's
what that script looks like for the maven-
On 8 Jun 07, at 11:26 AM 8 Jun 07, Arnaud HERITIER wrote:
Instead of writing specifications couldn't we write tests ? There's
no/few
doubts with tests ;-)
Kenney has already posted, and I agree with what he says but
essentially you can't write tests until you have the basic principles
d
I'm basically against this idea.
It can result in polluted jars very easily. Even if you
have 2 poms in the same dir, both specifying different source directories,
the files in target/ will overlap. the second executed pom will also contain
the files from the first executed pom.
Unless the tar
Arnaud HERITIER wrote:
Instead of writing specifications couldn't we write tests ? There's no/few
doubts with tests ;-)
(But we'll also write a complete documentation about that ...)
1) First we write the specification - what the software is supposed to do.
2) Then we write the design of the
I like the idea of a work in progress section in here. I've been wanting
to communicate in some way what I'm working on, but haven't found a good
way to do it.
We previously had two options to do this:
1. JIRA, for individual issues
2. Our release calendar, for the release dates
For me, who do
Sure. I think I've found out why the process stopped after the files had
been unzipped on the server. It turns out that we are using OS-dependent
file separators in the rename script. Here's what that script looks like
for the maven-one-plugin release that I tried earlier:
mv org\apache\maven\
