Date: Mon, 19 Aug 2013 21:35:57 -0400 From: George Neville-Neil <gnn@neville-neil.com> To: huanghwh <huanghwh@yahoo.com> Cc: "eclipse@freebsd.org" <eclipse@freebsd.org> Subject: =?utf-8?Q?Re=3A_=E5=9B=9E=E5=A4=8D=EF=BC=9A_Moving_eclipse-devel?= =?utf-8?Q?_to_eclipse?= Message-ID: <1AEFA579-91DB-4436-8FB2-27234EEC3AC9@neville-neil.com> In-Reply-To: <1376899438.36396.YahooMailNeo@web15304.mail.cnb.yahoo.com> References: <1376871829.53222.YahooMailNeo@web15306.mail.cnb.yahoo.com> <DA3E520F-6E73-46F8-8A7F-54F2576AF2B2@neville-neil.com> <1376899438.36396.YahooMailNeo@web15304.mail.cnb.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 19, 2013, at 4:03 , huanghwh <huanghwh@yahoo.com> wrote: >=20 >=20 >=20 >=20 > ________________________________ > =E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9A George Neville-Neil = <gnn@neville-neil.com> > =E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9A huanghwh <huanghwh@yahoo.com>=20 > =E6=8A=84=E9=80=81=EF=BC=9A "eclipse@freebsd.org" = <eclipse@freebsd.org>=20 > =E5=8F=91=E9=80=81=E6=97=A5=E6=9C=9F=EF=BC=9A 2013=E5=B9=B48=E6=9C=8819=E6= =97=A5, =E6=98=9F=E6=9C=9F=E4=B8=80, 10:58 =E4=B8=8A=E5=8D=88 > =E4=B8=BB=E9=A2=98: Re: Moving eclipse-devel to eclipse >=20 >=20 >=20 > On Aug 18, 2013, at 20:23 , huanghwh <huanghwh@yahoo.com> wrote: >=20 >>> Hi, >>>=20 >>> On 2013/08/19 04:07, George Neville-Neil wrote: >>>=20 >>> 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=20 >>> 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: >>>=20 >>> 1. eclipse is very slow switching editors, especially XML: = https://bugs.eclipse.org/bugs/show_bug.cgi?id=3D391868 >>> 2. If install EMF SDK from juno repository, all of installed >>> plug-in will be disable. >>>=20 >>> Maybe the better way is: Switch to eclipse from eclipse-devel >>> after eclipse-devel upgrade to 4.2.2 or 4.3. >>=20 >> 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=20 > version EMF Core Runtime 2.8.0, I will filed PR anyway. >>=20 >> 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. OK, it's all on my todo list. Best, George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1AEFA579-91DB-4436-8FB2-27234EEC3AC9>