From bugmaster at FreeBSD.org Mon Jun 1 11:06:48 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 1 11:07:38 2009 Subject: Current problem reports assigned to freebsd-eclipse@FreeBSD.org Message-ID: <200906011106.n51B6led021005@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/133457 eclipse [PATCH] java/eclipse-webtools: update to 3.0.3 o ports/133423 eclipse [PATCH] java/eclipse-emf: Update to 2.4.1 o ports/133417 eclipse [PATCH] java/eclipse-gef: update to 3.4.1 3 problems total. From crahman at gmail.com Fri Jun 5 23:33:07 2009 From: crahman at gmail.com (Cyrus Rahman) Date: Fri Jun 5 23:33:39 2009 Subject: RCP Delta Pack files for FreeBSD Message-ID: <9e77bdb50906051605v1a32f047mb5a62f805a97d6f0@mail.gmail.com> I'm trying to get an Eclipse RCP application to run on FreeBSD. It's been set up so that the target platform location has been moved from /usr/local/eclipse to a private directory containing many third party files and within which the distributed delta pack is installed. I can get it to build and run correctly on FreeBSD by copying files from /usr/local/eclipse to the target platform location, namely the *freebsd* files from /usr/local/eclipse/plugins - but only if I use the 'Launch an Eclipse application' approach. If I try to export the application using the export wizard, the export process succeeds but no launcher is present in the export directory. If I copy /usr/local/eclipse/eclipse into the export directory, I can start the application but it complains that MOZILLA_FIVE_HOME cannot be found in the environment and it exits after displaying the splash screen. If I set MOZILLA_FIVE_HOME to either of /usr/local/lib/firefox or /usr/local/lib/firefox3, it runs further but either exits with a java-out-of-memory error or it hangs and must be killed. I am guessing I have not set up the correct environment to run it outside of Eclipse. What do I need to do to generate the FreeBSD portion of a delta pack? It seems like I'm awfully close but that perhaps I'm linking to the wrong library - it is not necessary to set MOZILLA_FIVE_HOME if I export a simple RCP application when the target platform location is /usr/local/eclipse. In this simple case the launcher is correctly copied to the export directory, too. From heiner_ej at yahoo.de Sat Jun 6 17:07:02 2009 From: heiner_ej at yahoo.de (Heiner =?ISO-8859-1?Q?Strau=DF?=) Date: Sat Jun 6 17:07:33 2009 Subject: RCP Delta Pack files for FreeBSD In-Reply-To: <9e77bdb50906051605v1a32f047mb5a62f805a97d6f0@mail.gmail.com> References: <9e77bdb50906051605v1a32f047mb5a62f805a97d6f0@mail.gmail.com> Message-ID: <1244305616.14164.4.camel@think.schlaf.bilch.com> Am Freitag, den 05.06.2009, 17:05 -0600 schrieb Cyrus Rahman: > I'm trying to get an Eclipse RCP application to run on FreeBSD. It's > been set up so that the target platform location has been moved from > /usr/local/eclipse to a private directory containing many third party > files and within which the distributed delta pack is installed. > > I can get it to build and run correctly on FreeBSD by copying files > from /usr/local/eclipse to the target platform location, namely the > *freebsd* files from /usr/local/eclipse/plugins - but only if I use > the 'Launch an Eclipse application' approach. If I try to export the > application using the export wizard, the export process succeeds but > no launcher is present in the export directory. If I copy > /usr/local/eclipse/eclipse into the export directory, I can start the > application but it complains that MOZILLA_FIVE_HOME cannot be found in > the environment and it exits after displaying the splash screen. > > If I set MOZILLA_FIVE_HOME to either of /usr/local/lib/firefox or > /usr/local/lib/firefox3, it runs further but either exits with a > java-out-of-memory error or it hangs and must be killed. > > I am guessing I have not set up the correct environment to run it > outside of Eclipse. What do I need to do to generate the FreeBSD > portion of a delta pack? > > It seems like I'm awfully close but that perhaps I'm linking to the > wrong library - it is not necessary to set MOZILLA_FIVE_HOME if I > export a simple RCP application when the target platform location is > /usr/local/eclipse. > > In this simple case the launcher is correctly copied to the export > directory, too. Hi, when I had complaints about MOZILLA_FIVE_HOME I did this: # # FreeBSD-specific startup script for Eclipse Platform # # See: http://www.eclipse.org # # $FreeBSD: ports/java/eclipse/files/eclipse.in,v 1.12 2009/02/15 03:19:41 glewis Exp $ # DEFAULT_JAVA_HOME=/usr/local ECLIPSE_HOME=/usr/local/eclipse DEFAULT_JAVA_CMD=java MOZILLA_FIVE_HOME=/usr/local/lib/xulrunner LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$MOZILLA_FIVE_HOME export MOZILLA_FIVE_HOME LD_LIBRARY_PATH because firefox3 won't work. You need to install xulrunner from ports. Hope this helps. Greetings, Heiner From crahman at gmail.com Sun Jun 7 08:23:36 2009 From: crahman at gmail.com (Cyrus Rahman) Date: Sun Jun 7 08:23:59 2009 Subject: RCP Delta Pack files for FreeBSD In-Reply-To: <1244305616.14164.4.camel@think.schlaf.bilch.com> References: <9e77bdb50906051605v1a32f047mb5a62f805a97d6f0@mail.gmail.com> <1244305616.14164.4.camel@think.schlaf.bilch.com> Message-ID: <9e77bdb50906070123o2e1e335exd0060cc30c9af034@mail.gmail.com> > Hi, > when I had complaints about MOZILLA_FIVE_HOME I did this: > > # > # FreeBSD-specific startup script for Eclipse Platform > # > # See: http://www.eclipse.org > # > # $FreeBSD: ports/java/eclipse/files/eclipse.in,v 1.12 2009/02/15 > 03:19:41 glewis Exp $ > # > DEFAULT_JAVA_HOME=/usr/local > ECLIPSE_HOME=/usr/local/eclipse > DEFAULT_JAVA_CMD=java > MOZILLA_FIVE_HOME=/usr/local/lib/xulrunner > LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$MOZILLA_FIVE_HOME > export MOZILLA_FIVE_HOME LD_LIBRARY_PATH > > because firefox3 won't work. You need to install xulrunner from ports. > Hope this helps. Thanks for the suggestion, it helped me figure out what was happening. I had a project named 'appname'; it was exported into ~/appname. Because no launcher executable was placed into the exported directory ~/appname/eclipse by the export wizard, I copied /usr/local/eclipse/eclipse there. It started the application, but the application did not work correctly, even though it did work when launched from eclipse itself. As it happens, the problem was that there was a file ~/appname/eclipse/appname.ini which is needed to set the java memory requirements. This file is ignored if the application is launched from a file named 'eclipse'. However, if I instead did: cp /usr/local/eclipse/eclipse ~/appname/eclipse/appname and started the application using that launcher, appname.ini was used and everything worked ok. I did try using xulrunner instead of firefox, but in fact for me both firefox and firefox3 also worked correctly. My application simply wanted a copy of libwidget_gtk2.so to link against; I don't know if exported applications would always work with firefox but I did not, in the end, need xulrunner. So I can successfully start my application now using: MOZILLA_FIVE_HOME=/usr/local/lib/firefox $HOME/appname/eclipse/appname ***** It would be a lot easier to figure out and more generally useful if there were a way of making a delta pack that contained support for FreeBSD. From tomamundsen at gmail.com Sun Jun 7 17:04:03 2009 From: tomamundsen at gmail.com (Thomas Amundsen) Date: Sun Jun 7 17:04:09 2009 Subject: eclipse crashes with intellisense Message-ID: <59a37d400906070939s4183cd09y3dab83296a846a6f@mail.gmail.com> Hi, I installed eclipse on FreeBSD 7.2-RELEASE via the eclipse package (which installs Europa). I am now seeing eclipse crash everytime the intellisense box comes up. This obviously makes eclipse completely unusable for me. Has anyone had this problem before? And know how to fix it? - Tom From bugmaster at FreeBSD.org Mon Jun 8 11:06:50 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 8 11:07:44 2009 Subject: Current problem reports assigned to freebsd-eclipse@FreeBSD.org Message-ID: <200906081106.n58B6nno020572@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/133457 eclipse [PATCH] java/eclipse-webtools: update to 3.0.3 o ports/133423 eclipse [PATCH] java/eclipse-emf: Update to 2.4.1 o ports/133417 eclipse [PATCH] java/eclipse-gef: update to 3.4.1 3 problems total. From heiner_ej at yahoo.de Thu Jun 11 10:16:25 2009 From: heiner_ej at yahoo.de (Heiner =?ISO-8859-1?Q?Strau=DF?=) Date: Thu Jun 11 10:16:39 2009 Subject: Current problem reports assigned to freebsd-eclipse@FreeBSD.org In-Reply-To: <200906081106.n58B6nno020572@freefall.freebsd.org> References: <200906081106.n58B6nno020572@freefall.freebsd.org> Message-ID: <1244714160.1131.6.camel@think.schlaf.bilch.com> Am Montag, den 08.06.2009, 11:06 +0000 schrieb FreeBSD bugmaster: > Note: to view an individual PR, use: > http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). > > The following is a listing of current problems submitted by FreeBSD users. > These represent problem reports covering all versions including > experimental development code and obsolete releases. > > > S Tracker Resp. Description > -------------------------------------------------------------------------------- > o ports/133457 eclipse [PATCH] java/eclipse-webtools: update to 3.0.3 > o ports/133423 eclipse [PATCH] java/eclipse-emf: Update to 2.4.1 > o ports/133417 eclipse [PATCH] java/eclipse-gef: update to 3.4.1 > > 3 problems total. > I propose to drop these patches and the ports all together because with eclipse 3.4.2 the installation works with the eclipse update system. I think this will apply to all eclipse plugin ports except the CDT and other OS dependent ports. Greetings, Heiner From linimon at FreeBSD.org Thu Jun 11 20:29:20 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu Jun 11 20:29:26 2009 Subject: ports/135467: can not build java/eclipse with WITHOUT_MOZILLA=yes WITHOUT_GNOMEVFS=yes WITHOUT_CAIRO=yes Message-ID: <200906112029.n5BKTJGx022206@freefall.freebsd.org> Old Synopsis: can not build eclipse with WITHOUT_MOZILLA=yes WITHOUT_GNOMEVFS=yes WITHOUT_CAIRO=yes New Synopsis: can not build java/eclipse with WITHOUT_MOZILLA=yes WITHOUT_GNOMEVFS=yes WITHOUT_CAIRO=yes Responsible-Changed-From-To: freebsd-java->freebsd-eclipse Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jun 11 20:28:38 UTC 2009 Responsible-Changed-Why: Fix synopsis and assign. http://www.freebsd.org/cgi/query-pr.cgi?pr=135467 From dohzono at gmail.com Fri Jun 12 00:40:03 2009 From: dohzono at gmail.com (Kazuo Dohzono) Date: Fri Jun 12 00:40:09 2009 Subject: ports/135467: can not build java/eclipse with WITHOUT_MOZILLA=yes WITHOUT_GNOMEVFS=yes WITHOUT_CAIRO=yes Message-ID: <200906120040.n5C0e2w1021478@freefall.freebsd.org> The following reply was made to PR ports/135467; it has been noted by GNATS. From: Kazuo Dohzono To: bug-followup@FreeBSD.org, dohzono@gmail.com Cc: Subject: Re: ports/135467: can not build java/eclipse with WITHOUT_MOZILLA=yes WITHOUT_GNOMEVFS=yes WITHOUT_CAIRO=yes Date: Fri, 12 Jun 2009 09:11:05 +0900 > Try toggling the other two settings to see which one (if any) is breaking the build. Does this help you? $ cd /usr/ports/java/eclipse/ $ echo /var/db/pkg/*gnome* /var/db/pkg/*gnome* # I don't have any gnome environment $ make WITHOUT_GNOMEVFS=yes (snip) ===> Building for eclipse-3.4.2 [echo] TARGET: compiler [echo] UPDATE ecj.jar BUILD SUCCESSFUL Total time: 11 seconds [echo] TARGET: compiler2 [echo] compilerArg -enableJavadoc -nowarn -encoding ISO-8859-1 [echo] build compiler org.eclipse.jdt.core.JDTCompilerAdapter [echo] UPDATE ecj.jar BUILD SUCCESSFUL Total time: 10 seconds [echo] Deleting jars to recompile... [echo] Compiling... [echo] UPDATE jarprocessor.jar [echo] UPDATE jarprocessorsrc.zip [exec] javadoc: warning - Multiple sources of package comments found for package "org.eclipse.core.runtime" [exec] javadoc: warning - Multiple sources of package comments found for package "org.eclipse.jface.text" [exec] javadoc: warning - Multiple sources of package comments found for package "org.eclipse.jface.text.link" [exec] javadoc: warning - Multiple sources of package comments found for package "org.eclipse.jface.text.source" [exec] javadoc: warning - Multiple sources of package comments found for package "org.eclipse.jface.text.templates" [exec] javadoc: warning - Multiple sources of package comments found for package "org.eclipse.ui.texteditor" [exec] /usr/local/tmp/usr/ports/java/eclipse/work/plugins/org.eclipse.platform.doc.isv/../org.eclipse.swt/Eclipse SWT/win32/org/eclipse/swt/widgets/IME.java:351: warning - @return tag cannot be used in method with void return type. [echo] Extract .class file and properties for the batch compiler [echo] Extract .class file and properties for the ant adapter [echo] UPDATE ecj-global.jar [echo] UPDATE ecjsrc-global.zip [echo] UPDATE ecj-global.jar [echo] UPDATE ecjsrc-global.zip [echo] UPDATE ecj-global.jar [echo] UPDATE ecjsrc-global.zip [exec] gnome-config: not found [exec] gnome-config: not found [exec] gnome-config: not found [exec] callback.c: In function 'Java_org_eclipse_swt_internal_Callback_bind': [exec] callback.c:493: warning: unused variable 'pad' [exec] ../eclipseCommon.c: In function 'filter': [exec] ../eclipseCommon.c:356: warning: initialization discards qualifiers from pointer target type [exec] ../eclipse.c: In function 'findStartupJar': [exec] ../eclipse.c:1106: warning: comparison with string literal results in unspecified behaviour [exec] ../eclipseJNI.c: In function 'newJavaString': [exec] ../eclipseJNI.c:236: warning: pointer targets in passing argument 5 of '(*env)->SetByteArrayRegion' differ in signedness [exec] ../eclipseMozilla.c: In function 'fixEnvForMozilla': [exec] ../eclipseMozilla.c:166: warning: passing argument 3 of 'scandir' from incompatible pointer type [exec] ../getproxygnome.c:16:31: warning: gconf/gconf-value.h: No such file or directory [exec] ../getproxygnome.c:17:32: warning: gconf/gconf-client.h: No such file or directory [exec] ../getproxygnome.c:25: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token [exec] ../getproxygnome.c: In function 'gconfInit': [exec] ../getproxygnome.c:40: error: 'client' undeclared (first use in this function) [exec] ../getproxygnome.c:40: error: (Each undeclared identifier is reported only once [exec] ../getproxygnome.c:40: error: for each function it appears in.) [exec] ../getproxygnome.c:40: warning: implicit declaration of function 'gconf_client_get_default' [exec] ../getproxygnome.c: In function 'Java_org_eclipse_core_internal_net_proxy_unix_UnixProxyProvider_getGConfProxyInfo': [exec] ../getproxygnome.c:75: error: 'client' undeclared (first use in this function) [exec] ../getproxygnome.c:88: warning: implicit declaration of function 'gconf_client_get_bool' [exec] ../getproxygnome.c:99: warning: implicit declaration of function 'gconf_client_get_string' [exec] ../getproxygnome.c:100: warning: initialization makes pointer from integer without a cast [exec] ../getproxygnome.c:104: warning: implicit declaration of function 'gconf_client_get_int' [exec] ../getproxygnome.c:113: warning: initialization makes pointer from integer without a cast [exec] ../getproxygnome.c:118: warning: initialization makes pointer from integer without a cast [exec] ../getproxygnome.c:127: warning: initialization makes pointer from integer without a cast [exec] ../getproxygnome.c:150: warning: initialization makes pointer from integer without a cast [exec] ../getproxygnome.c: In function 'Java_org_eclipse_core_internal_net_proxy_unix_UnixProxyProvider_getGConfNonProxyHosts': [exec] ../getproxygnome.c:185: error: 'client' undeclared (first use in this function) [exec] ../getproxygnome.c:192: warning: implicit declaration of function 'gconf_client_get_list' [exec] ../getproxygnome.c:193: error: 'GCONF_VALUE_STRING' undeclared (first use in this function) [exec] ../getproxygnome.c:193: warning: assignment makes pointer from integer without a cast [exec] ../getproxygnome.c:200: warning: assignment makes pointer from integer without a cast [exec] gmake: *** [getproxygnome.o] Error 1 BUILD FAILED /usr/local/tmp/usr/ports/java/eclipse/work/build.xml:101: exec returned: 2 Total time: 5 minutes 55 seconds *** Error code 1 Stop in /usr/ports/java/eclipse. From avg at icyb.net.ua Fri Jun 12 19:00:22 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Fri Jun 12 19:00:34 2009 Subject: eclipse 3.4.2 problem Message-ID: <4A32A11B.6020409@icyb.net.ua> I upgraded from Eclipse 3.4.1 o 3.4.2 and now I can not start it: $ eclipse Cannot open "../../obj/ports/usr/ports/java/eclipse/work/eclipse/configuration/org.eclipse.osgi/bundles/128/data/1632909880/plugins/org.eclipse.equinox.launcher.gtk.freebsd.x86_64_1.0.101.R34x_v20080731" ../../obj/ports/usr/ports/java/eclipse/work/eclipse/ I see that eclipse.ini and many other files have lines with "../../obj/ports/usr/ports/java/eclipse/work" in them, which looks like something remembered from the build location. I am quite puzzled. -- Andriy Gapon From avg at icyb.net.ua Fri Jun 12 19:00:24 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Fri Jun 12 19:00:34 2009 Subject: eclipse 3.4.2 problem In-Reply-To: <4A32A11B.6020409@icyb.net.ua> References: <4A32A11B.6020409@icyb.net.ua> Message-ID: <4A32A165.10602@icyb.net.ua> on 12/06/2009 21:40 Andriy Gapon said the following: > I upgraded from Eclipse 3.4.1 o 3.4.2 and now I can not start it: > $ eclipse > Cannot open > "../../obj/ports/usr/ports/java/eclipse/work/eclipse/configuration/org.eclipse.osgi/bundles/128/data/1632909880/plugins/org.eclipse.equinox.launcher.gtk.freebsd.x86_64_1.0.101.R34x_v20080731" > ../../obj/ports/usr/ports/java/eclipse/work/eclipse/ > > I see that eclipse.ini and many other files have lines with > "../../obj/ports/usr/ports/java/eclipse/work" in them, which looks like something > remembered from the build location. > > I am quite puzzled. > Yes and I have WRKDIRPREFIX=/usr/obj/ports set in /etc/make.conf. -- Andriy Gapon From sepotvin at FreeBSD.org Fri Jun 12 20:40:31 2009 From: sepotvin at FreeBSD.org (Stephane E. Potvin) Date: Fri Jun 12 20:40:46 2009 Subject: eclipse 3.4.2 problem In-Reply-To: <4A32A165.10602@icyb.net.ua> References: <4A32A11B.6020409@icyb.net.ua> <4A32A165.10602@icyb.net.ua> Message-ID: <4A32BADF.3010106@FreeBSD.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Andriy Gapon wrote: > on 12/06/2009 21:40 Andriy Gapon said the following: >> I upgraded from Eclipse 3.4.1 o 3.4.2 and now I can not start it: >> $ eclipse >> Cannot open >> "../../obj/ports/usr/ports/java/eclipse/work/eclipse/configuration/org.eclipse.osgi/bundles/128/data/1632909880/plugins/org.eclipse.equinox.launcher.gtk.freebsd.x86_64_1.0.101.R34x_v20080731" >> ../../obj/ports/usr/ports/java/eclipse/work/eclipse/ >> >> I see that eclipse.ini and many other files have lines with >> "../../obj/ports/usr/ports/java/eclipse/work" in them, which looks like something >> remembered from the build location. >> >> I am quite puzzled. >> > > Yes and I have WRKDIRPREFIX=/usr/obj/ports set in /etc/make.conf. > > Hmm... I've never tried to build with an alternate WRKDIRPREFIX. I'll try to reproduce and fix asap. Steph -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoyut8ACgkQmdOXtTCX/nsLjwCffAxs4jOaPPN2NKVc7J4k5coC 2tcAoMuHMAptWGTHvn8WvlWKC5eQq57W =PKaq -----END PGP SIGNATURE----- From ken at tydfam.jp Sat Jun 13 02:28:14 2009 From: ken at tydfam.jp (ken) Date: Sat Jun 13 02:28:20 2009 Subject: eclipse 3.4.2 problem In-Reply-To: <4A32A11B.6020409@icyb.net.ua> References: <4A32A11B.6020409@icyb.net.ua> Message-ID: <20090613.110225.598552788702446289.ken@tydfam.jp> You may rename your old workspace and ~/.eclipse so that 3.4.2 can start from scratch. From heiner_ej at yahoo.de Sat Jun 13 14:10:59 2009 From: heiner_ej at yahoo.de (Heiner =?ISO-8859-1?Q?Strau=DF?=) Date: Sat Jun 13 14:11:05 2009 Subject: eclipse 3.4.2 problem In-Reply-To: <20090613.110225.598552788702446289.ken@tydfam.jp> References: <4A32A11B.6020409@icyb.net.ua> <20090613.110225.598552788702446289.ken@tydfam.jp> Message-ID: <1244901425.2409.4.camel@think.schlaf.bilch.com> Am Samstag, den 13.06.2009, 11:02 +0900 schrieb ken: > You may rename your old workspace and ~/.eclipse so that 3.4.2 can start from scratch. I deinstalled eclipse 3.4.1. This strange error is something like an install procedure bug, I think :) From avg at icyb.net.ua Mon Jun 15 04:21:03 2009 From: avg at icyb.net.ua (Andriy Gapon) Date: Mon Jun 15 04:21:10 2009 Subject: eclipse 3.4.2 problem In-Reply-To: <4A32BADF.3010106@FreeBSD.org> References: <4A32A11B.6020409@icyb.net.ua> <4A32A165.10602@icyb.net.ua> <4A32BADF.3010106@FreeBSD.org> Message-ID: <4A35CC29.2090804@icyb.net.ua> on 12/06/2009 23:30 Stephane E. Potvin said the following: > Andriy Gapon wrote: >> on 12/06/2009 21:40 Andriy Gapon said the following: >>> I upgraded from Eclipse 3.4.1 o 3.4.2 and now I can not start it: $ >>> eclipse Cannot open >>> "../../obj/ports/usr/ports/java/eclipse/work/eclipse/configuration/org.eclipse.osgi/bundles/128/data/1632909880/plugins/org.eclipse.equinox.launcher.gtk.freebsd.x86_64_1.0.101.R34x_v20080731" >>> ../../obj/ports/usr/ports/java/eclipse/work/eclipse/ >>> >>> I see that eclipse.ini and many other files have lines with >>> "../../obj/ports/usr/ports/java/eclipse/work" in them, which looks like >>> something remembered from the build location. >>> >>> I am quite puzzled. >>> >> Yes and I have WRKDIRPREFIX=/usr/obj/ports set in /etc/make.conf. > > > Hmm... I've never tried to build with an alternate WRKDIRPREFIX. I'll try to > reproduce and fix asap. I force-rebuilt the port again and everything is OK, so it was not WRKDIRPREFIX. I think what happened is that I had eclipse-devel port installed before the first upgrade. I thought that I didn't need to switch from eclipse-devel to eclipse earlier, because the ports installed the same version of Eclipse, just had different names (and -devel was marked IGNORE). So, I am not 100% sure but I think that it was eclipse-devel-3.4.1 => eclipse-3.4.2 upgrade that produced those broken paths. Sorry for the noise. -- Andriy Gapon From bugmaster at FreeBSD.org Mon Jun 15 11:06:51 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 15 11:07:35 2009 Subject: Current problem reports assigned to freebsd-eclipse@FreeBSD.org Message-ID: <200906151106.n5FB6oWM076845@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/135467 eclipse can not build java/eclipse with WITHOUT_MOZILLA=yes WI o ports/133457 eclipse [PATCH] java/eclipse-webtools: update to 3.0.3 o ports/133423 eclipse [PATCH] java/eclipse-emf: Update to 2.4.1 o ports/133417 eclipse [PATCH] java/eclipse-gef: update to 3.4.1 4 problems total. From bugmaster at FreeBSD.org Mon Jun 22 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 22 11:07:35 2009 Subject: Current problem reports assigned to freebsd-eclipse@FreeBSD.org Message-ID: <200906221106.n5MB6pc2017956@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/135467 eclipse can not build java/eclipse with WITHOUT_MOZILLA=yes WI o ports/133457 eclipse [PATCH] java/eclipse-webtools: update to 3.0.3 o ports/133423 eclipse [PATCH] java/eclipse-emf: Update to 2.4.1 o ports/133417 eclipse [PATCH] java/eclipse-gef: update to 3.4.1 4 problems total. From heiner_ej at yahoo.de Mon Jun 22 12:00:20 2009 From: heiner_ej at yahoo.de (=?iso-8859-1?Q?Heiner_Strau=DF?=) Date: Mon Jun 22 12:00:40 2009 Subject: ports/133417: [PATCH] java/eclipse-gef: update to 3.4.1 Message-ID: <200906221200.n5MC0JxQ061828@freefall.freebsd.org> The following reply was made to PR ports/133417; it has been noted by GNATS. From: =?iso-8859-1?Q?Heiner_Strau=DF?= To: bug-followup@FreeBSD.org, heiner_ej@yahoo.de Cc: Subject: Re: ports/133417: [PATCH] java/eclipse-gef: update to 3.4.1 Date: Mon, 22 Jun 2009 11:28:57 +0000 (GMT) I would like to drop this port. With eclipse 3.4.2 I can install this plugi= n via the updater.=0A ---=0AHeiner Strau=DF=0Aheiner_ej@yahoo.de=0A=0A=0A = From heiner_ej at yahoo.de Mon Jun 22 12:00:23 2009 From: heiner_ej at yahoo.de (=?iso-8859-1?Q?Heiner_Strau=DF?=) Date: Mon Jun 22 12:00:40 2009 Subject: ports/133423: [PATCH] java/eclipse-emf: Update to 2.4.1 Message-ID: <200906221200.n5MC0MZb061933@freefall.freebsd.org> The following reply was made to PR ports/133423; it has been noted by GNATS. From: =?iso-8859-1?Q?Heiner_Strau=DF?= To: bug-followup@FreeBSD.org, heiner_ej@yahoo.de Cc: Subject: Re: ports/133423: [PATCH] java/eclipse-emf: Update to 2.4.1 Date: Mon, 22 Jun 2009 11:29:27 +0000 (GMT) I would like to drop this port. With eclipse 3.4.2 I can install this plugi= n via the updater.=0A ---=0AHeiner Strau=DF=0Aheiner_ej@yahoo.de=0ATel.: 04= 0 3480667 Mobil: 0160 4460452=0A=0A=0A=0A From heiner_ej at yahoo.de Mon Jun 22 12:00:26 2009 From: heiner_ej at yahoo.de (=?iso-8859-1?Q?Heiner_Strau=DF?=) Date: Mon Jun 22 12:00:40 2009 Subject: ports/133457: [PATCH] java/eclipse-webtools: update to 3.0.3 Message-ID: <200906221200.n5MC0PqE062142@freefall.freebsd.org> The following reply was made to PR ports/133457; it has been noted by GNATS. From: =?iso-8859-1?Q?Heiner_Strau=DF?= To: bug-followup@FreeBSD.org, heiner_ej@yahoo.de Cc: Subject: Re: ports/133457: [PATCH] java/eclipse-webtools: update to 3.0.3 Date: Mon, 22 Jun 2009 11:30:06 +0000 (GMT) I would like to drop this port. With eclipse 3.4.2 I can install this plugi= n via the updater.=0A ---=0AHeiner Strau=DF=0Aheiner_ej@yahoo.de=0A=0A=0A = From schmidt at ze.tum.de Mon Jun 29 07:00:11 2009 From: schmidt at ze.tum.de (Gerhard Schmidt) Date: Mon Jun 29 07:00:17 2009 Subject: ports/133457: [PATCH] java/eclipse-webtools: update to 3.0.3 Message-ID: <200906290700.n5T70AQQ020741@freefall.freebsd.org> The following reply was made to PR ports/133457; it has been noted by GNATS. From: Gerhard Schmidt To: bug-followup@FreeBSD.org, heiner_ej@yahoo.de Cc: Subject: Re: ports/133457: [PATCH] java/eclipse-webtools: update to 3.0.3 Date: Mon, 29 Jun 2009 08:40:49 +0200 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigDF30E862FC75A04567C0C3A6 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Updates via eclipse updater are per user updates (stored in homedir of th= e User). The port is per Computer (stored in /usr/local). I maintain some Workstations with 200+ users. Please keep the Port. Regards Estartu --------------enigDF30E862FC75A04567C0C3A6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBSkhiBdl1K6RAAKkVAQqS5Af8DQmPjx+/R+8xek8YTgxgZQmcr9mO9yQP FPu9qgG7dGnSPbeyugk+gWTKuPk5JUYTiWl4J+aXvBp8gjozuzNw8y0LGWfenUk6 Vm1j1XD05flnTHBDFDpG5dfS/pVKhCixZGnnQwUT9HspX+PRavX7Q9oqxHqJg17B xqDtz2Qf/NBH9i8UC1NvE31i427ibxfEHcVkrYTzVsqr8cXboDhELYB6jCEdglgv RqS/XRAfTnkLk+w86P1xdzOI3Upc+qBc8mR8Yj13Iu5QXLlyY2EVlUlitS/Y2AJM wgoxPAJcaJBNvirWPa4GMQ9Z5hW6BQMh74ZLtt+/+Ca0lzOLTaY+5g== =MNAB -----END PGP SIGNATURE----- --------------enigDF30E862FC75A04567C0C3A6-- From heiner_ej at yahoo.de Mon Jun 29 10:42:31 2009 From: heiner_ej at yahoo.de (Heiner =?ISO-8859-1?Q?Strau=DF?=) Date: Mon Jun 29 10:42:40 2009 Subject: ports/133457: [PATCH] java/eclipse-webtools: update to 3.0.3 In-Reply-To: <200906290700.n5T70AQQ020741@freefall.freebsd.org> References: <200906290700.n5T70AQQ020741@freefall.freebsd.org> Message-ID: <1246272143.1356.19.camel@think.my.domain> Am Montag, den 29.06.2009, 07:00 +0000 schrieb Gerhard Schmidt: > The following reply was made to PR ports/133457; it has been noted by GNATS. > > From: Gerhard Schmidt > To: bug-followup@FreeBSD.org, heiner_ej@yahoo.de > Cc: > Subject: Re: ports/133457: [PATCH] java/eclipse-webtools: update to 3.0.3 > Date: Mon, 29 Jun 2009 08:40:49 +0200 > > This is an OpenPGP/MIME signed message (RFC 2440 and 3156) > --------------enigDF30E862FC75A04567C0C3A6 > Content-Type: text/plain; charset=ISO-8859-15 > Content-Transfer-Encoding: quoted-printable > > Updates via eclipse updater are per user updates (stored in homedir of th= > e > User). The port is per Computer (stored in /usr/local). I maintain some > Workstations with 200+ users. > > Please keep the Port. > That's a point. But someone has to keep them in sync with eclipse, testing and committing etc. If they are kept like now, they are adding more confusion and no help I think. It took me hours to find out what was wrong with them and how to fix :) Drop them or maintain. The actual webtools are 3.0.4 already. Maybe for bigger installs we could have an eclipse-plugin-mirror port or something, if you want a server centric install. Greetings, Heiner From bugmaster at FreeBSD.org Mon Jun 29 11:06:56 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jun 29 11:07:35 2009 Subject: Current problem reports assigned to freebsd-eclipse@FreeBSD.org Message-ID: <200906291106.n5TB6sE8046263@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/135467 eclipse can not build java/eclipse with WITHOUT_MOZILLA=yes WI o ports/133457 eclipse [PATCH] java/eclipse-webtools: update to 3.0.3 o ports/133423 eclipse [PATCH] java/eclipse-emf: Update to 2.4.1 o ports/133417 eclipse [PATCH] java/eclipse-gef: update to 3.4.1 4 problems total. From rick-freebsd2008 at kiwi-computer.com Tue Jun 30 00:12:54 2009 From: rick-freebsd2008 at kiwi-computer.com (Rick C. Petty) Date: Tue Jun 30 00:12:59 2009 Subject: ports/133457: [PATCH] java/eclipse-webtools: update to 3.0.3 In-Reply-To: <1246272143.1356.19.camel@think.my.domain> References: <200906290700.n5T70AQQ020741@freefall.freebsd.org> <1246272143.1356.19.camel@think.my.domain> Message-ID: <20090629234611.GB24986@keira.kiwi-computer.com> On Mon, Jun 29, 2009 at 12:42:23PM +0200, Heiner Strau? wrote: > Am Montag, den 29.06.2009, 07:00 +0000 schrieb Gerhard Schmidt: > > > > Updates via eclipse updater are per user updates (stored in homedir of th= > > e > > User). The port is per Computer (stored in /usr/local). I maintain some > > Workstations with 200+ users. > > > > Please keep the Port. > > That's a point. But someone has to keep them in sync with eclipse, > testing and committing etc. If they are kept like now, they are adding > more confusion and no help I think. It took me hours to find out what > was wrong with them and how to fix :) Drop them or maintain. The actual > webtools are 3.0.4 already. Maybe for bigger installs we could have an > eclipse-plugin-mirror port or something, if you want a server centric > install. I disagree with the OP. You can drop the user-installed plugins directly into /usr/local/eclipse/ with a modicum of effort. You can network mount that directory to avoid updating every machine too. In fact you can even have multiple versions of eclipse installed and run side-by-side with a little effort. I've played with modifications to my /usr/local/bin/eclipse script to do just that. There's absolutely no reason we should have any eclipse-* ports since every one of them is obtainable through eclipse's plugin architecture and software updates screens. It's especially painful if there are multiple supported eclipse versions in the ports tree. I hope that the OP's not suggesting that we create thousands of ports, one for each of Eclipse's 1200+ plugins times each version of Eclipse. Even if he were to volunteer to be the maintainer for each, it seems silly to have the plugins as ports. Although there is some precedence with p5-* ports (instead of using CPAN exclusively). In fact I've had troubles with many of the fbsd ports but all of them seem to behave when I grab them with Eclipse's updater. -- Rick C. Petty