Date: Sat, 21 Oct 2006 03:00:45 GMT From: "David Sledge" <dsledge@appriss.com> To: freebsd-ports-bugs@FreeBSD.org Subject: RE: ports/102993: New port: java/eclipse32 New port of Eclipse IDE version 3.2 Message-ID: <200610210300.k9L30jBL008281@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/102993; it has been noted by GNATS. From: "David Sledge" <dsledge@appriss.com> To: "Mikhail Teterin" <mi+mx@aldan.algebra.com>, <bug-followup@freebsd.org> Cc: Subject: RE: ports/102993: New port: java/eclipse32 New port of Eclipse IDE version 3.2 Date: Fri, 20 Oct 2006 22:54:12 -0400 This is a multi-part message in MIME format. ------_=_NextPart_001_01C6F4BC.2FEEAB9B Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -----Original Message----- From: Mikhail Teterin [mailto:mi+mx@aldan.algebra.com] Sent: Fri 10/20/2006 1:13 PM To: bug-followup@freebsd.org; David Sledge Subject: Re: ports/102993: New port: java/eclipse32 New port of Eclipse = IDE version 3.2 =20 > We need to keep the existing Eclipse IDE version 3.1.2 port = (java/eclipse) > as many other ports depend on it. The other ports will need to be fixed/updated anyway -- we are not going = to=20 keep eclipse-3.1 around forever... How bad is the problem? -mi The only problem is that a majority of the eclipse dependent ports are = owned by freebsd-eclipse which basically means their is no maintainer = for them. That is why it would be hard to update them all at the same = time. After some talk on the mailing list I think I am going to have = this PR closed and submit a new PR to have the existing eclipse port = (java/eclipse) updated to the 3.2.1 version of eclipse that I have = almost finished. This will break some of the other ports but will force = some of the developers that want to use them to update them. In the = transition people could use the plugin manager in eclipse to download = and install the plugins they need. I have tried several and have not = seen a problem with the plugins downloaded by the eclipse plugin = manager. ------_=_NextPart_001_01C6F4BC.2FEEAB9B Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Diso-8859-1"> <META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version = 6.5.7638.1"> <TITLE>RE: ports/102993: New port: java/eclipse32 New port of Eclipse = IDE version 3.2</TITLE> </HEAD> <BODY> <!-- Converted from text/plain format --> <BR> <BR> <BR> <P><FONT SIZE=3D2>-----Original Message-----<BR> From: Mikhail Teterin [<A = HREF=3D"mailto:mi+mx@aldan.algebra.com">mailto:mi+mx@aldan.algebra.com</A= >]<BR> Sent: Fri 10/20/2006 1:13 PM<BR> To: bug-followup@freebsd.org; David Sledge<BR> Subject: Re: ports/102993: New port: java/eclipse32 New port of Eclipse = IDE version 3.2<BR> <BR> > We need to keep the existing Eclipse IDE version 3.1.2 port = (java/eclipse)<BR> > as many other ports depend on it.<BR> <BR> The other ports will need to be fixed/updated anyway -- we are not going = to<BR> keep eclipse-3.1 around forever...<BR> <BR> How bad is the problem?<BR> <BR> -mi<BR> <BR> <BR> The only problem is that a majority of the eclipse dependent ports are = owned by freebsd-eclipse which basically means their is no maintainer = for them. That is why it would be hard to update them all at the same = time. After some talk on the mailing list I think I am going to have = this PR closed and submit a new PR to have the existing eclipse port = (java/eclipse) updated to the 3.2.1 version of eclipse that I have = almost finished. This will break some of the other ports but will force = some of the developers that want to use them to update them. In the = transition people could use the plugin manager in eclipse to download = and install the plugins they need. I have tried several and have not = seen a problem with the plugins downloaded by the eclipse plugin = manager.</FONT></P> </BODY> </HTML> ------_=_NextPart_001_01C6F4BC.2FEEAB9B--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610210300.k9L30jBL008281>