Re: [5.0] Build notes
Sort of a mini-gump.
No sense in over-doing what the build file is supposed to do. The idea
is cool, but, gump exists for a reason :) I suspect a change like this
would make things slightly more complex, confusing, and in general take
way to much time to implement - not to mention open up the possibility
for abuse.
But that is just my opinion. Anyhow, the one-step build-from-scratch
still rocks. Any idea when nightly Tomcat 5 builds will start appearing
on Jakarta?
Cheers,
Jayson
Bob Herrmann wrote:
On Sun, 2002-08-11 at 11:25, Jayson Falkner wrote:
I have been using the same thing. The only downside is the download
time, but, IMO it would be great to have this included and encouraged
for use with the Tomcat 5 build file.
Way to go Bob!
Thanks, although I just cut/pasted Ian Darwin's example.
It builds tomcat5 pretty well, but I would really like it if it also did
these things,
- building dist, start tomcat up
- download and run watchdog and generate a report
- If the report fails, then send an email to people who committed in
past 24 hours
- run automatically every 24 hours.
Sort of a mini-gump.
Cheers,
-bob
Jayson Falkner
[EMAIL PROTECTED]
Bob Herrmann wrote:
Yea, I liked your script, this one builds Tomcat 5.
BUILDING.TXT could almost just say All you need is JDK1.4 and Ant1.5
then just type 'ant' and a working Tomcat 5 development tree is built.
(If you are behind a firewall, you may need to adjust proxy settings.)
This should be cross platform (haven't tested it on Win32.)
Cheers,
-bob
project name=CVS Retrieval default=populate
property file=build.properties/
property name=apache.dir value=${user.home}/TC5/
property name=base.path value=${apache.dir}/download/
property name=cvsroot
value=:pserver:[EMAIL PROTECTED]:/home/cvspublic/
target name=populate depends=init,checkout,buildit /
target name=init
tstamp/
mkdir dir=${apache.dir}/
mkdir dir=${base.path}/
/target
target name=checkout depends=init
cvs package=jakarta-servletapi-5
cvsRoot=${cvsroot}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-catalina
cvsRoot=${cvsroot}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-5
cvsRoot=${cvsroot}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-connectors
cvsRoot=${cvsroot}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-jasper
cvsRoot=${cvsroot}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-5
cvsRoot=${cvsroot}
dest=${apache.dir}
/
/target
target name=buildit depends=init
echo message=Commons-logging build dies without this
file=${base.path}/LICENSE /
ant dir=${apache.dir}/jakarta-tomcat-5
target=download /
ant dir=${apache.dir}/jakarta-tomcat-5
target=dist /
/target
/project
On Tue, 2002-08-06 at 13:43, Ian Darwin wrote:
On August 6, 2002 01:01 pm, you wrote:
The main thing missing is a target which sets up the CVS repositories,
so it's quite close to what we have now. Problem is, I'm not too happy
at the idea of doing that automatically.
Trivial to do with Ant, but I agree, it's risky to automate this. OTOH if
it's well documented what it's doing, people should be OK with it.
Ian
project name=CVS Retrieval default=populate
!-- $Id: build.xml,v 1.1 2002/06/11 15:35:57 ian Exp $ --
!-- Maybe find a better way of setting this --
property name=apache.dir value=${user.home}/src/apache/
property name=cvs.root
value=:pserver:[EMAIL PROTECTED]:/home/cvspublic/
target name=init
tstamp/
mkdir dir=${apache.dir}/
/target
target name=populate depends=init
cvs package=jakarta-tomcat-4.0
cvsRoot=${cvs.root}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-connectors
cvsRoot=${cvs.root}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-jasper
cvsRoot=${cvs.root}
dest=${apache.dir}
/
/target
/project
--
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]
--
To unsubscribe
Re: [5.0] Build notes
I have been using the same thing. The only downside is the download
time, but, IMO it would be great to have this included and encouraged
for use with the Tomcat 5 build file.
Way to go Bob!
Jayson Falkner
[EMAIL PROTECTED]
Bob Herrmann wrote:
Yea, I liked your script, this one builds Tomcat 5.
BUILDING.TXT could almost just say All you need is JDK1.4 and Ant1.5
then just type 'ant' and a working Tomcat 5 development tree is built.
(If you are behind a firewall, you may need to adjust proxy settings.)
This should be cross platform (haven't tested it on Win32.)
Cheers,
-bob
project name=CVS Retrieval default=populate
property file=build.properties/
property name=apache.dir value=${user.home}/TC5/
property name=base.path value=${apache.dir}/download/
property name=cvsroot
value=:pserver:[EMAIL PROTECTED]:/home/cvspublic/
target name=populate depends=init,checkout,buildit /
target name=init
tstamp/
mkdir dir=${apache.dir}/
mkdir dir=${base.path}/
/target
target name=checkout depends=init
cvs package=jakarta-servletapi-5
cvsRoot=${cvsroot}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-catalina
cvsRoot=${cvsroot}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-5
cvsRoot=${cvsroot}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-connectors
cvsRoot=${cvsroot}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-jasper
cvsRoot=${cvsroot}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-5
cvsRoot=${cvsroot}
dest=${apache.dir}
/
/target
target name=buildit depends=init
echo message=Commons-logging build dies without this
file=${base.path}/LICENSE /
ant dir=${apache.dir}/jakarta-tomcat-5
target=download /
ant dir=${apache.dir}/jakarta-tomcat-5
target=dist /
/target
/project
On Tue, 2002-08-06 at 13:43, Ian Darwin wrote:
On August 6, 2002 01:01 pm, you wrote:
The main thing missing is a target which sets up the CVS repositories,
so it's quite close to what we have now. Problem is, I'm not too happy
at the idea of doing that automatically.
Trivial to do with Ant, but I agree, it's risky to automate this. OTOH if
it's well documented what it's doing, people should be OK with it.
Ian
project name=CVS Retrieval default=populate
!-- $Id: build.xml,v 1.1 2002/06/11 15:35:57 ian Exp $ --
!-- Maybe find a better way of setting this --
property name=apache.dir value=${user.home}/src/apache/
property name=cvs.root
value=:pserver:[EMAIL PROTECTED]:/home/cvspublic/
target name=init
tstamp/
mkdir dir=${apache.dir}/
/target
target name=populate depends=init
cvs package=jakarta-tomcat-4.0
cvsRoot=${cvs.root}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-connectors
cvsRoot=${cvs.root}
dest=${apache.dir}
/
cvs package=jakarta-tomcat-jasper
cvsRoot=${cvs.root}
dest=${apache.dir}
/
/target
/project
--
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]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Does the beta Tomcat 4 support multiple TLD files in a jar?
I assume it does. If so what is the correct way to use this functionality? I have been having little luck trying and can't find the answer documented. Here is a little insight on what I was attempting. The JAR has all of the class files in their correct directories along with a TLD in the META-INF directory named exampleTags.tld. exampleTags.tld has the uri element set with the value /exampleTags.tld. ... taglib ... uri/exampleTags.tld/uri /taglib I am trying the following with a JSP. --- %@ taglib prefix=e uri=/exampleTags.tld % Here is the example tag output: e:example / --- But a servlet exception error message keeps popping up. org.apache.jasper.JasperException: File /exampleTags.tld not found ... Anyone had this before? Advice would be appreciated. Jayson Falkner V.P./CTO, Amberjack Software LLC [EMAIL PROTECTED] www.jspinsider.com
Re: Does the beta Tomcat 4 support multiple TLD files in a jar?
Well, first it shouldn't be just plain uri: taglib taglib-uri/myPRlibrary/taglib-uri taglib-location/WEB-INF/tlds/PRlibrary_1_4.tld/taglib-uri /taglib Are you referring to an entry in the web.xml file? I was asking about having multiple Tag Library Descriptors in a JAR. According the the JSP 1.2 pfd anything in the META-INF directory with the .tld extension should get mapped accordingly by the uri attribute. I was snagging the uri element from the JSP 1.2 TLD DTD in the specs. The idea was to deploy the entire set of tags through a JAR, not by editing web.xml at all. As I understood this is possible. With JSP 1.1 you can do the same but may only have one TLD file in the JAR. Were you addressing this? Jayson Falkner V.P./CTO, Amberjack Software LLC [EMAIL PROTECTED] www.jspinsider.com
