From jonc at chen.org.nz Wed May 7 02:01:27 2008 From: jonc at chen.org.nz (Jonathan Chen) Date: Wed May 7 02:01:30 2008 Subject: java/eclipse update? Message-ID: <20080507014245.GA30347@osiris.chen.org.nz> Hi, After seeing some progress on the 3.3.2 port the past few months, I was hoping that someone would commit it to java/eclipse-devel, or even java/eclipse. Any possibility of that happening? Cheers. -- Jonathan Chen ---------------------------------------------------------------------- Power corrupts, Absolute Power is pretty neat From mbowie at buzmo.com Wed May 7 19:29:34 2008 From: mbowie at buzmo.com (Mike Bowie) Date: Wed May 7 19:29:42 2008 Subject: java/eclipse update? In-Reply-To: <20080507014245.GA30347@osiris.chen.org.nz> References: <20080507014245.GA30347@osiris.chen.org.nz> Message-ID: <4821FC04.7030908@buzmo.com> Jonathan Chen wrote: > Hi, > > After seeing some progress on the 3.3.2 port the past few months, I > was hoping that someone would commit it to java/eclipse-devel, or > even java/eclipse. Any possibility of that happening? > > Cheers. Of course, I'd be happy to jump on Jonathan's bandwagon here. I've been using Ken's 3.3.2 build since he first posted it and have no complaints. I'm using CDT, PHPeclipse (with xdebug), SQL Explorer, Subclipse, the Apache LDAP browser and Mylyn, all very happily thus far. (Might have a few others on the machine at home too.) While I hope not to hi-jack the primary message here, I do know that one of the issues previously raised with bumping java/eclipse was that of the port plugin dependencies. While this may be a foolish question to ask, for the most part, is there really a need for all these plugins to be available as ports? The Eclipse update mechanism serves me well for all the plugins I currently use and from what I can see at a glance, only eclipse-cdt actually includes any patches; the current value of which I might have to question given that I'm running it joyously from the update site. Having the ports there may offer a port lover a quick way to get their Eclipse install kitted out, but the list is certainly minor compared with the list of plugin's out there; which I'd imagine would lead most users to use the update mechanism anyway... and should the user choose to update their plugins, the installed port becomes somewhat unnecessary. I certainly don't wish this to be perceived as a lack of thanks for the porters out there; I'd just like to see java/eclipse closer to the current release... not just now, but as we move forward also. Cheers all, Mike. From mbowie at buzmo.com Wed May 7 20:46:53 2008 From: mbowie at buzmo.com (Mike Bowie) Date: Wed May 7 20:46:58 2008 Subject: java/eclipse update? In-Reply-To: <20080507203625.GA98738@keira.kiwi-computer.com> References: <20080507014245.GA30347@osiris.chen.org.nz> <4821FC04.7030908@buzmo.com> <20080507203625.GA98738@keira.kiwi-computer.com> Message-ID: <48221461.5020806@buzmo.com> Rick C. Petty wrote: > On Wed, May 07, 2008 at 11:59:16AM -0700, Mike Bowie wrote: > >>> After seeing some progress on the 3.3.2 port the past few months, I >>> was hoping that someone would commit it to java/eclipse-devel, or >>> even java/eclipse. Any possibility of that happening? >>> >> Of course, I'd be happy to jump on Jonathan's bandwagon here. >> >> While I hope not to hi-jack the primary message here, I do know that one >> of the issues previously raised with bumping java/eclipse was that of >> the port plugin dependencies. While this may be a foolish question to >> ask, for the most part, is there really a need for all these plugins to >> be available as ports? The Eclipse update mechanism serves me well for >> all the plugins I currently use and from what I can see at a glance, >> > > That has not been true in the past. I've had troubles with the update > mechanisms for eclipse as new as 3.2.1. > > Have the update issues been show-stoppers in terms of "ultimately without resolution"? I guess more to the point, are they issues that maintaining a port would resolve? >> Having the ports there may offer a port lover a quick way to get their >> Eclipse install kitted out, but the list is certainly minor compared >> with the list of plugin's out there; which I'd imagine would lead most >> users to use the update mechanism anyway... and should the user choose >> to update their plugins, the installed port becomes somewhat unnecessary. >> > > True. If there's ports which just install the plugin (no patches, no > special code, etc.), they should be removed... so long as the plugin > architecture works for that version of eclipse. There are added benefits > that you can get the proper plugins for each version of eclipse, as opposed > to having one eclipse-cdt port for java/eclipse and another for > java/eclipse-devel, etc. > > >> I certainly don't wish this to be perceived as a lack of thanks for the >> porters out there; I'd just like to see java/eclipse closer to the >> current release... not just now, but as we move forward also. >> > > Whatever anybody does, pleasp please *please* keep eclipse-3.2.1 around as > a possible port. There are so many annoying UI changes in 3.3 that are > driving me insane. For example, when refactoring the default is to > highlight the word or phrase and let the editor change the name. This > doesn't work well with the viPlugin. I'd much rather have the window popup > and ask, as 3.2.1 does. > > My suggestion is to keep a java/eclipse321 or java/eclipse32 around which > is the current java/eclipse. > > -- Rick C. Petty > I think that would be a smart move... at least for a minor version or two back. The goal being maximum usability, an end to which I think this makes sense. Interesting "New Zealand connection" trifecta we seem to have so far... Jon looks to be *in* NZ, I'm *from* NZ and Rick's "kiwi-computer.com" rounds it out. (Although who's to say if there's a really connection there, besides the name of our native flightless bird.) Cheers, Mike. From rick-freebsd at kiwi-computer.com Wed May 7 21:03:07 2008 From: rick-freebsd at kiwi-computer.com (Rick C. Petty) Date: Wed May 7 21:03:10 2008 Subject: java/eclipse update? In-Reply-To: <4821FC04.7030908@buzmo.com> References: <20080507014245.GA30347@osiris.chen.org.nz> <4821FC04.7030908@buzmo.com> Message-ID: <20080507203625.GA98738@keira.kiwi-computer.com> On Wed, May 07, 2008 at 11:59:16AM -0700, Mike Bowie wrote: > > > >After seeing some progress on the 3.3.2 port the past few months, I > >was hoping that someone would commit it to java/eclipse-devel, or > >even java/eclipse. Any possibility of that happening? > > Of course, I'd be happy to jump on Jonathan's bandwagon here. > > While I hope not to hi-jack the primary message here, I do know that one > of the issues previously raised with bumping java/eclipse was that of > the port plugin dependencies. While this may be a foolish question to > ask, for the most part, is there really a need for all these plugins to > be available as ports? The Eclipse update mechanism serves me well for > all the plugins I currently use and from what I can see at a glance, That has not been true in the past. I've had troubles with the update mechanisms for eclipse as new as 3.2.1. > Having the ports there may offer a port lover a quick way to get their > Eclipse install kitted out, but the list is certainly minor compared > with the list of plugin's out there; which I'd imagine would lead most > users to use the update mechanism anyway... and should the user choose > to update their plugins, the installed port becomes somewhat unnecessary. True. If there's ports which just install the plugin (no patches, no special code, etc.), they should be removed... so long as the plugin architecture works for that version of eclipse. There are added benefits that you can get the proper plugins for each version of eclipse, as opposed to having one eclipse-cdt port for java/eclipse and another for java/eclipse-devel, etc. > I certainly don't wish this to be perceived as a lack of thanks for the > porters out there; I'd just like to see java/eclipse closer to the > current release... not just now, but as we move forward also. Whatever anybody does, pleasp please *please* keep eclipse-3.2.1 around as a possible port. There are so many annoying UI changes in 3.3 that are driving me insane. For example, when refactoring the default is to highlight the word or phrase and let the editor change the name. This doesn't work well with the viPlugin. I'd much rather have the window popup and ask, as 3.2.1 does. My suggestion is to keep a java/eclipse321 or java/eclipse32 around which is the current java/eclipse. -- Rick C. Petty From rick-freebsd at kiwi-computer.com Wed May 7 21:07:33 2008 From: rick-freebsd at kiwi-computer.com (Rick C. Petty) Date: Wed May 7 21:07:36 2008 Subject: java/eclipse update? In-Reply-To: <48221461.5020806@buzmo.com> References: <20080507014245.GA30347@osiris.chen.org.nz> <4821FC04.7030908@buzmo.com> <20080507203625.GA98738@keira.kiwi-computer.com> <48221461.5020806@buzmo.com> Message-ID: <20080507210732.GB98738@keira.kiwi-computer.com> On Wed, May 07, 2008 at 01:43:13PM -0700, Mike Bowie wrote: > Rick C. Petty wrote: > > > >That has not been true in the past. I've had troubles with the update > >mechanisms for eclipse as new as 3.2.1. > > > Have the update issues been show-stoppers in terms of "ultimately > without resolution"? I guess more to the point, are they issues that > maintaining a port would resolve? I was unable to resolve the problems. I also spent a lot of time trying to get both eclipse 3.2.x and eclipse 3.3.x running on my systems (before the ports were maintained). If eclipse 3.2.1 is ever removed from the ports tree, I have backups of all the distfiles and ports directories and will continue to use them until eclipse fixes the behavior I described. > >My suggestion is to keep a java/eclipse321 or java/eclipse32 around which > >is the current java/eclipse. > > > I think that would be a smart move... at least for a minor version or > two back. The goal being maximum usability, an end to which I think > this makes sense. Agreed. I stopped using 3.1 after using 3.2 enough to realize it was improved. Maybe 3.3 will eventually add a preference to always pop up the dialog on refactoring. Or maybe I'll get around to simplifying the key sequence. For the meantime, I'm running into ENOTIME. > Interesting "New Zealand connection" trifecta we seem to have so far... > Jon looks to be *in* NZ, I'm *from* NZ and Rick's "kiwi-computer.com" > rounds it out. (Although who's to say if there's a really connection > there, besides the name of our native flightless bird.) Haha! I named mine after the fruit, not the bird. But I appreciate the resemblence! =) -- Rick C. Petty From mbowie at buzmo.com Sat May 10 03:57:25 2008 From: mbowie at buzmo.com (Mike Bowie) Date: Sat May 10 03:57:31 2008 Subject: java/eclipse update? In-Reply-To: <20080510035318.GA98527@misty.eyesbeyond.com> References: <20080507014245.GA30347@osiris.chen.org.nz> <4821FC04.7030908@buzmo.com> <20080507203625.GA98738@keira.kiwi-computer.com> <48221461.5020806@buzmo.com> <20080510035318.GA98527@misty.eyesbeyond.com> Message-ID: <48251D22.4020808@buzmo.com> Greg Lewis wrote: > On Wed, May 07, 2008 at 01:43:13PM -0700, Mike Bowie wrote: >> Interesting "New Zealand connection" trifecta we seem to have so far... >> Jon looks to be *in* NZ, I'm *from* NZ and Rick's "kiwi-computer.com" >> rounds it out. (Although who's to say if there's a really connection >> there, besides the name of our native flightless bird.) > > I've committed the update to 3.3.2 from Ken. You can go back to sheep > worrying now... ;-) > Greg, I'm not sure if I should thank you or suggest we step outside for fisty-cuffs. I thought you might chime-in on the plugins as ports bit... any thoughts? Cheers, Mike. -- "You don't see FreeBSD developers sitting in a smoke-filled room plotting the overthrow of Microsoft. We sit in light, airy rooms and plot where to get the best drinks." - Michael Lucas From mbowie at buzmo.com Sat May 10 04:07:20 2008 From: mbowie at buzmo.com (Mike Bowie) Date: Sat May 10 04:07:24 2008 Subject: java/eclipse update? In-Reply-To: <48251D22.4020808@buzmo.com> References: <20080507014245.GA30347@osiris.chen.org.nz> <4821FC04.7030908@buzmo.com> <20080507203625.GA98738@keira.kiwi-computer.com> <48221461.5020806@buzmo.com> <20080510035318.GA98527@misty.eyesbeyond.com> <48251D22.4020808@buzmo.com> Message-ID: <48251F75.1090907@buzmo.com> Mike Bowie wrote: > Greg Lewis wrote: >> On Wed, May 07, 2008 at 01:43:13PM -0700, Mike Bowie wrote: >>> Interesting "New Zealand connection" trifecta we seem to have so >>> far... Jon looks to be *in* NZ, I'm *from* NZ and Rick's >>> "kiwi-computer.com" rounds it out. (Although who's to say if there's >>> a really connection there, besides the name of our native flightless >>> bird.) >> >> I've committed the update to 3.3.2 from Ken. You can go back to sheep >> worrying now... ;-) >> > > Greg, > > I'm not sure if I should thank you or suggest we step outside for > fisty-cuffs. > > I thought you might chime-in on the plugins as ports bit... any thoughts? > > Cheers, > > Mike. > Doing a bit of a Greg here... replying to one's self. I guess I should have cvsup'd first to see the update; it's in java/eclipse... which I suppose negates the plugin status questions. ;-) No more drinks for me tonight. Cheers, Mike. -- "You don't see FreeBSD developers sitting in a smoke-filled room plotting the overthrow of Microsoft. We sit in light, airy rooms and plot where to get the best drinks." - Michael Lucas From mbowie at buzmo.com Sat May 10 04:09:11 2008 From: mbowie at buzmo.com (Mike Bowie) Date: Sat May 10 04:09:15 2008 Subject: java/eclipse update? In-Reply-To: <48251F75.1090907@buzmo.com> References: <20080507014245.GA30347@osiris.chen.org.nz> <4821FC04.7030908@buzmo.com> <20080507203625.GA98738@keira.kiwi-computer.com> <48221461.5020806@buzmo.com> <20080510035318.GA98527@misty.eyesbeyond.com> <48251D22.4020808@buzmo.com> <48251F75.1090907@buzmo.com> Message-ID: <48251FE4.2090002@buzmo.com> Mike Bowie wrote: > Mike Bowie wrote: >> Greg Lewis wrote: >>> On Wed, May 07, 2008 at 01:43:13PM -0700, Mike Bowie wrote: >>>> Interesting "New Zealand connection" trifecta we seem to have so >>>> far... Jon looks to be *in* NZ, I'm *from* NZ and Rick's >>>> "kiwi-computer.com" rounds it out. (Although who's to say if >>>> there's a really connection there, besides the name of our native >>>> flightless bird.) >>> >>> I've committed the update to 3.3.2 from Ken. You can go back to sheep >>> worrying now... ;-) >>> >> >> Greg, >> >> I'm not sure if I should thank you or suggest we step outside for >> fisty-cuffs. >> >> I thought you might chime-in on the plugins as ports bit... any thoughts? >> >> Cheers, >> >> Mike. >> > > Doing a bit of a Greg here... replying to one's self. > > I guess I should have cvsup'd first to see the update; it's in > java/eclipse... which I suppose negates the plugin status questions. ;-) > > No more drinks for me tonight. > > Cheers, > > Mike. > OMG!... disregard... ignore... abort... I'm going to bed. :-S Terribly sorry for all the noise. Mike. -- "You don't see FreeBSD developers sitting in a smoke-filled room plotting the overthrow of Microsoft. We sit in light, airy rooms and plot where to get the best drinks." - Michael Lucas From glewis at eyesbeyond.com Sat May 10 04:30:23 2008 From: glewis at eyesbeyond.com (Greg Lewis) Date: Sat May 10 04:30:25 2008 Subject: java/eclipse update? In-Reply-To: <48221461.5020806@buzmo.com> References: <20080507014245.GA30347@osiris.chen.org.nz> <4821FC04.7030908@buzmo.com> <20080507203625.GA98738@keira.kiwi-computer.com> <48221461.5020806@buzmo.com> Message-ID: <20080510035318.GA98527@misty.eyesbeyond.com> On Wed, May 07, 2008 at 01:43:13PM -0700, Mike Bowie wrote: > Interesting "New Zealand connection" trifecta we seem to have so far... > Jon looks to be *in* NZ, I'm *from* NZ and Rick's "kiwi-computer.com" > rounds it out. (Although who's to say if there's a really connection > there, besides the name of our native flightless bird.) I've committed the update to 3.3.2 from Ken. You can go back to sheep worrying now... ;-) -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org From glewis at eyesbeyond.com Sat May 10 04:42:49 2008 From: glewis at eyesbeyond.com (Greg Lewis) Date: Sat May 10 04:42:51 2008 Subject: java/eclipse update? In-Reply-To: <48251D22.4020808@buzmo.com> References: <20080507014245.GA30347@osiris.chen.org.nz> <4821FC04.7030908@buzmo.com> <20080507203625.GA98738@keira.kiwi-computer.com> <48221461.5020806@buzmo.com> <20080510035318.GA98527@misty.eyesbeyond.com> <48251D22.4020808@buzmo.com> Message-ID: <20080510044244.GA98822@misty.eyesbeyond.com> On Fri, May 09, 2008 at 08:57:22PM -0700, Mike Bowie wrote: > Greg Lewis wrote: > >On Wed, May 07, 2008 at 01:43:13PM -0700, Mike Bowie wrote: > >>Interesting "New Zealand connection" trifecta we seem to have so far... > >>Jon looks to be *in* NZ, I'm *from* NZ and Rick's "kiwi-computer.com" > >>rounds it out. (Although who's to say if there's a really connection > >>there, besides the name of our native flightless bird.) > > > >I've committed the update to 3.3.2 from Ken. You can go back to sheep > >worrying now... ;-) > > I'm not sure if I should thank you or suggest we step outside for > fisty-cuffs. Heh. There must have been a bit of biff in the rugby league test the other night, lets just agree thats enough Anzac hostilities for the moment :). > I thought you might chime-in on the plugins as ports bit... any thoughts? No real change from me, I still think the plugins should either be marked broken or upgraded to a version that works with whatever we put in the main eclipse port. If someone wants to go with something else then I'll take a look at patches and commit them, but I don't have the cycles to be the main eclipse maintainer. Same deal for keeping old versions around. If people want that then they need to come up with a workable system of how thats going to interact with plugin ports and the patches to the present eclipse port that would allow it to be committed as eclipse32 or whatever. Yes I realise there are multiple versions of emacs, for instance, but thats because someone was interested enough to do the work to make it so. I really think the Eclipse community on FreeBSD isn't large enough to do more than eclipse and eclipse-devel (and we even struggle to keep those up to date, which I'm just as guilty of as anyone else). -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org From ryan.r.ware at intel.com Sun May 11 20:02:41 2008 From: ryan.r.ware at intel.com (Ware, Ryan R) Date: Sun May 11 20:02:45 2008 Subject: Eclipse Plugins Message-ID: <3409751E7375C346A743B321A33B40D004A479A0@orsmsx416.amr.corp.intel.com> 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 From rick-freebsd at kiwi-computer.com Mon May 12 17:10:36 2008 From: rick-freebsd at kiwi-computer.com (Rick C. Petty) Date: Mon May 12 17:10:40 2008 Subject: Eclipse Plugins In-Reply-To: <3409751E7375C346A743B321A33B40D004A479A0@orsmsx416.amr.corp.intel.com> References: <3409751E7375C346A743B321A33B40D004A479A0@orsmsx416.amr.corp.intel.com> Message-ID: <20080512171035.GA78992@keira.kiwi-computer.com> 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 From ryan.r.ware at intel.com Mon May 12 17:13:47 2008 From: ryan.r.ware at intel.com (Ware, Ryan R) Date: Mon May 12 17:13:51 2008 Subject: Eclipse Plugins In-Reply-To: <20080512171035.GA78992@keira.kiwi-computer.com> References: <3409751E7375C346A743B321A33B40D004A479A0@orsmsx416.amr.corp.intel.com> <20080512171035.GA78992@keira.kiwi-computer.com> Message-ID: <3409751E7375C346A743B321A33B40D004AB76F8@orsmsx416.amr.corp.intel.com> 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@kiwi-computer.com] 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 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 8439 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-eclipse/attachments/20080512/64451e4e/smime.bin From fedex_courierbenin201 at yahoo.fr Sat May 24 03:22:31 2008 From: fedex_courierbenin201 at yahoo.fr (Barr Daniel Obiora (ESQ)) Date: Sat May 24 03:22:37 2008 Subject: ATTENTION Message-ID: <20080523154348.58E708792F5@austin.pins-web.net> Hello Dear, I have Paid the fee for your Cheque Draft.but the manager of Eko Bankn Benin told me that before the check will get to you that it will expire.So i told him to cash $1.5M USA DOLLar all the necessary arrangement of delivering the $1.5M USA DOLLar in cash was made with FedEX DELIVERY COURIER COMPANY. This is the information they need to delivery your package to you.with FEDEX DELIVERY COURIER COMPANY, contact them now. NAME:FEDEX COURIER DELIVERING COMPANY. ATTANTION: PERSON: DR.JERRY LAWRENCE POSITION: FOREIGN DELIVERY DEPARTMENT. ADDRESS: COTONOU BENIN REPUBLIC E-MAIL:fedex_courierbenin201@yahoo.fr Phone number: PHONE NUMBER: +229 9374 0412 Please, Send them your contacts information to able them locate you immediately they arrived in your country with your BOX .This is what they need from you. 1.YOUR FULL NAME 2.YOUR HOME ADDRESS. 3.YOUR CURRENT HOME TELEPHONE NUMBER. 4.YOUR CURRENT OFFICE TELEPHONE. 5. YOUR CURRENT HOME TELEPHONE NUMBER. 6.A COPY OF YOUR PICTURE Note that this is there E-mail contact (fedex_courierbenin201@yahoo.fr) Please make sure you send this needed info's to the Director general of FEDEX DELIVERY COURIER COMPANY BENIN REPUBLIC,DR.JERRY Lawrence with the address given to you. Note. The Fedex Delivery Courier Company don't know the contents of the Box. I registered it as a Box of an African cloths. They don't know it contents money, this is to avoid them delaying with the Box.don't let them know that is money that is in that Box. Thanks and Remain Blessed. Barr Daniel Obiora (ESQ) From vova at fbsd.ru Wed May 28 09:33:48 2008 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Wed May 28 09:33:52 2008 Subject: After recent upgrade of java/eclipse-devel and java/jdk16 eclipse does not work for my any more Message-ID: <1211964642.1600.39.camel@localhost> Hi FreeBSD 8-CURRENT. % pkg_info -I '*jdk*' '*eclipse*' eclipse-devel-3.3.2 An open extensible IDE for anything and nothing in particul jdk-1.6.0.3p4_1 Java Development Kit 1.6.0 % % java -version java version "1.6.0_03-p4" Java(TM) SE Runtime Environment (build 1.6.0_03-p4-root_28_may_2008_02_51-b00) Java HotSpot(TM) Server VM (build 1.6.0_03-p4-root_28_may_2008_02_51-b00, mixed mode) % Just before upgrade of these packages everything works fine. Starting eclipse shows splash-screen, and then show popup with reference on following log file % cat /usr/home/vova/.eclipse/org.eclipse.platform_3.3.0_1767688504/configuration/1211961335285.log !SESSION 2008-05-28 11:55:32.881 ----------------------------------------------- eclipse.buildId=M20080221-1800 java.version=1.6.0_03-p4 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=freebsd, ARCH=x86, WS=gtk, NL=ru_RU Command-line arguments: -os freebsd -ws gtk -arch x86 !ENTRY org.eclipse.equinox.app 2008-05-28 11:55:43.301 !MESSAGE Product org.eclipse.sdk.ide could not be found. !ENTRY org.eclipse.osgi 4 0 2008-05-28 11:55:43.401 !MESSAGE Application error !STACK 1 java.lang.RuntimeException: No application id has been found. at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:236) at org.eclipse.equinox.internal.app.EclipseAppContainer.start(EclipseAppContainer.java:98) at org.eclipse.equinox.internal.app.Activator.addingService(Activator.java:112) at org.osgi.util.tracker.ServiceTracker$Tracked.trackAdding(ServiceTracker.java:1064) at org.osgi.util.tracker.ServiceTracker$Tracked.trackInitialServices(ServiceTracker.java:926) at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:330) at org.osgi.util.tracker.ServiceTracker.open(ServiceTracker.java:274) at org.eclipse.equinox.internal.app.Activator.start(Activator.java:54) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:999) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:993) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:974) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346) at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:260) at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:400) at org.eclipse.core.runtime.internal.adaptor.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:111) at org.eclipse.osgi.baseadaptor.loader.ClasspathManager.findLocalClass(ClasspathManager.java:417) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.findLocalClass(DefaultClassLoader.java:189) at org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:340) at org.eclipse.osgi.framework.internal.core.SingleSourcePackage.loadClass(SingleSourcePackage.java:37) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClassInternal(BundleLoader.java:405) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:369) at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:357) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:83) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at org.eclipse.core.internal.runtime.PlatformActivator.startAppContainer(PlatformActivator.java:47) at org.eclipse.core.internal.runtime.PlatformActivator.start(PlatformActivator.java:32) at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:999) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:993) at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:974) at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:350) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1118) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:634) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:282) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:468) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:195) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:297) !ENTRY org.eclipse.osgi 2 0 2008-05-28 11:55:44.067 ... Any hints will be very appreciated. PS: Removing .eclipse does not helps. -- Vladimir B. Grebenschikov vova@fbsd.ru