on 12/15/2000 12:00 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]>
wrote:
> Let me describe what I just had to do, to get a feel for why I like the
> current approach.
>
> Recently, there were security issues with Tomcat 3.1 that required creating a
> 3.1.1 release. Now, Tomcat 3.1 was dependent
on 12/15/2000 10:50 AM, "Sam Ruby" <[EMAIL PROTECTED]> wrote:
>>
>> That makes building scripts dependent on these packages
>> much more painful than it needs to be -- it's not enough
>> to know what directory you've got these packages in, you
>> have to specify the version number as well.
>
>
I agree with Stuart!
Let me also state that 99% of the OSS C projects built with "configure" out
there build into their own directory by default. However, most have the
option to build to another directory. That is something I'm willing to
support.
-jon
on 12/15/2000 7:45 AM, "Stuart Roebuck" <
on 12/15/2000 3:56 AM, "Sam Ruby" <[EMAIL PROTECTED]> wrote:
> In the case of jakarta-regexp, can this be done instead of putting the
> version number on the name of the jar file itself?
>
> - Sam Ruby
There is nothing wrong with putting the version number on the .jar file and
it help WAY to ma
> > While jakarta-servletapi-4.0 and TC4.0 builds are being
> > re-developed, could we please *stop* them creating
> > directories higher in the hierarchy thantheir own root?
> > ie
> >
> > /jakarta-tomcat/ shouldn't then create ../build/ - it's
> > not nice!
>
> An alternate perspective - I like
e-
> From: Jon S. Stevens [mailto:[EMAIL PROTECTED]]
> Sent: 14 December 2000 9:13 pm
> To: [EMAIL PROTECTED]
> Subject: Re: [PROPOSAL] building is easy (was: Re:
> [tomcat-4.0] building
> is hard)
>
>
> >
> > Jon Stevens wrote:
> > >
> > &
I've switched from TC 4.0-m4 to TC 4.0-m5 in minutes using my RPMs build
process. I've only adapted my spec file (the file which tell how to build the
binary package from sources, patches...)
Since I allready many of the RPM needed by tomcat (from jakarta.apache.org and
xml.apache.org), I have
>
> Jon Stevens wrote:
> >
> > If the above files do not exist, then attempt to look
> > for relative paths (ie: ../../jakarta-servletapi) to
> > the .jar files here:
> >
> > /jakarta-servletapi
> > /jsse*
> > /jmx*
>
> It is not clear to me why property files with reasonable defaults are
> "eas
Jon Stevens wrote:
>
> If the above files do not exist, then attempt to look
> for relative paths (ie: ../../jakarta-servletapi) to
> the .jar files here:
>
> /jakarta-servletapi
> /jsse*
> /jmx*
It is not clear to me why property files with reasonable defaults are
"easy" whereas environment vari
Punky Tse wrote:
> Hi,
> Craig and Pier: Let's fix it! We have a beautiful build tool (Ant) ,
> why can't we have a good build system?
>
Agreed.
One of the reasons Tomcat 4 is complex is actually Jon's fault :-). He wanted a
way to build just the servlet container portion (Catalina), whi
Stuart Roebuck typed the following on 16:41 14/12/2000 +
>On Thursday, December 14, 2000, at 09:44 AM, Pier P. Fumagalli wrote:
>> Someone (me! :) proposed to do as they do in XML land with the Xerces
>> project. They distribute a simple "xerces-tools..." JAR containing all
>> libraries requ
On Thursday, December 14, 2000, at 09:44 AM, Pier P. Fumagalli wrote:
> Stuart Roebuck <[EMAIL PROTECTED]> wrote:
>
> > My preference would be to simply include the distributable jar files of
> > required libraries in a lib/ or similar directory inside the tomcat directory.
> > Those librar
TECTED]>
Sent: Thursday, December 14, 2000 5:44 PM
Subject: Re: [tomcat-4.0] building is hard
> Stuart Roebuck <[EMAIL PROTECTED]> wrote:
>
> > Jon,
> >
> > I *absolutely* agree with the need to make the Tomcat build environment
easier
> > to setup.
Stuart Roebuck <[EMAIL PROTECTED]> wrote:
> Jon,
>
> I *absolutely* agree with the need to make the Tomcat build environment easier
> to setup. The current situation is a *serious* barrier to encouraging wider
> participation. There's no rocket science required at present, but few of us
> have
Jon,
I *absolutely* agree with the need to make the Tomcat build environment easier to
setup. The current situation is a *serious* barrier to encouraging wider
participation. There's no rocket science required at present, but few of us have time
to mess about and I for one gave up at least t
on 12/13/2000 9:11 PM, "Craig R. McClanahan" <[EMAIL PROTECTED]>
wrote:
> One issue to keep in mind when you look at the build scripts is that there are
> two goals that sometimes compete:
> * Build Tomcat itself (i.e. make the right JARs
> available to the right javac tasks)
> * Build a binary d
Jon Stevens wrote:
> i would just like to point out that setting up an environment to build the
> java portion of tomcat-4.0 from CVS is WAY to hard. you have to know way to
> much about where things should go and such.
>
> for example, the documentation states that you should point to your JSSE
i would just like to point out that setting up an environment to build the
java portion of tomcat-4.0 from CVS is WAY to hard. you have to know way to
much about where things should go and such.
for example, the documentation states that you should point to your JSSE
installation directory. given
18 matches
Mail list logo
