You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Paul Hammant <Pa...@yahoo.com> on 2002/04/08 22:15:58 UTC

Re: cvs commit: jakarta-avalon-excalibur depchecker.xml

Jeff,

Here is a patch that makes the output as follows :

.----------------------------------------------------------------.
| CLASS NOT FOUND                                                |
|                                                                |
| Can't find class: junit.framework.Test
|----------------------------------------------------------------|
| Error when building module:                                    |
| C:\Apache-CVS-UPD\jakarta-avalon-excalibur\all
|                                                                |
| A jar containing class:                                        |
|   junit.framework.Test
| must be in your classpath or Ant lib directory                 |
|   C:\Java\ant-1.4.1\bin\\../lib
| Typically it is in a jar called:                               |
|   junit.jar
| Suggested Remedy:                                              |
|   In all/ copy ant.properties.sample to ant.properties & edit it

'----------------------------------------------------------------'

Thoughts ?

- Paul

>hammant     02/04/08 11:46:53
>
>  Modified:    all      build.xml
>               .        depchecker.xml
>  Log:
>  Remedy added to depchecker for thoughts.
>  
>  Revision  Changes    Path
>  1.132     +1 -0      jakarta-avalon-excalibur/all/build.xml
>  
>  Index: build.xml
>  ===================================================================
>  RCS file: /home/cvs/jakarta-avalon-excalibur/all/build.xml,v
>  retrieving revision 1.131
>  retrieving revision 1.132
>  diff -u -r1.131 -r1.132
>  --- build.xml	8 Apr 2002 12:15:40 -0000	1.131
>  +++ build.xml	8 Apr 2002 18:46:53 -0000	1.132
>  @@ -167,6 +167,7 @@
>         <property name="name" value="junit.jar"/>
>         <property name="class" value="junit.framework.Test"/>
>         <property name="classpath" value="${cp}"/>
>  +      <property name="remedy" value="In all/ copy ant.properties.sample to ant.properties &amp; edit it"/>
>     </ant>
>       <ant antfile="${depchecker.prefix}/depchecker.xml" target="checkRequiredFile">
>         <property name="name" value="excalibur-collections.jar"/>
>  
>  
>  
>  1.6       +2 -0      jakarta-avalon-excalibur/depchecker.xml
>  
>  Index: depchecker.xml
>  ===================================================================
>  RCS file: /home/cvs/jakarta-avalon-excalibur/depchecker.xml,v
>  retrieving revision 1.5
>  retrieving revision 1.6
>  diff -u -r1.5 -r1.6
>  --- depchecker.xml	8 Apr 2002 12:02:12 -0000	1.5
>  +++ depchecker.xml	8 Apr 2002 18:46:53 -0000	1.6
>  @@ -357,6 +357,8 @@
>               |   ${ant.home}/lib
>               | Typically it is in a jar called:                               |
>               |   ${name}                                                      
>  +            | Suggested Remedy:                                              |
>  +            |   ${remedy}                                                                  
>               '----------------------------------------------------------------'
>           </echo>
>           <fail message="Failed requirement: class not found"/>
>  
>  
>  
>
>--
>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>




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


Re: cvs commit: jakarta-avalon-excalibur depchecker.xml

Posted by Jeff Turner <je...@socialchange.net.au>.
On Mon, Apr 08, 2002 at 09:15:58PM +0100, Paul Hammant wrote:
> Jeff,
> 
> Here is a patch that makes the output as follows :
... 
> | Suggested Remedy:                                              |
> |   In all/ copy ant.properties.sample to ant.properties & edit it


Good stuff. I added the ${message} param with the vague intention of meeting
this need, but this is better. Only thing is that the <junit> task must have
junit.jar in ${ant.home}/lib, and it won't help to define it in ant.properties.
I've changed it so it prints this:

    .----------------------------------------------------------------.
    | CLASS NOT FOUND                                                |
    |                                                                |
    | Can't find class: junit.framework.Test
    |----------------------------------------------------------------|
    | Error when building module:                                    |
    | /home/jeff/apache/jakarta/jakarta-avalon-excalibur/all 
    |                                                                |
    | A jar containing class:                                        |
    |   junit.framework.Test
    | must be in your classpath or Ant lib directory                 |
    |   /home/jeff/jakarta-ant-1.4.1/lib
    | Typically it is in a jar called:                               |
    |   junit.jar                                                      
    | Suggested Remedy:                                              |
    |   Download JUnit from http://www.junit.org and copy junit.jar 
    |   to /home/jeff/jakarta-ant-1.4.1/lib                                                                  
    '----------------------------------------------------------------'

Seem okay?

--Jeff


> Thoughts ?
> 
> - Paul

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