ChangeLog file?

[la...@masq.ca]

Hi,

Is it possible to have a ChangeLog file somewhere in the source tree? The
purpose would be for someone like me, who does an update, to see what has
changed most recently in the sources. I'm asking because I just did an
update and I'm having a compilation problem:

BUILD FAILED
/usr/local/soft/cactus/src/default/i686_pc_linux_gnu/jakarta-cactus/framework/build.xml:406: 
taskdef class com.puppycrawl.tools.checkstyle.CheckStyleTask cannot be found

Total time: 23 seconds

So I'm wondering if I now need another tool to build?

L

-- 
Laurent Duperval <ma...@masq.ca>

Je connais un rémède de bonne femme et de cheval qui est d'une efficacité à
casser les vitres dans un rayon de cent mètres!
                                             -Alambic Talon


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: ChangeLog file?

[Vincent Massol <vm...@octo.com>]

Laurent,

> -----Original Message-----
> From: laurent.duperval@masq.ca [mailto:laurent.duperval@masq.ca]
> Sent: 15 April 2002 15:33
> To: Cactus Mailing List
> Subject: ChangeLog file?
> 
> Hi,
> 
> Is it possible to have a ChangeLog file somewhere in the source tree?
The
> purpose would be for someone like me, who does an update, to see what
has
> changed most recently in the sources. I'm asking because I just did an
> update and I'm having a compilation problem:

Solution 1 : Have a look at the changes in changes.xml (in
documentation/docs/xdocs/changes.xml). It contains the Cactus changes
(coarse greained level).

Solution 2 : If you're really interested in CVS changes, then simply go
to Cactus top level and type (for example) :

cvs log -d >= 2002-04-14 10:00

That would tell you all the changes that happened after the 14th of
april 2002 10:00 AM.

> 
> BUILD FAILED
> /usr/local/soft/cactus/src/default/i686_pc_linux_gnu/jakarta-
> cactus/framework/build.xml:406:
> taskdef class com.puppycrawl.tools.checkstyle.CheckStyleTask cannot be
> found
> 

This is because I have added the "checkstyle" target as part of the
"dist" target yesterday in framework/build.xml. I will make the
necessary changes now so that this is not run if you do not have the
checkstyle jar in your ANT_HOME/lib directory. FYI, checkstyle is used
to verify conformance of code to our coding and naming standards and
must be run by committers before they commit code to CVS.

Secondly, I'll soon added a new prepackaged version of Ant in the Cactus
download area that will contain the needed checkstyle jars. The other
option is to auto-download the needed jars in the Ant build file is
newer versions are found. I'll need to think about that ... I know it is
being done on some Jakarta projects.

> Total time: 23 seconds
> 
> So I'm wondering if I now need another tool to build?
> 
> L
> 

Merci et desole :-)
-Vincent

> --
> Laurent Duperval <ma...@masq.ca>
> 
> Je connais un rémède de bonne femme et de cheval qui est d'une
efficacité
> à
> casser les vitres dans un rayon de cent mètres!
>                                              -Alambic Talon
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:cactus-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:cactus-user-
> help@jakarta.apache.org>
> 




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>