Davanum Srinivas wrote:
>
> st is an Ant Task and the class is in bin directory. Do you want us to patch
>build.xml to fix
> this? Is there a "recommended" way to register Optional Ant Tasks (to be
>Gump-Friendly)?
Generally, if there needs to be anything in the classpath, the gump build
definitions need to be updated. Thanks for the heads up, I have now made
the update.
Normally, my preference would be that there be an ant target to build this,
which might even require running as a separate step. You can see an
example of this at
http://jakarta.apache.org/builds/gump/latest/fop-buildtools.html. Note: as
you are checking in a class file instead of a jar file, it quite probable
that the class files will have a later timestamp, thereby defeating the
purpose.
However, in this case, st.java seems to only depend on java.io.* -
something that is unlikely to change, so this does seem like overkill.
- Sam Ruby
P.S. it does not appear to me that st is an Ant task. If it were, it
might not be overkill to verify that the Ant team hasn't made any
incompatible change that will affect you down the road.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
