donaldp wrote:
>
> Now I just need to figure out how to get it to compile without the
presence of X windows ;)
On rubix (my Linux box), I installed Xvfb and added the following lines to
my cron job, before and after the build respectively:
/usr/X11R6/bin/Xvfb :8 &
export DISPLAY=:8
kill `ps -eo pid,comm | awk '/Xvfb/ { print $1 }'`
> - <ant>
> - <property name="version" value="@@DATE@@"/>
> - </ant>
> + <ant/>
I see that you figured out where the -Dversion came from. ;-)
> <jar id="jrefactory" name="ant.build/lib/PrettyPrinter-@@DATE@@.jar"/>
Chances are good that the jar produced isn't going to have this name. Some
background on how this evolved: originally I simply captured the name of
the jar produced by the build. It would seem weird to build a jar named
foo-v2.1 when the jar produced wasn't an official version, but that's how
some projects did it, and who was I to question the wisdom of such a
scheme? :P
Inevitably, v2.1 would yield to v2.2. The next build would have a lot of
yellow in it as prereqs weren't found. No problem, simple to fix.
Eventually, the list of projects grew to the point where it became a
frequent event that somebody would be tweaking the version number.
Ultimately, I had to solve this somehow, so I started specifying the
version. Originally, I specified a fixed string ("gump") which solved my
problem, and clearly identified the source of the jar if somebody
downloaded a nightly build. Ultimately I refined this to specify the date
so that jars so there was a better correlation between the jar and which
build was used to produce it.
- Sam Ruby
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
