Eclipse Plugins

[Ware, Ryan R]

Let's get this discussion on its own thread.  The questions I have are:

 

*       Do any of the plugin ports add significant functionality for
FreeBSD?

*       Do we want to be in the business of maintaining ports for each
and every Eclipse plugin?

 

For the first, I'm only personally familiar with the CDT port and must
say that the modifications from the generic CDT source are quite small.
In fact, most of the patches are there simply to change any references
from "Linux" to "FreeBSD" which I would suggest isn't the best way to
include this.  I'd actually think the best way to handle this is to get
the appropriate changes added in upstream, but that might be a bit more
of a philosophical discussion.  Regardless, one problem with porting CDT
to the latest version for 3.3.x is that they no longer keep snapshots
available via FTP.  They are only available via svn.  I imagine that
ports has a way of dealing with that, but I haven't seen an example yet.

 

Second, I wouldn't think the FreeBSD community wouldn't want to be in
the business of keeping ports for each potential Eclipse plugin.  That
said, I don't have the history to know why it happened in the first
place.  If the plugin ports continue to be maintained, I think a hard
look would need to be taken to determine what qualifies a plugin to be
included as a port.  I could understand if the particular plugin just
simply won't work under FreeBSD if installed from the Eclipse updater.
However, in the case of something like CDT, it would seem to be more of
a problem then it is worth.

 

What do others think?

 

Ryan

_______________________________________________
freebsd-eclipse@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-eclipse
To unsubscribe, send any mail to "freebsd-eclipse-unsubscribe@..."

[Rick C. Petty-3]

On Sun, May 11, 2008 at 12:34:15PM -0700, Ware, Ryan R wrote:
> Let's get this discussion on its own thread.  The questions I have are:
>
> *       Do any of the plugin ports add significant functionality for
> FreeBSD?

After a quick look through all the eclipse-* ports, none of them seem to do
anything FreeBSD-specific.  Only eclipse-cdt has patches.  CDT had a few
minor tweaks that should probably be pushed upstream.  Don't forget that
there are other eclipse plugins not in the java directory (I only know of
subclipse).

> *       Do we want to be in the business of maintaining ports for each
> and every Eclipse plugin?

Absolutely not, if it can be helped.

> Regardless, one problem with porting CDT
> to the latest version for 3.3.x is that they no longer keep snapshots
> available via FTP.  They are only available via svn.  I imagine that
> ports has a way of dealing with that, but I haven't seen an example yet.

There are examples; just make the port have a build dependency on
subversion and do a checkout on a specific rev.  This may be the only way
to get the source for some plugins.

> Second, I wouldn't think the FreeBSD community wouldn't want to be in
> the business of keeping ports for each potential Eclipse plugin.  That

I'm confused by your double negative.  I would say that we want to minimize
the number of ports and rely upon eclipse's plugin mechanism for the rest.
In the past I've had troubles with their upgrades, but any problems we find
should be fixed and pushed upstream.

-- Rick C. Petty
_______________________________________________
freebsd-eclipse@... mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-eclipse
To unsubscribe, send any mail to "freebsd-eclipse-unsubscribe@..."

[Ware, Ryan R]

Oops.  Sorry for the double negative.  The second "wouldn't" should have
been a "would".  That should teach me to try and write something
intelligible when my daughters are running around like banshees.  ;-)

Ryan

-----Original Message-----
From: Rick C. Petty [mailto:rick-freebsd@...]
Sent: Monday, May 12, 2008 10:11 AM
To: Ware, Ryan R
Cc: freebsd-eclipse@...
Subject: Re: Eclipse Plugins

On Sun, May 11, 2008 at 12:34:15PM -0700, Ware, Ryan R wrote:
> Let's get this discussion on its own thread.  The questions I have are:
>
> *       Do any of the plugin ports add significant functionality for
> FreeBSD?

After a quick look through all the eclipse-* ports, none of them seem to do
anything FreeBSD-specific.  Only eclipse-cdt has patches.  CDT had a few
minor tweaks that should probably be pushed upstream.  Don't forget that
there are other eclipse plugins not in the java directory (I only know of
subclipse).

> *       Do we want to be in the business of maintaining ports for each
> and every Eclipse plugin?

Absolutely not, if it can be helped.

> Regardless, one problem with porting CDT
> to the latest version for 3.3.x is that they no longer keep snapshots
> available via FTP.  They are only available via svn.  I imagine that
> ports has a way of dealing with that, but I haven't seen an example yet.

There are examples; just make the port have a build dependency on
subversion and do a checkout on a specific rev.  This may be the only way
to get the source for some plugins.

> Second, I wouldn't think the FreeBSD community wouldn't want to be in
> the business of keeping ports for each potential Eclipse plugin.  That

I'm confused by your double negative.  I would say that we want to minimize
the number of ports and rely upon eclipse's plugin mechanism for the rest.
In the past I've had troubles with their upgrades, but any problems we find
should be fixed and pushed upstream.

-- Rick C. Petty