Seems to me that avoiding a custom task is the way to go.
Ted
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, November 26, 2002 1:13 PM
Subject: Re: xjavac missing. commenting out right solution?
> Hi Ted,
>
> But what do we do if it's not available--i.e., how do we tell ant
>
> if( -e xjavac) use xjavac to compile stuff
> else use javac
>
> (to use a vaguely sh-ish pseudocode). I've no doubt if can be done; just
> not sure how to model conditional execution in ant (let alone conditional
> task definition).
>
> Anyway, perhaps I should repost the tools distros. I also think Xalan
> found a solution to massaging the bootclasspath that didn't use a custom
> task; perhaps we should move in that direction in the long run.
>
> Cheers,
> Neil
> Neil Graham
> XML Parser Development
> IBM Toronto Lab
> Phone: 905-413-3519, T/L 969-3519
> E-mail: [EMAIL PROTECTED]
>
>
>
>
> |---------+---------------------------->
> | | "Ted Leung" |
> | | <[EMAIL PROTECTED]|
> | | om> |
> | | |
> | | 11/26/2002 03:53 |
> | | PM |
> | | Please respond to|
> | | xerces-j-dev |
> | | |
> |---------+---------------------------->
>
>---------------------------------------------------------------------------
------------------------------------------------------------------|
> |
|
> | To: <[EMAIL PROTECTED]>
|
> | cc:
|
> | Subject: Re: xjavac missing. commenting out right solution?
|
> |
|
> |
|
>
>---------------------------------------------------------------------------
------------------------------------------------------------------|
>
>
>
> Hi Neil,
>
> This bit me during the Hackathon as well. I seem to recall that Ant has a
> way of detecting whether a taskdef is present. I think it would be worth
> it
> to see if the xjavac task can be invoked only when its available.
>
> Ted
> ----- Original Message -----
> From: <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, November 26, 2002 12:02 PM
> Subject: Re: xjavac missing. commenting out right solution?
>
>
> > Hi Troy,
> >
> > Commenting this out should work fine, so long as you're not compiling
> under
> > an IBM JDK1.4.x. The root of the problem was that our tools generation
> > code was a bit broken--more seriously than this, is also removed the
> > LICENSE files for the jars included there...--and this only became
> evident
> > after 2.2.1.
> >
> > Cheers,
> > Neil
> > Neil Graham
> > XML Parser Development
> > IBM Toronto Lab
> > Phone: 905-413-3519, T/L 969-3519
> > E-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> > |---------+---------------------------->
> > | | "Troy" |
> > | | <[EMAIL PROTECTED]> |
> > | | |
> > | | 11/26/2002 07:53 |
> > | | AM |
> > | | Please respond to|
> > | | xerces-j-dev |
> > | | |
> > |---------+---------------------------->
> >
> >
> --------------------------------------------------------------------------
-
> ------------------------------------------------------------------|
> > |
> |
> > | To: [EMAIL PROTECTED]
> |
> > | cc:
> |
> > | Subject: xjavac missing. commenting out right solution?
> |
> > |
> |
> > |
> |
> >
> >
> --------------------------------------------------------------------------
-
> ------------------------------------------------------------------|
> >
> >
> >
> >
> > I just downloaded the xerces xerces-2_2_1 and built
> > them on linux and j2sdk 1.4.1.
> >
> > The file tools/bin/xjavac.jar is missing, and I
> > couldn't find where to get it, so I commented out
> > the relevant portions in the build.xml file.
> > This seemed to work.
> >
> > I was wondering if this is what was intended.
> >
> >
> > Thanks,
> >
> >
> > Troy
> >
> > Troy Korjuslommi Tksoft Inc.
> > [EMAIL PROTECTED]
> >
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
