Hi Rajiv,
The issue with Xerces and the IBM JDK is the same one Xalan's had with the
Sun JDK for a while: If the product is included in the JDK, then, unless
you fiddle with the JDK's bootclasspath, when attempting to compile you'll
pick up the old files before the new ones--which can result in problems.
It's not obvious to me how Ant could really help here: Unless it were to
somehow be able to relate what it's been asked to compile and what's in the
JDK it's compiling upon, that is. And that sounds a little onerous to me.
The best solution here is for someone to spelunk the Xalan build file and
port their solution over to Xerces. I think some Xerces committers have
spent a fair bit of time in Xalan-land--I've seen Neeraj and Rahul there in
the short time I sojourned over--so perhaps they'd be sufficiently familiar
with the Xalan method to be able to do that easily? I'd certainly be in
favour of this; it was kind of fun writing the xjavac task, but if it's
replaced by something cleaner and as complete, I'll be the first to
celebrate.
Cheers!
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone: 905-413-3519, T/L 969-3519
E-mail: [EMAIL PROTECTED]
|---------+---------------------------->
| | Rajiv Mordani |
| | <Rajiv.Mordani@Su|
| | n.COM> |
| | |
| | 12/06/2002 01:32 |
| | AM |
| | Please respond to|
| | xerces-j-dev |
| | |
|---------+---------------------------->
>---------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: xjavac missing. commenting out right solution?
|
|
|
|
|
>---------------------------------------------------------------------------------------------------------------------------------------------|
I agree. If at all I think we should try to get the ant community to do
some of the changes to make it possible to build using the IBM jdk. They
did something earlier on for jikes I think. Maybe they can do similarly
for the IBM 1.4 sdk.
- Rajiv
--
:wq
On Tue, 26 Nov 2002, Ted Leung wrote:
> 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]
>
---------------------------------------------------------------------
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]
