So the source was always going to be the primary dist, but it is convenient to have the WAR download.
GitHub can attach binaries to releases, we do it already: https://github.com/cdk/cdk/releases/tag/cdk-1.5.11. Given the whole SourceForge Gimp fiasco I’m wary of using it. John On Oct 25, 2015, at 1:43 PM, Egon Willighagen <egon.willigha...@gmail.com> wrote: > On Sat, Oct 24, 2015 at 8:26 PM, John M <john.wilkinson...@gmail.com> wrote: >> Anyways, just deployed one to OpenShift running the latest CDK SnapShot with >> some improvements to layout: >> http://cdkdepict-openchem.rhcloud.com/depict.html > > Nice! > >> Are there any objections to distributing source/war via github >> ('/cdk/depict') as an app people can deploy locally? > > In general not a good idea to share binaries... I rather see a Maven > build that creates the war, and use an FTP server to distribute the > binaries... like with the CDK jar on SourceForge... > > That said, I am not sure how GitHub handles this need... but I think > sharing the binaries are a good idea. Why not use SourceForge for > this? > > If not clear, I don't have strong arguments against it, but if you > choose GitHub to distribute them, I recommend a separate repository, > outside the source code repos for the CDK Depict project. > > Egon > > -- > E.L. Willighagen > Department of Bioinformatics - BiGCaT > Maastricht University (http://www.bigcat.unimaas.nl/) > Homepage: http://egonw.github.com/ > LinkedIn: http://se.linkedin.com/in/egonw > Blog: http://chem-bla-ics.blogspot.com/ > PubList: http://www.citeulike.org/user/egonw/tag/papers > ORCID: 0000-0001-7542-0286 > ImpactStory: https://impactstory.org/EgonWillighagen
------------------------------------------------------------------------------
_______________________________________________ Cdk-user mailing list Cdk-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdk-user
