Voting aside, it’s really up to the
projects that own those directories to clean them up since they’re the
ones that need to make sure their build scripts continue to work and that their
developers’ don’t get hosed. Is someone willing to co-ordinate
this, especially with TPTP who left their, uh, stuff behind…
From:
tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx] On Behalf Of Mik Kersten
Sent: Friday, July 06, 2007 3:52
PM
To: 'Tools
PMC mailing list'
Subject: RE: [tools-pmc] Tools
Plug-in location reorganization
+1 (just in case my
long-winded reply was not clear).
Note that in my
message below I meant to say “root directory/module per-project setup
that
the *Technology*
Project is using has some very good advantages”.
Mik
From: Jeff McAffer [mailto:Jeff_McAffer@xxxxxxxxxx]
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.
Jeff
|
"Mik Kersten"
<mik@xxxxxxxxxxx>
Sent
by: tools-pmc-bounces@xxxxxxxxxxx
07/06/2007
02:00 PM
|
Please respond
to
mik@xxxxxxxxxxx; Please respond to
Tools PMC mailing list <tools-pmc@xxxxxxxxxxx>
|
|
|
To
|
"'Tools PMC mailing list'"
<tools-pmc@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
|
RE: [tools-pmc] Tools Plug-in location reorganization
|
|
++1
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 out the
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
https://bugs.eclipse.org/bugs/show_bug.cgi?id=195682
While Doug's repository per project suggestion
also seems worth exploring
for similar reasons, I that the root
directory/module per-project setup that
the Tools Project has some very good advantages,
e.g.:
1) Much easier for integrators and potential
contributors to browse. On
Mylyn we also heavily on project sets but
there are still times where the
repository needs to be browsed. Seeing the
10 tools projects as top-level
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 someone can
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 structuring, and
project sets can be used to ensure an easy
checkout no matter what the
structure.
Mik
> -----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.
>
> Greg
>
> On Jul 6, 2007, at 9:08 AM, Doug Schaefer wrote:
>
> > That's great point. I'm lucky that cdt
falls alphabetically ahead of
> > 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 when
> > 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 a
> > top level
> > repository if they wish. This makes
sense for a lot of subprojects,
> > especially those in Tools and Technology
that aren't related to
> > each other
> > and don't share committers and where the
shared cvsroot is somewhat
> > 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 all
> >> the tools
> >> projects. "We sure get tired of
scrolling through all those old
> >> hyadies
> >> directories :) "
> >>
> >> For example, compare the top level
list for
> >>
http://dev.eclipse.org/viewcvs/index.cgi/?root=Technology_Project to
> >> 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@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/tools-pmc
_______________________________________________
tools-pmc mailing list
tools-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tools-pmc
|
