Thanks for that advice, John. I completely agree with it. I am actually trying to avoid as much as possible to fracture my project's code base into multiple repositories for exactly the reasons you cite :) .
Unfortunately, we may not be able to avoid it in this case because the code we're trying to integrate (and yet make independently available) is quite small in comparison to the size of the overall project, and cloning time is a major concern for this scenario. We're trying to find ways to have our project development occur universally in the main repository while using the secondary repo as a vehicle to streamline clone time for that particular piece. Mark Stoodley 8200 Warden Avenue Senior Software Developer Markham, L6G 1C7 IBM Runtime Technologies Canada Phone: +1-905-413-5831 e-mail: [email protected] We cannot solve our problems with the same thinking we used when we created them - Albert Einstein From: John Arthorne <[email protected]> To: Discussions for new Eclipse projects <[email protected]> Date: 2016/03/22 01:04 PM Subject: Re: [incubation] possible for one project to have multiple git repositories? Sent by: [email protected] FWIW, keep in mind that having multiple repositories can create additional work for the committers on the project, and confusion for consumers as well. There are certainly good use cases for it, but I think there are benefits to consolidating as much as possible. I know in Orion project it was a burden to have multiple repositories connected in a single CI, multiple repositories to tag with releases, multiple commits needed when a change spans repositories, multiple readme files to maintain, etc. It is perfectly allowed but my experience has been that generally less repositories is better. John On Tue, Mar 22, 2016 at 11:25 AM, Roger Light <[email protected]> wrote: Hi Mark, As a fairly extreme example (I presume), the Paho project has 11 repositories on github and I don't believe all of the project repos have been migrated. https://github.com/eclipse/?utf8=%E2%9C%93&query=paho Cheers, Roger On Tue, Mar 22, 2016 at 1:40 PM, Mark Stoodley <[email protected]> wrote: A use case has come up for the OMR project where we have a significant piece of functionality that could be consumed both as part of the OMR project but also independently of the rest of the OMR project. The easiest way to manage that would probably be to have it reside in its own git repository, although we haven't decided 100% that's the way to go. Just testing the waters on that solution: is it possible for an Eclipse project to have more than one associated git repo? Say eclipse/omr and eclipse/omr/agentcore (where agentcore is the name of the significant piece of functionality). Or is that only possible with top-level projects and then creating a sub-project? Mark Stoodley 8200 Warden Avenue Senior Software Developer Markham, L6G 1C7 IBM Runtime Technologies Canada Phone: +1-905-413-5831 e-mail: [email protected] We cannot solve our problems with the same thinking we used when we created them - Albert Einstein _______________________________________________ incubation mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation _______________________________________________ incubation mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation _______________________________________________ incubation mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation
_______________________________________________ incubation mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation
