OW2 TC IRC discussion summary
Maven/Nexus
------------------------
* Maven is more and more used in the OW2 Java community
* But OW2 is NOT maven dominated, it's just ATM the better (or less worst) existing tool available
* Having an OW2 repository manager should be good
* Akquinet has tried Artifactory and Nexus, they think that Nexus is better
** Artifactory corrupted some artifacts indexes
* Nexus provides release staging, artifact proxying, ...
* Nexus is not OpenSource, but there is a free (feature limited) version.
** We can ask Sonatype for a licence for the enterprise Edition
** They already did that for Apache, why not for us :)
* Sonatype has already made an offer to setup a Nexus Pro (ith staging and so on) for OW2
* We have to provide some significant disk space to this repository manager
** Currently, Akquinet repo is 50Gb large !
** Our own should be quite large too (only 1 JOnAS release is some hundreds Mb, not talking about snapshots)
* Nexus requires an LDAP
** It will be connected to the OW2 LDAP (GSA: which one ?)
* No major issues foreseen to install Nexus
(Out of the discussion)
Some benefits to use Nexus:
* Release Staging: Allow you to cut a release, try it without exposing it widely, then push it or retract it (important feature for release checking)
* Automated reposition cleanup: Auto deletion of old snapshots for example
* Virtual repository: Group your artifacts together, means better repository organisation
* Nexus correctly check and generate SHA1 and MD5 key
* The OSGi support may be useful for projects using OSGi
Git
------------------------
* Akquinet use SVN as their main dev stream (trunk/releases)
* Dev are free to use Git on their machine (GitSVN bridges exists)
* Some OW2 Members are willing to move to GitHub
* GitHub provides some additional features to bare Git:
** "Social" coding
** a complete forge (tracker, reviews, ...)
* Cedric raised a concern WRT to "Git is not good for maintaining a reference copy of the code"
** IMHO (GSA) it's all about organisation, with DCVS there is no central point, there is only a well know repository (available on/from OW2 infrastructure) that is CONSIDERED the reference
-> CE : That's why we use SVN as our main stream. SVN is our reference (trunk / release)
** Anyway, if peoples/projects want to move to Git/Mercurial they should already know that
* A pointer on Git/SVN bridge (from E.Bernard, an Hibernate project leader): http://blog.emmanuelbernard.com/2010/05/git-how-my-life-has-improved-since-last-month-when-i-used-svn/
* Is installing a GitHub on OW2 an option (is this possible ? Is this OpenSource ? ...)
* An option maybe to mirror or clone OW2 repository on GitHub
** Apache did that with their own Git (SVN mirror) repositories (They are read-only)
** Clement should ask the Apache infra to know how they do that
* Apparently GitHub is selled for private networks
(Out of the discussion)
* Linus Torvald on Git: http://www.youtube.com/watch?v=4XpnKHJAok8
Sonar
------------------------
* Sonar is a code quality report generator (provides multiple code metrics)
** See it live: http://nemo.sonarsource.org
* Usually it's used in conjonction with a CI server (Hudson triggering Sonar daily for example)
* Generating reports is CPU consummong (although only triggering daily run reduce it)
* Storing reports is disk space consumming
* Bull: NovaForge provides Sonar for its projects