"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.

> > 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.

<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'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.

> 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?

> 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).

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to