[lang] Release Candidiate 8 available

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

[lang] Release Candidiate 8 available

Steven Caswell
Commons-lang 2.1 release candidate 8 is available at
http://www.apache.org/~stevencaswell/commons-lang-2.1/

Primary change is Gary's working out the oddball build and class loading
issue that only seems to happen on Windows XP (SP2) since Simon reports that
the ant build works fine for him on Linux.

As with previous RCs, verification against as many JDK versions would be
appreciated, and a sanity check of the docs would also be welcome.

Vote to follow if no reports of problems.

--
Steven Caswell
[hidden email]

Take back the web - http://www.mozilla.org
Reply | Threaded
Open this post in threaded view
|

Re: [lang] Release Candidiate 8 available

Simon Kitching
On Tue, 2005-05-31 at 22:38 -0400, Steven Caswell wrote:

> Commons-lang 2.1 release candidate 8 is available at
> http://www.apache.org/~stevencaswell/commons-lang-2.1/
>
> Primary change is Gary's working out the oddball build and class loading
> issue that only seems to happen on Windows XP (SP2) since Simon reports that
> the ant build works fine for him on Linux.
>
> As with previous RCs, verification against as many JDK versions would be
> appreciated, and a sanity check of the docs would also be welcome.
>
> Vote to follow if no reports of problems.
>

When running "ant test", I get:

<output>
BUILD FAILED
/home/simon/downloads/lang/commons-lang-2.1-RC8/build.xml:149: The
following error occurred while executing this line:
/home/simon/downloads/lang/commons-lang-2.1-RC8/build.xml:142: Could not
create task or type of type: junit.

Ant could not find the task or a class this task relies upon.
</output>

I have ant 1.6.3:
<output>
simon@blackbox:~/downloads/lang/commons-lang-2.1-RC8$ ant -version
Apache Ant version 1.6.3 compiled on April 28 2005
</output>

It seems that the <junit> task is an *optional* task that must be
installed in addition to standard ant. I'm not in favour of requiring
users to install optional ant tasks.
  http://ant.apache.org/manual/OptionalTasks/junit.html

Regards,

Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: [lang] Release Candidiate 8 available

Gary Gregory
In reply to this post by Steven Caswell
Simon:

You probably need to copy junit.jar to %ANT_HOME%\lib

Gary

-----Original Message-----
From: Simon Kitching [mailto:[hidden email]]
Sent: Tuesday, May 31, 2005 10:37 PM
To: Jakarta Commons Developers List
Subject: Re: [lang] Release Candidiate 8 available

On Tue, 2005-05-31 at 22:38 -0400, Steven Caswell wrote:
> Commons-lang 2.1 release candidate 8 is available at
> http://www.apache.org/~stevencaswell/commons-lang-2.1/
>
> Primary change is Gary's working out the oddball build and class
loading
> issue that only seems to happen on Windows XP (SP2) since Simon
reports that
> the ant build works fine for him on Linux.
>
> As with previous RCs, verification against as many JDK versions would
be
> appreciated, and a sanity check of the docs would also be welcome.
>
> Vote to follow if no reports of problems.
>

When running "ant test", I get:

<output>
BUILD FAILED
/home/simon/downloads/lang/commons-lang-2.1-RC8/build.xml:149: The
following error occurred while executing this line:
/home/simon/downloads/lang/commons-lang-2.1-RC8/build.xml:142: Could not
create task or type of type: junit.

Ant could not find the task or a class this task relies upon.
</output>

I have ant 1.6.3:
<output>
simon@blackbox:~/downloads/lang/commons-lang-2.1-RC8$ ant -version
Apache Ant version 1.6.3 compiled on April 28 2005
</output>

It seems that the <junit> task is an *optional* task that must be
installed in addition to standard ant. I'm not in favour of requiring
users to install optional ant tasks.
  http://ant.apache.org/manual/OptionalTasks/junit.html

Regards,

Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: [lang] Release Candidiate 8 available

Gary Gregory
In reply to this post by Steven Caswell
BTW, this and other ant dependencies can be looked up here:
http://ant.apache.org/manual/install.html#librarydependencies

Gary

-----Original Message-----
From: Gary Gregory [mailto:[hidden email]]
Sent: Tuesday, May 31, 2005 10:55 PM
To: Jakarta Commons Developers List; [hidden email]
Subject: RE: [lang] Release Candidiate 8 available

Simon:

You probably need to copy junit.jar to %ANT_HOME%\lib

Gary

-----Original Message-----
From: Simon Kitching [mailto:[hidden email]]
Sent: Tuesday, May 31, 2005 10:37 PM
To: Jakarta Commons Developers List
Subject: Re: [lang] Release Candidiate 8 available

On Tue, 2005-05-31 at 22:38 -0400, Steven Caswell wrote:
> Commons-lang 2.1 release candidate 8 is available at
> http://www.apache.org/~stevencaswell/commons-lang-2.1/
>
> Primary change is Gary's working out the oddball build and class
loading
> issue that only seems to happen on Windows XP (SP2) since Simon
reports that
> the ant build works fine for him on Linux.
>
> As with previous RCs, verification against as many JDK versions would
be
> appreciated, and a sanity check of the docs would also be welcome.
>
> Vote to follow if no reports of problems.
>

When running "ant test", I get:

<output>
BUILD FAILED
/home/simon/downloads/lang/commons-lang-2.1-RC8/build.xml:149: The
following error occurred while executing this line:
/home/simon/downloads/lang/commons-lang-2.1-RC8/build.xml:142: Could not
create task or type of type: junit.

Ant could not find the task or a class this task relies upon.
</output>

I have ant 1.6.3:
<output>
simon@blackbox:~/downloads/lang/commons-lang-2.1-RC8$ ant -version
Apache Ant version 1.6.3 compiled on April 28 2005
</output>

It seems that the <junit> task is an *optional* task that must be
installed in addition to standard ant. I'm not in favour of requiring
users to install optional ant tasks.
  http://ant.apache.org/manual/OptionalTasks/junit.html

Regards,

Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: [lang] Release Candidiate 8 available

Gary Gregory
In reply to this post by Steven Caswell
Hello All:

I have run the following with success on Window XP SP2 based on
unzipping
http://people.apache.org/~stevencaswell/commons-lang-2.1/distributions/c
ommons-lang-2.1-RC8-src.zip.

Ant 1.6.4 with the command "ant clean dist-build-2.1 test" with:

Sun Java 1.5.0_03
Sun Java 1.4.2_08
Sun Java 1.3.1_14

Maven 1.0.2 with the command "maven clean site:generate" (for all Sun
java versions above) always gives me:

BUILD FAILED
File...... C:\Documents and
Settings\ggregory.SSSI\.maven\cache\maven-checkstyle-plugin-2.5\plugin.j
elly
Element... ant:checkstyle
Line...... 144
Column.... 63
Unable to create a Checker: unable to find file:checkstyle.xml
Total time: 5 seconds
Finished at: Tue May 31 23:06:42 PDT 2005

The checkstyle file(s) are missing from the src dist. Do we still need
BOTH checkstyle.properties and checkstyle.xml in SVN?

Thanks,
Gary

-----Original Message-----
From: Steven Caswell [mailto:[hidden email]]
Sent: Tuesday, May 31, 2005 7:38 PM
To: Jakarta Commons Developers List
Subject: [lang] Release Candidiate 8 available

Commons-lang 2.1 release candidate 8 is available at
http://www.apache.org/~stevencaswell/commons-lang-2.1/

Primary change is Gary's working out the oddball build and class loading

issue that only seems to happen on Windows XP (SP2) since Simon reports
that
the ant build works fine for him on Linux.

As with previous RCs, verification against as many JDK versions would be

appreciated, and a sanity check of the docs would also be welcome.

Vote to follow if no reports of problems.

--
Steven Caswell
[hidden email]

Take back the web - http://www.mozilla.org

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: [lang] Release Candidiate 8 available

Simon Kitching
In reply to this post by Gary Gregory
On Wed, 2005-06-01 at 01:55 -0400, Gary Gregory wrote:
> Simon:
>
> You probably need to copy junit.jar to %ANT_HOME%\lib

Yep, that will make things work. But I'm questioning whether it is
reasonable for the lang 2.1 build process to require users to do this.
What is wrong with the old way of running junit?

Alternatively, according to the documentations the junit ant task will
work if the <classpath> tag is used to point to the junit jar. And there
is already a property defined for that, right? So maybe the build.xml
could be modified to provide an explicit taskdef for junit?

Below is an example from the FAQ:
   <taskdef name="junit"
            class="org.apache.tools.ant.taskdefs.optional.junit.JUnitTask">
      <classpath>
        <pathelement location="${junit.jar}"/>
        <pathelement location="NEW-HOME-OF/ant-junit.jar"/>
      </classpath>
    </taskdef>

Regards,

Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lang] Release Candidiate 8 available

Simon Kitching
In reply to this post by Steven Caswell
On Tue, 2005-05-31 at 22:38 -0400, Steven Caswell wrote:

> Commons-lang 2.1 release candidate 8 is available at
> http://www.apache.org/~stevencaswell/commons-lang-2.1/
>
> Primary change is Gary's working out the oddball build and class loading
> issue that only seems to happen on Windows XP (SP2) since Simon reports that
> the ant build works fine for him on Linux.
>
> As with previous RCs, verification against as many JDK versions would be
> appreciated, and a sanity check of the docs would also be welcome.
>
> Vote to follow if no reports of problems.
>

Ok, apart from the issue that junit.jar had to be copied to ant's lib
directory both build and test appears to go fine on:
  * java 1.2.2 on linux (ant)
  * java 1.3.1 on linux (ant and maven)
  * java 1.5 on linux (ant and maven)


However I think that that information in STATUS.html regarding
dependencies for the project really should be in the RELEASE-NOTES.txt
file. In particular, it should be noted that ant 1.6 is now needed to
build.

And if you do go with using the <junit> tag in the build.xml, then I
think the RELEASE-NOTES.txt file should mention installing junit.jar
into ant's lib dir (or point to the info in the STATUS.html file).

Regards,

Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lang] Release Candidiate 8 available

Michael Heuer-2
In reply to this post by Steven Caswell

Steven Caswell wrote:

> Commons-lang 2.1 release candidate 8 is available at
> http://www.apache.org/~stevencaswell/commons-lang-2.1/
>
> Primary change is Gary's working out the oddball build and class loading
> issue that only seems to happen on Windows XP (SP2) since Simon reports that
> the ant build works fine for him on Linux.
>
> As with previous RCs, verification against as many JDK versions would be
> appreciated, and a sanity check of the docs would also be welcome.

Works for me with maven 1.0.2 on MacOSX Tiger and JDKs

java version "1.5.0_02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-56)
Java HotSpot(TM) Client VM (build 1.5.0_02-36, mixed mode, sharing)

java version "1.4.2_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_07-215)
Java HotSpot(TM) Client VM (build 1.4.2-50, mixed mode)

   michael


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lang] Release Candidiate 8 available

Michael Heuer-2

Michael Heuer wrote:

>
> Steven Caswell wrote:
>
> > Commons-lang 2.1 release candidate 8 is available at
> > http://www.apache.org/~stevencaswell/commons-lang-2.1/
> >
> > Primary change is Gary's working out the oddball build and class loading
> > issue that only seems to happen on Windows XP (SP2) since Simon reports that
> > the ant build works fine for him on Linux.
> >
> > As with previous RCs, verification against as many JDK versions would be
> > appreciated, and a sanity check of the docs would also be welcome.
>
> Works for me with maven 1.0.2 on MacOSX Tiger and JDKs
>
> java version "1.5.0_02"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_02-56)
> Java HotSpot(TM) Client VM (build 1.5.0_02-36, mixed mode, sharing)
>
> java version "1.4.2_07"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_07-215)
> Java HotSpot(TM) Client VM (build 1.4.2-50, mixed mode)
>

Found an older one, although not significantly different; also works
for me with maven 1.0.2 on MacOSX 10.3.9 and JDK

java version "1.4.2_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-141.4)
Java HotSpot(TM) Client VM (build 1.4.2-38, mixed mode)

   michael


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: [lang] Release Candidiate 8 available

Gary Gregory
In reply to this post by Steven Caswell
Hello:

I think it is quite reasonable to use the junit task to invoke junit
tests, IMO it is the best way since it is both clear and succinct.

Invoking junit tests the old way feels to me like a bit of hack, it just
happens to work by some side effect. Using the junit task states: This
is a junit test, run!

Personally, I would not favor the taskdef approach. My view on the
subject is that one's development environment has to be set up in a
certain way and JUnit is part of that. We already need Java, Ant and
Maven. JUnit in Ant is another layer.

We can always change is back of course ;-)

Gary

-----Original Message-----
From: Simon Kitching [mailto:[hidden email]]
Sent: Wednesday, June 01, 2005 5:36 AM
To: Jakarta Commons Developers List
Subject: RE: [lang] Release Candidiate 8 available

On Wed, 2005-06-01 at 01:55 -0400, Gary Gregory wrote:
> Simon:
>
> You probably need to copy junit.jar to %ANT_HOME%\lib

Yep, that will make things work. But I'm questioning whether it is
reasonable for the lang 2.1 build process to require users to do this.
What is wrong with the old way of running junit?

Alternatively, according to the documentations the junit ant task will
work if the <classpath> tag is used to point to the junit jar. And there
is already a property defined for that, right? So maybe the build.xml
could be modified to provide an explicit taskdef for junit?

Below is an example from the FAQ:
   <taskdef name="junit"
 
class="org.apache.tools.ant.taskdefs.optional.junit.JUnitTask">
      <classpath>
        <pathelement location="${junit.jar}"/>
        <pathelement location="NEW-HOME-OF/ant-junit.jar"/>
      </classpath>
    </taskdef>

Regards,

Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: [lang] Release Candidiate 8 available

Gary Gregory
In reply to this post by Steven Caswell
Hello:

I've added the following to RELEASE-NOTES.txt:

- Starting with version 2.1, Ant version 1.6.x is required to build.
Copy
junit.jar to ANT_HOME/lib. You can get JUnit from http://www.junit.org.

Gary

-----Original Message-----
From: Simon Kitching [mailto:[hidden email]]
Sent: Wednesday, June 01, 2005 6:43 AM
To: Jakarta Commons Developers List
Subject: Re: [lang] Release Candidiate 8 available

On Tue, 2005-05-31 at 22:38 -0400, Steven Caswell wrote:
> Commons-lang 2.1 release candidate 8 is available at
> http://www.apache.org/~stevencaswell/commons-lang-2.1/
>
> Primary change is Gary's working out the oddball build and class
loading
> issue that only seems to happen on Windows XP (SP2) since Simon
reports that
> the ant build works fine for him on Linux.
>
> As with previous RCs, verification against as many JDK versions would
be
> appreciated, and a sanity check of the docs would also be welcome.
>
> Vote to follow if no reports of problems.
>

Ok, apart from the issue that junit.jar had to be copied to ant's lib
directory both build and test appears to go fine on:
  * java 1.2.2 on linux (ant)
  * java 1.3.1 on linux (ant and maven)
  * java 1.5 on linux (ant and maven)


However I think that that information in STATUS.html regarding
dependencies for the project really should be in the RELEASE-NOTES.txt
file. In particular, it should be noted that ant 1.6 is now needed to
build.

And if you do go with using the <junit> tag in the build.xml, then I
think the RELEASE-NOTES.txt file should mention installing junit.jar
into ant's lib dir (or point to the info in the STATUS.html file).

Regards,

Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lang] Release Candidiate 8 available

Steven Caswell
In reply to this post by Gary Gregory
I agree with Gary. I don't have a problem putting the junit.jar into the ant
lib folder. Simon has a good point about documenting the dependency. IMHO
there should be a mention in the release notes with a fuller explanation in
the developer's guide. I'll take a first cut and we can dress it up from
there.

On 6/1/05, Gary Gregory <[hidden email]> wrote:

>
> Hello:
>
> I think it is quite reasonable to use the junit task to invoke junit
> tests, IMO it is the best way since it is both clear and succinct.
>
> Invoking junit tests the old way feels to me like a bit of hack, it just
> happens to work by some side effect. Using the junit task states: This
> is a junit test, run!
>
> Personally, I would not favor the taskdef approach. My view on the
> subject is that one's development environment has to be set up in a
> certain way and JUnit is part of that. We already need Java, Ant and
> Maven. JUnit in Ant is another layer.
>
> We can always change is back of course ;-)
>
> Gary
>
> -----Original Message-----
> From: Simon Kitching [mailto:[hidden email]]
> Sent: Wednesday, June 01, 2005 5:36 AM
> To: Jakarta Commons Developers List
> Subject: RE: [lang] Release Candidiate 8 available
>
> On Wed, 2005-06-01 at 01:55 -0400, Gary Gregory wrote:
> > Simon:
> >
> > You probably need to copy junit.jar to %ANT_HOME%\lib
>
> Yep, that will make things work. But I'm questioning whether it is
> reasonable for the lang 2.1 build process to require users to do this.
> What is wrong with the old way of running junit?
>
> Alternatively, according to the documentations the junit ant task will
> work if the <classpath> tag is used to point to the junit jar. And there
> is already a property defined for that, right? So maybe the build.xml
> could be modified to provide an explicit taskdef for junit?
>
> Below is an example from the FAQ:
> <taskdef name="junit"
>
> class="org.apache.tools.ant.taskdefs.optional.junit.JUnitTask">
> <classpath>
> <pathelement location="${junit.jar}"/>
> <pathelement location="NEW-HOME-OF/ant-junit.jar"/>
> </classpath>
> </taskdef>
>
> Regards,
>
> Simon
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Steven Caswell
[hidden email]

Take back the web - http://www.mozilla.org
Reply | Threaded
Open this post in threaded view
|

RE: [lang] Release Candidiate 8 available

Gary Gregory
In reply to this post by Steven Caswell
Ah, good, feel free to nuke or redo my RELEASE-NOTES.txt changes.

Gary

-----Original Message-----
From: Steven Caswell [mailto:[hidden email]]
Sent: Wednesday, June 01, 2005 1:38 PM
To: Jakarta Commons Developers List
Cc: [hidden email]
Subject: Re: [lang] Release Candidiate 8 available

I agree with Gary. I don't have a problem putting the junit.jar into the
ant
lib folder. Simon has a good point about documenting the dependency.
IMHO
there should be a mention in the release notes with a fuller explanation
in
the developer's guide. I'll take a first cut and we can dress it up from

there.

On 6/1/05, Gary Gregory <[hidden email]> wrote:
>
> Hello:
>
> I think it is quite reasonable to use the junit task to invoke junit
> tests, IMO it is the best way since it is both clear and succinct.
>
> Invoking junit tests the old way feels to me like a bit of hack, it
just

> happens to work by some side effect. Using the junit task states: This
> is a junit test, run!
>
> Personally, I would not favor the taskdef approach. My view on the
> subject is that one's development environment has to be set up in a
> certain way and JUnit is part of that. We already need Java, Ant and
> Maven. JUnit in Ant is another layer.
>
> We can always change is back of course ;-)
>
> Gary
>
> -----Original Message-----
> From: Simon Kitching [mailto:[hidden email]]
> Sent: Wednesday, June 01, 2005 5:36 AM
> To: Jakarta Commons Developers List
> Subject: RE: [lang] Release Candidiate 8 available
>
> On Wed, 2005-06-01 at 01:55 -0400, Gary Gregory wrote:
> > Simon:
> >
> > You probably need to copy junit.jar to %ANT_HOME%\lib
>
> Yep, that will make things work. But I'm questioning whether it is
> reasonable for the lang 2.1 build process to require users to do this.
> What is wrong with the old way of running junit?
>
> Alternatively, according to the documentations the junit ant task will
> work if the <classpath> tag is used to point to the junit jar. And
there

> is already a property defined for that, right? So maybe the build.xml
> could be modified to provide an explicit taskdef for junit?
>
> Below is an example from the FAQ:
> <taskdef name="junit"
>
> class="org.apache.tools.ant.taskdefs.optional.junit.JUnitTask">
> <classpath>
> <pathelement location="${junit.jar}"/>
> <pathelement location="NEW-HOME-OF/ant-junit.jar"/>
> </classpath>
> </taskdef>
>
> Regards,
>
> Simon
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


--
Steven Caswell
[hidden email]

Take back the web - http://www.mozilla.org

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lang] Release Candidiate 8 available

Steven Caswell
In reply to this post by Gary Gregory
It looks like checkstyle.xml is the file that is required and that
checkstyle.properties is no longer used. It is easy enough to copy
checkstyle.xml into the source distribution, but that alone won't enable
maven site:generate to be run on the unzipped source. Various pieces of the
maven setup require commons-build to also be available, so I'm not sure that
it is necessary that the source distribution pass site:generate. I think
passing test:test should be sufficient.

I propose we wait until after the release and then remove
checkstyle.properties. There should be plenty of time from there to verify
it really isn't used.

On 6/1/05, Gary Gregory <[hidden email]> wrote:

>
> Hello All:
>
> I have run the following with success on Window XP SP2 based on
> unzipping
> http://people.apache.org/~stevencaswell/commons-lang-2.1/distributions/c
> ommons-lang-2.1-RC8-src.zip.
>
> Ant 1.6.4 with the command "ant clean dist-build-2.1 test" with:
>
> Sun Java 1.5.0_03
> Sun Java 1.4.2_08
> Sun Java 1.3.1_14
>
> Maven 1.0.2 with the command "maven clean site:generate" (for all Sun
> java versions above) always gives me:
>
> BUILD FAILED
> File...... C:\Documents and
> Settings\ggregory.SSSI\.maven\cache\maven-checkstyle-plugin-2.5\plugin.j
> elly
> Element... ant:checkstyle
> Line...... 144
> Column.... 63
> Unable to create a Checker: unable to find file:checkstyle.xml
> Total time: 5 seconds
> Finished at: Tue May 31 23:06:42 PDT 2005
>
> The checkstyle file(s) are missing from the src dist. Do we still need
> BOTH checkstyle.properties and checkstyle.xml in SVN?
>
> Thanks,
> Gary
>
> -----Original Message-----
> From: Steven Caswell [mailto:[hidden email]]
> Sent: Tuesday, May 31, 2005 7:38 PM
> To: Jakarta Commons Developers List
> Subject: [lang] Release Candidiate 8 available
>
> Commons-lang 2.1 release candidate 8 is available at
> http://www.apache.org/~stevencaswell/commons-lang-2.1/
>
> Primary change is Gary's working out the oddball build and class loading
>
> issue that only seems to happen on Windows XP (SP2) since Simon reports
> that
> the ant build works fine for him on Linux.
>
> As with previous RCs, verification against as many JDK versions would be
>
> appreciated, and a sanity check of the docs would also be welcome.
>
> Vote to follow if no reports of problems.
>
> --
> Steven Caswell
> [hidden email]
>
> Take back the web - http://www.mozilla.org
>



--
Steven Caswell
[hidden email]

Take back the web - http://www.mozilla.org
Reply | Threaded
Open this post in threaded view
|

RE: [lang] Release Candidiate 8 available

Gary Gregory
In reply to this post by Steven Caswell
True, if had not thought of the commons-build dependency. In this case,
passing Ant builds and tests is enough I think.

 

Gary

 

________________________________

From: Steven Caswell [mailto:[hidden email]]
Sent: Wednesday, June 01, 2005 3:01 PM
To: Gary Gregory
Cc: Jakarta Commons Developers List
Subject: Re: [lang] Release Candidiate 8 available

 

It looks like checkstyle.xml is the file that is required and that
checkstyle.properties is no longer used. It is easy enough to copy
checkstyle.xml into the source distribution, but that alone won't enable
maven site:generate to be run on the unzipped source. Various pieces of
the maven setup require commons-build to also be available, so I'm not
sure that it is necessary that the source distribution pass
site:generate. I think passing test:test should be sufficient.

I propose we wait until after the release and then remove
checkstyle.properties. There should be plenty of time from there to
verify it really isn't used.

On 6/1/05, Gary Gregory <[hidden email]> wrote:

Hello All:

I have run the following with success on Window XP SP2 based on
unzipping
http://people.apache.org/~stevencaswell/commons-lang-2.1/distributions/c
ommons-lang-2.1-RC8-src.zip.

Ant 1.6.4 with the command "ant clean dist-build-2.1 test" with:

Sun Java 1.5.0_03
Sun Java 1.4.2_08
Sun Java 1.3.1_14

Maven 1.0.2 with the command "maven clean site:generate" (for all Sun
java versions above) always gives me:

BUILD FAILED
File...... C:\Documents and
Settings\ggregory.SSSI\.maven\cache\maven-checkstyle-plugin-2.5\plugin.j
elly
Element... ant:checkstyle
Line...... 144
Column.... 63
Unable to create a Checker: unable to find file: checkstyle.xml
Total time: 5 seconds
Finished at: Tue May 31 23:06:42 PDT 2005

The checkstyle file(s) are missing from the src dist. Do we still need
BOTH checkstyle.properties and checkstyle.xml in SVN?

Thanks,
Gary

-----Original Message-----
From: Steven Caswell [mailto:[hidden email]]
Sent: Tuesday, May 31, 2005 7:38 PM
To: Jakarta Commons Developers List
Subject: [lang] Release Candidiate 8 available

Commons-lang 2.1 release candidate 8 is available at
http://www.apache.org/~stevencaswell/commons-lang-2.1/ 

Primary change is Gary's working out the oddball build and class loading

issue that only seems to happen on Windows XP (SP2) since Simon reports
that
the ant build works fine for him on Linux.

As with previous RCs, verification against as many JDK versions would be

appreciated, and a sanity check of the docs would also be welcome.

Vote to follow if no reports of problems.

--
Steven Caswell
[hidden email]

Take back the web - http://www.mozilla.org




--
Steven Caswell
[hidden email]

Take back the web - http://www.mozilla.org