This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 190883 - I get "provide a valid google app engine location" when I point to the correct path of GAE
Summary: I get "provide a valid google app engine location" when I point to the correc...
Status: RESOLVED WONTFIX
Alias: None
Product: third-party
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 7.0
Hardware: PC Windows 7 x64
: P4 normal with 1 vote (vote)
Assignee: issues@third-party
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-10 17:42 UTC by webdesignporto
Modified: 2012-03-21 03:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: "provide a valid google app engine location"

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description webdesignporto 2010-10-10 17:42:51 UTC 
I get "provide a valid google app engine location" when I point to the correct path of GAE.

I have the version 6.9.1 and the google engine plugin for 6.9.
I have installed the GAE 1.3.7 SDK and I keep getting this error "provide a valid google app engine location" when I point to the correct path of GAE.

How to get this:
Install google app engine plugin for 6.9
Then in the services->Servers right click -> "Add server" -> next
Here you have to put the installation location and when I point to the valid app engine installation i get: "provide a valid google app engine location".

What I've try:
Reinstall netbeans
Reinstall gae
Try different paths to install gae
Try different subpaths of the root folder of gae to set as installation location
Restart

Can somebody fix it, so I can use it? thanks a lot!  ;)
Comment 1 webdesignporto 2010-10-10 17:43:11 UTC 
none
Comment 2 Marian Mirilovic 2011-11-07 08:53:15 UTC 
Please report against http://code.google.com/p/googleappengine/issues/list
Comment 3 thufir 2012-03-21 03:05:36 UTC 
the request is to fix it, however.