From: Jeff McAffer
Sent: Friday, July 06, 2007 12:39 PM
To: mik@xxxxxxxxxxx; Tools PMC mailing list
Subject: RE: [tools-pmc] Tools Plug-in location reorganization
I was unclear
with my previous approval. I think we should have one top level
*directory* per project in the Tools project.
Please respond to
mik@xxxxxxxxxxx; Please respond to
Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>
PMC mailing list'" <tools-pmc@xxxxxxxxxxx>
[tools-pmc] Tools Plug-in location reorganization
I didn't to start out by complaining when Mylyn first moved, but I found
this problematic when we moved from Technology and all of the Mylyn
committers complained about this too. In case anyone wants to point
irony about me complaining about a scrollbar in any Eclipse view, we now
have a bug for this :)
195682: add focus to the CVS Repositories view
While Doug's repository per project suggestion also seems worth exploring
for similar reasons, I that the root directory/module per-project setup
the Tools Project has some very good advantages, e.g.:
1) Much easier for integrators and potential contributors to browse.
Mylyn we also heavily on project sets but there are still times where
repository needs to be browsed. Seeing the 10 tools projects as
directory under /cvsroot/tools will make the structure of the Tools Project
explicit in CVS.
2) One project with many plug-ins doesn't dominate the repository. As
pointed out by Greg makes projects below it painful to get to.
3) Projects can decide on how they structure the contents in their
directory. On Mylyn we have opted for a flat structure so that
check out everything in our root and end up with a workspace that has no
errors or warnings. But there are also benefits to the GEF
project sets can be used to ensure an easy checkout no matter what the
> -----Original Message-----
> From: tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-
> bounces@xxxxxxxxxxx] On Behalf Of Greg Watson
> Sent: Friday, July 06, 2007 8:40 AM
> To: Tools PMC mailing list
> Subject: Re: [tools-pmc] Tools Plug-in location reorganization
> As a plugin that falls alphabetically *after* hyadies (and cdt :-)),
> we would heartily support such a cleanup.
> On Jul 6, 2007, at 9:08 AM, Doug Schaefer wrote:
> > That's great point. I'm lucky that cdt falls alphabetically ahead
> > hyadies. But in general this is a mess across all of eclipse.
> > I think though, practically, it needs to be up to the projects
> > themselves to
> > initiate this change, just as you did with GEF, and as we did
> > we moved
> > the CDT plugins off of the /tools root into a cdt folder.
> > One thing I would suggest, though is to allow each project to be
> > top level
> > repository if they wish. This makes sense for a lot of
> > especially those in Tools and Technology that aren't related to
> > each other
> > and don't share committers and where the shared cvsroot is
> > artificial. That way projects below hyadies just leave the tools
> > cvsroot all
> > together. Maybe we can bring that up with the EMO.
> > Doug Schaefer, QNX Software Systems
> > Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
> >> -----Original Message-----
> >> From: tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-
> >> bounces@xxxxxxxxxxx]
> >> On Behalf Of Anthony Hunter
> >> Sent: Friday, July 06, 2007 10:20 AM
> >> To: tools-pmc@xxxxxxxxxxx
> >> Subject: [tools-pmc] Tools Plug-in location reorganization
> >> Hi Team,
> >> I just completed https://bugs.eclipse.org/bugs/show_bug.cgi?
> >> id=195565 for
> >> GEF.
> >> David Williams suggested that we should do this cleanup for
> >> the tools
> >> projects. "We sure get tired of scrolling through all
> >> hyadies
> >> directories :) "
> >> For example, compare the top level list for
> >> http://dev.eclipse.org/viewcvs/index.cgi/?root=Technology_Project
> >> http://dev.eclipse.org/viewcvs/index.cgi/?root=Tools_Project
> >> Cheers...
> >> Anthony
> >> --
> >> Anthony Hunter mailto:anthonyh@xxxxxxxxxx
> >> Software Development Manager: Eclipse Open Source Components
> >> IBM Rational Software: Aurora / Modeling Tools
> >> Phone: 613-591-7037
> >> _______________________________________________
> >> tools-pmc mailing list
> >> tools-pmc@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/tools-pmc
> > _______________________________________________
> > tools-pmc mailing list
> > tools-pmc@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/tools-pmc
> tools-pmc mailing list
tools-pmc mailing list