Synopsis: java/eclipse: plugins doesn't work in eclipse-3.5.2_1
State-Changed-From-To: open->closed
State-Changed-By: glewis
State-Changed-When: Tue Jan 4 06:21:47 UTC 2011
State-Changed-Why:
This seems to work with 3.6.2, the current version of the eclipse port, so
I'm closing t
49704 eclipsejava/eclipse: plugins doesn't work in
eclipse-3.5.2_1
o ports/149513 eclipsejava/eclipse can not compile with
'WITH_TESTS=true'
o ports/135467 eclipsecan not build java/eclipse with
WITHOUT_MOZILLA=yes W
In there aren't strong objections in the next days I'm going to commit
the following patchset:
http://www.alexdupre.com/eclipse.diff
What it does:
- add a common makefile (eclipse/Makefile.plugins) to simplify
installing eclipse plugins
- use the correct/recommended equinox dropins
The following reply was made to PR ports/149704; it has been noted by GNATS.
From: aditya sarawgi
To: bug-follo...@freebsd.org, mitchn...@gmail.com, zhoushu...@gmail.com
Cc:
Subject: Re: ports/149704: java/eclipse: plugins doesn't work in eclipse-3.5.2_1
Date: Wed, 18 Aug 2010 00:11:39
The following reply was made to PR ports/149704; it has been noted by GNATS.
From: Mark Linimon
To: bug-follo...@freebsd.org
Cc:
Subject: Re: ports/149704: java/eclipse: plugins doesn't work in
eclipse-3.5.2_1
Date: Mon, 16 Aug 2010 17:07:20 -0500
- Forwarded message from
rk in eclipse-3.5.2_1
New Synopsis: java/eclipse: plugins doesn't work in eclipse-3.5.2_1
Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-eclipse
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon Aug 16 15:49:16 UTC 2010
Responsible-Changed-Why:
Fix synopsis and assign.
I encountered this issue too, so when I upgrade the eclipse-webtools
port, I installed them into the dropins
directory(/usr/local/lib/eclipse/dropins), see PR 148992.
On Mon, Aug 16, 2010 at 11:50 PM, wrote:
> Old Synopsis: plugins doesn't work in eclipse-3.5.2_1
> New Synopsis: j
Old Synopsis: plugins doesn't work in eclipse-3.5.2_1
New Synopsis: java/eclipse: plugins doesn't work in eclipse-3.5.2_1
Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-eclipse
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon Aug 16 15:49:16 UTC 2010
Responsibl
of value out
>> of having FreeBSD ports for those plugins that we do have and why?
>
> IIRC, in the original discussion we wanted to get rid of all eclipse
> plugins as ports and use Eclipse's plugin management system. However there
> were some patches against some of these pl
he original discussion we wanted to get rid of all eclipse
plugins as ports and use Eclipse's plugin management system. However there
were some patches against some of these plugins. My suggestion was to push
those patches upstream and remove the plugins from our ports.
As to the removal of o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Lewis wrote:
> G'day all,
>
> I'm looking into a problem with one of the Eclipse plugin ports and I have
> to say that I wonder why we bother having plugin ports. Eclipse has good
> built in plugin management tools, so the only reason I can see
Greg Lewis wrote:
> G'day all,
>
> I'm looking into a problem with one of the Eclipse plugin ports and I have
> to say that I wonder why we bother having plugin ports. Eclipse has good
> built in plugin management tools, so the only reason I can see for having
> a port for one is if there is some
G'day all,
I'm looking into a problem with one of the Eclipse plugin ports and I have
to say that I wonder why we bother having plugin ports. Eclipse has good
built in plugin management tools, so the only reason I can see for having
a port for one is if there is some code that needs changes (and
o:[EMAIL PROTECTED]
Sent: Monday, May 12, 2008 10:11 AM
To: Ware, Ryan R
Cc: freebsd-eclipse@freebsd.org
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
f 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
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
16 matches
Mail list logo
