Hi Denis, " • More • 42127 • changed 73 files • trunk renamed org.jboss.tests.tests to org.jboss.tests.test to follow the common name pattern for test plugins. it also included into feature for consistency " Do we really need to rename this ? And without warning ? Everyone needs to exit their eclipse if they have this loaded and then do svn update otherwise everything will look like it is still there because eclipse will create the project dirs if deleted under it. Please - lets not rename plugins "just for fun" and without warning! /max

Hi Max, I dunno if it helps you with the eclipse update dance...

I wrote a plugin which adds a button to the Package Explorer view ... 1) Click the button and file dialog is displayed. 2) Select codebase repository working directory. 3) All projects in workspace are synchronized against selected directory. * Any new projects in the selected directory are added to the workspace; * Invalid projects (deleted) are removed from the workspace; * Projects moved into working sets named by the parent directory of the plugin. This works for me but might not be appropriate for you.

Interested to hear feedback and whether it is useful to people...

My Update Site http://www.phantomjinx.co.uk/org.phantomjinx.site Regards PGR -- Paul Richardson (a.k.a. phantomjinx) * p.g.richardson(a)redhat.com * pgrichardson(a)linux.com * mob: +44 (0)9780 869490

Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: > Hi Max, > > I dunno if it helps you with the eclipse update dance... It sounds interesting - I will try it out once I got a minute free! > > I wrote a plugin which adds a button to the Package Explorer view ... > > 1) Click the button and file dialog is displayed. > 2) Select codebase repository working directory. > 3) All projects in workspace are synchronized against selected directory. > * Any new projects in the selected directory are added to the workspace; > * Invalid projects (deleted) are removed from the workspace; > * Projects moved into working sets named by the parent directory of > the plugin. This works for me but might not be appropriate for you. I actually implemented a similar idea but based on a regular expression for the project name; for us it would have to be the ../../ since we have things in features/plugins... > Interested to hear feedback and whether it is useful to people... I'll definitely try it out - thanks for the tip! is the code available somewhere too? > > My Update Site > http://www.phantomjinx.co.uk/org.phantomjinx.site > > Regards > > PGR > > -- > Paul Richardson (a.k.a. phantomjinx) > > * p.g.richardson(a)redhat.com > * pgrichardson(a)linux.com > * mob: +44 (0)9780 869490 > ------------------------------------------------------------------------ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev Only on my machine but I'll push it to github over the weekend. PGR