: Re: [tomcat-4.0] building
i s hard)
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
suppor
Craig,
Thanks for this. If my analysis is correct I think our preferences are very similar,
but we started with different viewpoints:
1. I saw Tomcat as a stand-alone project dependent on other stand-alone projects : you
saw Tomcat as part of one interdependent Jakarta project.
2. I saw the
> There's still the "religious" war over "build inside my source directory"
> versus "build someplace else". I am of the latter camp -- partly
> because that's the way Tomcat has built ever since it was first released
to Apache,
> and partly because I've grown to like it -- but if everyone wants
WARNING: Comments below relate to the build process the way it currently is. After
Jon gets done, it will undoubtedly look quite different.
Stuart Roebuck wrote:
> On Friday, December 15, 2000, at 05:51 PM, Craig R. McClanahan wrote:
>
> > If you follow the recommended approach (create a "Jak
Sam Ruby wrote:
>
> Additionally, I would be in favor of standardizing - even if it is only
> across jakarta projects - a mechanism for embedding the version number in a
> standard location inside the jar file itself.
>
I have a suggestion for how to approach this one.
The JDK 1.3 docs describe
On Friday, December 15, 2000, at 05:51 PM, Craig R. McClanahan wrote:
> If you follow the recommended approach (create a "Jakarta" directory in your home
> directory or wherever, and install all the project source distros inside it), this
>is a
> given.
Apologies, I didn't realise I had to
[ disclaimer: I am a fan of keeping the source separate from the outputs,
but in the interest of fairness, I feel I must point out a few items ]
Craig R. McClanahan wrote:
>
> > 3. different projects will create subdirectories of the
> > "build" directory and these subdirectory names will never
>
Jon Stevens wrote:
>
> There is nothing wrong with putting the version number on
> the .jar file and it help WAY to many people to do so.
I'm sure that putting the version number in a conspiquous place has helped
innumerable people.
However, as Craig pointed out:
>
> That makes building scripts
"Craig R. McClanahan" wrote:
>
>
> Try doing a "cvs commit" or "cvs update" in your source
> directory -- are the files marked with "?" ones that I forgot to
> register with CVS or are they just outputs of the build process?
> You have to think about that *every single time*.
>
N
Stuart Roebuck wrote:
> On Friday, December 15, 2000, at 03:24 PM, [EMAIL PROTECTED] wrote:
>
> > > >
> > > > /jakarta-tomcat/ shouldn't then create ../build/ - it's
> > > > not nice!
> > >
> > > An alternate perspective - I like the fact that building a cvs checkout
> > > does not modify the che
On Friday, December 15, 2000, at 03:24 PM, [EMAIL PROTECTED] wrote:
> > >
> > > /jakarta-tomcat/ shouldn't then create ../build/ - it's
> > > not nice!
> >
> > An alternate perspective - I like the fact that building a cvs checkout
> > does not modify the checkout itself.
>
> +1 !
>
m Ruby [mailto:[EMAIL PROTECTED]]
> Sent: 15 December 2000 11:59 am
> To: [EMAIL PROTECTED]
> Subject: RE: [PROPOSAL] building is easy (was: Re:
> [tomcat-4.0] building
> i s hard)
>
>
> John Morrison wrote:
> >
> > While jakarta-servletapi-4.0 and TC4.0 build
Jon Stevens wrote:
>
> I would say that the servlet api build process should
> be "fixed" to build/install into directories with the
> version number attached.
Agreed.
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
John Morrison wrote:
>
> 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
14 matches
Mail list logo
