- This topic has 13 replies, 4 voices, and was last updated 10 years, 3 months ago by
.
-
Posts
-
I’m getting this error now when I try to build my PhoneGap projects:
Primary rutnime of project ### does not support available PhoneGap Target Runtimes. Do you want to choose a different one now?It worked before the 2014-07-30 update.
Switching to a different runtime solved the problem. Anything to consider? Also, is it still not possible to use PhoneGap 3.5.0?
Thank you for the help.
Lofi,
There was an error in the runtime Ids of PhoneGap projects created in CI1 and CI2, we decided to nip this problem in the bud and change the Id now before we hit GA.
However, a migration process is supposed to take care of this problem, you should have seen a migration wizard that would prompt you to migrate the project. Did no wizard appear for you?
Alternatively, there is a Project Migration view which would allow you to migrate the projects manually (though as I stated above, you should have been guided through the process). If you revert your project back to original state (if you have one in a VCS) – then you could use the migration view to migrate though right now you don’t need to do anything.
Do let us know if the wizard did not show up for you.
Regarding PhoneGap 3.5.0, it’s still not supported for remote builds from our testing and so we are unable to move to it globally yet.
You are free to install a copy locally (I believe we discussed this in another post) and use that for local builds.
@Support-Brian wrote:
However, a migration process is supposed to take care of this problem, you should have seen a migration wizard that would prompt you to migrate the project. Did no wizard appear for you?
Alternatively, there is a Project Migration view which would allow you to migrate the projects manually (though as I stated above, you should have been guided through the process). If you revert your project back to original state (if you have one in a VCS) – then you could use the migration view to migrate though right now you don’t need to do anything.
Do let us know if the wizard did not show up for you.
No, the wizard didn’t show up. And I can’t migrate via the Migration view. Nothing happens when I open the view. Is there some kind of trigger I can invoke? My test project still has the old runtime. I can try stuff if you like, but I’m happy the way it is with changing it all manually. Just let me know.
@Support-Brian wrote:
Regarding PhoneGap 3.5.0, it’s still not supported for remote builds from our testing and so we are unable to move to it globally yet.
You are free to install a copy locally (I believe we discussed this in another post) and use that for local builds.
Yes, I couldn’t find the thread anymore. But thank you, I’ll add it manually.
Lofi,
There is MyEclipse Menu -> Migrate Workspace , when you click the Migration wizard should pop-up. Can you please try this ?
————————————–
Swapna R
MyEclipse SupportYes, that worked. So the problem is only that the wizard doesn’t pop up automatically. Fyi, neither closing and reopening, nor refreshing the project activates the wizard. If you want me to try other stuff, let me know. I still got 4 projects which need migration and which I can try.
Can you please check if Build Automatically is selected ? Project Menu -> Build Automatically, if this is not selected then On Project -> Clean the builder will poop-up the Migration wizard, You can try either of them.
——————————————————
Swapna R
MyEclipse SupportYes, Project -> Build Automatically is selected. And Project -> Clean doesn’t do anything as far as I can see.
Oh then there is another Preferences setting which could have been turned on
Can you please go to Preferences -> MyEclipse -> Project Migration and check if the check box “Disable Automatic scanning for Migration” is selected, if yes then please unselect this option and try to restart MyEclipse.
Swapna R
MyEclipse SupportNo, it’s not selected. And even if I select it and restart MyEclipse, it isn’t selected afterwards, which is a bug.
However, I’m getting the license expiration reminders. Maybe it got sth to do with the license stuff? License should be fully valid though.
@Support-Brian wrote:
Regarding PhoneGap 3.5.0, it’s still not supported for remote builds from our testing and so we are unable to move to it globally yet.
You are free to install a copy locally (I believe we discussed this in another post) and use that for local builds.
How would you do that? The MyEclipse Embedded PhoneGap 3.3.0 Runtime seems to be hardcoded. I downloaded the PhoneGap files, but have no idea about where to put them. eg files seem to be injected during a build. But from where?
Thank you very much for the help.
Never mind, found it myself. Here’s what to do in case others feel like doing the same:
+ download phonegap 3.5.0: http://phonegap.com/install/
+ in MyEclipse: Window -> Preferences -> MyEclipse -> Mobile Tools -> PhoneGap Runtimes -> Add
Runtime Name: PhoneGap 3.5.0 Runtime
Runtime Location: C:\PhoneGap_3.5.0\node_modules\phonegap+ click Validate
=> PhoneGap version is displayed
That was it.
Lofi,
We’ve added support for PhoneGap 3.5.0 with 2015 CI 4 (including security fixes required for Android), so you if you update, you should see an embedded version of PG as well – remote build also works.
Note: For now, you do need to be online when creating PhoneGap projects, we’ll fix that in the next release.
Do let us know how it works for you.
