James Fuller wrote:
no, I have already gone through the input masking funits more about
locking down...or giving the opportunity to lock down; e.g. secure class
loading, working with digital certs, etc...
to run ant secure you'd need to generate a JAR of everything in the
tasks and tasks.opt
Steve Loughran wrote:
[EMAIL PROTECTED] wrote:
- manual needs some pretty generous scrubbing and reorganisation
(note: not a fan of any of task styles used...ex. WhichResource) and
generally a fresher look and feel.
WhichResource is one of the xdoclet generated docs. New velocity/XSLT
can impro
Matt Benson wrote:
--- Peter Reilly <[EMAIL PROTECTED]> wrote:
* local properties for macros (most likely Jose's
solution with
an auto removal of the local properties at
the end of the macro)
Do you think the ThreadLocals are just not going to
behave themselves?
Thread locals can
[EMAIL PROTECTED] wrote:
- manual needs some pretty generous scrubbing and reorganisation (note: not a fan of any of task styles used...ex. WhichResource) and generally a fresher look and feel.
WhichResource is one of the xdoclet generated docs. New velocity/XSLT
can improve that.
- would like to
--- Peter Reilly <[EMAIL PROTECTED]> wrote:
>* local properties for macros (most likely Jose's
> solution with
>an auto removal of the local properties at
> the end of the macro)
Do you think the ThreadLocals are just not going to
behave themselves?
-Matt
I think we should aim to have an ant 1.6.3 release soon,
this should include the current fixes and some minor
features (-noclasspath for example).
and a 1.7 for around the start of summer
to include the
*
* local properties for macros (most likely Jose's solution with
an auto removal of
As the Eclipse Ant integration team lead and not trying to influence your decision but I thought I would give the Eclipse perspective.
Eclipse 3.1 is coming out in June 2005 as Jan indicated.
For me to have a chance to update and release Ant 1.7 within Eclipse it would be great to get an Ant rel
note to myself re wish list for Ant 1.7 for the summer...
+1 to minor release to 'bed down' some of the structurally big changes
w/o cross referencing with current buglist/wish listsoff the top of my head;
- manual needs some pretty generous scrubbing and reorganisation (note: not a
fan of
[EMAIL PROTECTED] wrote:
Mmh & smartfrog: if you are the author you should be able to
change the license, IMO ;-)
no, because I wrote it for my employer.
I can redo it from scratch though, it wasnt hard.
-
To unsubscribe, e-mail: