Hi, I'd like to have a continuous build system for JabRef running. Travis-CI offers that for github (http://about.travis-ci.org/docs/user/languages/java/).
Is anyone aware of a similar tool for sourceforge? If not, I would suggest to move or copy the code to github, too... Thereby, I would split the repository: * /jabref as jabref * /htdocs as branch "htdocs" in jabref or as subfolder in jabref * /jpfcodegen as jpfcodegen * /plugins/net.sf.jabref.export.xml as net.sf.jabref.export.xml * /plugins/net.sf.jabref.imports.acm1 as net.sf.jabref.imports.acm1 * /plugins/net.sf.jabref.imports.dblppp as net.sf.jabref.imports.dblppp Possibly, a shut down of the source forge repository would be the best way. We can easily keep the ticketing system, the wiki, and the homepage on sourceforge. Possibly, I'd vote to move the wiki to github, too :) There seems to be a possibility to migrate the ticketing system, too. However, it looses information. Therefore, I'd keep that on sf.net :) https://github.com/ttencate/sf2github What do you think? Cheers, Oliver ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Jabref-devel mailing list Jabref-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jabref-devel
