Re: [5.0] Build notes

2002-08-12 Thread Jayson Falkner

 > 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
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>>>   value=":pserver:[EMAIL PROTECTED]:/home/cvspublic"/>
>>>
>>>
>>>
>>>
>>>
>>> 
>>> 
>>>
>>>
>>>
>>>
>>>>>cvsRoot="${cvsroot}"
>>>dest="${apache.dir}"
>>>/>
>>>>>cvsRoot="${cvsroot}"
>>>dest="${apache.dir}"
>>>/>
>>>>>cvsRoot="${cvsroot}"
>>>dest="${apache.dir}"
>>>/>
>>>>>cvsRoot="${cvsroot}"
>>>dest="${apache.dir}"
>>>/>
>>>>>cvsRoot="${cvsroot}"
>>>dest="${apache.dir}"
>>>/>
>>>>>cvsRoot="${cvsroot}"
>>>dest="${apache.dir}"
>>>/>
>>>
>>>
>>>
>>>
>>>
>>>>> file="${base.path}/LICENSE" />
>>>
>>>>> target="download" />
>>>
>>>>> target="dist" />
>>>
>>>
>>>
>>> 
>>>
>>>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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>>>value=":pserver:[EMAIL PROTECTED]:/home/cvspublic"/>
>>>>
>>>>
>>>>
>>>> 
>>>>
>>>>
>>>>
>>>>
>>>>>>>cvsRoot="${cvs.root}"
>>>>dest="${apache.dir}"
>>>>/>
>>>>>>>cvsRoot="${cvs.root}"
>>>>dest="${apache.dir}"
>>>>/>
>>>>>>>cvsRoot="${cvs.root}"
>>>>dest="${apache.dir}"
>>>>/>
>>>>
>>>>
>>>>
>>>>--
>>>>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]>
> 



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




Re: [5.0] Build notes

2002-08-11 Thread Jayson Falkner

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
> 
> 
> 
> 
> 
> 
> 
> 
> value=":pserver:[EMAIL PROTECTED]:/home/cvspublic"/>
> 
> 
> 
> 
> 
>  
>  
> 
> 
> 
> 
>  cvsRoot="${cvsroot}"
> dest="${apache.dir}"
> />
>  cvsRoot="${cvsroot}"
> dest="${apache.dir}"
> />
>  cvsRoot="${cvsroot}"
> dest="${apache.dir}"
> />
>  cvsRoot="${cvsroot}"
> dest="${apache.dir}"
> />
>  cvsRoot="${cvsroot}"
> dest="${apache.dir}"
> />
>  cvsRoot="${cvsroot}"
> dest="${apache.dir}"
> />
> 
> 
> 
> 
> 
>   file="${base.path}/LICENSE" />
> 
>   target="download" />
> 
>   target="dist" />
> 
> 
> 
>   
> 
> 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
>>
>>
>>
>>  
>>
>>  
>>  
>>  >  value=":pserver:[EMAIL PROTECTED]:/home/cvspublic"/>
>>
>>  
>>  
>>   
>>  
>>
>>  
>>
>>  >  cvsRoot="${cvs.root}"
>>  dest="${apache.dir}"
>>  />
>>  >  cvsRoot="${cvs.root}"
>>  dest="${apache.dir}"
>>  />
>>  >  cvsRoot="${cvs.root}"
>>  dest="${apache.dir}"
>>  />
>>  
>>
>>
>>--
>>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]>




Re: [5.0] Building, running, examples, API repository reorg

2002-07-26 Thread Jayson Falkner

Bad question to ask, but by build and runs do you mean what can be 
checked out via anoncvs? It appeared like no code can be checked out 
that way.

FYI, I don't mean to be a pest - I'd just like to help a bit on Tomcat 5.

Cheers,

Jayson

Remy Maucherat wrote:
> Tomcat 5 now builds (and runs), although the build process is not 
> documented yet (and obviously is also lacking some testing).
> 
> There are a few changes which should be made in the near future (in 
> addition to the implementation of the new specs):
> 
> - as has been voted, we need to split the servlet and JSP APIs in the 
> jakarta-servletapi-5 repository (and possibly rename it to jakarta-api, 
> as has been suggested)
> 
> - I'd like the examples webapp to be part of the respective API 
> repository, as it has nothing to do in the Tomcat repository
> 
> - Use commons-launcher; I will do that ASAP, which may not be soon
> 
> - Continue to improve the build system
> 
> Remy
> 
> 
> -- 
> To unsubscribe, e-mail:   
> 
> For additional commands, e-mail: 
> 
> 
> 
> 



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




Re: Does the beta Tomcat 4 support multiple TLD files in a jar?

2001-05-19 Thread Jayson Falkner

> Well, first it shouldn't be just plain "uri":
>
> 
> /myPRlibrary
> /WEB-INF/tlds/PRlibrary_1_4.tld
> 

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






Does the beta Tomcat 4 support multiple TLD files in a jar?

2001-05-19 Thread Jayson Falkner

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".

...

  ...
  /exampleTags.tld


I am trying the following with a JSP.
---
<%@ taglib prefix="e" uri="/exampleTags.tld" %>
Here is the example tag output: 
---
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