All,
I added the ability to specify a classpath in framework notation for
compiling, i.e.:
<wocompile ...> ("..." is the same as with javac)
<frameworks root="${wo.localroot}" if="uses.mysql">
<include name="Mysql.framework">
</frameworks>
<classpath>
<fileset dir="${foo}">
<include name="**/*.jar">
</fileset>
</classpath>
</wocompile>
This makes it far easier to write flexible scripts that use the same
settings as the final app CLASSPATH.txt files. Also I find it more
reasonable to use the same "language" as the other tasks (IE, you're
dealing with frameworks, not jars). Otherwise this is the same as the
<javac> task.
I'm not familiar with the procedure for additions here? Is there a vote
or something, or do I just go ahead?
On another note: at Wonder, Patrice Gautier set up the CVS with
syncmail - that's a phython script that can send mail on commits to the
respository containing the file diffs and the commit message. He set up
a "wonder-cvs" mailing list that everyone can subscribe to and keep up
to date.
I found that absolute fantastic because you donīt need to announce
every little change on the dev-list. Should we also install that?
Cheers, Anjo
This archive was generated by hypermail 2.0.0 : Fri Oct 25 2002 - 10:03:23 EDT