[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mylyn-reviews-dev] Git structure
|
+1 for the second option, but if it's built with Maven we should avoid
nested POMs (confuses users and some functionality in Eclipse).
On Fri, Oct 8, 2010 at 9:40 AM, Lohre, Jan <jan.lohre@xxxxxxx> wrote:
> +1 for the second option. In particular if we will build with maven / tycho.
>
>> -----Original Message-----
>> From: mylyn-reviews-dev-bounces@xxxxxxxxxxx [mailto:mylyn-reviews-dev-
>> bounces@xxxxxxxxxxx] On Behalf Of Kilian Matt
>> Sent: Donnerstag, 7. Oktober 2010 22:29
>> To: mylyn-reviews-dev
>> Subject: [mylyn-reviews-dev] Git structure
>>
>> Hi,
>>
>> as we soon have a few more projects in our git repository, I would
>> like to ask, what structure is preferred.
>>
>> flat: all eclipse projects in one directory
>> e.g.
>> /org.eclipse.mylyn.reviews.framework
>> /org.eclipse.mylyn.reviews.gerrit.core
>> /org.eclipse.mylyn.reviews.gerrit.ui
>> ...
>>
>> nested: one directory for each (sub)project containing its eclipse
>> projects
>> /tbr/org.eclipse.mylyn.reviews.tbr.core
>> /tbr/org.eclipse.mylyn.reviews.tbr.ui
>> /framework + subfolders
>>
>>
>> With the flat structure it's maybe easier to check the whole project
>> out at once, while the second one is a bit more organized and more
>> suitable for maven tycho.
>>
>> Kilian
>> _______________________________________________
>> mylyn-reviews-dev mailing list
>> mylyn-reviews-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/mylyn-reviews-dev
> _______________________________________________
> mylyn-reviews-dev mailing list
> mylyn-reviews-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/mylyn-reviews-dev
>
