I'm wondering how well things work with the nested maven projects, things in maven works most easily if the modules are subdirectories of the parent project. This works nicely with svn, allowing to check out the whole project or just an individual submodules whilemaintaining the default maven project structure.
Cheers, reto On Sun, Sep 12, 2010 at 6:51 PM, Toni Menzel <t...@okidokiteam.com> wrote: > What are pseudo maven repos ?? ;) > Ah, you mean the runner-repository ?? > Why not exactly ? > If there is a reason, that could stay on svn. Its not that everything has to > be turned over to git .. > > On Sun, Sep 12, 2010 at 6:43 PM, Andreas Pieber <anpie...@gmail.com> wrote: >> >> nothing to add; basically +1 to all three ideas; nevertheless there's one >> problem. git is not half as good as svn for >> "pseudo-maven-repos" >> >> kind regards, >> andreas >> >> On Sun, Sep 12, 2010 at 05:19:22PM +0200, Toni Menzel wrote: >> > Hi guys, >> > >> > OPS4J currently only allows source code to be hosted on the own ops4j >> > SVN repository. >> > >> > The benefits of GIT can be read elsewhere, at least you probably have >> > heard,it is not the worst thing in OSS history. >> > >> > Regarding that topic, i have some questions to the community: >> > >> > 1. >> > >> > Would you think GIT to be a worthy second SCM for developers at OPS4J >> > ? >> > >> > 2. >> > Sure, there should be also a trustworthy central point, even though >> > git >> > a de-central. >> > I would propose Github.com as a valid ops4j git host because of: >> > - taking away infrastructure issues from our own servers >> > - broaden visibility >> > - Github for Organizations sounds just right [1] >> > - its just a good tool (web) >> > Of cause, this may not be without drawbacks (not 100% about for >> > example >> > community integrity). >> > Also git does not have the adoption svn has, yet. >> > 3. >> > How could that work ? >> > Well, existing projects can be imported with full history. The svn >> > repo >> > should then be removed, a README file pointing to the new repo should >> > replace it. >> > Documentation,Mailinglist,Issues,CI build, Releases using >> > [1]oss.sonatype.org all that will stay the same. >> > In order to test what i ask for, there is already a github >> > organization >> > account "OPS4J" with some pax projects imported. [2] >> > Tell me what you guys think! >> > Toni >> > [1] [2]http://github.com/blog/674-introducing-organizations >> > [2] [3]http://github.com/ops4j >> > -- >> > Toni Menzel || [4]http://okidokiteam.com >> > >> > References >> > >> > 1. http://oss.sonatype.org/ >> > 2. http://github.com/blog/674-introducing-organizations >> > 3. http://github.com/ops4j >> > 4. http://okidokiteam.com/ >> > _______________________________________________ >> > general mailing list >> > general@lists.ops4j.org >> > http://lists.ops4j.org/mailman/listinfo/general >> > > > > -- > Toni Menzel || http://okidokiteam.com > > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > > _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
