Moving eclipse-devel to eclipse

[George Neville-Neil]

On Aug 18, 2013, at 20:23 , huanghwh <huanghwh at yahoo.com> wrote:

> Hi,
> 
> On 2013/08/19 04:07, George Neville-Neil wrote:
> 
> This work is nearly done.  I've tested locally and the new eclipse, formerly eclipse-devel, installs and runs.
> Since this is now going to be eclipse instead of devel I am planning to commit this port with 
> a .1  PORTREVISION.  That would make eclipse show up as: eclipse-4.2.0_1 Does that make sense to everyone?
> I often used eclipse-devel and got two main problems of our eclipse-devel:
> 
> 1.  eclipse is very slow switching editors, especially XML: https://bugs.eclipse.org/bugs/show_bug.cgi?id=391868
> 2.  If install EMF SDK from juno repository, all of installed
>    plug-in will be disable.
> 
>  Maybe the better way is:  Switch to eclipse from eclipse-devel
>    after eclipse-devel upgrade to 4.2.2 or 4.3.

Have you filed PRs for these issues?  The first issue has a patch available so that could be applied in the
eclipse area after the move.  The second one I don't anything about.  Has it been discussed here before?

I'd like to get eclipse out of the way as it's very very old, and then fix bugs in the new eclipse while porting
the newest eclipse-devel.  I do not want to block the move on bugs that have patches.

Best,
George