+1 for option 3.
I would also suggest moving any 'non-UI e4-tools' code into a separate package for future management, as it might not be appropriate in a *.ui project.
Has anyone looked in the the dependency overlap between e4-tools and the other projects. I think this is more of an issue then 'commiter overlap'. In my experience, the dependencies usually spell out where a code-base should live.
Steven Spungin
TwelveTone LLC
From: "Olivier Prouvost" <olivier.prouvost@xxxxxxxxxxx>
To: "E4 Project developer mailing list" <e4-dev@xxxxxxxxxxx>
Sent: Tuesday, September 16, 2014 3:35:48 AM
Subject: Re: [e4-dev] Moving e4 tools to a new project?
+1 for me
+1
Do Gerrit reviews count as well?
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/e4-dev
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/e4-dev