Hi Matthieu, thank you for your fast response.
I looked into the older IP cases. The jaxen lib was rejected because of pedigree issues. In this case they where not able to document that all comitters are getting through a process stating that they make their contributions below BSD before getting access to SVN. Eclipse did get into touch with the jaxen team and they said that they are not able to suport Eclipse on this pedigree point. Therefore Eclipse IP has no other choice than permitting this library usage. This was end of 2007. Is there a way to make some of those libraries pluggable? E.g. by adding the saxen lib to classpath? That would be a great benefit for our commercial distribution. We love saxon but our choices are a bit limited at Eclipse due to IP process. Kind Regards, Georg Committer for the Eclipse SMILA project http://www.eclipse.org/smila -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthieu Riou Sent: Montag, 20. Oktober 2008 16:54 To: [email protected] Subject: Re: Library usage in ODE Hi Georg, I'm surprised that Jaxen didn't meet your IP requirements, it's MIT licensed which is fairly liberal. We could even relicense it under ASL 2.0 if we wanted to. It's hard to remove the dependency toward both Jaxen and Saxon: the former is provided to support XPath 1.0 and the latter XPath 2.0 (and XQuery). We could provide one without the other (i.e. Jaxen but not Saxon), forcing the usage of one version of XPath over the other, but if we remove both it's going to be very hard to run a BPEL process with no XPath support. If you really can't accept Jaxen we could replace it with Xalan (ASL 2.0) for XPath 1.0 support but I'd like to know why Jaxen isn't acceptable before going down that road. Thanks, Matthieu On Mon, Oct 20, 2008 at 7:33 AM, August Georg Schmidt <[EMAIL PROTECTED]>wrote: > Hi, > > currently we try to use the ODE BPEL engine within our SMILA project to > process annotation pipelines. > > Due to our IP process at Eclipse we must declare some libraries as external > references, because they did not meet IP requirements set by the foundation. > > These libraries are: > > * jaxen-1.1.1.jar > > * saxon-8.7.jar > > * saxon-dom-8.7.jar > > * saxon-xpath-8.7.jar > > Is there a way to use a another library (e.g. one under ASL 2.0) or make > those implementations exchangeable? In other way we will not be able to > create a 100% download at Eclipse. > > Kind Regards, > > Georg > > Committer for the Eclipse SMILA project http://www.eclipse.org/smila > >
