[ormf-dev] Re: Rejection of Jaxen and workarounds

[Joel Rosi-Schwartz <Joel.Rosi-Schwartz@xxxxxxxxx>]

Eike,

No you got it right, well sort of. The problems is being able to redistribute Jaxen and that required the approval of legal via the EMO IP team. Without that we cannot reference it code base that is being distributed. To date Jaxen has been rejected on numerous occasions in IPZilla. Take a look at the rejected CQ for details by running this search. 

If you are fulfilling your 3rd party decencies dynamically via download from Spring Source, how are you meeting the due diligence requirements? Or are these downloads only for build purposes and not redistribution.

Thanks,

Joel

On 5 Aug 2008, at 17:44, Eike Stepper wrote:

Joel Rosi-Schwartz schrieb:

Hi Eike,

That is certainly interesting, but I am missing just how it relates to my question. I guess I am being a bit obtuse today.  Could possibly enlighten me :-)

I thought your problem is that you can not get Jaxen from Eclipse.org (Orbit or so).
A ready to use bundle is here:
http://www.springsource.com/repository/app/bundle/version/detail?name=com.springsource.org.jaxen&version=1.1.1&searchType=bundlesByName&searchQuery=jaxen

If you still feel that this is not related to your problem I probably got something wrong. Just ignore...

Cheers
/Eike

Thanks,

Joel

On 5 Aug 2008, at 17:27, Eike Stepper wrote:

Hi Joel,

I recently switched to using SpringSource (http://www.springsource.com/repository/app) for my non-EPL dependencies. For the local target platform setup as well as for the automated build I have prepared an Ant script that automatically downloads and installs the bundles:
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.emf/org.eclipse.emf.cdo/develop/setup/?root=Modeling_Project

Here is a wiki description:
http://wiki.eclipse.org/CDO_Source_Installation

I also filed an enhancement request for SpringSource to provide a P2 update site for their repository:
https://issuetracker.springsource.com/browse/BRITS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

I'd appreciate your feedback on my solution!

Cheers
/Eike


Joel Rosi-Schwartz schrieb:

Hello Eike, Frederic, Eric, Mary, 

I am a project leads for a new EF project ORMF and  I am in process of filing the CQ's for all our 3rd party library dependencies. The one serious glitch I have hit is that we are heavily dependent on Jaxen in our initial code contribution. Since you all use dom4j you are probably aware that Jaxen has been rejected on numerous CQ requests.

I am hoping that you will be able share with me your experiences on how you worked around not being able to use Jaxen for handling xpath support?

All the best,

Joel  

P Please consider the environment before printing this e-mail. Thank you.

http://www.etish.org                                                                     http://www.eclipse.org/ormf