Re: java/eclipse and jdk1.6

ken wrote:
>   Mike,
>   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.  
>   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.
> 
> 

Ken,

That sounds like a reasonable proposition and clearly it's a
model 
already in use.  IIRC, there was also mention previously of
moving all 
of the "eclipse bits" to /usr/ports/eclipse...
although it's late and 
the details escape me at this moment.  I think perhaps Dan
suggested 
it... I'll have to scan the archives.  (Or someone can chime
in.) 
Perhaps this is something that could be considered at the
same time, if 
changes are being made.

I'll give 3.3.1.1 a try tomorrow at the office and will let
you know how 
it goes!

Thanks for your superb work... I for one am most
appreciative!

Mike.
_______________________________________________
freebsd-eclipsefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-eclip
se
To unsubscribe, send any mail to
"freebsd-eclipse-unsubscribefreebsd.org"

Mike Bowie wrote:
> Ken,
> 
> That sounds like a reasonable proposition and clearly
it's a model 
> already in use.  IIRC, there was also mention
previously of moving all 
> of the "eclipse bits" to
/usr/ports/eclipse... although it's late and 
> the details escape me at this moment.  I think perhaps
Dan suggested 
> it... I'll have to scan the archives.  (Or someone can
chime in.) 
> Perhaps this is something that could be considered at
the same time, if 
> changes are being made.

Well my 2 cents..

An argument against retaining java as the main category for
eclipse and 
most of its plugins. The porters handbook suggests using
ports/java/ as 
the main category for ports directly related to the java
language [1].

With that said, the main category for the base eclipse ports
would 
probably go in devel. Ports like those related to
sql/databases could 
have their main category be set as database and the  pydev
eclipse 
feature in python, etc.

Although it follows the suggestion of  the handbook, we are
then losing 
our neat folder containing _almost_ all of the eclipse
ports, which 
could be viewed as a regression.

Checking how something like zope handles this, they mention
zope as 
their second category, this doesn't create a zope/ folder in
my ports 
directory but the category is created on the website so
perhaps theres a 
way to access this directly on the system as well.

In any case, theres about 40 ports related to eclipse, it
wouldn't be 
the smallest category.

Is there a guideline for what justifies a new category?


[1] 
http://www.freebsd.org
/doc/en_US.ISO8859-1/books/porters-handbook/makefile-categor
ies.html
_______________________________________________
freebsd-eclipsefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-eclip
se
To unsubscribe, send any mail to
"freebsd-eclipse-unsubscribefreebsd.org"