> -----Original Message-----
> From: Berin Loritsch [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 27 September 2001 2:23 pm
> To: [EMAIL PROTECTED]
> Subject: Re: Build.xml standardization
>
>
> "Morrison, John" wrote:
> >
> > > The "test" alias is optional.
> >
> > Yeah, but if they didn't want it it's easier to delete than
> to add :)
>
> Agreed. I was thinking a simple comment inside (or above) the target
> stating that would bring attention to that.
OK.
Should we check this into somewhere (alexandria since we both(?) have
access, cocoon?)?
> > > Lastly, if "printerdocs" is really only meant for users then
> > > it should be
> > > renamed to "userdocs". Also, please note that
> > > printerfriendly documentation
> > > is something that many professional sites have employed.
> > > They have a "Print
> > > This" link that removes all the extraneous formatting. It
> > > might be a good
> > > idea to adopt that approach if possible. The idea I had when
> > > presenting
> > > this target was that we really need documentation that can be
> > > printed out.
> > > most of the projects have the formatting on the documentation
> > > so that the
> > > printer cuts off the right side.
> >
> > I'm +0 on this - I don't think it'll really be used on it's
> own - it'll prob
> > only be used by the docs target.
>
> Maybe not. I know Cocoon has that target, and I use it alot.
AYW
> <gripe type="personal">
> Both Jakarta and XML sites ignore principals of designing
> for HTML. Because
> they both use templating engines, they both used the
> simplist approach from
> a templating engine. A properly designed template will
> still produce good
> HTML and even look the same (or similar). Good HTML IMNSHO
> is designed to
> be light weight and not be too constrained.
> </gripe>
>
> Ok, now I'm off my personal soap box--I know this is not the
> forum for that.
> I may revamp the Avalon project templates to prove my point though....
I agree - just because you're templating shouldn't mean that the html is
gross!
> > I'd also like to define some other properties to do with javadocs.
>
> I am +1 for that. I just don't know the inner details of how
> the javadoc
> tag works.
Me neither :( I just think they would be useful.
> > Also, did I put the property file= instructions in the
> correct place and
> > does Ant function as I think (ie, putting them where they
> are and in the
> > order they are would mean that, for example, project.name
> couldn't be
> > overridden...?)
>
> I think so. Question: doesn't the Ant shell scripts already
> apply the user
> properties before the build.xml file is even read?
I don't know. I only know that the file can exist!
> > Oh, while I think about it, isn't project.name already
> defined in the
> > <project> at the top?
>
> I'm not sure. I'd have to look a little deeper into that
> aspect of ant.
> (I am by no means an Ant guru--I only know how to make it do
> what I want).
Join the club. I don't think that anybody out of the ant developers are
gurus - everyone I know who creates ant build.xml files does what I did -
find a couple of other projects and rip them to shreds then recombine to be
what you want ;) Could be a good thing for the old CV (resume for those
from the states ;)
=======================================================================
Information in this email and any attachments are confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed
to any third party without our permission. There is no intention to
create any legally binding contract or other commitment through the use
of this email.
Experian Limited (registration number 653331).
Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
