Hi, if I understood Jaroslav correct he is proposing two changes
1. Download 3rd party binaries needed to build NetBeans from a maven repository (maven central, jcenter or if you behinf corporate firewalls a synced self hosted repo using nexus or artifactory) 2. Use Maven repository as storahe backend for the plugin portal, so that only the metadata is hosted at the portal not the module binaries.. Both ideas seem to be really good enhancements to the way this works now! Thanks Jaroslav for the great idea and support Sven Am 28.09.2016 11:25 schrieb "Greg Stein" <gst...@gmail.com>: > On Tue, Sep 27, 2016 at 10:13 PM, Jaroslav Tulach < > jaroslav.tul...@gmail.com > > wrote: > >... > > > One idea that keeps puzzling in my mind is to reuse central Maven > > repository > > more than we used to. If I understand correctly while the Maven central > is > > operated by Sonatype, it is just "leased" to them and still oversight by > > Apache. > > > Not so much. We license the "Apache Maven" trademark to them, to provide a > fantastic service to the Maven community. But Maven Central is *all* > Sonatype, and the ASF generally just provides oversight over trademark use > (rather than operation). > > To state things another way: the ASF has zero control over what goes onto > their platform. Shoot, we have a copy of the software which runs Maven > Central, but it is proprietary and we merely hold a license to run it. This > isn't pillows and unicorns. You will need to make a business case with > Sonatype to include stuff beyond artifacts that Apache Maven can consume > from their repository. > > (that is my reasonably-informed understanding; a discussion with Sonatype > and the Apache Maven PMC is your best bet) > > Cheers, > -g >
