[EMAIL PROTECTED] wrote:
bodewig     2003/01/15 01:27:39

  Modified:    project  jakarta-avalon-apps.xml
  Log:
  JVMs >= 1.3 drop CLASSPATH entries that do not exist, so you need a
  <mkdir> for each <work> most of the time.
Perhaps we should auto-emit a mkdir for each work?

  <work> doesn't respect <home>, should it?
Insight into my original thinking... (not something etched in stone tablets or anything, just something to consider)... once upon a time I envisioned multiple profiles... with avalon and turbine being examples of ones that I could see as benefitting from something like gump. In those cases, they might not want to build ant, so they would not include the ant descriptor and simply install the ant package.

If a profile did include jakarta-ant.xml, however, the <home nested="dist"> element in jakarta-ant.xml would indicate a directory which had a layout quite similar to an installed package.

One thing I did not have the foresight to envision is cvs trees with multiply nested projects like jelly-tags. This is a frequent source of error as the path needs to be repeated in things like <work> elements.

- Sam Ruby



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

Reply via email to