Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 15807 invoked from network); 2 Jan 2001 15:37:49 -0000 Received: from unknown (HELO ?195.115.98.1?) (195.115.98.1) by h31.sny.collab.net with SMTP; 2 Jan 2001 15:37:49 -0000 Received: from maileu.imediation.com by [195.115.98.1] via smtpd (for h31.sny.collab.net [64.208.42.41]) with SMTP; 2 Jan 2001 16:37:35 UT Received: (private information removed) Message-ID: <9B3E950CB293D411ADF4009027B0A4D25E76F1@maileu.imediation.com> From: Stephane Bailliez To: ant-dev@jakarta.apache.org Subject: RE: License problem Date: Tue, 2 Jan 2001 15:40:50 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C074D2.6236E8B6" X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N ------_=_NextPart_001_01C074D2.6236E8B6 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I don't like the idea of being so tighted to a specific implementation (especially a xml parser) but AFAIK this feature unfortunately does not exist in other parsers (except with the DOM L2 importNode), and I = didn't feel like cloning all elements of the tree right now (this is prototype after all, no need to reinvent the wheel :-). Once this is validated I would prefer to remains parser independant and = add additional code, at least it will avoid parser transition problem, and = plus performance should not be an issue. --=20 St=E9phane Bailliez=20 Software Engineer, Paris - France=20 iMediation - http://www.imediation.com=20 Disclaimer: All the opinions expressed above are mine and not those = from my company.=20 > -----Original Message----- > From: Conor MacNeill [mailto:conor@cognet.com.au] > Sent: Tuesday, January 02, 2001 2:18 PM > To: ant-dev@jakarta.apache.org > Subject: Re: License problem >=20 >=20 > Stephane, >=20 > Sure, I didn't consider antidote as I don't use the GUI, at=20 > least not yet. > Not that keen on tying the GUI or JUnit to a particular XML=20 > parser either. >=20 > Conor >=20 >=20 > ----- Original Message ----- > From: "Stephane Bailliez" > To: > Cc: > Sent: Tuesday, January 02, 2001 11:28 PM > Subject: RE: License problem >=20 >=20 >=20 > Actually this is possible for the ant core, but there are=20 > explicit import > of > com.sun.xml into ACS and there possibly could be some in the=20 > optional tasks > (even though there is no one right now) >=20 > I'm writing some prototype classes for the JUnit task that involves > (unfortunatly) a specific operation of the sun xml parser=20 > (the ability to > aggregate xml documents by using changeNodeOwner). The intent is to = be > somewhat a quick fix to aggregate all test results into a=20 > single document > while I'm thinking about an enhanced design of the JUnit task. >=20 > -- > St=E9phane Bailliez > Software Engineer, Paris - France > iMediation - http://www.imediation.com > Disclaimer: All the opinions expressed above are mine and=20 > not those from > my > company. >=20 >=20 >=20 > > -----Original Message----- > > From: Conor MacNeill [mailto:conor@cognet.com.au] > > Sent: Tuesday, January 02, 2001 12:57 PM > > To: ant-dev@jakarta.apache.org > > Cc: Guillaume.Rousse@univ-reunion.fr > > Subject: Re: License problem > > > > > > Guillaume, > > > > I think you have two choices. > > > > 1. Take out the two jars and instruct the users to place > > their favourite > > JAXP parser into the ant/lib directory > > 2. just drop xerces.jar in there in their place. > > > > I tried this with a xerces.jar, I built from the latest=20 > source and it > > worked nicely. If you do go down that path, you need to pick > > a particular > > xerces released version, I guess. You would probably want to > > test that it > > works too. > > > > The downside of the xerces solution is that the xerces.jar is = ~770k, > > compared with ~140k for the reference JAXP implementation. > > Not a big deal, > > IMHO, but may be important to some. > > > > Cheers > > Conor > > > > > > ----- Original Message ----- > > From: "Guillaume Rousse" > > To: > > Sent: Tuesday, January 02, 2001 10:51 AM > > Subject: License problem > > > > > > > Hello. > > > I wanted to package ant for Mandrake, but i saw those two = infamous > > > binaries ;-) file in ant sources : jaxp.jar and parser.jar, > > which are (i > > > suppose) covered by Sun's java license. If i wanted to do a > > open-source > > > only package, can i: > > > -externalise those two files into another binary package, than = put > > > depencies on it for building/running ant ? > > > -replace them completly by xerces ? > > > In both case, what sould i change in ant buildfile for=20 > building it ? > > > > > > As i'm not subscribed, please send your answer to my adress too. > > > Thanks for your help. > > > -- > > > Guillaume Rousse > > > > > > Murphy's law : If anything can go wrong, it will. > > > O'Tool's commentary : Murphy was an optimist. > > > > > > > >=20 > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org > > > For additional commands, e-mail: ant-dev-help@jakarta.apache.org > > > > > > > > >=20 > --------------------------------------------------------------------- > > To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org > > For additional commands, e-mail: ant-dev-help@jakarta.apache.org > > >=20 >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: ant-dev-help@jakarta.apache.org >=20 ------_=_NextPart_001_01C074D2.6236E8B6 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: License problem

I don't like the idea of being so tighted to a = specific implementation (especially a xml parser) but AFAIK this = feature unfortunately does not exist in other parsers (except with the = DOM L2 importNode), and I didn't feel like cloning all elements of the = tree right now (this is prototype after all, no need to reinvent the = wheel :-).

Once this is validated I would prefer to remains = parser independant and add additional code, at least it will avoid = parser transition problem, and plus performance should not be an = issue.

--
 St=E9phane Bailliez
 Software Engineer, Paris - France
 iMediation - http://www.imediation.com
 Disclaimer: All the opinions expressed above = are mine and not those from my company.



> -----Original Message-----
> From: Conor MacNeill [mailto:conor@cognet.com.au]
> Sent: Tuesday, January 02, 2001 2:18 PM
> To: ant-dev@jakarta.apache.org
> Subject: Re: License problem
>
>
> Stephane,
>
> Sure, I didn't consider antidote as I don't use = the GUI, at
> least not yet.
> Not that keen on tying the GUI or JUnit to a = particular XML
> parser either.
>
> Conor
>
>
> ----- Original Message -----
> From: "Stephane Bailliez" = <sbailliez@imediation.com>
> To: <ant-dev@jakarta.apache.org>
> Cc: = <Guillaume.Rousse@univ-reunion.fr>
> Sent: Tuesday, January 02, 2001 11:28 PM
> Subject: RE: License problem
>
>
>
> Actually this is possible for the ant core, but = there are
> explicit import
> of
> com.sun.xml into ACS and there possibly could = be some in the
> optional tasks
> (even though there is no one right now)
>
> I'm writing some prototype classes for the = JUnit task that involves
> (unfortunatly) a specific operation of the sun = xml parser
> (the ability to
> aggregate xml documents by using = changeNodeOwner). The intent is to be
> somewhat a quick fix to aggregate all test = results into a
> single document
> while I'm thinking about an enhanced design of = the JUnit task.
>
> --
>  St=E9phane Bailliez
>  Software Engineer, Paris - France
>  iMediation - http://www.imediation.com
>  Disclaimer: All the opinions expressed = above are mine and
> not those from
> my
> company.
>
>
>
> > -----Original Message-----
> > From: Conor MacNeill [mailto:conor@cognet.com.au]
> > Sent: Tuesday, January 02, 2001 12:57 = PM
> > To: ant-dev@jakarta.apache.org
> > Cc: = Guillaume.Rousse@univ-reunion.fr
> > Subject: Re: License problem
> >
> >
> > Guillaume,
> >
> > I think you have two choices.
> >
> > 1. Take out the two jars and instruct the = users to place
> > their favourite
> > JAXP parser into the ant/lib = directory
> > 2. just drop xerces.jar in there in their = place.
> >
> > I tried this with a xerces.jar, I built = from the latest
> source and it
> > worked nicely. If you do go down that = path, you need to pick
> > a particular
> > xerces released version, I guess. You = would probably want to
> > test that it
> > works too.
> >
> > The downside of the xerces solution is = that the xerces.jar is ~770k,
> > compared with ~140k for the reference JAXP = implementation.
> > Not a big deal,
> > IMHO, but may be important to some.
> >
> > Cheers
> > Conor
> >
> >
> > ----- Original Message -----
> > From: "Guillaume Rousse" = <Guillaume.Rousse@univ-reunion.fr>
> > To: = <ant-dev@jakarta.apache.org>
> > Sent: Tuesday, January 02, 2001 10:51 = AM
> > Subject: License problem
> >
> >
> > > Hello.
> > > I wanted to package ant for Mandrake, = but i saw those two infamous
> > > binaries ;-) file in ant sources : = jaxp.jar and parser.jar,
> > which are (i
> > > suppose) covered by Sun's java = license. If i wanted to do a
> > open-source
> > > only package, can i:
> > > -externalise those two files into = another binary package, than put
> > > depencies on it for building/running = ant ?
> > > -replace them completly by xerces = ?
> > > In both case, what sould i change in = ant buildfile for
> building it ?
> > >
> > > As i'm not subscribed, please send = your answer to my adress too.
> > > Thanks for your help.
> > > --
> > > Guillaume Rousse
> > >
> > > Murphy's law : If anything can go = wrong, it will.
> > > O'Tool's commentary : Murphy was an = optimist.
> > >
> > >
> >
> = ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: = ant-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: = ant-dev-help@jakarta.apache.org
> > >
> >
> >
> >
> = ---------------------------------------------------------------------
> > To unsubscribe, e-mail: = ant-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: = ant-dev-help@jakarta.apache.org
> >
>
>
>
> = ---------------------------------------------------------------------
> To unsubscribe, e-mail: = ant-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: = ant-dev-help@jakarta.apache.org
>

------_=_NextPart_001_01C074D2.6236E8B6--