Community
Participate
Working Groups
This covers: com.springsource.net.sourceforge.jwebunit-2.1.0.jar com.springsource.net.sourceforge.jwebunit-2.2.0.jar com.springsource.net.sourceforge.jwebunit.htmlunit-2.1.0.jar com.springsource.net.sourceforge.jwebunit.htmlunit-2.2.0.jar See https://dev.eclipse.org/ipzilla/show_bug.cgi?id=4158.
No CQ needed. On 15 Jul 2010, at 15:36, Barb Cochrane wrote: Hi Glyn, Following up on our conversation this morning, one thing I neglected to mention is that to the extent your requirement for a third party package is limited to testing on the build server, then no CQ would be required. At the current time, we do not perform due diligence on tools whose use is limited to the build server. The only caveat I would mention is that to the extent any third party package on the build server is required by your downstream consumer, then you would need to enter a "workswith" or "exempt pre-req" CQ for such packages, as applicable. As you are no doubt aware, these types of CQs are not subject to the same level of due diligence as that which is performed for applications which go in our repository. I hope this helps. Barb Cochrane Eclipse Foundation, Inc. Phone 613.224.9461 ext 232 (GMT -5)
