[wtp-pmc] [CQ 4665] Zorba XQuery Processor Version: HEAD

[emo-ip-team@xxxxxxxxxxx]

http://dev.eclipse.org/ipzilla/show_bug.cgi?id=4665


Gabriel Petrovay <gabipetrovay@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|awaiting_committer          |awaiting_pmc




--- Comment #7 from Gabriel Petrovay <gabipetrovay@xxxxxxxxx>  2010-11-30 16:33:34 ---
(In reply to comment #5)
> If you do not plan do distribute this 3rd party code, I do not think you need a
> CQ for it. But doesn't hurt to document what you are doing here in this CQ. 
> 
> If I understand things (from quick read of some mailing lists), you just simply
> plan to use this on the build machine? And no one else needs access to it? 

Yes, this is true. Currently, we only want to check our build for conformance
with this XQuery processor. Only the build will use it internally.

> What does is it used for, exactly? Is it the simply, and literally, the actual
> tests? Or does it provide something to allow testing? Or is it that you want to
> test your code against this particular runtime, just to verify your code, but
> you do not plan to distribute the runtime through Eclipse.org?

We want to parse the XQuery test queries in the Zorba SVN repository to test
the parsers in XQDT. This gives us an image of what features are we missing
from XQDT. This is because Zorba implements [tries to] all the XQuery standards
from W3C: XQuery 1.0, Updating, Scripting, 1.1, Full-text. But currently, we do
not plan to distribute Zorba from Eclipse.org.

> 
> Just to check, is this just an issue of accessing "external" sites during your
> build? Not sure how that works, or if that is "allowed", but if not, there is
> probably some way to you can prepare a zip of what you need during your build,
> and put it "on" the build machine in some special spot, and then your scripts
> access it from there. 

As the webmaster said, it is technically possible. But is this allowed? Now,
about accessing "external" websites, this all what Maven does during the build.
It accesses the "external" plug-in repositories and it downloads the needed
plug-ins. A similar use case was also in our Hudson build a while ago. An ant
build step was downloading findbugs.zip form SourceForge and was checking the
build for posible problems. Now we use findbugs as a maven plugin which is
basically the same. The current use case of the Zorba SourceFoge SVN repository
is the same thing that we do with findbugs: find the bugs. 

More technically, JUnit test (>1500 of them) are dynamically generated from the
test queries.

> Feel free to let me know if I've misunderstood. I don't know of any reason not
> to approve this ... but do not think we need the IP Staff's "expense" (time) if
> you do not plan to distribute it. 

In the case that we later might want do distribute it, I wanted to avoid
duplication of work for the IP staff. Now the tests, afterwards the rest. If
it's all in there are no problems any more. But, as I previously sald, we
currently do not plan to distribute Zorba with our plug-ins.

> Thanks, 
> 

Thanks for the help.


-- 
Configure CQmail: http://dev.eclipse.org/ipzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the CQ.