Haha for me. I'm just experimenting with GIT for the first time and this repository per module thing has caused me a bit of of head scratching. Maybe I can learn how to do it with my own 40+ modules by watching this thread. :) Sure hope so.
On Wed, Feb 1, 2012 at 10:19 AM, Andreas Pieber <[email protected]> wrote: > Well, I've never tried, but in theory it should also be able to use the > plugin only for subprojects. But I think it would be extremely confusing to > have many tags on one repository. The question is: would it be feasible to > create a new repository for each project? The advantage would be definitely > to be able to use default git/maven methods; the BIG disadvantage would be > that you need administration rights to start such a new project. > > Kind regards, > Andreas > > > On Wed, Feb 1, 2012 at 11:58, Toni Menzel <[email protected]> wrote: > >> FYI, i just draft a wiki site here >> http://team.ops4j.org/wiki/display/ops4j/Pax+Tipi >> >> to pin the stuff we agreed on in this thread. Contribution is highly >> appreciated. >> Keep this discussion up here - i think its just hard to keep up with all >> the information spread over a long conversation. >> >> One special note on Andreas last mail, about the "how to structure the >> source repository keeping the release plugin in mind": its indeed a problem >> we need to solve in a safe way. Actually i think the copy for modification >> solution cannot be the solution. >> - I'd rather bounce on the release plugin (see what can be done there) >> or >> - maybe spread tipi into 4 or 5 sub projects (all repos) grouped after >> some category thinking. Like "bundle origin" (say >> org.ops4j.pax.tipi.apache, and ...eclipse) or group by purpose >> (org.ops4j.pax.tipi.data , org.ops4j.pax.tipi.ui , >> org.ops4j.pax.tipi.testing etc.) >> and then release those groups AS a project. Would give the whole thing a >> possibly more concise end-user experience. On the other hand this depends >> on the grade of changes and possibly just makes sense for artifacts with >> more than just BND descriptors as sources (so for the GREEN labeled stuff >> with OPS4J-made Activators and other code contributions). >> >> I am still really unclear about this. >> Still thinking ;) >> >> >> On Tue, Jan 31, 2012 at 6:04 AM, Andreas Pieber <[email protected]>wrote: >> >>> So, late; but better late than never :-) >>> >>> First of all I really like the idea of pax-tipi. Bundle repository with >>> low entry barriers. This could attract lots of users (and also take some >>> work from the SMX team). Besides it would make it possible to share some of >>> my own work here not really fitting to SMX otherwise. >>> >>
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
