Steve,
Steve Loughran apache.org> writes:
>
> that is a simple enough defect that we can patch in situ.
>
> OK. done!.
>
Great!
Thanks,
--knut
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Hi all!
A long time ago I submitted some patches to get Ant running on
OpenVMS. There didn't seem to be much interest in this at the time,
but I've now noticed that there actually seem to be people using it
and requesting enhancements.
I here have a quite embarassing patch to my original patch to
Hi,
With a previous patch for runant.py I wrote to use the new ant-launcher.jar
I accidentally introduced some redundant double quotes in the command to be
executed. As it turns out these quotes are more than redundant, they're
even wrong. If the user doesn't supply a target to run (i.e. run the
Regarding XML namespaces...
Something else that would interest me is how namespaced attributes will be
handled. IMHO they should be allowed and ignored. But will a task
implementation have the ability to query them?
Cheers,
--knut
"peter reilly" <[EMAIL PROTECTED]> wrote in message
news:[EMAI
Stefan,
> > I have been working a little bit again to get Ant to run on
> > OpenVMS.
>
> Thanks, patch committed with some slight indentation changes (if only
> you could stop using tabs 8-).
Cool. I'll try :-)
--knut
-
To u
The attached patch should make the python script work.
--knut
> Yes, I do not know python, so please do !!!
> I did not change the os/2 script either.
begin 666 runant-python-launcher-patch.txt
[EMAIL PROTECTED](')U;F%N="YP>0T*/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3T]
M/3T]/3T]/3T]/3T]/3T]/3T]/3T]/3
Maybe the task could be modified to use the current target (the
target in which the task is contained) as the default, instead of
the called project's default target. That's how my own works and I
think it is a reasonable default.
--
knut
"Sean Rohead" <[EMAIL PROTECTED]> wrote in message
new
Hi,
I have been working a little bit again to get Ant to run on OpenVMS. It
seems like most things actually run quite well, which is encouraging. Also
the latest maintainance release of the Java VM (1.4.1-2) fixes some problems
that kept me from using Ant on OpenVMS (e.g. the File#setLastModified(
>
> These changes expand on Antoine's -lib code to support multiple -lib
options.
> In addition, the -lib option can now name a directory containing jars and
all
> jars in that directory will be added to Ant's launch classpath.
>
So I suppose it isn't possible to add a directory with classes in it
Antoine,
I noticed that the runant.py wasn't updated in the same run. Do you want me
to write a patch for this?
--knut
> antoine 2003/09/22 14:10:10
>
> Modified:src/script ant ant.bat runant.pl
>src/main/org/apache/tools/ant/launch Launcher.java
>src/m
> > > 3. and
> > >
> > a) resolution of properties
> > The issue here is that properties get resolved when the
> > macro is used and not when the macro is defined.
> > I think that it would be difficult to resolve the
> > properties correctly when the macro is defined.
> >
>
Hi,
This patch for the runant.py Ant launcher script uses the new
ant-launcher.jar to run Ant instead of adding the contents of the lib
directory to the system classpath explicitly.
I've further patched the script to:
- better match the structure of the 'ant' script
- insert the -Djikes.class.
Different people understand different things under MACRO. But I'd say to
anybody who's familiar with Lisp, this is certainly has MACRO like
semantics. The difference would be that in Lisp you explicitly (using
"quote") have to tell the evalutor not to evaluate an expression in a macro
definition.
> >
> > One thing you could do here is redefine itself
> > by doing something like:
> >
> >
> >
> >
> >
> >
> > which would realize your desired effect. This could be done internally
> > by when for example no name attribute is given.
>
> This could also be done by:
>
>
>
>
What's the line:
if (uri.startsWith("ant:") && !uri.startsWith("antlib:")) {
in MacroDef#setURI(String) about? It can surely be written better :-)
But the code looks like it will be the same for many tasks, so maybe an
abstract AntlibTask and AntlibTaskContainer would be nice to have. What
Costin,
> > This raises a question: Are properties whose values are resolved by
custom
> > PropertyHelpers always converted to Strings? I see that the return type
> > of PropertyHelper#getPropertyHook(String, String, boolean) has Object as
> > the
> > return type. But if that's always converted
Hi,
Up until now I've been using my own like task. But now that Ant
1.6 doesn't seem too distant anymore I'd like to integrate with .
There's one thing I'm wondering about: Can reuse the same Project
object corresponding to a buildfile in multiple calls? The reason that I'm
askin this is that
This looks excellent! It makes Ant a lot more flexible, but at the same
time also more compilcated to use. Buildfiles with (possibly nested)
s and s could be a lot harder to understand and
maintain. But if used correctly, probably easier!
A question: is a special task in the sense that it seem
Sounds great!
In anticipation of this feature I have used a few namespaced properties for
my custom tasks. And since Ant 1.5 doesn't have any value for these, I've
just made the tasks resolve them explicitly.
This raises a question: Are properties whose values are resolved by custom
PropertyHelp
> > The others are antlib/namespace/polymorph stuff. I'm wondering if we can
> > get to the point where the ant optional tasks are packaged as antlibs
and
> > potentially not added to the root loader if their supporting libraries
are
> > not also available to the root loader. This would allow them
> >>
> >>>Just to get you up to speed, the current issue is about multiple
> >>>inheritance, and how the current system allows cross-import (unwanted?)
> >>>side-effects, as Conor has brilliantly shown.
> >>
> >> What I'm not sure I understand is what import has to do with multiple
> >> inheritance
The old native file system (ODS-2) on OpenVMS is completely case
insensitive. A file will have all uppercase letters in the name and can be
accessed using lowercase, uppercase, or mixed case.
With the new ODS-5 file system this is a little bit different; I'd call it
"partially case sensitive". F
22 matches
Mail list logo
