ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wannamaker" <Ke...@Wannamaker.org>
Subject RE: Tomcat precompile task
Date Tue, 14 May 2002 19:42:38 GMT
That might be a better approach.  If JspC supported
a filename mapper, then it would be able to decide to
compile the files individually (only way JspC supports
output classname) rather than a batch.

The other task of writing a simple .ver file would be
trivial.

Keith

| -----Original Message-----
| From: Steve Loughran [mailto:steve_l@iseran.com]
| Sent: Tuesday, May 14, 2002 1:22 PM
| To: Ant Developers List
| Subject: Re: Tomcat precompile task
| 
| 
| 
| ----- Original Message -----
| From: "Keith Wannamaker" <Keith@Wannamaker.org>
| To: <ant-dev@jakarta.apache.org>
| Sent: Tuesday, May 14, 2002 8:13 AM
| Subject: Tomcat precompile task
| 
| 
| > Hi, I'm thinking of extending the JspC task to a new
| > Tomcat 3.3 precompile task.  The task would prepare
| > a JSP in a manner suitable for use by Tomcat 3.3 --
| > that is, appending _1 to the class, and writing a
| > .ver file.  The current JspC task is problematic
| > because it passes all the files at once to JspC,
| > therefore the output classes can't be renamed.
| 
| there is support for plugin filename mappers; each compiler implementation
| can provide something that maps from java source to the output filename.
| Sounds like this isnt enough, correct?
| 
| 
| 
| --
| To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
| For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
| 
| 

--
To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>


Mime
View raw message