Hi Fabio, I'm not sure you're following the instructions for installing the plugin from a zip file. You should be extracting the contents of the zip into the <eclipse>/dropins folder (if it doesn't already exists, go ahead and create it). Also, you should not need to use Eclipse "Install new software" dialog at all... plugins in /dropins are registered automatically, without any UI interaction on your part.
Try following these instructions for installing from zip files: http://code.google.com/eclipse/docs/install-from-zip.html Hope this helps, Keith On Thu, Mar 4, 2010 at 3:59 PM, Fabio Kaminski <[email protected]>wrote: > Hi Keith, > > my version is Galileo 3.5.1 64 on fedora linux > with all WST plugins installed and recent updates.. > > the google plugin never worked for me on this platform (no Google menu on > windows > preferences, no GWT project wizard and buttons available) > > i even try your last patch .. unziping in the eclipse folder... > and after update google plugin using the "install new software" > everything went fine.. and eclipse detects plugin installed sucesfully.. > > i thought this was normal with this version.. so i give up of the plugins > and do things manually(a lot of hacks :s).. > > but i guess i can have some hope now :) > > Thanks > > > On Thu, Mar 4, 2010 at 3:49 PM, Keith Platfoot <[email protected]>wrote: > >> Hi Fabio, >> >> What's your specific issue with Eclipse on 64-bit Linux? We've tested the >> 1.3 plugin on 64-bit versions of all 3 versions of Eclipse (3.3, 3.4, 3.5) >> and did not encounter any problems. >> >> If you can provide a few details, we'll see if we can work out a >> resolution for you. >> >> Keith >> >> >> On Thu, Mar 4, 2010 at 12:14 PM, Fabio Kaminski >> <[email protected]>wrote: >> >>> any workarounds for eclipse 64 bit on linux? >>> >>> or there is some hack in eclipse to work smoothly with it.. >>> >>> im still doing things by hand.. >>> >>> Thanks >>> >>> Fabio Kaminski >>> >>> On Thu, Mar 4, 2010 at 1:40 PM, Keith Platfoot <[email protected]>wrote: >>> >>>> Hey again, >>>> >>>> Just wanted to mention that to actually customize your project's WAR >>>> directory (enhancement bullet 1 in the announcement email), you'll need to >>>> navigate to Google > Web Application in your project properties dialog. >>>> You >>>> can use any project-relative path as the WAR directory (e.g. >>>> src/main/webapp) and you can also use the checkbox below to toggle whether >>>> or not you want to launch and deploy from that directory, by default. If >>>> you uncheck that option, Eclipse will prompt you for a location the first >>>> time you launch your project, and will not mess with the JARs in >>>> <WAR>/WEB-INF/lib or try to move your build output directory to >>>> <WAR>/WEB-INF/classes. You can think of the checkbox as the *Keep your >>>> hands off my runtime WAR directory!* option. :-) >>>> >>>> If anyone runs into issues or has questions about any of the new >>>> features, don't hesitate to ask. Thanks! >>>> >>>> Keith >>>> >>>> >>>> On Wed, Mar 3, 2010 at 7:25 PM, Keith Platfoot <[email protected]>wrote: >>>> >>>>> Hi everyone, >>>>> >>>>> Last month, I announced some of the changes we had planned for the 1.3 >>>>> version of the Google Plugin for Eclipse. To recap, this release is >>>>> focused >>>>> on making life easier for developers using GWT/App Engine alongside >>>>> third-party tools, including Maven and Eclipse for Java EE. In my post, I >>>>> promised we'd let you download a preview of 1.3 to get some hands-on >>>>> testing >>>>> of the new features and provide us with your feedback before the official >>>>> release. >>>>> >>>>> I'm happy to announce that the time has come. An early preview of 1.3 >>>>> is now available for download at the following URLs: >>>>> >>>>> >>>>> http://dl.google.com/eclipse/plugin/3.5/zips/com.google.gdt.eclipse.suite.e35.feature_1.2.101.v201003031407.zip >>>>> >>>>> >>>>> http://dl.google.com/eclipse/plugin/3.4/zips/com.google.gdt.eclipse.suite.e34.feature_1.2.101.v201003031407.zip >>>>> >>>>> >>>>> http://dl.google.com/eclipse/plugin/3.3/zips/com.google.gdt.eclipse.suite.e33.feature_1.2.101.v201003031407.zip >>>>> >>>>> Note: Ensure that your version of Eclipse has Eclipse's Web Standard >>>>> Tools (WST) installed before installing the plugin. WST can be installed >>>>> by >>>>> navigating to the Software Installation section, and selecting the the >>>>> appropriate WST feature from the update site for your version of Eclipse. >>>>> The update sites and feature names are provided below: >>>>> >>>>> >>>>> - 3.5 (Galileo): Galileo > Web, XML, and Java EE Development > >>>>> Eclipse Web Developer Tools >>>>> - 3.4 (Ganymede): Ganymede Update Site > Web and Java EE >>>>> Development > Web Developer Tools >>>>> - 3.3 (Europa): Europa Discovery Site > Web and JEE Development > >>>>> Web Standard Tools Project >>>>> >>>>> This is a preview build, so the usual caveats and warnings apply: it >>>>> is not officially supported, and we recommend using a clean installation >>>>> of >>>>> Eclipse and a new workspace. Also, we're distributing this preview as a >>>>> zip >>>>> file so be sure to follow the instructions on our Installing the >>>>> Google Plugin for Eclipse from zip files page ( >>>>> http://code.google.com/eclipse/docs/install-from-zip.html). >>>>> >>>>> *Known Issues* >>>>> >>>>> >>>>> - If you change launch configuration settings in the Server or GWT >>>>> tab, you'll need to switch to the Arguments tab before clicking Apply >>>>> or >>>>> Run/Debug. This will be fixed in the final release. >>>>> >>>>> That being said, we are very interested in your experience with this >>>>> new release, which we hope will allow the Google plugin to interoperate >>>>> much >>>>> better with alternative project structures and third-party tools. The >>>>> tentative 1.3 release notes are as follows: >>>>> >>>>> Enhancements >>>>> >>>>> >>>>> - Configurable WAR directory to allow better integration with Eclipse >>>>> for Java EE <http://www.eclipse.org/downloads/moreinfo/jee.php> and >>>>> projects built with Maven <http://maven.apache.org/> >>>>> - Web Application launch configurations now display and allow >>>>> editing of generated Program and VM arguments >>>>> - Errors/Warnings preference page for customizing the severity of >>>>> any generated problem marker >>>>> - Projects can reference GWT/App Engine SDKs directly via JARs >>>>> instead of through SDK library >>>>> - GWT+App Engine projects automatically configured for optimal >>>>> caching >>>>> >>>>> Fixes >>>>> >>>>> >>>>> - GWT Issue >>>>> 3583<http://code.google.com/p/google-web-toolkit/issues/detail?id=3583>: >>>>> Google Eclipse Plugin configuration is too strict >>>>> - GWT Issue >>>>> 3592<http://code.google.com/p/google-web-toolkit/issues/detail?id=3592>: >>>>> Eclipse plugin to add 'cache forever' configuration for new 'GWT + App >>>>> Engine' projects >>>>> - GWT Issue >>>>> 3902<http://code.google.com/p/google-web-toolkit/issues/detail?id=3902>: >>>>> Allow users to configure the severity of problems reported by the >>>>> eclipse >>>>> plugin >>>>> - App Engine Issue >>>>> 1515<http://code.google.com/p/googleappengine/issues/detail?id=1515>: >>>>> Eclipse plugin requires fixed location for war directory >>>>> - App Engine Issue >>>>> 2115<http://code.google.com/p/googleappengine/issues/detail?id=2115>: >>>>> Using the @PersistenceAware annotation puts the Eclipse Enhancer in an >>>>> Infinite Loop >>>>> - App Engine Issue >>>>> 1941<http://code.google.com/p/googleappengine/issues/detail?id=1941>: >>>>> Plugin fails to enhance dependent classes on source level changes >>>>> >>>>> For a complete list of fixed issues, see the GWT issue >>>>> tracker<http://code.google.com/p/google-web-toolkit/issues/list?can=1&q=label:GPE_1_3> >>>>> and App Engine issue >>>>> tracker<http://code.google.com/p/googleappengine/issues/list?can=1&q=label:GPE_1_3> >>>>> . >>>>> >>>>> We encourage all interested developers to take the preview build for a >>>>> spin, and let us know what you think. We'll do everything possible to >>>>> incorporate your feedback before the final release, slated for later this >>>>> month. Thanks! >>>>> >>>>> Keith, on behalf of the Google Plugin for Eclipse team >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Google Web Toolkit" group. >>>> To post to this group, send email to >>>> [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]<google-web-toolkit%[email protected]> >>>> . >>>> For more options, visit this group at >>>> http://groups.google.com/group/google-web-toolkit?hl=en. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Google Web Toolkit" group. >>> To post to this group, send email to [email protected] >>> . >>> To unsubscribe from this group, send email to >>> [email protected]<google-web-toolkit%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/google-web-toolkit?hl=en. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Web Toolkit" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<google-web-toolkit%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-web-toolkit%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
