+1 also
Here are some comments I have after reading the dirlayout.html file (for the
first time, I have to admit. Actually I don't know where it is linked to on
the jakarta web site !) ...
I don't want to start a lengthy discussion (as it is very difficult to reach
an agreement on these subjects ... :) ) but I still wanted to help ... :)
1) There is no directory defined for configuration files (top level
properties file, top level xml files, manifest file to include in jar, ...).
Do we want to define a location for these ?
2) The rule for the output directory says : either bin/ or build/. I think
that a) we must make up our minds on one choice only and b) then names are
not well choosen as they be misinterpreted. I would suggest something less
equivocal like out/ : build/ can be both the location of the files needed
for building the project or the result of the build and bin/ can be location
of generated executables or executable needed by the project for some tasks.
Also, bin/ is inherited from previous languages like C/C++ where you built
and executable. In java it is not really an executable, more like a library
but lib/ wouldn't be good either.
3) Until we all agree, I would let the project decide on how to use Ant :
a) as an application that need to be installed on the computer doing the
build. This means no need to have ant.jar, optional.jar, xerces.jar,
xalan.jar, stylebook.jar, .... in the build/lib directory and no .bat or .sh
files needed either.
b) as a "component", i.e. located in build/lib with all it's needed jar
files
4) The section on docs/ is not clear. Is it output docs not in CVS or non
generated docs in CVS. It seems to be both. Should be clarified I think
5) There should be only one name for the build scripts and tools. I would
tend to prefer build/ with the output directory named out/. I don't really
care about the name but there should be only one proposed
6) 2 options should be left to the project for the external jar needed to
build/run the project. Until we reach an agreement on course ... (maybe
CJAN/JJAR - see the discussion on jakarta-commons mailing list - will help)
:
a) leave the external jars out of CVS. i.e. use a build.properties file
(used by Ant) that defines the location of needed external jars
b) or check the needed external libs in CVS with the project.
Hope it helps.
Thanks
Vincent.
----- Original Message -----
From: "Conor MacNeill" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, May 07, 2001 1:51 PM
Subject: Re: Proposed dirlayout document
> Ceki,
>
> +1
>
> I agree. Too much optionality in a standard means there is nothing
standard
> about it. I raised some issues about the original layout. These were just
> raising what I thought was the common Jakarta approach to some of these
> things.
>
> So, lets have a single approach with little optionality. It should be
> non-binding with a goal to move current projects to this standard.
>
> I don't think Ant should dictate the structure. I'm confident it will be
> able to support anything reasonable.
>
> Bring it on ...
>
> Conor
>
> ----- Original Message -----
> From: "Ceki G�lc�" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, May 07, 2001 9:13 PM
> Subject: Proposed dirlayout document
>
>
>
> Hi everyone,
>
> Having recently looked at http://jakarta.apache.org/site/dirlayout.html,
my
> impression was that it allowed too many alternatives on a large number of
> points rendering the document somewhat confusing (useless?). I am against
> making the dirlayout document an exhaustive list of all possible layout
> structures. A guideline document should be a bit more assertive.
>
> With your permission I would like to eliminate some of the alternatives.
> This is surely going upset some people. I am asking for the permission to
> make some potentially controversial changes. Let me repeat that I do not
> consider myself as an expert in ANT or to know the optimal directory
> structures. As such, you are strongly encouraged to make suggestions.
>
> In order to avoid endless discussion, I am willing to cede my role if
> anyone volunteers to take up the responsibility for the document. Best
> regards, Ceki
>
>
>
> --
> Ceki G�lc�
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
