#5644 Switch over to maven+git(hub) ?

closed-wont-fix
nobody
None
5
2013-04-05
2013-03-26
Cinquero
No

If you want to do that switch, I can do it for you.

Automatic third-party license report, no more bundled libs, automatic site report including cobertura coverage reports etc.

Discussion

  • Hendrik Brummermann

    • status: open --> closed-wont-fix
     
  • Hendrik Brummermann

    Please see the article on the Stendhal wiki about the status of migration to git and its blockers.

    Github does not offer any advantage over SourceForge and our Jenkins at all. So we do not consider to migrate to that platform.

    Maven adds a huge layer of complexity for all contrbutors. With the relativley small number of libraries required, bundling them is preferable: Do a CVS update and things just work without having to install external tools.

     
  • Cinquero

    Cinquero - 2013-04-05

    Maven+Git+Netbeans is the way to go. You will have more and more problems when you stick to the really outdated stuff. Upgrading dependencies in maven just requires a specific cmdline call and updating the version specs in the build descriptor. And putting binaries into CSV is an absolute no-go. In addition to that, support for cvs has been removed from many IDEs. And Jenkins has A LOT of plugin to support maven report plugins etc. On top of that, maven is MUCH MORE standardized than ant. It has strictly defined compile/resource processing/testing/integration-testing/package etc. phases. If you know maven, you know *EVERY* project's structure.

     


Anonymous

Cancel  Add attachments





Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks