You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Dominique Devienne <DD...@lgc.com> on 2003/10/02 00:34:22 UTC

Ant 1.6beta1 comments

Preliminary report on what I have seems with the Beta1 release of Ant 1.6.

I hope this helps. --DD


1 - Things I noticed changed
  
  This is currently limited to using Ant 1.6 with a single project,
  where I code all my custom tasks and types.

1.1 - New deprecation warnings

P:\com_lgc\buildmagic-dd\buildmagic\src\com\lgc\buildmagic\BuildPath.java:12
0: warning: initializeCl
ass(java.lang.Class) in org.apache.tools.ant.AntClassLoader has been
deprecated
                AntClassLoader.initializeClass(c);
                              ^
P:\com_lgc\buildmagic-dd\buildmagic\src\com\lgc\buildmagic\JUnitx.java:51:
warning: addSysproperty(o
rg.apache.tools.ant.types.Environment.Variable) in
org.apache.tools.ant.taskdefs.optional.junit.JUni
tTask has been deprecated
                super.addSysproperty(var);
                     ^
P:\com_lgc\buildmagic-dd\buildmagic\src\com\lgc\buildmagic\util\BuildFileTes
tCase.java:236: warning:
 configureProject(org.apache.tools.ant.Project,java.io.File) in
org.apache.tools.ant.ProjectHelper h
as been deprecated
        ProjectHelper.configureProject(project, buildfile);
                     ^
3 warnings

1.2 - Change of formatting in JUnit???

  Instead of having a single blank line in between each test suite,
  I now get 3, which is not very pretty. And yes, and verified it was
  not my custom logger the culprit.

    <junit fork="true" printsummary="off">
      <!-- Plain console formatter for now -->
      <formatter type="brief" usefile="false" />

      <!-- XML formatter to later convert test logs to HTML -->
      <formatter type="xml" usefile="true" />

      <batchtest todir="build/logs/tests">
        <fileset dir="build/classes" includes="${testcases}" />
      </batchtest>
    </junit>

  So what used to be:

-test:
Created dir: P:\com_lgc\buildmagic-dd\buildmagic\build\logs\tests
--- testcases = **/test/*Test.class ---

Testsuite: com.lgc.buildmagic.test.AntReturnTest
Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 2.687 sec

Testsuite: com.lgc.buildmagic.test.BinaryConfigTest
Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 2.921 sec

Testsuite: com.lgc.buildmagic.test.BuildNumberTest
Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4.594 sec

  Is now:

-test:
Created dir: P:\com_lgc\buildmagic-dd\buildmagic\build\logs\tests
--- testcases = **/test/*Test.class ---
Testsuite: com.lgc.buildmagic.test.AntReturnTest
Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 3.125 sec



Testsuite: com.lgc.buildmagic.test.BinaryConfigTest
Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 2.234 sec



Testsuite: com.lgc.buildmagic.test.BuildNumberTest
Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 4.594 sec

  Also, a test for a custom selector, which uses log(..) statements,
  which used to look simply like this:

Testsuite: com.lgc.buildmagic.test.TestTypeAndConfigSelectorTest
Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 3.672 sec

Testsuite: com.lgc.decisionspace.test.DspVersionFormatTest
Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.734 sec

  now includes a Standard Error section corresponding all the
  log statements.

Testsuite: com.lgc.buildmagic.test.TestTypeAndConfigSelectorTest
Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 3.938 sec

------------- Standard Error -----------------
(very long output)
------------- ---------------- ---------------


Testsuite: com.lgc.decisionspace.test.DspVersionFormatTest
Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.75 sec

  I'm not sure where this is coming from, as I have other tested
  tasks/types using the Ant logging sub-system... Granted, I use
  a modified BuildFileTestCase, but that class didn't change, but
  Ant did...

1.3 - Optional.jar has been split!

  Some of my projects, including the one I was testing, have
  includeAntRuntime=false, and explicitly include just the JARs
  in ant/lib they need (I have extras JAR in there). I was thus
  bitten by the removal of optional.jar.

  That made me look in ant/lib, and (re)discover that optional.jar
  was no more, and had been replaced by ant-*.jar. I find it odd
  though that there is a nodeps.jar file, instead of ant-nodeps.jar.

  I think I understand the rational for it, but given the fact that
  other JARs are often added to ant/lib, renaming that JAR to
  ant-nodeps.jar would make it obvious it's an Ant jar, and make it
  consistent with the other JAR (although the interpretation of
  classes that depend on nodeps is stretch a bit).

2 - Documentation / Manual

  In general, I'd like the new feature in Ant 1.6 to be more visible,
  Maybe with a [New in 1.6!] icon!?!?

2.1 - Main (Welcom) Page
  docs/index.html by default opens the Welcome page on the bottom left
  frame, which still shows Ant 1.5.4 as the release number.
  Also, I don't think ApacheCon 2003 is relevant to an Ant release...

2.2 - Weird vertical blank area
  When viewing the Manual using IE 6.0 on W2K, the License and Relate
  Project sections both have a blank empty area (in the bottom left frame)
  which seems to end at the bottom of the left-hand-side menuy.

2.3 - Concepts and Types
  The new sections on Antlib and Custom Components have a first link to a
  given document, then other links to subpart of that same document. All
  other "older" entries in the left-hand-side menu point to different
documents.
  I find this a little inconsistent.

2.4 - Optional Types
  The Set of Extension Packages provide an example with an external
  <libfileset> (later refid'd) which should thus be described on it own
  somewhere.

2.5 - Running Ant
  I don't see any mention of the new Launcher, or the new -lib command line
  Argument.

2.6 - Installing Ant
  The Platform Specific Issues does not mention OpenVMS at all, although
  several things have been done to better support OpenVMS.

2.7 - Ant API
  The Javadoc of the source code still doesn't have many package.html
  descriptions, nor an overview, which are both rather useful.
  Class JavaDoc is OTOH very complete ;-)

2.8 - ant/Welcome.html
  Is not linked from docs/index.html (the reverse is also true),
  although that page also has a welcome section.

  Also, I haven't read it all (yet?), but I'd find prefer something
  A little less verbose & OT, and more to the point about Ant 1.6...

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: Ant 1.6beta1 comments

Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 2 Oct 2003, Conor MacNeill <co...@cortexebusiness.com.au>
wrote:

> We could add back optional.jar as a manifest-only class-path jar to
> collect all the other optional jars together.

OK.

> This could be provided in lib or even a "legacy" dir for those who
> want to use it.

I'd rather move it to a separate dir so that people have to move it
knowing what they do instead of picking it up by surprise.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Re: Ant 1.6beta1 comments

Posted by Conor MacNeill <co...@cortexebusiness.com.au>.
On Thu, 2 Oct 2003 08:34 am, Dominique Devienne wrote:
> Preliminary report on what I have seems with the Beta1 release of Ant 1.6.
>
> I hope this helps. --DD
>

Absolutely. It is exactly what a beta is for and I hope a lot more people can 
do this level of analysis. 

I'll quickly address the things I can in a first pass.

>
> 1.1 - New deprecation warnings
>
> P:\com_lgc\buildmagic-dd\buildmagic\src\com\lgc\buildmagic\BuildPath.java:1
>2 0: warning: initializeCl
> ass(java.lang.Class) in org.apache.tools.ant.AntClassLoader has been
> deprecated
>                 AntClassLoader.initializeClass(c);
>                               ^

Under JDK 1.2, classes can be initialized when loaded and this is done in the 
rest of Ant (i.e. initializeClass is no longer used within Ant itself). 
Please see bug 14171 for an instance where the current initializeClass 
approach caused problems. So it is still supported but now deprecated. Is 
there an issue with that.

> P:\com_lgc\buildmagic-dd\buildmagic\src\com\lgc\buildmagic\JUnitx.java:51:
> warning: addSysproperty(o
> rg.apache.tools.ant.types.Environment.Variable) in
> org.apache.tools.ant.taskdefs.optional.junit.JUni
> tTask has been deprecated
>                 super.addSysproperty(var);
>                      ^
> P:\com_lgc\buildmagic-dd\buildmagic\src\com\lgc\buildmagic\util\BuildFileTe
>s tCase.java:236: warning:
>  configureProject(org.apache.tools.ant.Project,java.io.File) in
> org.apache.tools.ant.ProjectHelper h
> as been deprecated
>         ProjectHelper.configureProject(project, buildfile);
>                      ^
> 3 warnings
>
> 1.2 - Change of formatting in JUnit???
>
>   Instead of having a single blank line in between each test suite,
>   I now get 3, which is not very pretty. And yes, and verified it was
>   not my custom logger the culprit.

This may be due to a change in the IO redirection in Ant to pass stuff through 
with the line endings intact. Not sure. On my Linux and Windows boxes, there 
are two blank lines :-)

I'll have a look.

>
>   Also, a test for a custom selector, which uses log(..) statements,
>   which used to look simply like this:
>

Can you put a test case together for that?

>
> 1.3 - Optional.jar has been split!
>
>   Some of my projects, including the one I was testing, have
>   includeAntRuntime=false, and explicitly include just the JARs
>   in ant/lib they need (I have extras JAR in there). I was thus
>   bitten by the removal of optional.jar.

OK, I'm not sure what is best here. We can choose to live with the change and 
some potential pain for longer term benefit (i.e. finer control over optional 
task deployment as antlibs, with non-deployment when supporting jars are 
absent). We could add back optional.jar as a manifest-only class-path jar to 
collect all the other optional jars together. This could be provided in lib 
or even a "legacy" dir for those who want to use it.

>
>   That made me look in ant/lib, and (re)discover that optional.jar
>   was no more, and had been replaced by ant-*.jar. I find it odd
>   though that there is a nodeps.jar file, instead of ant-nodeps.jar.

Agreed  - should be ant-nodeps.jar

>
> 2 - Documentation / Manual
>
>   In general, I'd like the new feature in Ant 1.6 to be more visible,
>   Maybe with a [New in 1.6!] icon!?!?
>
> 2.1 - Main (Welcom) Page
>   docs/index.html by default opens the Welcome page on the bottom left
>   frame, which still shows Ant 1.5.4 as the release number.
>   Also, I don't think ApacheCon 2003 is relevant to an Ant release...

We used to not include the site but people wanted the site as part of the 
documentation. It is a snapshot and therefore included things which may be 
only relevant at the time of a snapshot. I not sure this should change. The 
release manager could tweak the docs at the time of build.

>
> 2.2 - Weird vertical blank area
>   When viewing the Manual using IE 6.0 on W2K, the License and Relate
>   Project sections both have a blank empty area (in the bottom left frame)
>   which seems to end at the bottom of the left-hand-side menuy.

IE bug ? :-)

Conor


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org