cvs commit: ant/docs/manual conceptstypeslist.html

[stevel]

stevel  2003/09/29 17:10:12

  Modified:docs/manual/CoreTypes Tag: ANT_16_BRANCH assertions.html
   docs/manual Tag: ANT_16_BRANCH conceptstypeslist.html
  Log:
  assert docs go in
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.2.2.2   +14 -6 ant/docs/manual/CoreTypes/assertions.html
  
  Index: assertions.html
  ===
  RCS file: /home/cvs/ant/docs/manual/CoreTypes/assertions.html,v
  retrieving revision 1.2.2.1
  retrieving revision 1.2.2.2
  diff -u -r1.2.2.1 -r1.2.2.2
  --- assertions.html   27 Sep 2003 03:19:49 -  1.2.2.1
  +++ assertions.html   30 Sep 2003 00:10:12 -  1.2.2.2
  @@ -147,11 +147,15 @@
   Example: set system assertions and all org.apache packages except
   for ant, and the class org.apache.tools.ant.Main.
   pre
  -lt;assertions enableSystemAssertions=true gt;
  -  lt;enable package=org.apache /gt;
  -  lt;disable package=org.apache.ant /gt;
  -  lt;enable class=org.apache.tools.ant.Main/gt;
  -lt;/assertionsgt;
  +lt;java fork=true failonerror=true
  +  classname=${classname}
  +  classpathref=assert.classpathgt;
  +  lt;assertions enableSystemAssertions=true gt;
  +lt;enable package=org.apache /gt;
  +lt;disable package=org.apache.ant /gt;
  +lt;enable class=org.apache.tools.ant.Main/gt;
  +  lt;/assertionsgt;
  +lt;/javagt;
   /pre
   
   h5Example: disabled and anonymous package assertions/h5
  @@ -173,7 +177,11 @@
 lt;enable package=org.apache.test /gt;
   lt;/assertionsgt;
   
  -lt;assertions refid=project.assertions /gt;
  +lt;java fork=true failonerror=true
  +  classname=${classname}
  +  classpathref=assert.classpathgt;
  +  lt;assertions refid=project.assertions/gt;
  +lt;/javagt;
   /pre
   
   hr
  
  
  
  No   revision
  No   revision
  1.13.2.1  +1 -0  ant/docs/manual/conceptstypeslist.html
  
  Index: conceptstypeslist.html
  ===
  RCS file: /home/cvs/ant/docs/manual/conceptstypeslist.html,v
  retrieving revision 1.13
  retrieving revision 1.13.2.1
  diff -u -r1.13 -r1.13.2.1
  --- conceptstypeslist.html1 Sep 2003 14:22:04 -   1.13
  +++ conceptstypeslist.html30 Sep 2003 00:10:12 -  1.13.2.1
  @@ -15,6 +15,7 @@
   a href=CoreTasks/common.htmlCommon Attributes/abr
   
   h3Core Types/h3
  +a href=CoreTypes/assertions.htmlAssertions Type/abr
   a href=CoreTypes/description.htmlDescription Type/abr
   a href=dirtasks.htmlDirectory-based Tasks/abr
   a href=CoreTypes/dirset.htmlDirSet/abr
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant welcome.html

[stevel]

stevel  2003/09/29 17:10:57

  Modified:.Tag: ANT_16_BRANCH welcome.html
  Log:
  quote fixup, and some frivolousness at the end.
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.2.2.5   +83 -30ant/welcome.html
  
  Index: welcome.html
  ===
  RCS file: /home/cvs/ant/welcome.html,v
  retrieving revision 1.2.2.4
  retrieving revision 1.2.2.5
  diff -u -r1.2.2.4 -r1.2.2.5
  --- welcome.html  29 Sep 2003 09:02:56 -  1.2.2.4
  +++ welcome.html  30 Sep 2003 00:10:56 -  1.2.2.5
  @@ -2,10 +2,10 @@
   HTML
   HEAD
META HTTP-EQUIV=CONTENT-TYPE CONTENT=text/html; 
charset=windows-1252
  - TITLEWelcome to Ant1.6/TITLE
  + TITLEWelcome to Apache Ant 1.6/TITLE
   /HEAD
   BODY LANG=en-US BGCOLOR=#ff DIR=LTR
  -H1Welcome to Ant1.6/H1
  +H1Welcome to Apache Ant 1.6/H1
   PBRBR
   /P
   H2Your life just got better. 
  @@ -19,18 +19,18 @@
   subdued technology and software industries. 
   /P
   PNo, Ant1.6 will not fundamentally change your life. But if you do
  -have to get software out on time -quot;roughly what you asked for,
  -roughly when you askedquot;, then Ant1.6 provides lots of little
  +have to get software out on time -roughly what you asked for,
  +roughly when you asked, then Ant1.6 provides lots of little
   improvements over the existing version. 
   /P
   PBefore we look at those details, lets look at the world of The
   Automated Build./P
   PFirstly, we'd like to thank everyone for all those awards that
  -have been flowing in. The JavaWorld Editors' Choice Award for quot;Most
  -Useful Java Community-Developed Technologyquot;, The Java
  -Developer's Journal quot;Editors Choice Awardquot;, and Java Pro
  -Reader's Choice award for quot;Most Valuable Java Deployment
  -Technology.quot; Wow. That's a lot of awards. Aardman Animations
  +have been flowing in. The JavaWorld Editors' Choice Award for Most
  +Useful Java Community-Developed Technology, The Java
  +Developer's Journal Editors Choice Award, and Java Pro
  +Reader's Choice award for Most Valuable Java Deployment
  +Technology. Wow. That's a lot of awards. Aardman Animations
   keep all their Wallace and Gromit -related oscars in a cabinet in
   their tea room. If the Apache organization had a tea room, those Ant
   awards would be forcing all the other (excellent) Apache products to
  @@ -42,8 +42,8 @@
   over the past four years, it has moved from a tool used simply to
   build Tomcat cross-platform, to a tool used across many open source
   projects, and now to a tool used by almost all Java projects. Indeed,
  -pretty much the only competitor in the Java space is a sibling project under
  -the Apache banner, A HREF=http://maven.apache.org/; 
TARGET=otherMaven/A.
  +pretty much the only competitor in the Java space is a sibling
  +project under the Apache banner, A HREF=http://maven.apache.org/; 
TARGET=otherMaven/A.
   One of the obvious signs of Ant's success is that all the popular
   IDEs, from the Open Source -Emacs JDE, Eclipse, NetBeans and jEdit -
   to the commercial: IntelliJ IDEA, Borland JBuilder- all ship with
  @@ -62,8 +62,8 @@
   /P
   PThe other metric of success is the pre-announcement hints from our
   distant software colleagues in Redmond, Microsoft, of a new build
  -tool, quot;MSBuildquot;, which quot;might be the single most
  -important feature innovation in our pipelinequot;, according to one
  +tool, MSBuild, which might be the single most
  +important feature innovation in our pipeline, according to one
   MS developer. That is surely the greatest metric of success: XML
   based build tools are now viewed as so essential to the modern build
   process, that Microsoft has to come up with a competitor to Ant to
  @@ -78,7 +78,7 @@
   builds. Its sad, but there are lots of little minor faults with Ant
   that we don't dare fix because, well, things might break. For
   example, why don't if= and unless= clauses also support
  -if=quot;${property}quot; clauses? Alternatively, why isn't it an
  +if=${property} clauses? Alternatively, why isn't it an
   error to use a property that isn't defined. Everyone that has ever
   seen directories called ${build.dir} popping up the source tree will
   understand why that behaviour is not always what you want. Well, we
  @@ -124,7 +124,8 @@
   development. 
   /P
   PWhether we call the next version of Ant 1.7 or 2.0 is something we
  -have yet to decide. Maybe we should call it 3.0 just to surprise people./P
  +have yet to decide. Maybe we should call it 3.0 just to surprise
  +people./P
   H2What has changed/H2
   PLook at the A HREF=WHATSNEW TARGET=otherWHATSNEW/A
   document to get a full list of changes. Here are some of the core
  @@ -169,15 +170,14 @@
something we will fix in Ant1.7/P
   /OL
   H3Adapters/H3
  -P These are Java classes that
  -Iadapt/Igt;nbsp;arbitrary Java classes into ant 

Re: tests of ant.1.6beta

[Steve Loughran]

Antoine Lévy-Lambert wrote:
I have made a build on my PC with jdk 1.4.
The following tests are failing for me :
org.apache.tools.ant.taskdefs.optional.XalanLiaisonTest
org.apache.tools.ant.taskdefs.optional.XslpLiaisonTest
because they cannot find org/apache/xerces/framework/XMLParser
Are you running build/test or ant/test?
org.apache.tools.ant.types.AssertionsTest
[junit] Testcase:
testReferences(org.apache.tools.ant.types.AssertionsTest):
[junit] Testcase:
testReferenceAbuse(org.apache.tools.ant.types.AssertionsTest):
these 2 tests seem to fail because the corresponding build file should put
in the classpath of the forked java task the ant run time, and does not do
it.
will look at these. if it was the problem you emailed me earlier about, 
that is now fixed (no registry of assertions in types/defaults.properties)

I have also seen that there is no html documentation for assertions.
that is fixed.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: touch should allow nested filelist elements

[Conor MacNeill]

On Tue, 30 Sep 2003 05:27 am, Matt Benson wrote:
 ... any reason why not?


It does and has for a while according to CVS. Is there a problem?

Conor


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 23496] - Not picking up environment variables?

[bugzilla]

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=23496.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23496

Not picking up environment variables?





--- Additional Comments From [EMAIL PROTECTED]  2003-09-30 06:15 ---
And MacOS X is a Unix and therefore casesensitive ...

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: cvs commit: ant welcome.html

[Stefan Bodewig]

On 30 Sep 2003, [EMAIL PROTECTED] wrote:

   and some frivolousness at the end.

I'm not too happy with the call to action part, I agree with the call
to inaction, though.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: still one test failing in ant 1.6 : ModifiedSelectorTest

[Jan . Materne]

Sorry, I can´t - because I don´t get this error.
All tests pass on my machine. On JDK 1.2 and 1.4 (Win2000)

And I can only (try to) fix errors which occur ...



Jan



Classic VM (build JDK-1.2.1_004, native threads)

antbuild
  ... Bootstrapping Ant Distribution
  JAVA_HOME=c:\seu\jdk121_04
  JAVA=c:\seu\jdk121_04\bin\java
  JAVAC=c:\seu\jdk121_04\bin\javac
  ...
antant test -Dtest.haltonfailure=false
  ...
  run-which:
[which] java.version=1.2.1
  run-tests:
...
Testcase:
testVector(org.apache.tools.ant.taskdefs.optional.sitraka.ClassFileTest):
FAILED
void init()
junit.framework.AssertionFailedError: void init()
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Compiled Code)
at
org.apache.tools.ant.taskdefs.optional.sitraka.ClassFileTest.assertHasMethod
(Compiled Code)
at
org.apache.tools.ant.taskdefs.optional.sitraka.ClassFileTest.testVector(Clas
sFileTest.java:83)
...
Testsuite: org.apache.tools.ant.types.selectors.ModifiedSelectorTest
Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 10,075 sec



Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)

antbuild.bat
  ... Bootstrapping Ant Distribution
  JAVA_HOME=c:\seu\jdk142
  JAVA=c:\seu\jdk142\bin\java
  JAVAC=c:\seu\jdk142\bin\javac
  ...
antant test -Dtest.haltonfailure=false
  ...
  [which] java.version=1.4.2
  ...
  Testcase:
testRecreateWithUpdateNewerFile(org.apache.tools.ant.taskdefs.JarTest):
FAILED
  jar has been recreated in testRecreateWithUpdateNewerFile
  junit.framework.AssertionFailedError: jar has been recreated in
testRecreateWithUpdateNewerFile
  at junit.framework.Assert.fail(Assert.java:47)
  at junit.framework.Assert.assertTrue(Assert.java:20)
  at
org.apache.tools.ant.taskdefs.JarTest.testRecreate(JarTest.java:171)
  at
org.apache.tools.ant.taskdefs.JarTest.testRecreateWithUpdateNewerFile(JarTes
t.java:157)
  ...
  Testsuite: org.apache.tools.ant.types.selectors.ModifiedSelectorTest
  Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 8,472 sec
  ...


 -Original Message-
 From: Antoine Lévy-Lambert [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, September 30, 2003 10:18 AM
 To: Ant Developers List
 Subject: still one test failing in ant 1.6 : ModifiedSelectorTest
 
 
 Jan, could you try to fix this ?
 Maybe there is a timing issue there.
 I am running the test on Windows2000.
 I get the same failure within cygwin and running the test in 
 the JunitTest
 runner of IDEA.
 Cheers,
 Antoine
 
 [junit] Testsuite:
 org.apache.tools.ant.types.selectors.ModifiedSelectorTest
 [junit] Tests run: 22, Failures: 3, Errors: 0, Time 
 elapsed: 7,171 sec
 
 [junit] Testcase:
 testScenarioCoreSelectorDefaults(org.apache.tools.ant.types.se
 lectors.Modifi
 edSelectorTest):  FAILED
 [junit] Too much files copied on second time.
 [junit] junit.framework.AssertionFailedError: Too much 
 files copied on
 second time.
 [junit]   at junit.framework.Assert.fail(Assert.java:47)
 [junit]   at junit.framework.Assert.assertTrue(Assert.java:20)
 [junit]   at
 org.apache.tools.ant.types.selectors.ModifiedSelectorTest.doSc
 enarioTest(Mod
 ifiedSelectorTest.java:536)
 [junit]   at
 org.apache.tools.ant.types.selectors.ModifiedSelectorTest.test
 ScenarioCoreSe
 lectorDefaults(ModifiedSelectorTest.java:503)
 ...
 
 
 [junit] Testcase:
 testSceanrioCoreSelectorSettings(org.apache.tools.ant.types.se
 lectors.Modifi
 edSelectorTest):  FAILED
 [junit] Too much files copied on second time.
 [junit] junit.framework.AssertionFailedError: Too much 
 files copied on
 second time.
 
 [junit] Testcase:
 testScenarioCustomSelectorSettings(org.apache.tools.ant.types.
 selectors.Modi
 fiedSelectorTest):FAILED
 [junit] Too much files copied on second time.
 [junit] junit.framework.AssertionFailedError: Too much 
 files copied on
 second time.
 
 
 [junit] TEST 
 org.apache.tools.ant.types.selectors.ModifiedSelectorTest
 FAILED
 [junit] Testsuite:
 org.apache.tools.ant.types.selectors.PresentSelectorTest
 [junit] Tests run: 3, Failures: 0, Errors: 0, Time 
 elapsed: 7,371 sec
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

AW: still one test failing in ant 1.6 : ModifiedSelectorTest

[Antoine Lévy-Lambert]

Hi Jan,

there is a subdirectory called old on in my test environment :

src\etc\testcases\types\selectortest\src

this one gets copied to to-2, generating the error.
I do not know whether this is something dirty in my environment or an error
in the testcase.

Cheers,
Antoine
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 30. September 2003 11:10
An: [EMAIL PROTECTED]
Betreff: RE: still one test failing in ant 1.6 : ModifiedSelectorTest


Sorry, I can´t - because I don´t get this error.
All tests pass on my machine. On JDK 1.2 and 1.4 (Win2000)

And I can only (try to) fix errors which occur ...



Jan



Classic VM (build JDK-1.2.1_004, native threads)

antbuild
  ... Bootstrapping Ant Distribution
  JAVA_HOME=c:\seu\jdk121_04
  JAVA=c:\seu\jdk121_04\bin\java
  JAVAC=c:\seu\jdk121_04\bin\javac
  ...
antant test -Dtest.haltonfailure=false
  ...
  run-which:
[which] java.version=1.2.1
  run-tests:
...
Testcase:
testVector(org.apache.tools.ant.taskdefs.optional.sitraka.ClassFileTest):
FAILED
void init()
junit.framework.AssertionFailedError: void init()
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Compiled Code)
at
org.apache.tools.ant.taskdefs.optional.sitraka.ClassFileTest.assertHasMethod
(Compiled Code)
at
org.apache.tools.ant.taskdefs.optional.sitraka.ClassFileTest.testVector(Clas
sFileTest.java:83)
...
Testsuite: org.apache.tools.ant.types.selectors.ModifiedSelectorTest
Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 10,075 sec



Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)

antbuild.bat
  ... Bootstrapping Ant Distribution
  JAVA_HOME=c:\seu\jdk142
  JAVA=c:\seu\jdk142\bin\java
  JAVAC=c:\seu\jdk142\bin\javac
  ...
antant test -Dtest.haltonfailure=false
  ...
  [which] java.version=1.4.2
  ...
  Testcase:
testRecreateWithUpdateNewerFile(org.apache.tools.ant.taskdefs.JarTest):
FAILED
  jar has been recreated in testRecreateWithUpdateNewerFile
  junit.framework.AssertionFailedError: jar has been recreated in
testRecreateWithUpdateNewerFile
  at junit.framework.Assert.fail(Assert.java:47)
  at junit.framework.Assert.assertTrue(Assert.java:20)
  at
org.apache.tools.ant.taskdefs.JarTest.testRecreate(JarTest.java:171)
  at
org.apache.tools.ant.taskdefs.JarTest.testRecreateWithUpdateNewerFile(JarTes
t.java:157)
  ...
  Testsuite: org.apache.tools.ant.types.selectors.ModifiedSelectorTest
  Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 8,472 sec
  ...


 -Original Message-
 From: Antoine Lévy-Lambert [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, September 30, 2003 10:18 AM
 To: Ant Developers List
 Subject: still one test failing in ant 1.6 : ModifiedSelectorTest


 Jan, could you try to fix this ?
 Maybe there is a timing issue there.
 I am running the test on Windows2000.
 I get the same failure within cygwin and running the test in
 the JunitTest
 runner of IDEA.
 Cheers,
 Antoine

 [junit] Testsuite:
 org.apache.tools.ant.types.selectors.ModifiedSelectorTest
 [junit] Tests run: 22, Failures: 3, Errors: 0, Time
 elapsed: 7,171 sec

 [junit] Testcase:
 testScenarioCoreSelectorDefaults(org.apache.tools.ant.types.se
 lectors.Modifi
 edSelectorTest):  FAILED
 [junit] Too much files copied on second time.
 [junit] junit.framework.AssertionFailedError: Too much
 files copied on
 second time.
 [junit]   at junit.framework.Assert.fail(Assert.java:47)
 [junit]   at junit.framework.Assert.assertTrue(Assert.java:20)
 [junit]   at
 org.apache.tools.ant.types.selectors.ModifiedSelectorTest.doSc
 enarioTest(Mod
 ifiedSelectorTest.java:536)
 [junit]   at
 org.apache.tools.ant.types.selectors.ModifiedSelectorTest.test
 ScenarioCoreSe
 lectorDefaults(ModifiedSelectorTest.java:503)
 ...


 [junit] Testcase:
 testSceanrioCoreSelectorSettings(org.apache.tools.ant.types.se
 lectors.Modifi
 edSelectorTest):  FAILED
 [junit] Too much files copied on second time.
 [junit] junit.framework.AssertionFailedError: Too much
 files copied on
 second time.

 [junit] Testcase:
 testScenarioCustomSelectorSettings(org.apache.tools.ant.types.
 selectors.Modi
 fiedSelectorTest):FAILED
 [junit] Too much files copied on second time.
 [junit] junit.framework.AssertionFailedError: Too much
 files copied on
 second time.


 [junit] TEST
 org.apache.tools.ant.types.selectors.ModifiedSelectorTest
 FAILED
 [junit] Testsuite:
 org.apache.tools.ant.types.selectors.PresentSelectorTest
 [junit] Tests run: 3, Failures: 0, Errors: 0, Time
 elapsed: 7,371 sec


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

Re: [PROPOSAL] javadoc refactoring and supporting gjdoc

[Stefan Bodewig]

On Sat, 27 Sep 2003, Takashi Okamoto [EMAIL PROTECTED] wrote:

 Debian have 'main' and 'contrib' section. 'main' group is official
 debian package which mean it's compiled and run opensource
 platform(e.g. kaffe/gcj) 'contrib' group is non-official which mean
 it's opensource but can't be built nor run with opensource platform.

I'll refrain from commenting on this policy.

 So, most of opensource java software create javadoc document with
 javadoc task. This means I can't put such a package into main
 section beacuse javadoc depend on SUN's implentation which is not
 oss.

Strictly speaking, you can build the package but you can't build the
docs.

 Then ,if gjdoc task is separated, I must modify build.xml file for
 all javadoc generation to create Debian package.

The alternative - coming in an Ant 1.6 release close to you soon - is
to provide a different build file for your Debian build.  In that
build file import the original build file and override the target[1]
that creates the javadocs with one that uses gjdoc.

 BTW, I already send the patch in bugzilla. Please close it.

will do.

Stefan

Footnotes: 

[1] I've never thought I'd recommend to override targets - and
certainly not that soon.  Let's say I haven't been in control of
myself while I've written the paragraph above.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: cvs over SSH

[Stefan Bodewig]

On Mon, 29 Sep 2003, [EMAIL PROTECTED] wrote:

 Any thaughts?

Other than the usual works on Linux/MacOS X with OpenSSH using ssh-agent?

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [PROPOSAL] javadoc refactoring and supporting gjdoc

[Jan . Materne]

  So, most of opensource java software create javadoc document with
  javadoc task. This means I can't put such a package into main
  section beacuse javadoc depend on SUN's implentation which is not
  oss.
 
 Strictly speaking, you can build the package but you can't build the
 docs.

If I remember right javadoc can be generated with XDoclet ...


Jan

RE: cvs over SSH

[Jan . Materne]

aha, with ssh-agent. That is the deamon which serves the right 
passphrase/password for a server, right?

Exactly there is the problem (I think) - cvs opens a ssh (but not with
a command line interface) and I can´t type my passphrase in it.

It seems that ssh on your machine asks the deamon and all works ...

Does the deamon work on win? ...


 -Original Message-
 From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, September 30, 2003 11:25 AM
 To: [EMAIL PROTECTED]
 Subject: Re: cvs over SSH
 
 
 On Mon, 29 Sep 2003, [EMAIL PROTECTED] wrote:
 
  Any thaughts?
 
 Other than the usual works on Linux/MacOS X with OpenSSH 
 using ssh-agent?
 
 Stefan
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

DO NOT REPLY [Bug 23510] New: - provide a append_unique attribute for echo task

[bugzilla]

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=23510.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23510

provide a append_unique attribute for echo task

   Summary: provide a append_unique attribute for echo task
   Product: Ant
   Version: 1.5.3
  Platform: Other
   URL: http://ant.apache.org/manual/CoreTasks/echo.html
OS/Version: Other
Status: NEW
  Severity: Enhancement
  Priority: Other
 Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


My build.xml creates a (txt or ftl) file containing a record per line.

Now, each ant run re-creates a possibly slightly changed set of records.

When using shell scripts, I can use uniq to solve the problem of getting rid
of duplicate lines (although I first have to sort which I rather would not).

== it would be great if the echo task could do that too!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 23441] - support gjdoc with javadoc task

[bugzilla]

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=23441.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23441

support gjdoc with javadoc task

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|Normal  |Enhancement
 Status|NEW |RESOLVED
 Resolution||INVALID



--- Additional Comments From [EMAIL PROTECTED]  2003-09-30 09:35 ---
closing on user's request.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant/src/etc/testcases/types selectors.xml

[antoine]

antoine 2003/09/30 02:38:53

  Modified:src/etc/testcases/types Tag: ANT_16_BRANCH selectors.xml
  Log:
  Make ModifiedSelectorTest pass.
  I had been hassled by a subdir $ANT_HOME/bin/old which I had created to keep
  the old version of the ant scripts.
  It seems that an empty directory is always out of date for ModifiedSelector ?
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.6.2.1   +6 -2  ant/src/etc/testcases/types/selectors.xml
  
  Index: selectors.xml
  ===
  RCS file: /home/cvs/ant/src/etc/testcases/types/selectors.xml,v
  retrieving revision 1.6
  retrieving revision 1.6.2.1
  diff -u -r1.6 -r1.6.2.1
  --- selectors.xml 13 Sep 2003 16:35:52 -  1.6
  +++ selectors.xml 30 Sep 2003 09:38:53 -  1.6.2.1
  @@ -130,8 +130,12 @@
 target name=modifiedselectortest-scenario-prepare
 mkdir dir=${test.dir}/src/
 copy todir=${test.dir}/src
  -  fileset dir=${ant.home}/lib includes=ant.jar/
  -  fileset dir=${ant.home}/bin/
  +  fileset dir=${ant.home}/lib includes=ant.jar
  +  type type=file/
  +  /fileset
  +  fileset dir=${ant.home}/bin
  +type type=file/
  +  /fileset
 /copy
 touch datetime=12/24/2002 4:00 pm
 fileset dir=${test.dir}/
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: still one test failing in ant 1.6 : ModifiedSelectorTest

[Jan . Materne]

That directory is created in selector.xml target
modifiedselectortest-scenario-prepare
src\etc\testcases\types\selectortest\src is the value of ${test.dir}/src.
And
${test.dir} is deleted in target cleanup which is called from 
ModifiedSelectorTest.doScenarioTest():542:bft.tearDown();

All three scenario-tests use that common method. ... ops, spell check of
line 508:
  testSceanrioCoreSelectorSettings()
should be
  testScenarioCoreSelectorSettings()
 ^^
 

The bft.tearDown() is done in a finally block so it should be executed.
What do you think?



Jan




 -Original Message-
 From: Antoine Lévy-Lambert [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, September 30, 2003 11:16 AM
 To: Ant Developers List
 Subject: AW: still one test failing in ant 1.6 : ModifiedSelectorTest
 
 
 
 Hi Jan,
 
 there is a subdirectory called old on in my test environment :
 
 src\etc\testcases\types\selectortest\src
 
 this one gets copied to to-2, generating the error.
 I do not know whether this is something dirty in my 
 environment or an error
 in the testcase.
 
 Cheers,
 Antoine
 -Ursprüngliche Nachricht-
 Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Gesendet: Dienstag, 30. September 2003 11:10
 An: [EMAIL PROTECTED]
 Betreff: RE: still one test failing in ant 1.6 : ModifiedSelectorTest
 
 
 Sorry, I can´t - because I don´t get this error.
 All tests pass on my machine. On JDK 1.2 and 1.4 (Win2000)
 
 And I can only (try to) fix errors which occur ...
 
 
 
 Jan
 
 
 
 Classic VM (build JDK-1.2.1_004, native threads)
 
 antbuild
   ... Bootstrapping Ant Distribution
   JAVA_HOME=c:\seu\jdk121_04
   JAVA=c:\seu\jdk121_04\bin\java
   JAVAC=c:\seu\jdk121_04\bin\javac
   ...
 antant test -Dtest.haltonfailure=false
   ...
   run-which:
 [which] java.version=1.2.1
   run-tests:
 ...
 Testcase:
 testVector(org.apache.tools.ant.taskdefs.optional.sitraka.Clas
 sFileTest):
 FAILED
 void init()
 junit.framework.AssertionFailedError: void init()
 at junit.framework.Assert.fail(Assert.java:47)
 at junit.framework.Assert.assertTrue(Compiled Code)
 at
 org.apache.tools.ant.taskdefs.optional.sitraka.ClassFileTest.a
 ssertHasMethod
 (Compiled Code)
 at
 org.apache.tools.ant.taskdefs.optional.sitraka.ClassFileTest.t
 estVector(Clas
 sFileTest.java:83)
 ...
 Testsuite: 
 org.apache.tools.ant.types.selectors.ModifiedSelectorTest
 Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 10,075 sec
 
 
 
 Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
 
 antbuild.bat
   ... Bootstrapping Ant Distribution
   JAVA_HOME=c:\seu\jdk142
   JAVA=c:\seu\jdk142\bin\java
   JAVAC=c:\seu\jdk142\bin\javac
   ...
 antant test -Dtest.haltonfailure=false
   ...
   [which] java.version=1.4.2
   ...
   Testcase:
 testRecreateWithUpdateNewerFile(org.apache.tools.ant.taskdefs.
 JarTest):
 FAILED
   jar has been recreated in testRecreateWithUpdateNewerFile
   junit.framework.AssertionFailedError: jar has been recreated in
 testRecreateWithUpdateNewerFile
   at junit.framework.Assert.fail(Assert.java:47)
   at junit.framework.Assert.assertTrue(Assert.java:20)
   at
 org.apache.tools.ant.taskdefs.JarTest.testRecreate(JarTest.java:171)
   at
 org.apache.tools.ant.taskdefs.JarTest.testRecreateWithUpdateNe
 werFile(JarTes
 t.java:157)
   ...
   Testsuite: org.apache.tools.ant.types.selectors.ModifiedSelectorTest
   Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 8,472 sec
   ...
 
 
  -Original Message-
  From: Antoine Lévy-Lambert [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, September 30, 2003 10:18 AM
  To: Ant Developers List
  Subject: still one test failing in ant 1.6 : ModifiedSelectorTest
 
 
  Jan, could you try to fix this ?
  Maybe there is a timing issue there.
  I am running the test on Windows2000.
  I get the same failure within cygwin and running the test in
  the JunitTest
  runner of IDEA.
  Cheers,
  Antoine
 
  [junit] Testsuite:
  org.apache.tools.ant.types.selectors.ModifiedSelectorTest
  [junit] Tests run: 22, Failures: 3, Errors: 0, Time
  elapsed: 7,171 sec
 
  [junit] Testcase:
  testScenarioCoreSelectorDefaults(org.apache.tools.ant.types.se
  lectors.Modifi
  edSelectorTest):FAILED
  [junit] Too much files copied on second time.
  [junit] junit.framework.AssertionFailedError: Too much
  files copied on
  second time.
  [junit] at junit.framework.Assert.fail(Assert.java:47)
  [junit] at 
 junit.framework.Assert.assertTrue(Assert.java:20)
  [junit] at
  org.apache.tools.ant.types.selectors.ModifiedSelectorTest.doSc
  enarioTest(Mod
  ifiedSelectorTest.java:536)
  [junit] at
  org.apache.tools.ant.types.selectors.ModifiedSelectorTest.test
  ScenarioCoreSe
  lectorDefaults(ModifiedSelectorTest.java:503)
  ...
 
 
  [junit] Testcase:
  

DO NOT REPLY [Bug 23440] - imporove native2ascii task for opensource JVM

[bugzilla]

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=23440.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23440

imporove native2ascii task for opensource JVM

[EMAIL PROTECTED] changed:

   What|Removed |Added

   Severity|Normal  |Enhancement

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: cvs commit: ant/src/etc/testcases/types selectors.xml

[Antoine Lévy-Lambert]

Hi Jan,

good, this has been the opportunity for me to learn something about
modified/

Cheers,

Antoine

-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 30. September 2003 11:42
An: [EMAIL PROTECTED]
Betreff: RE: cvs commit: ant/src/etc/testcases/types selectors.xml


   It seems that an empty directory is always out of date for
 ModifiedSelector ?


The selector computes a hashvalue for files. For directories it can´t.
Therefore you can specify whether it should select directories or not.
Default is true.


Jan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 23508] - JAVAC ignores excludes

[bugzilla]

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=23508.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23508

JAVAC ignores excludes

[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||INVALID

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: cvs over SSH

[Christopher Lenz]

[EMAIL PROTECTED] wrote:
aha, with ssh-agent. That is the deamon which serves the right 
passphrase/password for a server, right?

Exactly there is the problem (I think) - cvs opens a ssh (but not with
a command line interface) and I can´t type my passphrase in it.
It seems that ssh on your machine asks the deamon and all works ...
Does the deamon work on win? ...
I'm using ssh-agent with Cygwin without any problems so far.
  $ eval `ssh-agent`
  $ ssh-add
  [enter passphrase]
  [ready to go]
-chris
-Original Message-
From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 11:25 AM
To: [EMAIL PROTECTED]
Subject: Re: cvs over SSH
On Mon, 29 Sep 2003, [EMAIL PROTECTED] wrote:

Any thaughts?
Other than the usual works on Linux/MacOS X with OpenSSH 
using ssh-agent?

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Ant 1.6 beta

[Antoine Lévy-Lambert]

I have created the label ANT_16_B1 and I am uploading the beta to my account
on cvs.apache.org

Cheers,

Antoine



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: cvs over SSH

[Jan . Materne]

I will look and try, thanks so far.

Jan

 -Original Message-
 From: Christopher Lenz [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, September 30, 2003 12:33 PM
 To: Ant Developers List
 Subject: Re: cvs over SSH
 
 
 [EMAIL PROTECTED] wrote:
  aha, with ssh-agent. That is the deamon which serves the right 
  passphrase/password for a server, right?
  
  Exactly there is the problem (I think) - cvs opens a ssh 
 (but not with
  a command line interface) and I can´t type my passphrase in it.
  
  It seems that ssh on your machine asks the deamon and all works ...
  
  Does the deamon work on win? ...
 
 I'm using ssh-agent with Cygwin without any problems so far.
 
$ eval `ssh-agent`
$ ssh-add
[enter passphrase]
[ready to go]
 
 -chris
 
 -Original Message-
 From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, September 30, 2003 11:25 AM
 To: [EMAIL PROTECTED]
 Subject: Re: cvs over SSH
 
 
 On Mon, 29 Sep 2003, [EMAIL PROTECTED] wrote:
 
 
 Any thaughts?
 
 Other than the usual works on Linux/MacOS X with OpenSSH 
 using ssh-agent?
 
 Stefan
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

cvs commit: ant/docs/manual/OptionalTasks scriptdef.html

[conor]

conor   2003/09/30 04:42:06

  Modified:docs/manual Tag: ANT_16_BRANCH optionaltasklist.html
  Added:   docs/manual/OptionalTasks Tag: ANT_16_BRANCH scriptdef.html
  Log:
  scriptdef documentation
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.39.2.1  +1 -0  ant/docs/manual/optionaltasklist.html
  
  Index: optionaltasklist.html
  ===
  RCS file: /home/cvs/ant/docs/manual/optionaltasklist.html,v
  retrieving revision 1.39
  retrieving revision 1.39.2.1
  diff -u -w -u -r1.39 -r1.39.2.1
  --- optionaltasklist.html 23 Jul 2003 14:12:11 -  1.39
  +++ optionaltasklist.html 30 Sep 2003 11:42:05 -  1.39.2.1
  @@ -60,6 +60,7 @@
   a href=OptionalTasks/setproxy.htmlSetproxy/abr
   a href=OptionalTasks/scp.htmlScp/abr
   a href=OptionalTasks/script.htmlScript/abr
  +a href=OptionalTasks/scriptdef.htmlScriptdef/abr
   a href=OptionalTasks/sound.htmlSound/abr
   a href=OptionalTasks/sos.htmlSourceOffSite/abr
   a href=OptionalTasks/splash.htmlSplash/abr
  
  
  
  No   revision
  No   revision
  1.1.2.1   +190 -0ant/docs/manual/OptionalTasks/Attic/scriptdef.html
  
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant ReleaseInstructions

[antoine]

antoine 2003/09/30 05:59:13

  Modified:.Tag: ANT_16_BRANCH ReleaseInstructions
  Log:
  Roll over version numbers from 1.5 to 1.6
  Emphasize version property in build.xml
  Move ahead updating of credits.html and cover.html
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.17.2.2  +40 -29ant/ReleaseInstructions
  
  Index: ReleaseInstructions
  ===
  RCS file: /home/cvs/ant/ReleaseInstructions,v
  retrieving revision 1.17.2.1
  retrieving revision 1.17.2.2
  diff -u -r1.17.2.1 -r1.17.2.2
  --- ReleaseInstructions   29 Sep 2003 08:40:57 -  1.17.2.1
  +++ ReleaseInstructions   30 Sep 2003 12:59:13 -  1.17.2.2
  @@ -4,7 +4,7 @@
Stefan Bodewig
Magesh Umasankar
   
  -Note: This document was created in the context of releasing Ant 1.5.
  +Note: This document was updated in the context of releasing Ant 1.6.
 Please interpret the branch names, tags, etc. according to
 your context.
   
  @@ -29,25 +29,37 @@
   For more information on performing branching and merging, please visit
   http://www.durak.org/cvswebsites/doc/cvs_54.php#SEC54
   
  -Label such branches ANT_15_BRANCH.
  +Label such branches ANT_16_BRANCH.
   
   4.  Once the branch is setup, the version numbers in CVS are changed. On the 
  -branch, the build.xml version becomes 1.5Beta1 while the main branch is 
  -updated to 1.6alpha. 
  +branch, the version property in build.xml becomes 1.6Beta,
  +while the main branch is updated to 1.7alpha.
   
   [[ TODO: Check if the documentation files also need to be updated to 
point 
   to the right areas of Ant's website. ]]
   
  -5.  Ensure you have all the external libraries that Ant uses in your
  +5.  Before a build :
  +Update the following files for version number, and commit your changes.
  +
  +* docs/manual/cover.html
  +* docs/manual/credits.html
  +* build.xml (version property)
  +
  +the first beta on the 1.6 branch should be calle 1.6Beta1, ...
  +
  +the version property in build.xml governs the output of ant -version and
  +the naming of the distribution files.
  +
  +6.  Ensure you have all the external libraries that Ant uses in your
   lib/optional directory.  To find out what libraries you need, execute
   the build with -verbose option and scan for lines beginning with 
   Unable to load
   
  -6.  Next bootstrap, build and run the tests.  Then build the distribution 
  +7.  Next bootstrap, build and run the tests.  Then build the distribution
   on the branch. It is important that this be a clean build. Label this 
with 
  -a tag ANT_15_B1.
  +a tag ANT_16_B1.
   
  -7.  Sign the distribution files using the following simple script
  +8.  Sign the distribution files using the following simple script
   #!/bin/sh
   for i in distribution/*
   do
  @@ -65,11 +77,12 @@
   Also make sure you have sent the key that you use to a public 
   keyserver.
   
  -8.  The beta distribution is now ready to go. Bundle it up into a tar.gz 
file 
  +9.  The beta distribution is now ready to go. Bundle it up into a tar.gz file
   and scp to your apache account.
   
  -9.  Meanwhile, convert the WHATSNEW file into HTML for the README file on 
the 
  -website. See the previous release directories for examples of these 
files. 
  +10. Meanwhile, convert the part of the WHATSNEW file covering the changes
  +since the last release into HTML for the README file on the
  +website. See the previous release directories for examples of these 
files.
   Add instructions and warnings (GNU tar format issues, etc).
   
   You may choose to use the text2html convertor present at
  @@ -79,18 +92,18 @@
   
   [[ TODO: This must perhaps be an Ant task. ]]
   
  -10. Once this is uploaded, unpack things, create the release directory, 
  -something like v1.5Beta1, push the release and RELEASE-NOTES files
  +11. Once this is uploaded, unpack things, create the release directory,
  +something like v1.6Beta1, push the release and RELEASE-NOTES files
   into this directory.  Create a symbolic link named README.html
   that points to the RELEASE-NOTES.
   
   The files should go to /www/cvs.apache.org/dist/ant/ on minotaur.
   
  -11. Address the available release tags in BugZilla. Create a new tag 
1.5Beta1 
  -and a 1.6alpha. Assign all existing 1.5 alpha bugs to one of these 
release 
  +12. Address the available release tags in BugZilla. Create a new tag 1.6Beta1
  +and a 1.7Alpha. Assign all existing 1.6 alpha bugs to one of these 
release
   labels.
   
  -12. Once that is done, do a test download to make sure everything is OK. A 
  +13. Once that is done, do a test download to make sure everything is OK. A
   common problem may 

cvs commit: ant ReleaseInstructions

[antoine]

antoine 2003/09/30 06:01:32

  Modified:.ReleaseInstructions
  Log:
  Merge from ANT_16_BRANCH
  
  Revision  ChangesPath
  1.19  +40 -29ant/ReleaseInstructions
  
  Index: ReleaseInstructions
  ===
  RCS file: /home/cvs/ant/ReleaseInstructions,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- ReleaseInstructions   29 Sep 2003 08:37:32 -  1.18
  +++ ReleaseInstructions   30 Sep 2003 13:01:32 -  1.19
  @@ -4,7 +4,7 @@
Stefan Bodewig
Magesh Umasankar
   
  -Note: This document was created in the context of releasing Ant 1.5.
  +Note: This document was updated in the context of releasing Ant 1.6.
 Please interpret the branch names, tags, etc. according to
 your context.
   
  @@ -29,25 +29,37 @@
   For more information on performing branching and merging, please visit
   http://www.durak.org/cvswebsites/doc/cvs_54.php#SEC54
   
  -Label such branches ANT_15_BRANCH.
  +Label such branches ANT_16_BRANCH.
   
   4.  Once the branch is setup, the version numbers in CVS are changed. On the 
  -branch, the build.xml version becomes 1.5Beta1 while the main branch is 
  -updated to 1.6alpha. 
  +branch, the version property in build.xml becomes 1.6Beta,
  +while the main branch is updated to 1.7alpha.
   
   [[ TODO: Check if the documentation files also need to be updated to 
point 
   to the right areas of Ant's website. ]]
   
  -5.  Ensure you have all the external libraries that Ant uses in your
  +5.  Before a build :
  +Update the following files for version number, and commit your changes.
  +
  +* docs/manual/cover.html
  +* docs/manual/credits.html
  +* build.xml (version property)
  +
  +the first beta on the 1.6 branch should be calle 1.6Beta1, ...
  +
  +the version property in build.xml governs the output of ant -version and
  +the naming of the distribution files.
  +
  +6.  Ensure you have all the external libraries that Ant uses in your
   lib/optional directory.  To find out what libraries you need, execute
   the build with -verbose option and scan for lines beginning with 
   Unable to load
   
  -6.  Next bootstrap, build and run the tests.  Then build the distribution 
  +7.  Next bootstrap, build and run the tests.  Then build the distribution
   on the branch. It is important that this be a clean build. Label this 
with 
  -a tag ANT_15_B1.
  +a tag ANT_16_B1.
   
  -7.  Sign the distribution files using the following simple script
  +8.  Sign the distribution files using the following simple script
   #!/bin/sh
   for i in distribution/*
   do
  @@ -65,11 +77,12 @@
   Also make sure you have sent the key that you use to a public 
   keyserver.
   
  -8.  The beta distribution is now ready to go. Bundle it up into a tar.gz 
file 
  +9.  The beta distribution is now ready to go. Bundle it up into a tar.gz file
   and scp to your apache account.
   
  -9.  Meanwhile, convert the WHATSNEW file into HTML for the README file on 
the 
  -website. See the previous release directories for examples of these 
files. 
  +10. Meanwhile, convert the part of the WHATSNEW file covering the changes
  +since the last release into HTML for the README file on the
  +website. See the previous release directories for examples of these 
files.
   Add instructions and warnings (GNU tar format issues, etc).
   
   You may choose to use the text2html convertor present at
  @@ -79,18 +92,18 @@
   
   [[ TODO: This must perhaps be an Ant task. ]]
   
  -10. Once this is uploaded, unpack things, create the release directory, 
  -something like v1.5Beta1, push the release and RELEASE-NOTES files
  +11. Once this is uploaded, unpack things, create the release directory,
  +something like v1.6Beta1, push the release and RELEASE-NOTES files
   into this directory.  Create a symbolic link named README.html
   that points to the RELEASE-NOTES.
   
   The files should go to /www/cvs.apache.org/dist/ant/ on minotaur.
   
  -11. Address the available release tags in BugZilla. Create a new tag 
1.5Beta1 
  -and a 1.6alpha. Assign all existing 1.5 alpha bugs to one of these 
release 
  +12. Address the available release tags in BugZilla. Create a new tag 1.6Beta1
  +and a 1.7Alpha. Assign all existing 1.6 alpha bugs to one of these 
release
   labels.
   
  -12. Once that is done, do a test download to make sure everything is OK. A 
  +13. Once that is done, do a test download to make sure everything is OK. A
   common problem may be:
   * the file's mime type is not recognized and is interpreted as 
 text/plain.  Fix it by using some .htaccess magic (AddEncoding stuff)
  @@ -102,8 +115,6 @@
   etc).
   
   Also ensure 

cvs commit: ant ReleaseInstructions

[antoine]

antoine 2003/09/30 06:06:33

  Modified:.Tag: ANT_16_BRANCH ReleaseInstructions
  Log:
  Fix typo
  
  Revision  ChangesPath
  No   revision
  No   revision
  1.17.2.3  +30 -30ant/ReleaseInstructions
  
  Index: ReleaseInstructions
  ===
  RCS file: /home/cvs/ant/ReleaseInstructions,v
  retrieving revision 1.17.2.2
  retrieving revision 1.17.2.3
  diff -u -r1.17.2.2 -r1.17.2.3
  --- ReleaseInstructions   30 Sep 2003 12:59:13 -  1.17.2.2
  +++ ReleaseInstructions   30 Sep 2003 13:06:32 -  1.17.2.3
  @@ -9,33 +9,33 @@
 your context.
   
   1.  Propose a release plan for vote.  This should set out the timetable for
  -the release under ideal circumstances.  The level of bugs reported 
  -can delay things. Generally, give a few weeks to close the source tree 
  +the release under ideal circumstances.  The level of bugs reported
  +can delay things. Generally, give a few weeks to close the source tree
   to further changes so people can finalise contributions, etc. At this 
time,
   the first beta will be cut and there will be then a period of beta 
testing,
   usually 1 month but this should be flexible.
   
   2.  Note that any mention of a deadline causes a flood of bug fixes, new 
tasks,
  -etc.  This needs to be managed as best it can. Some fixes will be 
applied, 
  -others held over. Make this clear in the release plan. The committers 
and 
  -particularly the release manager will need to make judgement calls here. 
  +etc.  This needs to be managed as best it can. Some fixes will be 
applied,
  +others held over. Make this clear in the release plan. The committers and
  +particularly the release manager will need to make judgement calls here.
   Anything too big is likely to be held over.
  -
  -3.  Once the freeze date arrives, create a branch for the release builds. 
You 
  -will need to be comfortable in handling CVS branches with mutliple 
  -merge-backs to the main branch and even selected merges from the the 
main 
  -branch to the release branch.  
  -
  +
  +3.  Once the freeze date arrives, create a branch for the release builds. You
  +will need to be comfortable in handling CVS branches with mutliple
  +merge-backs to the main branch and even selected merges from the the main
  +branch to the release branch.
  +
   For more information on performing branching and merging, please visit
   http://www.durak.org/cvswebsites/doc/cvs_54.php#SEC54
   
   Label such branches ANT_16_BRANCH.
  -
  -4.  Once the branch is setup, the version numbers in CVS are changed. On the 
  +
  +4.  Once the branch is setup, the version numbers in CVS are changed. On the
   branch, the version property in build.xml becomes 1.6Beta,
   while the main branch is updated to 1.7alpha.
  -
  -[[ TODO: Check if the documentation files also need to be updated to 
point 
  +
  +[[ TODO: Check if the documentation files also need to be updated to 
point
   to the right areas of Ant's website. ]]
   
   5.  Before a build :
  @@ -45,20 +45,20 @@
   * docs/manual/credits.html
   * build.xml (version property)
   
  -the first beta on the 1.6 branch should be calle 1.6Beta1, ...
  +the first beta on the 1.6 branch should be called 1.6Beta1, ...
   
   the version property in build.xml governs the output of ant -version and
   the naming of the distribution files.
   
   6.  Ensure you have all the external libraries that Ant uses in your
   lib/optional directory.  To find out what libraries you need, execute
  -the build with -verbose option and scan for lines beginning with 
  +the build with -verbose option and scan for lines beginning with
   Unable to load
   
   7.  Next bootstrap, build and run the tests.  Then build the distribution
  -on the branch. It is important that this be a clean build. Label this 
with 
  +on the branch. It is important that this be a clean build. Label this 
with
   a tag ANT_16_B1.
  -
  +
   8.  Sign the distribution files using the following simple script
   #!/bin/sh
   for i in distribution/*
  @@ -73,13 +73,13 @@
   Before you do that, ensure that the key you use is inside the KEYS
   file in Ant's CVS repository - and that you perform a cvs update on
   the KEYS file in /www/www.apache.org/dist/ant/
  -
  -Also make sure you have sent the key that you use to a public 
  +
  +Also make sure you have sent the key that you use to a public
   keyserver.
   
   9.  The beta distribution is now ready to go. Bundle it up into a tar.gz file
   and scp to your apache account.
  -
  +
   10. Meanwhile, convert the part of the WHATSNEW file covering the changes
   since the last release into HTML for the README file 

AW: cvs commit: ant ReleaseInstructions

[Antoine Lévy-Lambert]

Will fix this, thanks Jan.
Antoine

-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 30. September 2003 15:05
An: [EMAIL PROTECTED]
Betreff: RE: cvs commit: ant ReleaseInstructions


   +the first beta on the 1.6 branch should be calle 1.6Beta1, ...

called instead calle


Jan


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant/xdocs antnews.xml index.xml

[bodewig]

bodewig 2003/09/30 06:07:57

  Modified:docs antnews.html index.html
   xdocsantnews.xml index.xml
  Log:
  Announce the 1.6beta release
  
  Revision  ChangesPath
  1.79  +16 -0 ant/docs/antnews.html
  
  Index: antnews.html
  ===
  RCS file: /home/cvs/ant/docs/antnews.html,v
  retrieving revision 1.78
  retrieving revision 1.79
  diff -u -r1.78 -r1.79
  --- antnews.html  23 Sep 2003 11:04:09 -  1.78
  +++ antnews.html  30 Sep 2003 13:07:57 -  1.79
  @@ -175,6 +175,22 @@
 div class=content
   h1 class=titleNews/h1
   h3 class=section
  +  a name=Ant 1.6beta1/a
  +  Ant 1.6beta1
  +/h3
  +h3September 30, 2003 - Ant 1.6beta1 Available/h3
  +pApache Ant 1.6beta1 is now available for 
a href=http://cvs.apache.org/dist/ant/v1.6beta1/;download/a.  As
  +we've already said in the announcements of Ant 1.5.4, this release
  +requires JDK 1.2 or later to run./p
  +pWe encourage user to give this beta a 
release a try and report
  +any bugs found so that we get a chance to fix them before we make
  +the final release of Ant 1.6./p
  +pAnt 1.6 adds a lot of new features, most 
prominently support
  +for XML namespaces as well as a new concept of Ant libraries that
  +makes use of namespaces to avoid name clashes of custom tasks.
  +For a longer list of fixed bugs and new features see the release
  +notes./p
  +h3 class=section
 a name=Ant 1.5.4/a
 Ant 1.5.4
   /h3
  
  
  
  1.289 +15 -0 ant/docs/index.html
  
  Index: index.html
  ===
  RCS file: /home/cvs/ant/docs/index.html,v
  retrieving revision 1.288
  retrieving revision 1.289
  diff -u -r1.288 -r1.289
  --- index.html23 Sep 2003 11:04:09 -  1.288
  +++ index.html30 Sep 2003 13:07:57 -  1.289
  @@ -183,6 +183,21 @@
   Apache folks and share the knowledge.
   /p
   h3 class=section
  +  a name=Ant 1.6beta1/a
  +  Ant 1.6beta1
  +/h3
  +pApache Ant 1.6beta1 is now available for a 
href=http://cvs.apache.org/dist/ant/v1.6beta1/;download/a.  As
  +we've already said in the announcements of Ant 1.5.4, this release
  +requires JDK 1.2 or later to run./p
  +pWe encourage user to give this beta a 
release a try and report
  +any bugs found so that we get a chance to fix them before we make
  +the final release of Ant 1.6./p
  +pAnt 1.6 adds a lot of new features, most 
prominently support
  +for XML namespaces as well as a new concept of Ant libraries that
  +makes use of namespaces to avoid name clashes of custom tasks.
  +For a longer list of fixed bugs and new features see the release
  +notes./p
  +h3 class=section
 a name=Ant 1.5.4/a
 Ant 1.5.4
   /h3
  
  
  
  1.49  +19 -0 ant/xdocs/antnews.xml
  
  Index: antnews.xml
  ===
  RCS file: /home/cvs/ant/xdocs/antnews.xml,v
  retrieving revision 1.48
  retrieving revision 1.49
  diff -u -r1.48 -r1.49
  --- antnews.xml   20 Aug 2003 23:28:59 -  1.48
  +++ antnews.xml   30 Sep 2003 13:07:57 -  1.49
  @@ -9,6 +9,25 @@
 /properties
   
   body
  +   section name=Ant 1.6beta1
  +h3September 30, 2003 - Ant 1.6beta1 Available/h3
  +pApache Ant 1.6beta1 is now available for a
  +href=http://cvs.apache.org/dist/ant/v1.6beta1/;download/a.  As
  +we've already said in the announcements of Ant 1.5.4, this release
  +requires JDK 1.2 or later to run./p
  +
  +pWe encourage user to give this beta a release a try and report
  +any bugs found so that we get a chance to fix them before we make
  +the final release of Ant 1.6./p
  +
  +pAnt 1.6 adds a lot of new features, most prominently support
  +for XML namespaces as well as a new concept of Ant libraries that
  +makes use of namespaces to avoid name clashes of custom tasks.
  +For a longer list of fixed bugs and new features see the release
  +notes./p
  +
  +   /section
  +
 section name=Ant 1.5.4
   h3August 12, 2003 - Ant 1.5.4 Available/h3
   pApache Ant 1.5.4 is now available for 
  
  
  
  1.54  +18 -0 ant/xdocs/index.xml
  
  Index: index.xml
  ===
  RCS file: /home/cvs/ant/xdocs/index.xml,v
  retrieving revision 1.53
  retrieving revision 1.54
  diff -u -r1.53 -r1.54
  --- index.xml 23 Sep 2003 11:04:10 -  1.53
  +++ index.xml 30 Sep 2003 13:07:57 -  1.54
  @@ -18,6 

cvs commit: ant ReleaseInstructions

[antoine]

antoine 2003/09/30 06:08:00

  Modified:.ReleaseInstructions
  Log:
  Merge from ANT_16_BRANCH
  
  Revision  ChangesPath
  1.20  +30 -30ant/ReleaseInstructions
  
  Index: ReleaseInstructions
  ===
  RCS file: /home/cvs/ant/ReleaseInstructions,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- ReleaseInstructions   30 Sep 2003 13:01:32 -  1.19
  +++ ReleaseInstructions   30 Sep 2003 13:08:00 -  1.20
  @@ -9,33 +9,33 @@
 your context.
   
   1.  Propose a release plan for vote.  This should set out the timetable for
  -the release under ideal circumstances.  The level of bugs reported 
  -can delay things. Generally, give a few weeks to close the source tree 
  +the release under ideal circumstances.  The level of bugs reported
  +can delay things. Generally, give a few weeks to close the source tree
   to further changes so people can finalise contributions, etc. At this 
time,
   the first beta will be cut and there will be then a period of beta 
testing,
   usually 1 month but this should be flexible.
   
   2.  Note that any mention of a deadline causes a flood of bug fixes, new 
tasks,
  -etc.  This needs to be managed as best it can. Some fixes will be 
applied, 
  -others held over. Make this clear in the release plan. The committers 
and 
  -particularly the release manager will need to make judgement calls here. 
  +etc.  This needs to be managed as best it can. Some fixes will be 
applied,
  +others held over. Make this clear in the release plan. The committers and
  +particularly the release manager will need to make judgement calls here.
   Anything too big is likely to be held over.
  -
  -3.  Once the freeze date arrives, create a branch for the release builds. 
You 
  -will need to be comfortable in handling CVS branches with mutliple 
  -merge-backs to the main branch and even selected merges from the the 
main 
  -branch to the release branch.  
  -
  +
  +3.  Once the freeze date arrives, create a branch for the release builds. You
  +will need to be comfortable in handling CVS branches with mutliple
  +merge-backs to the main branch and even selected merges from the the main
  +branch to the release branch.
  +
   For more information on performing branching and merging, please visit
   http://www.durak.org/cvswebsites/doc/cvs_54.php#SEC54
   
   Label such branches ANT_16_BRANCH.
  -
  -4.  Once the branch is setup, the version numbers in CVS are changed. On the 
  +
  +4.  Once the branch is setup, the version numbers in CVS are changed. On the
   branch, the version property in build.xml becomes 1.6Beta,
   while the main branch is updated to 1.7alpha.
  -
  -[[ TODO: Check if the documentation files also need to be updated to 
point 
  +
  +[[ TODO: Check if the documentation files also need to be updated to 
point
   to the right areas of Ant's website. ]]
   
   5.  Before a build :
  @@ -45,20 +45,20 @@
   * docs/manual/credits.html
   * build.xml (version property)
   
  -the first beta on the 1.6 branch should be calle 1.6Beta1, ...
  +the first beta on the 1.6 branch should be called 1.6Beta1, ...
   
   the version property in build.xml governs the output of ant -version and
   the naming of the distribution files.
   
   6.  Ensure you have all the external libraries that Ant uses in your
   lib/optional directory.  To find out what libraries you need, execute
  -the build with -verbose option and scan for lines beginning with 
  +the build with -verbose option and scan for lines beginning with
   Unable to load
   
   7.  Next bootstrap, build and run the tests.  Then build the distribution
  -on the branch. It is important that this be a clean build. Label this 
with 
  +on the branch. It is important that this be a clean build. Label this 
with
   a tag ANT_16_B1.
  -
  +
   8.  Sign the distribution files using the following simple script
   #!/bin/sh
   for i in distribution/*
  @@ -73,13 +73,13 @@
   Before you do that, ensure that the key you use is inside the KEYS
   file in Ant's CVS repository - and that you perform a cvs update on
   the KEYS file in /www/www.apache.org/dist/ant/
  -
  -Also make sure you have sent the key that you use to a public 
  +
  +Also make sure you have sent the key that you use to a public
   keyserver.
   
   9.  The beta distribution is now ready to go. Bundle it up into a tar.gz file
   and scp to your apache account.
  -
  +
   10. Meanwhile, convert the part of the WHATSNEW file covering the changes
   since the last release into HTML for the README file on the
   website. See the previous release directories for examples of these 
files.
  

Which version should the online manual be?

[Stefan Bodewig]

I can't remember what we did the last time around.

Do we switch to the 1.6beta manual or do we keep 1.5.4 until 1.6 final
has been released?

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Which version should the online manual be?

[Jan . Materne]

I prefer 1.5.4 online until 1.6 is released.
1.5.4 is the last official version for production.


Jan

 -Original Message-
 From: Stefan Bodewig [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, September 30, 2003 3:23 PM
 To: [EMAIL PROTECTED]
 Subject: Which version should the online manual be?
 
 
 I can't remember what we did the last time around.
 
 Do we switch to the 1.6beta manual or do we keep 1.5.4 until 1.6 final
 has been released?
 
 Stefan
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

Use stdin as input for a forked java task

[Bart Golsteijn]

I saw it possible to specify an input file for a (forked) java task in Ant 
1.60. Is there (going to be) a possibility to read input from stdin? (for 
example 'input=-' reads from stdin)

Thanks in advance,
Bart
_
MSN Zoeken, voor duidelijke zoekresultaten! http://search.msn.nl
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Which version should the online manual be?

[Magesh Umasankar]

We kept the manual of the final released version and
not the beta version.

If there are no space issues, let us consider having
the released version as well as the beta version of
the manual online, after clearly displaying that the
beta manual is in fact beta (using a background image
reading BETA across the sheet, for example)...

Cheers,
Magesh

- Original Message - 
From: Stefan Bodewig [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 30, 2003 9:23 AM
Subject: Which version should the online manual be?


 I can't remember what we did the last time around.
 
 Do we switch to the 1.6beta manual or do we keep 1.5.4 until 1.6 final
 has been released?
 
 Stefan
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Which version should the online manual be?

[Jan . Materne]

 We kept the manual of the final released version and
 not the beta version.
 
 If there are no space issues, let us consider having
 the released version as well as the beta version of
 the manual online, after clearly displaying that the
 beta manual is in fact beta (using a background image
 reading BETA across the sheet, for example)...

Then why not put the actual CVS version online?
With another background image...


Jan



 
 Cheers,
 Magesh
 
 - Original Message - 
 From: Stefan Bodewig [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Tuesday, September 30, 2003 9:23 AM
 Subject: Which version should the online manual be?
 
 
  I can't remember what we did the last time around.
  
  Do we switch to the 1.6beta manual or do we keep 1.5.4 
 until 1.6 final
  has been released?
  
  Stefan
  
  
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

cvs commit: ant/xdocs bindownload.xml srcdownload.xml

[bodewig]

bodewig 2003/09/30 06:36:41

  Modified:docs bindownload.html srcdownload.html
   xdocsbindownload.xml srcdownload.xml
  Log:
  Add pointers to 1.6beta to the download pages as well
  
  Revision  ChangesPath
  1.38  +6 -0  ant/docs/bindownload.html
  
  Index: bindownload.html
  ===
  RCS file: /home/cvs/ant/docs/bindownload.html,v
  retrieving revision 1.37
  retrieving revision 1.38
  diff -u -r1.37 -r1.38
  --- bindownload.html  23 Sep 2003 11:04:09 -  1.37
  +++ bindownload.html  30 Sep 2003 13:36:41 -  1.38
  @@ -191,6 +191,12 @@
   the a href=http://www.apache.org/dist/ant/;master distribution
   directory/a or, preferably, its a href=[preferred]/ant/mirror/a./p
   h3 class=section
  +  a name=Downloading Ant 1.6beta/a
  +  Downloading Ant 1.6beta
  +/h3
  +pBeta releases are not mirrored, you can find our 
latest beta
  +release at a 
href=http://cvs.apache.org/dist/ant/;http://cvs.apache.org/dist/ant//a./p
  +h3 class=section
 a name=Mirror/a
 Mirror
   /h3
  
  
  
  1.37  +6 -0  ant/docs/srcdownload.html
  
  Index: srcdownload.html
  ===
  RCS file: /home/cvs/ant/docs/srcdownload.html,v
  retrieving revision 1.36
  retrieving revision 1.37
  diff -u -r1.36 -r1.37
  --- srcdownload.html  23 Sep 2003 11:04:09 -  1.36
  +++ srcdownload.html  30 Sep 2003 13:36:41 -  1.37
  @@ -189,6 +189,12 @@
   the a href=http://www.apache.org/dist/ant/;master distribution
   directory/a or, preferably, its a href=[preferred]/ant/mirror/a./p
   h3 class=section
  +  a name=Downloading Ant 1.6beta/a
  +  Downloading Ant 1.6beta
  +/h3
  +pBeta releases are not mirrored, you can find our 
latest beta
  +release at a 
href=http://cvs.apache.org/dist/ant/;http://cvs.apache.org/dist/ant//a./p
  +h3 class=section
 a name=Mirror/a
 Mirror
   /h3
  
  
  
  1.18  +8 -0  ant/xdocs/bindownload.xml
  
  Index: bindownload.xml
  ===
  RCS file: /home/cvs/ant/xdocs/bindownload.xml,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- bindownload.xml   18 Aug 2003 09:58:27 -  1.17
  +++ bindownload.xml   30 Sep 2003 13:36:41 -  1.18
  @@ -34,6 +34,14 @@
   
   /section
   
  +section name=Downloading Ant 1.6beta
  +
  +pBeta releases are not mirrored, you can find our latest beta
  +release at a
  
+href=http://cvs.apache.org/dist/ant/;http://cvs.apache.org/dist/ant//a./p
  +
  +/section
  +
   section name=Mirror
   
   pYou are currently using b[preferred]/b.  If you encounter a
  
  
  
  1.16  +8 -0  ant/xdocs/srcdownload.xml
  
  Index: srcdownload.xml
  ===
  RCS file: /home/cvs/ant/xdocs/srcdownload.xml,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- srcdownload.xml   18 Aug 2003 09:58:27 -  1.15
  +++ srcdownload.xml   30 Sep 2003 13:36:41 -  1.16
  @@ -31,6 +31,14 @@
   
   /section
   
  +section name=Downloading Ant 1.6beta
  +
  +pBeta releases are not mirrored, you can find our latest beta
  +release at a
  
+href=http://cvs.apache.org/dist/ant/;http://cvs.apache.org/dist/ant//a./p
  +
  +/section
  +
   section name=Mirror
   
   pYou are currently using b[preferred]/b.  If you encounter a
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

1.6 migration guide?

[Steve Cohen]

I haven't had much to do with the 1.6 release and am still using 1.5.4.
(Actually, in fact, probably 1.5.3).  I don't care which manual is
online as long as I can get to the 1.5.4 manual without too much hassle.

But my question has more to do with the 1.6 documentation itself.  From
following the discussion threads it seems that while a few things may
break in 1.5.4 build scripts, there are whole new possibilities to do
things elegantly in 1.6 that could only be done in a kludgey fashion in
1.5.  My impression is that it's sort of like Java 1.2.  When it came
out you could still write Java 1.1 code with 1.2, but unless you were
aiming for backward compatibility, why would you want to?

In other words, I'm looking for a migration guide that shows off the 1.6
way of doing things against the 1.5 way wherever the 1.6 way is more
powerful, not just the list of new features that is in the release
notes.  Is someone working on such documentation?  I think it would be
valuable.

RE: 1.6 migration guide?

[Jan . Materne]

 But my question has more to do with the 1.6 documentation 
 itself.  From
 following the discussion threads it seems that while a few things may
 break in 1.5.4 build scripts, there are whole new possibilities to do
 things elegantly in 1.6 that could only be done in a kludgey 
 fashion in
 1.5.  My impression is that it's sort of like Java 1.2.  When it came
 out you could still write Java 1.1 code with 1.2, but unless you were
 aiming for backward compatibility, why would you want to?
 
 In other words, I'm looking for a migration guide that shows 
 off the 1.6
 way of doing things against the 1.5 way wherever the 1.6 way is more
 powerful, not just the list of new features that is in the release
 notes.  Is someone working on such documentation?  I think it would be
 valuable.

Sounds good.
When we will recieve your document? :-)


Jan

RE: 1.6 migration guide?

[Steve Cohen]

Jan, my comments are based on the fact that this is what I want as a
user.  The point is that, as I said, I haven't been involved in 1.6
development and I don't know much, if anything, about what these
features are.  So I can't write this document.  But if one of the
developers who is centrally involved can write this document, it would
be very useful.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2003 8:46 AM
To: [EMAIL PROTECTED]
Subject: RE: 1.6 migration guide?


 But my question has more to do with the 1.6 documentation
 itself.  From
 following the discussion threads it seems that while a few things may
 break in 1.5.4 build scripts, there are whole new possibilities to do
 things elegantly in 1.6 that could only be done in a kludgey 
 fashion in
 1.5.  My impression is that it's sort of like Java 1.2.  When it came
 out you could still write Java 1.1 code with 1.2, but unless you were
 aiming for backward compatibility, why would you want to?
 
 In other words, I'm looking for a migration guide that shows
 off the 1.6
 way of doing things against the 1.5 way wherever the 1.6 way is more
 powerful, not just the list of new features that is in the release
 notes.  Is someone working on such documentation?  I think it would be
 valuable.

Sounds good.
When we will recieve your document? :-)


Jan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Which version should the online manual be?

[Magesh Umasankar]

- Original Message - 
From: [EMAIL PROTECTED]


 Then why not put the actual CVS version online?
 With another background image...

The historical 'problem' has been that betas did not 
get a good enough visibility to be well tested.  Having 
the beta manual online may be a catalyst to get more 
people to test the beta.  They would surf to the beta 
manual just to check out how things are different or 
if there is something that they need in it.  If they 
see something useful, they'll hopefully give it a try 
and hopefully provide us feedback.  Currently, for the 
user to try out the beta, she would have to download it 
to see if there is anything that is particularly useful 
- granted we keep the WhatsNew upto date, but it may not 
always provide enough details.

On the other hand, if somebody is interested in the cvs
version (alpha version) of the manual, it is because of
self-interest.  I don't think many 'users' would look at
work in progress and report a lot of issues.  Sigh, it 
hasn't happened even with betas yet ;-(

For the above two reasons, I suggest we have the released
version of the manual and the beta version of the manual, 
but not the alpha version.

 Jan

Cheers,
Magesh


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Which version should the online manual be?

[Jan . Materne]

  Then why not put the actual CVS version online?
  With another background image...
 
 The historical 'problem' has been that betas did not 
 get a good enough visibility to be well tested.  Having 
 the beta manual online may be a catalyst to get more 
 people to test the beta.  They would surf to the beta 
 manual just to check out how things are different or 
 if there is something that they need in it.  If they 
 see something useful, they'll hopefully give it a try 
 and hopefully provide us feedback.  Currently, for the 
 user to try out the beta, she would have to download it 
 to see if there is anything that is particularly useful 
 - granted we keep the WhatsNew upto date, but it may not 
 always provide enough details.
 
 On the other hand, if somebody is interested in the cvs
 version (alpha version) of the manual, it is because of
 self-interest.  I don't think many 'users' would look at
 work in progress and report a lot of issues.  Sigh, it 
 hasn't happened even with betas yet ;-(
 
 For the above two reasons, I suggest we have the released
 version of the manual and the beta version of the manual, 
 but not the alpha version.
 
  Jan
 
 Cheers,
 Magesh


ok, convinced.
Beta-manual as commercial for the beta :-)


Jan

RE: 1.6 migration guide?

[Steve Cohen]

Thank you.  This is very helpful, a start, anyway, on what I was after.
If Peter has time, I would really like to see what he comes up with.

On antlib, I guess I don't understand yet why I would want to do what it
does.  I'm sure there must be some power in this concept but I don't yet
understand what that is.

-Original Message-
From: Antoine Levy-Lambert [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 30, 2003 9:53 AM
To: Ant Developers List
Subject: AW: 1.6 migration guide?


First of all, the change from ant1.5 to ant1.6 is not that drastic.

There are new tasks and extensions of existing tasks.

The most revolutionary feature is antlib. It should allow users to
create jar files with a descriptor containing all the taskdefs and
typedefs that are required.

This work done by Peter Reilly should also make it easier to deliver
custom conditions, filters, ...

Really, Peter Reilly should be the one to write this migration guide.

Read the docs/manual/CoreTypes/antlib.html file,
docs/manual/CoreTypes/custom-programming.html.

Apart from antlib, the import/ task is certainly useful. I am not 100%
sure myself what you can do and not do with it, but in principle it is
there to allow several build files to use a common part containing for
instance property definitions, but also targets and whatever is legal in
a main build file.

Then subant/ is a nice wrapper around ant/ to run ant/ against a
fileset of build files, or to run ant/ n times against the same build
file, changing the base dir.

Other than that, there is the possibility to put normal tasks directly
under the project/ task (outside of any targets) which is nice if you
want to write a small build file.

Then the ssh/ and scp/ tasks will be very useful for deployment.

That's the main points which spring to my mind.

Antoine

-Ursprungliche Nachricht-
Von: Steve Cohen [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 30. September 2003 15:51
An: Ant Developers List
Betreff: RE: 1.6 migration guide?


Jan, my comments are based on the fact that this is what I want as a
user.  The point is that, as I said, I haven't been involved in 1.6
development and I don't know much, if anything, about what these
features are.  So I can't write this document.  But if one of the
developers who is centrally involved can write this document, it would
be very useful.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: 1.6 migration guide?

[Jan . Materne]

Antlibs are interesting for people writing and publishing tasks and
for peoples who managing the ant installations.

Jan

 -Original Message-
 From: Steve Cohen [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, September 30, 2003 5:00 PM
 To: Ant Developers List
 Subject: RE: 1.6 migration guide?
 
 
 Thank you.  This is very helpful, a start, anyway, on what I 
 was after.
 If Peter has time, I would really like to see what he comes up with.
 
 On antlib, I guess I don't understand yet why I would want to 
 do what it
 does.  I'm sure there must be some power in this concept but 
 I don't yet
 understand what that is.
 
 -Original Message-
 From: Antoine Levy-Lambert [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, September 30, 2003 9:53 AM
 To: Ant Developers List
 Subject: AW: 1.6 migration guide?
 
 
 First of all, the change from ant1.5 to ant1.6 is not that drastic.
 
 There are new tasks and extensions of existing tasks.
 
 The most revolutionary feature is antlib. It should allow users to
 create jar files with a descriptor containing all the taskdefs and
 typedefs that are required.
 
 This work done by Peter Reilly should also make it easier to deliver
 custom conditions, filters, ...
 
 Really, Peter Reilly should be the one to write this migration guide.
 
 Read the docs/manual/CoreTypes/antlib.html file,
 docs/manual/CoreTypes/custom-programming.html.
 
 Apart from antlib, the import/ task is certainly useful. I 
 am not 100%
 sure myself what you can do and not do with it, but in principle it is
 there to allow several build files to use a common part containing for
 instance property definitions, but also targets and whatever 
 is legal in
 a main build file.
 
 Then subant/ is a nice wrapper around ant/ to run ant/ against a
 fileset of build files, or to run ant/ n times against the 
 same build
 file, changing the base dir.
 
 Other than that, there is the possibility to put normal tasks directly
 under the project/ task (outside of any targets) which is 
 nice if you
 want to write a small build file.
 
 Then the ssh/ and scp/ tasks will be very useful for deployment.
 
 That's the main points which spring to my mind.
 
 Antoine
 
 -Ursprungliche Nachricht-
 Von: Steve Cohen [mailto:[EMAIL PROTECTED]
 Gesendet: Dienstag, 30. September 2003 15:51
 An: Ant Developers List
 Betreff: RE: 1.6 migration guide?
 
 
 Jan, my comments are based on the fact that this is what I want as a
 user.  The point is that, as I said, I haven't been involved in 1.6
 development and I don't know much, if anything, about what these
 features are.  So I can't write this document.  But if one of the
 developers who is centrally involved can write this document, it would
 be very useful.
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

Re: AW: 1.6 migration guide?

[peter reilly]

On Tuesday 30 September 2003 15:52, Antoine Levy-Lambert wrote:
 First of all, the change from ant1.5 to ant1.6 is not that drastic.

 There are new tasks and extensions of existing tasks.

 The most revolutionary feature is antlib. It should allow users to create
 jar files with
 a descriptor containing all the taskdefs and typedefs that are required.

 This work done by Peter Reilly should also make it easier to deliver custom
 conditions, filters, ...

 Really, Peter Reilly should be the one to write this migration guide.

Yikes.
  In any case these are for people that write custom extensions to ant.


 Read the docs/manual/CoreTypes/antlib.html file,
 docs/manual/CoreTypes/custom-programming.html.

That is my current contribution.

 Apart from antlib, the import/ task is certainly useful. I am not 100%
 sure myself what you can do and not do
 with it, but in principle it is there to allow several build files to use a
 common part containing for instance
 property definitions, but also targets and whatever is legal in a main
 build file.

 Then subant/ is a nice wrapper around ant/ to run ant/ against a
 fileset of build files, or
 to run ant/ n times against the same build file, changing the base dir.

 Other than that, there is the possibility to put normal tasks directly
 under the project/ task (outside of any targets)
 which is nice if you want to write a small build file.

 Then the ssh/ and scp/ tasks will be very useful for deployment.

 That's the main points which spring to my mind.

macrodef is also something that could be usefull for removing the need
for a lot of current usage of antcall

Peter


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: cvs over SSH

[Shatzer, Larry]

Also might want to read this: http://www.tortoisecvs.org/faq.html#sshkeys
for a non-cygwin solution, which I use.

-- Larry

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: Tuesday, September 30, 2003 3:45 AM
 To: [EMAIL PROTECTED]
 Subject: RE: cvs over SSH
 
 
 I will look and try, thanks so far.
 
 Jan
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[PATCH] update cvs.html

[Shatzer, Larry]

v1.11.7 of CVS was released. Updated cvs.html to link to the latest stable
version of CVS's documents.

-- Larry

Index: docs/manual/CoreTasks/cvs.html
===
RCS file: /home/cvspublic/ant/docs/manual/CoreTasks/cvs.html,v
retrieving revision 1.19
diff -u -r1.19 cvs.html
--- docs/manual/CoreTasks/cvs.html  22 Sep 2003 15:41:44 -  1.19
+++ docs/manual/CoreTasks/cvs.html  30 Sep 2003 15:14:52 -
@@ -168,8 +168,8 @@
 pUpdates from the head of repository ignoring sticky bits (code-A/code) 
and creating any new directories as necessary (code-d/code)./p
 pNote: the text of the command is passed to cvs quot;as-isquot; so any cvs 
options should appear
 before the command, and any command options should appear after the command as 
in the diff example
-above. See a href=http://www.cvshome.org/docs/manual/cvs-1.11.6/cvs.html; 
target=_topthe cvs manual/a for details,
-specifically the a 
href=http://www.cvshome.org/docs/manual/cvs-1.11.6/cvs_16.html; 
target=_topGuide to CVS commands/a/p
+above. See a href=http://www.cvshome.org/docs/manual/cvs-1.11.7/cvs.html; 
target=_topthe cvs manual/a for details,
+specifically the a 
href=http://www.cvshome.org/docs/manual/cvs-1.11.7/cvs_16.html; 
target=_topGuide to CVS commands/a/p
 hr
 p align=centerCopyright copy; 2000-2003 Apache Software
 Foundation.  All rights Reserved./p

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 23524] - ant and javacc

[bugzilla]

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=23524.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23524

ant and javacc





--- Additional Comments From [EMAIL PROTECTED]  2003-09-30 16:21 ---
I always get:

jjtree:
   [jjtree] java.lang.NoClassDefFoundError: COM/sun/labs/jjtree/Main
   [jjtree] Exception in thread main

br
piri

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 23526] New: - touch should support nested filelist elements

[bugzilla]

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=23526.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23526

touch should support nested filelist elements

   Summary: touch should support nested filelist elements
   Product: Ant
   Version: 1.6Beta
  Platform: All
OS/Version: Other
Status: NEW
  Severity: Enhancement
  Priority: Other
 Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]


The touch task currently supports a File attribute, which may or may not exist, 
and nested FileSets, whose components, by definition, exist.  The behavior of 
the Unix touch command would be more faithfully modeled if nested FileLists 
were also permitted, as this would provide support for touching several 
possibly nonexistent files with one task invocation.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 23526] - touch should support nested filelist elements

[bugzilla]

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=23526.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23526

touch should support nested filelist elements





--- Additional Comments From [EMAIL PROTECTED]  2003-09-30 17:08 ---
Created an attachment (id=8399)
patch for the manual page

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 23496] - Not picking up environment variables?

[bugzilla]

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=23496.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23496

Not picking up environment variables?





--- Additional Comments From [EMAIL PROTECTED]  2003-09-30 18:07 ---
I tried PATH and it produced the system default PATH. So I don't believe this 
is a bug anymore. 
This seems to be an artifact of the way GUI applications (such as Eclipse) pick 
up environment 
variables on OS X, or possibly a bug in Eclipse itself... in any event, it's 
probably not a problem 
within ant.

Thanks for taking a look at it.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 23524] - ant and javacc

[bugzilla]

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=23524.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23524

ant and javacc





--- Additional Comments From [EMAIL PROTECTED]  2003-09-30 19:50 ---

I have a feeling that you are using the javacc v3.x and that distribution is
different then the javacc v2.x. The package name have been changed from
COM.sun.labs.jjtree to org.netbeans.javacc.jjtree. I do not think that the
javacc task takes this into account.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: ant/docs/manual/CoreTasks cvs.html

[antoine]

antoine 2003/09/30 12:47:26

  Modified:docs/manual/CoreTasks cvs.html
  Log:
  cvs 1.11.7 has been released (Merge from ANT_16_BRANCH)
  Submitted by: Larry Shatzer (larry dot shatzer at spirent dot com)
  
  Revision  ChangesPath
  1.20  +2 -2  ant/docs/manual/CoreTasks/cvs.html
  
  Index: cvs.html
  ===
  RCS file: /home/cvs/ant/docs/manual/CoreTasks/cvs.html,v
  retrieving revision 1.19
  retrieving revision 1.20
  diff -u -r1.19 -r1.20
  --- cvs.html  22 Sep 2003 15:41:44 -  1.19
  +++ cvs.html  30 Sep 2003 19:47:26 -  1.20
  @@ -168,8 +168,8 @@
   pUpdates from the head of repository ignoring sticky bits 
(code-A/code) and creating any new directories as necessary 
(code-d/code)./p
   pNote: the text of the command is passed to cvs quot;as-isquot; so any 
cvs options should appear
   before the command, and any command options should appear after the command 
as in the diff example
  -above. See a href=http://www.cvshome.org/docs/manual/cvs-1.11.6/cvs.html; 
target=_topthe cvs manual/a for details,
  -specifically the a 
href=http://www.cvshome.org/docs/manual/cvs-1.11.6/cvs_16.html; 
target=_topGuide to CVS commands/a/p
  +above. See a href=http://www.cvshome.org/docs/manual/cvs-1.11.7/cvs.html; 
target=_topthe cvs manual/a for details,
  +specifically the a 
href=http://www.cvshome.org/docs/manual/cvs-1.11.7/cvs_16.html; 
target=_topGuide to CVS commands/a/p
   hr
   p align=centerCopyright copy; 2000-2003 Apache Software
   Foundation.  All rights Reserved./p
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

AW: [PATCH] update cvs.html

[Antoine Lévy-Lambert]

Patch submitted, merci beaucoup.
Antoine

-Ursprüngliche Nachricht-
Von: Shatzer, Larry [mailto:[EMAIL PROTECTED]
Gesendet: Dienstag, 30. September 2003 17:17
An: '[EMAIL PROTECTED]'
Betreff: [PATCH] update cvs.html


v1.11.7 of CVS was released. Updated cvs.html to link to the latest stable
version of CVS's documents.

-- Larry




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

DO NOT REPLY [Bug 23524] - ant and javacc

[bugzilla]

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=23524.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23524

ant and javacc





--- Additional Comments From [EMAIL PROTECTED]  2003-09-30 20:11 ---
Piri,
can you tell us :

   - which version of javaCC you have installed,

   - which of these files are present in your java CC home directory ?
JavaCC.zip, 
bin/lib/JavaCC.zip,
bin/lib/javacc.jar,
javacc.jar, // used by jpackage for JavaCC 3.x

   - ant will assume you are running javaCC version 3 if you have either
bin/lib/javacc.jar or javacc.jar in your javacchome but !!! not !!! JavaCC.zip

- also can you check that the attribute javacchome points to the right
directory in your build file ?

Antoine

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]