Peter Donald wrote:
Gonna have to disagree. You do whats best when there is no
significant advantage of doing it otherways. Standardizing
on a crap standard because someone decrees it a standard is
near lunacy.
I'm 180 off of this position.
If there IS a significant advantage to doing it
Conor,
At 11:02 15.03.2001 +1100, Conor MacNeill wrote:
Ceki,
I would like to give you some feedback on the common directory layout
http://jakarta.apache.org/site/dirlayout.html
This is mostly from my Ant perspective and somewhat from my impression of
some other common practices in the
Ceki Glc [EMAIL PROTECTED] wrote:
At 11:02 15.03.2001 +1100, Conor MacNeill wrote:
I think that there should be a recommendation that any file/dir not
under CVS control should go into the .cvsignore file.
There is no need to adding any files to .cvsignore if you add files
to CVS control
At 01:34 16.03.2001 +1100, Peter Donald wrote:
build directory
Many of the Jakarta projects put the build files in the project's root
directory and use the build directory for build results, such as build
classes which will be jarred up into the distribution
So by build/ you
At 02:46 16.03.2001 +1100, Peter Donald wrote:
At 04:17 15/3/01 +0100, Ceki Glc wrote:
A lot of projects use dist/, in my personal projects I use out/ while some
projects use bin/.
See, these names are like colors, blue, green, or yellow... At face value,
they are all equivalent. That's what I
on 3/14/01 4:02 PM, "Conor MacNeill" [EMAIL PROTECTED] wrote:
Ceki,
I would like to give you some feedback on the common directory layout
http://jakarta.apache.org/site/dirlayout.html
This is mostly from my Ant perspective and somewhat from my impression of
some other common practices
On Thu, Mar 15, 2001 at 11:02:27AM +1100, Conor MacNeill wrote:
Ceki,
I would like to give you some feedback on the common directory layout
http://jakarta.apache.org/site/dirlayout.html
This is mostly from my Ant perspective and somewhat from my impression of
some other common practices
Jon,
From: Jon Stevens [mailto:[EMAIL PROTECTED]]
I disagree. Documentation == website. All of the documentation
for a product
should be available on the website. The reason is simple...we are creating
open source. Documentation is lacking in general as well as people to
maintain it. So,
