Hi, devs,
I'm going to move HtmlUnitDriver from the main Selenium code base to a subproject / a separate repository.
Two main reasons are:
1) We move drivers outside the main Selenium distribution. This allows to synchronize a driver release cycle with the target browser release cycle. The same is true for HtmlUnit.
2) It's HUGE -- HtmlUnit (with its dependencies) represents about 50% of selenium server standalone! And it is rarely used (I hope) as a remove driver.
The plan is:
1) Move HtmlUnitDriver to a separate repository and delete its source code from the main Selenium code base.
2) Provide a Maven artifact for HtmlIUnitDriver that can be added as an independent driver; break selenium-java dependency on it.
3) Put HtmlUnitDriver artifact to the third-party jar collection as a test only dependency.
4) Provide an uber jar for HtmlUnitDriver that can be deployed to selenium server (or a grid node) and write an installation instruction.
Any objections?
Regards,
--
Alexei Barantsev
Software-Testing.Ru
Selenium2.Ru