RE: ant tools for 3.3 and dtomcat3/rc script

[Keith Wannamaker]

You've got it.  I thought you were talking post-install, but,
again, if Ant's available you can use the task whenever you 
wanted to.

Keith

| -Original Message-
| From: Jason Corley [mailto:[EMAIL PROTECTED]]
| Sent: Friday, May 17, 2002 9:50 AM
| To: Tomcat Developers List
| Subject: RE: ant tools for 3.3 and dtomcat3/rc script
| 
| 
| 
| Hmm, perhaps I'm a little confused (not that difficult to believe :-) 
| but I thought jspc didn't create files with the proper naming scheme 
| for tomcat.  I thought the ant task was a wrapper around jspc that 
| solves that problem (along with the other ant task you posted that 
| creates the appropriate .class/.ver files).
| Jason
| 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: ant tools for 3.3 and dtomcat3/rc script

[Keith Wannamaker]

I agree that's why I wrote the task :-)  
Maybe I misuderstood Jason,.. thought he wanted to use
the ant tool post-installation-- tomcat recompile would
be a better option in that case, IMO.  But, of course, 
the ant tool can be used, if ant is available.

Keith

| -Original Message-
| From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
| Sent: Friday, May 17, 2002 9:47 AM
| To: Tomcat Developers List
| Subject: RE: ant tools for 3.3 and dtomcat3/rc script
| 
| 
| >No, for a Tomcat which has already been installed,
| >you should use the JspC tomcat option to precompile
| >JSPs.
| >
| >What I did is to create an Ant task with the same 
| >functionality as the already-present JspC option,
| >for use in build environments.
| 
| From my experience in production deployement having
| jspc in ant is much better than just using tomcat recompile.
| 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: ant tools for 3.3 and dtomcat3/rc script

[Jason Corley]

Hmm, perhaps I'm a little confused (not that difficult to believe :-) but I thought 
jspc didn't create files with the proper naming scheme for tomcat.  I thought the ant 
task was a wrapper around jspc that solves that problem (along with the other ant task 
you posted that creates the appropriate .class/.ver files).
Jason

-Original Message-
From: Keith Wannamaker [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 17, 2002 11:36 AM
To: Tomcat Developers List
Subject: RE: ant tools for 3.3 and dtomcat3/rc script


No, for a Tomcat which has already been installed,
you should use the JspC tomcat option to precompile
JSPs.

What I did is to create an Ant task with the same 
functionality as the already-present JspC option,
for use in build environments.

Keith

| -Original Message-
| From: Jason Corley [mailto:[EMAIL PROTECTED]]
| Sent: Friday, May 17, 2002 9:26 AM
| To: [EMAIL PROTECTED]
| Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
| Subject: ant tools for 3.3 and dtomcat3/rc script
| 
| 
| 
| Would it be possible to take Keith's tomcat3 JSP precompiler and add 
| it as an option to dtomcat3 (and rc script for the RPM)?  What I'm 
| thinking of is being able to run:
|   /etc/rc.d/init.d/tomcat3 precompile
|   /etc/rc.d/init.d/tomcat3 start
| Henri you've probably already thought about this for the 3.3.2 
| release RPM; were you planning on trying to implement?
| 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

RE: ant tools for 3.3 and dtomcat3/rc script

[GOMEZ Henri]

>No, for a Tomcat which has already been installed,
>you should use the JspC tomcat option to precompile
>JSPs.
>
>What I did is to create an Ant task with the same 
>functionality as the already-present JspC option,
>for use in build environments.

>From my experience in production deployement having
jspc in ant is much better than just using tomcat recompile.

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: ant tools for 3.3 and dtomcat3/rc script

[Keith Wannamaker]

No, for a Tomcat which has already been installed,
you should use the JspC tomcat option to precompile
JSPs.

What I did is to create an Ant task with the same 
functionality as the already-present JspC option,
for use in build environments.

Keith

| -Original Message-
| From: Jason Corley [mailto:[EMAIL PROTECTED]]
| Sent: Friday, May 17, 2002 9:26 AM
| To: [EMAIL PROTECTED]
| Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
| Subject: ant tools for 3.3 and dtomcat3/rc script
| 
| 
| 
| Would it be possible to take Keith's tomcat3 JSP precompiler and add 
| it as an option to dtomcat3 (and rc script for the RPM)?  What I'm 
| thinking of is being able to run:
|   /etc/rc.d/init.d/tomcat3 precompile
|   /etc/rc.d/init.d/tomcat3 start
| Henri you've probably already thought about this for the 3.3.2 
| release RPM; were you planning on trying to implement?
| 

--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

RE: ant tools for 3.3

[Keith Wannamaker]

Ok, I added it to the build, but not the distribution
(no good place for it?).  Also, I didn't put ant.props
in META-INF because it could not be found by the app 
there.  It's just in the top level of the jar.  I know
I'm missing something here.. 

Also, I went ahead and put the adapter in j-t for now,
rather than j-t-j.  It can always be moved later, especially
since I know nothing about the mangler j-t-j.  Yes, optimally,
mangling support would be more flexible and it should go over
there, but it's ok for now in j-t.

Keith


| -Original Message-
| From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
| Sent: Wednesday, May 15, 2002 7:06 PM
| To: Tomcat Developers List
| Subject: Re: ant tools for 3.3
| 
| 
| On Wed, 15 May 2002, Keith Wannamaker wrote:
| 
| > I've written some ant tools that allow builds to populate 
| > the Tomcat work directories with precompiled JSPs.  I'm
| > trying to decide a home for them, if any, and was thinking
| > of a new package org.apache.tomcat.ant .. any other
| > preference?
| 
| +1
| 
| Just make sure the build.xml is able to exclude the tasks from
| the 'main' jars and create separate jars for the new tasks.
| 
| Also - please include META-INF/ant.properties ( for multiple
| taskdefs with resource= )
| 
| Costin
| 

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Re: ant tools for 3.3

[costinm]

On Wed, 15 May 2002, Keith Wannamaker wrote:

> I've written some ant tools that allow builds to populate 
> the Tomcat work directories with precompiled JSPs.  I'm
> trying to decide a home for them, if any, and was thinking
> of a new package org.apache.tomcat.ant .. any other
> preference?

BTW, for jasper tasks: it may be a good idea to include them
in jakarta-tomcat-jasper. 

Maybe we'll generalize them and make it work with the new
jasper. I haven't looked at the new mangler, but porting
the 3.3 mangler or supporting multiple styles in the tasks
would be usefull.

( I think it's reasonably easy to use the new jasper with 3.3,
modulo few minor changes - and porting the tag pooling if 
it hasn't been done yet )

Costin


--
To unsubscribe, e-mail:   
For additional commands, e-mail: 

Re: ant tools for 3.3

[costinm]

On Wed, 15 May 2002, Keith Wannamaker wrote:

> I've written some ant tools that allow builds to populate 
> the Tomcat work directories with precompiled JSPs.  I'm
> trying to decide a home for them, if any, and was thinking
> of a new package org.apache.tomcat.ant .. any other
> preference?

+1

Just make sure the build.xml is able to exclude the tasks from
the 'main' jars and create separate jars for the new tasks.

Also - please include META-INF/ant.properties ( for multiple
taskdefs with resource= )

Costin


--
To unsubscribe, e-mail:   
For additional commands, e-mail: