DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10719.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
What about releasing an ant 1.5.4 before 1.6 with the current head revision
in it, plus as many bugs from bugzilla as possible ?
This would help a number of people and be encouraging for all the ant users
who have reported bugs or suggested patches in bugzilla.
Plus this would bring the import/
On Wed, 12 Mar 2003, Costin Manolache [EMAIL PROTECTED] wrote:
It'll have documentation after it is reviewed by more people and we
know it's going to be stable.
I don't like this approach at all. How are you expecting user
feedback on an undocumented feature?
Stefan
Steve Loughran wrote, On 13/03/2003 0.39:
...
That's the import task that doesnt have any documentation, right?
Jikes, you're right. How do I submit it, as the usual HTML page or the
@tags... I'm a bit behind the Ant documentation efforts, sorry.
Maybe the thing to do is look at what major
On Wed, 12 Mar 2003, Costin Manolache [EMAIL PROTECTED] wrote:
Do we have any plan or idea on when we'll start distributing 1.6
milestone builds ?
Ant has never released any milestone builds so far, so no, there is no
plan yet AFAIK. If there was, you'd know it for sure 8-)
Before we release
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17934.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17871.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
On Thu, 13 Mar 2003 09:50 am, Costin Manolache wrote:
Hi,
Do we have any plan or idea on when we'll start distributing 1.6 milestone
builds ?
I'm not really sure what a milestone build means and, more importantly, what
expectations it creates for stability of feature set.
For 1.6 I think
On Thu, 13 Mar 2003 06:29 pm, Antoine Levy-Lambert wrote:
What about releasing an ant 1.5.4 before 1.6 with the current head revision
in it, plus as many bugs from bugzilla as possible ?
A rose by any other name. If we release the HEAD revision, we'll call it 1.6
This would help a number of
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17952.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
I think it would be useful in some cases.
For instance I have the attribute dependency=full and dependency analyzer
includes in myejb.jar classes that have to be in app server classpath. So I
have them double and probably class loading issues.
What do you mind? Does it make sense to include an
This is indeed interesting. I do something quite similar for another purpose
(scans a JAR for all classes having a give static method signature, executes
all these methods, gathering the meta-info required, generate a XML file
then stuck into the JAR's META-INF directory).
Something I do is to
The current ant task runs an ant process for a specified build file in a
specified directory. I wanted to be able to give it more than one
directory, and execute the build file found in each directory specified,
or give it a set of build files to execute. This can be really useful
for building
Dominique Devienne wrote:
This is indeed interesting. I do something quite similar for another purpose
(scans a JAR for all classes having a give static method signature, executes
all these methods, gathering the meta-info required, generate a XML file
then stuck into the JAR's META-INF
Why not posting it? Seems interesting enough, and once it's posted people
can start using it or tweaking it. Best way to post it is to open a new
Enhancement in Ant's BugZilla. This keeps everything in one place (posted
sources, JARs, ZIPs, whatever and the discussions about it).
Using
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17871.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14553.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17506.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17961.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14553.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Mmm...spoken like someone with an emotional attachment to SubAnt due to
your involvement with it. Let's be constructive and stick with the
merits of my proposal because you've got some good points. BTW, this is
my first submittal to any open source project so let's approach this
from a today's
I am more minded to put the subant in there, with perhaps some minor tweaks.
The reason to use a separate task when there are major changes in
functionality are
(a) we can have more sensible defaults (here: property inheritance, and what
happens when you invoke a target called . I'd like that to
Yeah, if you put subant out in CVS, I'd be happy to play around with
it to see how it could fit for me.
Andy
[EMAIL PROTECTED] 3/13/2003 11:07:53 AM
I am more minded to put the subant in there, with perhaps some minor
tweaks.
The reason to use a separate task when there are major changes in
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17871.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17961.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
- Original Message -
From: Dominique Devienne [EMAIL PROTECTED]
To: 'Ant Developers List' [EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 07:55
Subject: RE: [PATCH] Ant Task - Proposed Enhancement
But where does it stop? subant also supports automatic ordering of the
projects called
Steve, My build process will rely heavily on this task to load packages,
procedures, triggers, view, types, and apply grants in Oracle9i. I agree
that some tests are needed and I will look into creating some. Thanks,
-Rob Anderson
-Original Message-
From: Steve Loughran [mailto:[EMAIL
+1
-Original Message-
From: Conor MacNeill [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2003 5:29 PM
To: [EMAIL PROTECTED]
Subject: JDK 1.1 support
I'd like to throw this up again. What are peoples thoughts on the following
1. Make Ant 1.6.x the last JDK 1.1 release. This would
28 matches
Mail list logo
