1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
|
{ stdenv, fetchurl, gcj, junit }:
let version = "1.7.1"; in
/* TODO: Once we have Icedtea, use this Nix expression to build Ant with
Sun's javac. */
stdenv.mkDerivation {
name = "ant-gcj-${version}";
src = fetchurl {
url = "mirror://apache/ant/source/apache-ant-${version}-src.tar.bz2";
sha256 = "19pvqvgkxgpgsqm4lvbki5sm0z84kxmykdqicvfad47gc1r9mi2d";
};
patches = [ ./use-gcj.patch ];
buildInputs = [ gcj junit ];
configurePhase = ''
mkdir -p "tool-aliases/bin"
cd "tool-aliases/bin"
cat > javac <<EOF
#!/bin/sh
opts="-C"
echo 'running \`gcj '"\$opts \$@'..."
exec "$(type -P gcj)" \$opts \$@
EOF
chmod +x javac
ln -sv $(type -P gij) java
export PATH="$PWD:$PATH"
cd ../..
export JAVA_HOME="$PWD/tool-aliases"
# Make JUnit visible.
export CLASSPATH="$(find ${junit} -name \*.jar -printf "%p:")"
'';
# Note: We don't build the javadoc.
buildPhase = ''
mkdir -p "$out"
./build.sh -Dant.install="$out" install-lite
'';
installPhase = ''
# Actually, everything is already installed at this point, so we just
# rearrange a few things.
rm -v "$out/bin/"*.bat
mkdir -p "$out/lib/java"
mv -v "$out/lib/"*.jar "$out/lib/java"
sed -i "$out/bin/ant" \
-e "s|^ANT_LIB=.*$|ANT_LIB=$out/lib/java|g ;
s|JAVACMD=java.*$|JAVACMD=${gcj}/lib/jvm/bin/java|g ;
/^ant_exec_command/i export ANT_HOME=$out"
'';
meta = {
description = "Apache Ant, a Java-based build tool";
longDescription = ''
Apache Ant is a Java-based build tool. In theory, it is kind of like
Make, but without Make's wrinkles.
Why another build tool when there is already make, gnumake, nmake, jam,
and others? Because all those tools have limitations that Ant's
original author couldn't live with when developing software across
multiple platforms. Make-like tools are inherently shell-based -- they
evaluate a set of dependencies, then execute commands not unlike what
you would issue in a shell. This means that you can easily extend
these tools by using or writing any program for the OS that you are
working on. However, this also means that you limit yourself to the
OS, or at least the OS type such as Unix, that you are working on.
Ant is different. Instead of a model where it is extended with
shell-based commands, Ant is extended using Java classes. Instead of
writing shell commands, the configuration files are XML-based, calling
out a target tree where various tasks get executed. Each task is run
by an object that implements a particular Task interface.
'';
homepage = http://ant.apache.org/;
license = "APLv2";
maintainers = [ stdenv.lib.maintainers.ludo ];
platforms = stdenv.lib.platforms.gnu; # arbitrary choice
};
}
|