Hi Jose,
Jose Alberto Fernandez wrote:
In my opinion, we should add code (if possible) to check for the version of Jasper and if it is further than X warn that the task is deprecated and you should move to the new jasper provided task.
If there are any problems, users had been warned.
Sounds good. +1
I would apply such strategy across the board as we shed 3rd party tasks to the providers of the 3er party functionality.
What do people think?
Jose Alberto
-----Original Message-----
From: Steve Loughran [mailto:[EMAIL PROTECTED] Sent: 14 June 2004 12:42
To: Ant Developers List
Subject: Re: DO NOT REPLY [Bug 29514] -
[EMAIL PROTECTED] wrote:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=29514>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29514
Jasper Compiler Task: unregognized option -v0
This is going to recur. we really need a strategy.
1. patch everything to not bother with the -v0 option.
2. catch the fault, and when it occurs, tell people to move to the tomcat <jspc> implementation
3. add a new handler for tomcat5, with whatever logic goes in there.
(2) and (3) may not be incompatible;
-steve
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
