Here's a copy of what I posted. This will affect how we publish the new P2 update site, I think.
-------- Start of copy As part of our Apache UIMA component release, we update an Eclipse-update-site. This is essentially a special packaging of released JARs for our project's features and plugins for Eclipse, with some extra metadata, to allow Eclipse to install these. We are in the process of updating the format of our project's Eclipse update site to the "P2" style, to conform to the evolving development in Eclipse of how these sites are structured. The site would contain the exact same (already released) versions of the plugin and feature JARs. It's all very do-able, but a question comes up: for the updated build tooling we use to produce the new format of the Eclipse update site, do we need to make a source release of those build tools? It seems to me that this might fall into a bit of a gray area regarding Apache's mandate to distribute source code, because the build tooling is not really part of what we intend to distribute; rather it's incidental things the developers use to produce the distributed artifacts. So far, we've been following a practice that I think that has been used by many others where the source for build tooling used by our project (but which is not part of what we consider our distributed artifacts) is not put on the Apache Mirror system. For example, the common Apache-wide shared "parent" POM (you can see it here: http://repo1.maven.org/maven2/org/apache/apache/) I don't believe has it's source on the Apache Mirror distribution system (but I could be wrong). Is this OK? Thanks for any guidance here. ----- End of copy -Marshall
