On Wed, Feb 20, 2008 at 01:13:04PM +0900, ken wrote:
> Yea, I am surviving...
> I am using it and touching it every time I have a
problem. So, it is a turtle walk...
> About plugins;
> I know that JBossTools GUI which requires newer
version of xulrunner does not work properly. Also, GUI
editor of eclipse may/may not work. I am not sure if it is
updated recently or not, though.
>
> I understand that Eclipse schedules to update every
spring and fall. And next version for spring will be 3.4
(now it is 3.4M5). So, we may better settle the port before
the new release comes in.
Unless there are other showstoppers, I would agree that its
about time to
move 3.3.1 from eclipse-devel to eclipse. That will trigger
problems with
many of the plugins though, so there is more work here than
just moving
a single port over. What we need is to get people to
volunteer to try and
build all plugins to check whether they fail (at least) and
then hopefully
update/fix them (or mark them broken if noone is interested
in fixing
them).
> I see that we have emacs (22), emacs21 and
emacs-devel in /usr/ports/editors, and I feel that it is
suggestiong the way we manage eclipse under /usr/ports/java
- current version = eclipse, previous version = eclipseXX,
and next version = eclipse-devel.
Implicit in this is that you'd need to maintain multiple
versions of some
of the plugins, so you're proposing more than 3 ports here.
The question
this raises for me is whether there are enough people active
in ports who
are interested enough in Eclipse that they're prepared to
commit to this.
If there aren't I would suggest sticking with the current
model.
--
Greg Lewis Email : glewis eyesbeyond.com
Eyes Beyond Web : http://www.eyesbeyond.com
Information Technology FreeBSD : glewisFreeBSD.org
_______________________________________________
freebsd-eclipsefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-eclip
se
To unsubscribe, send any mail to
"freebsd-eclipse-unsubscribefreebsd.org"
|
