Date: Mon, 28 Aug 2006 22:22:36 -0700 From: Sean McNeil <sean@mcneil.com> To: Norberto Meijome <freebsd@meijome.net> Cc: freebsd-java@freebsd.org, Ronald Klop <ronald-freebsd8@klop.yi.org> Subject: Re: Q) eclipse 3.2 (Callisto) Message-ID: <1156828956.62479.4.camel@triton.mcneil.com> In-Reply-To: <20060829150400.739ae7d2@localhost> References: <970c0a6b0607280839qc05e2b8p51118955745b7cda@mail.gmail.com> <20060828161538.GI89053@vision.anyware> <44F332FF.5050809@appriss.com> <op.te0bpbbu8527sy@guido.klop.ws> <20060829150400.739ae7d2@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2006-08-29 at 15:04 +1000, Norberto Meijome wrote: > On Mon, 28 Aug 2006 20:45:01 +0200 > "Ronald Klop" <ronald-freebsd8@klop.yi.org> wrote: > > > Maybe it is possible to repocopy eclipse to eclipse31. And change the > > depending ports for the new location. > > Just an idea. Don't know how much work it is. > > or, given that most ports that depend on 3.1.2 wont work out of the box with > 3.2 , just call this one eclipse32 ? > > I remember seeing an email on this list suggesting against doing any of > this.... but IMVHO, is better to have both out there and then have a reason to > upgrade all the plugins ... otherwise I can see we may have a gap when we have > java/eclipse (3.2) but no compatible plugins available yet.... The big problem that I see is there are a number of plugins that have decayed and no longer install. At lease I've seen posts to eclipse@ about this. Perhaps they have been updated by now, but what I saw was that the download was no longer valid. If this is the case, then just update them all to 3.2 or compatible. If there is enough interest, then make an eclipse31. But it seems like it will just get harder to maintain the older version as time marches on.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1156828956.62479.4.camel>