Sounds like a good idea.
I'd still like at least a build.sh and build.bat, then, to bootstrap
the $CLASSPATH so that ant.jar and jakarta-ant-optional.jar get loaded
from the lib/ directory.
If you can do the rest of the classpath munging from build.xml, that'd
be groovy.
-bob
On Wed, 19 Dec 2001, Geir Magnusson Jr. wrote:
> On 12/19/01 12:36 AM, "Son Truong" <[EMAIL PROTECTED]> wrote:
>
> > Hi Bob,
> >
> > I just wrote a batch file to build Jaxen on Windows platform (mainly
> > based on Xalan project). Well, if you think it's useful then you can add
> > it to the Jaxen repository.
> >
>
> I've been thinking about the same problem.
>
> In the Velocity project, we abandoned any build scripts for specific OSs due
> to the displeasure of maintenance - the idea is that developers will build
> (rather than 'users'), they have to have ant anyway, so why not just have a
> naked build.xml script.
>
> I this case, you would need to alter the build.xml to deal better with
> adding the lib jars to the classpath, but that can be done pretty easily.
>
> I'll take a whack at it if bob wouldn't mind seeing his beautiful .pl go
> away. :)
> --
> Geir Magnusson Jr. [EMAIL PROTECTED]
> System and Software Consulting
> "They that can give up essential liberty to obtain a little temporary safety
> deserve neither liberty nor safety." - Benjamin Franklin
>
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> _______________________________________________
> Jaxen-interest mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jaxen-interest
>
_______________________________________________
Jaxen-interest mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jaxen-interest
