[ 
https://issues.apache.org/jira/browse/VELOCITY-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715482#action_12715482
 ] 

Aruna Venkataraman commented on VELOCITY-724:
---------------------------------------------

As per your suggestion i posted this issue of Velocity build faling on ant 
command to [email protected] and our velocity users maling list.

There are two solutions:
1. Copy junit.jar into ANT_HOME/lib directory
(or)
2. Upgrade to the latest version of ant which includes junit.jar in it

I just copied junit.jar into ANT_HOME/lib directory and the build is successful 
now.

Suggestion: Can we change the required column from No to yes for junit.jar in 
jar dependencies.xml file as it is misleading from user perspective. Even build 
fails without junit.jar for velocity-1.6.2.

Regards,
Aruna


> Is junit-3.8.1.jar optional for Velocity as specified in jar dependencies?
> --------------------------------------------------------------------------
>
>                 Key: VELOCITY-724
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-724
>             Project: Velocity
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: 1.6.2
>            Reporter: Aruna Venkataraman
>            Priority: Trivial
>         Attachments: jnuit build failed.jpg
>
>
> When i navigate to the build directory in Velocity 1.6.2 and invoke "ant" 
> then the below error is got:
> Could not create task or type of type: junit. lib\test. 
> Ant could not find the task or a class this task relies upon.
> Refer screenshot
> I deleted the junit-3.8.1.jar file from bin\test-lib as it was specified to 
> be optional, but it gets created automatically. 
> Do we need to remove the dependency on this junit-3.8.1.jar manually? 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Reply via email to