And then maybe the issue https://issues.apache.org/jira/browse/OFBIZ-680 would 
still be interesting

Jacques

From: "Brett Palmer" <brettgpal...@gmail.com>
Update on SeleniumXml:

There was an effort to replace some of the LGPL code in Selenium a few
months back. I am following up with the developers to see how this is coming
along.

Over the holiday break I will open up a Jira issue with a patch to include
all the SeleniumXml source and the build to download the selenium-core
library.  I'll also see if we could host the JavaScript files separately
from the core and make them available over the net.  This would avoid the
whole library download issue.

This will give everyone a chance to play with the solution and make any
proposals for the best way to move forward on the testing framework.  I'll
continue to drive the effort, but I'm always appreciative of feedback from
the community on how to proceed.

Thanks,


Brett

On Fri, Dec 12, 2008 at 8:55 PM, David E Jones
<david.jo...@hotwaxmedia.com>wrote:


On Dec 11, 2008, at 3:27 PM, Brett Palmer wrote:

 *Proposed Solutions*

 1.

 Create a custom ant target (e.g. install-selenium-xml) that downloads the
 selenium-server.jar from a non-Apache hosted website (e.g. SourceForge).
For
 example, the Apache Velocity project does this with their build which may
be
 to work around possible license problems as we have here.


I think I like #2 better, but for this option one alternative we could
consider with these is that if the files are only used by the client
(browser) we could host them somewhere where they are accessed as needed.
This means that to run the tests the machine would have to be connected to
the internet, but it would eliminate the need for any extra steps during
build/run.

-David



  2.

 Another possibility is to replace the LGPL JavaScript files with our own
 version and then get the Selenium project to adopt the Apache licensed
 version. There isn't a lot of code to change, but it would take an effort
to
 test it thoroughly to make sure all the Selenium code still worked with
the
 change.




Reply via email to