Are you saying, Apache projects must not include a single "3rd party" JAR in the automated build?[?]
Eclipse has something called "Orbit" for exactly that purpose. Libraries like Apache Commons, etc. despite not EPL are located there. For Eclipse UOMo which I lead there's been a careful IP assessment and each external dependency like Unit-API or soon JSR 363 from JCP has to be registered and approved. I assume there is something similar for Apache, otherwise Pluto (RI for Portlet API 1.0-3.0) or Jackrabbit (same for JCR) or Tomcat (the RI for Servlet/JSP) would all be impossible and illegal[?] The "burden" of adding let's say "servlet-api" was pretty much taken away by those projecs, or are you saying there is no CI server that builds Tomcat with any of the JCP artifacts not written by Apache itself? W3C DDR is effectively the same as a JCP, OASIS, OGC or other standard. The JAR manifests the public API and projects implementing it, even though in this case there is no official "Reference Implementation" are allowed to use the binary. Whether the person who created the GitHub repo did so with their consent or not, I don't need to bother about. We used the JAR and currently still do, that should be OK and not require people to manually build those artifacts. They can download it and the Readme e.g. for Tomcat 6 looks as follows: http://mir2.ovh.net/ftp.apache.org/dist/tomcat/tomcat-6/v6.0.41/RELEASE-NOTES ============= Bundled APIs: ============= A standard installation of Tomcat 6.0 makes all of the following APIs available... AFAIS we probably needed RELEASE-NOTES similar to what Reza started adding to a few other artifacts, and at least for SimpleDDR (or if we intended to have a "W3C compliant" aspect to the new Java Client, also there at some point) a paragraph like "Bundled APIs" explaining that the W3C standard library is used seems the way to go here. Werner On Wed, Jul 9, 2014 at 12:30 PM, Bertrand Delacretaz <[email protected] > wrote: > On Wed, Jul 9, 2014 at 10:41 AM, Werner Keil <[email protected]> > wrote: > > > ...unless we get the result of the Maven-JAR copy to place it with our > own > > artifacts, IDE users will have to live with the missing dependency or > > manually resolve that... > > > > Yes - we could have instructions on how to download and build that jar, > pointing for example to the github repository where you copied the w3c code > from. What's important is to put the burden on our users to decide whether > that dependency is ok for them, as opposed to code that belongs to the ASF > and that we are releasing ourselves. > > -Bertrand >
