> Why only sources? I guess (not checked yet) the Sharepoint / Meridio ones > could not be redistributed as binaries with an Apache License but I think > the Solr stuff can be.
The binaries are actually checked into the main ManifoldCF tree, and are delivered with ManifoldCF. > We may create a module called "MCF-integration" which aggregates the > sources for each of these modules. > I've seen this being done in the past where the source release contained > all the modules' sources while the single source artifacts could be > retrieved from the Apache Maven repository. The update/release cycle for each component is different. For instance, I wouldn't anticipate releasing the SharePoint/Meridio release again for years, perhaps. Thanks! Karl On Fri, Dec 9, 2011 at 1:21 AM, Tommaso Teofili <[email protected]> wrote: > Hi all > > 2011/12/8 Karl Wright <[email protected]> > >> Hi Folks, >> >> The manifoldcf 0.4-incubating release does not include sources for the >> following components that are meant to be installed on repositories, >> in order to enable the corresponding connector: >> >> - the solr 3.x security plugin >> - the solr 4.x security plugin >> - the SharePoint 3.0 MCPermissions.asmx web service >> - the Meridio user lookup web service >> >> I have put together all of these under >> https://svn.apache.org/repos/asf/incubator/lcf/integration. Each of >> them has their own license, notice, etc. My plan was to release them >> independently and somewhat before ManifoldCF 0.4-incubating, as >> separate packages with different names and version numbers (e.g. >> "Apache SharePoint 3.0 ManifoldCF Plugin", >> "apache-sharepoint-3.0-manifoldcf-plugin-0.1-incubating"). >> >> First, some things to note: >> (1) I have no intention to deliver anything other than source >> zips/tar.gzs for these, and of course corresponding signature files. >> > > Why only sources? I guess (not checked yet) the Sharepoint / Meridio ones > could not be redistributed as binaries with an Apache License but I think > the Solr stuff can be. > > >> (2) I have no idea what the incubator release process should look like >> for something like this. Tommaso, what do you think? Should we put >> the packages up and request an incubator vote on each one? >> > > We may create a module called "MCF-integration" which aggregates the > sources for each of these modules. > I've seen this being done in the past where the source release contained > all the modules' sources while the single source artifacts could be > retrieved from the Apache Maven repository. > > Otherwise if you want to have separate source packages being released > separately then yes we have to call a vote on general@ for each of them. > > >> I'd like to get the ball rolling quickly, before the holidays mess us >> up, since these are prerequisites for the main 0.4 release. >> >> Karl >> > > Tommaso
