回复： Moving eclipse-devel to eclipse

[huanghwh]

________________________________
 发件人： George Neville-Neil <gnn at neville-neil.com>
收件人： huanghwh <huanghwh at yahoo.com> 
抄送： "eclipse at freebsd.org" <eclipse at freebsd.org> 
发送日期： 2013年8月19日, 星期一, 10:58 上午
主题: Re: Moving eclipse-devel to eclipse
 


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?
NO, I suppose no way to fixed it except upgrade to 4.2.2 as our eclipse-devel use old 
version EMF  Core Runtime 2.8.0,  I will filed PR anyway.
>
>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.
OK.

Cheers,
--hwh