> Ok, I think something might be wrong with eclipse's ant? Earlier
today
> I downloaded ant 5, so I could find a way to work around not having
> available as a task. Opened up the manual for the ant core tasks,
and
> there it is. Ok, then I look at the build file, Jody says it
doesn't
> work with 1.3.8. Ok, download 1.3, to look at the manual, to see
what
> I might be able to use instead, where I'm limited. available is a
> totally valid task for 1.3. So I grab 1.1, just to see. And, uh,
it's
> there too. So this is a core task that has been there since version
> 1.1, as far as I can tell. That said, I can't get it running on
> eclipse either. Ideas anyone? I did a bit of google searching and
> found nothing, but my time is short, so maybe someone can find a
> solution? I do find it odd that none of us on eclipse can get the
> available task to work. I don't think I wrote it wrong, and it
works
> on the command line...
You can set eclipse up to use an external ANT (is that what you did?)-
but most
of our developers won't right off the bat.
The latest eclipse M8 uses ant 6 (and a horrible new look). It has a
lot of
actually ant changes so it may help. Just check it handles you
available element
correctly.
Hope this helps?
I'm actually completely fine with doing all my ant building from the
command line. I was more wondering about you guys, and then about
developers in general. The question is if the available tags are worth
it if developers starting up in eclipse don't have it work right away.
Are you guys able to get it running with available tags on eclipse? I
tried setting external ant, but didn't meet success, but again, I don't
really care. I should tell you what the available tags let me do:
The first is a fix for Pierrick Brihaye's complaint (which I found
totally valid), of checking out for the first time from cvs and having
no conf directory and thus failing. So what the available tag does is
check to see if there is a conf directory that exists, and if not
constructs one from UserBasic.
The second fix I may be able to find a way around, basically it allows
you to type 'ant run', which just runs jetty without first building the
war and copying it over (through 'ant test'). Actually, if we did a
binary distribution then this would not be necessary, since I think
we'd just unwar the app for them, and so 'ant run' would not fail. So
it's actually not too important.
So on the one hand we could fairly easily live without these. But on
the other hand, why the hell does eclipse not support the available
task? And if it's as simple as saying somewhere that if you have that
problem with eclipse then you can just set it to use a different ant,
then is that reasonable? Since it would only be developers who would
have the problem (then again, the big wins for the available tags are
for developers).
Though I guess M8 it does work, so at least eclipse knows its a problem,
and it will eventually fade away...
Chris
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/