I have downloaded the latest version of eclipse and the latest version of javafx, created a new user library which contains all of the javafx files (I have used this tutorial).
I've noticed that unlike older eclipse versions, there is no "scene builder path" setting in the latest eclipse, and when I attempt to create a new project there is no such thing as "JavaFX Project" (I remember having this option that automatically created an fxml file and control,main classes.)
My question is how do I make it all work together like it used to in the older eclipse versions?
(I know that there's something called e(fx)clipse but I believe it is outdated since it refers to javafx 2, and I have downloaded version 11)
Just go to the eclipse marketplace and install e(fx)clipse. It is not outdated and should provide you with the functionality that you are looking for.
Related
I am using the Vaadin Plug-in for Netbeans version 1.1.0 with NetBeans 8.1 & 8.2 (as shown here. This plugin defaults to using Vaadin 7.5.9 rather than the current version of Vaadin for a new project created by choosing File > New Project > Categories (list) > Vaadin > Projects (list) > Vaadin Multi Module Project.
How does one change the Vaadin version from 7.5.9 to 7.7.3 (the latest)?
By context-clicking on the “…-ui” module in the Projects navigator in NetBeans, I accessed the Properties > Project Properties > Categories (list) > Vaadin (list item) > Vaadin Version pop-up menu.
This seemed to work. But when I do a clean-and-build on the …-parent module, I still see line items for Vaadin version 7.5.9 in the NetBeans console output.
So what is the proper way to get a Vaadin multi-module project in NetBeans 8 to use a later version of Vaadin?
You are right. Something is broken with latest Vaadin version support for projects.
Version 7.5.9 used to be the latest available version when the NetBeans plugin has been built. To be able to support latest stable versions plugin reads some URL from vaadin.com site and uses versions from there.
But apparently this is broken. New projects are created with old version.
Could you please create a ticket for that here https://github.com/vaadin/netbeans-plugin/issues ? Thanks a lot.
We are working currently on Vaadin version 8.0 and soon we will have to release new NetBeans plugin version to support it. So this issue might be fixed in this update.
Multimodule project support is not completely implemented unfortunately. That's why version is not correctly updated via project settings.
You can create an issue about this as well (though I think I already made it in our old tracker https://dev.vaadin.com/).
But back to your issue: you can fix it via editing POM file manually.
Please open POM.xml file in your root parent project and find
<properties>
section.
There is <vaadin.version>7.5.9</vaadin.version> string. Just replace 7.5.9 with required version.
Thanks and sorry for inconvenience.
I have an Eclipse plugin that was originally written (not by me, and I don't have access to the original developer) that I'm trying to update for Eclipse Luna, because it stopped working when my team updated to Eclipse 4.4.
I downloaded the Luna Plugin development version, cleared a few warnings, updated some broken code, fixed a few bugs, and tested with "Run As -> Eclipse Application
This worked fine: all the views showed up, the preferences pages, etc.
So then I tried to export the plugin so I could test on a fresh installation of vanilla Eclipse Luna. I did that by using the Export Wizard:
And generated a deployable set of jars with said wizard:
I copied the generated folder (which contains all the jars appropriately) into the dropins folder of my fresh vanilla Eclipse Luna and started it up.
Unfortunately, I got the following error:
Which led me to this SO question and this Eclipse bug report, which explains that I have a 2.x style plugin that uses the plugin.xml instead of an OSGi style manifest.mf. Continuing my search, I found this SO question, which was directed at a 3.x version of Eclipse, but I used the 4.x equivalent:
Which I used with the following options checked:
And I accepted all the changes in the previous pane after the (long-running) changeset. However, upon deploying to my vanilla install, I got the same error about the plugin converter. That led me back to this SO question, which recommending installing the Eclipse 2.0 plugin support package. I did so and restarted Eclipse. The error in my error log did stop showing up, however the view/preferences/etc for my plugin are still not showing up. The plugin does show up under Help -> Installation Details -> Plug-ins, but doesn't seem to be interacting at all.
The text of the plugin.xml can be found here at Pastebin. The text of the MANIFEST.MF can by found at this other Pastebin link
Any suggestions for getting my plugin to work through the manual export so the other developers on my team can test my changes before I try releasing the update to the world?
I'm trying to learn the new application model thingy in Eclipse 4, coming from the previous 3.x world. One thing that is unclear to me is...How to make a Plug-in project like the plain old Plug-in project in 3.x version?
I'm asking because when I try to create a new Eclipse 4 project:
File -> New -> Other -> Eclipse 4 -> Eclipse 4 Application Project and fill the necessary fields, I get a project that if I right click in the .product file and run it, always get a RCP application.
I tried comparing an old 3.x plugin.xml file from a Plug-in 3.x project with a Eclipse 4 plugin.xml project and I can't see any difference that indicates that is going to be a RCP instead of an IDE extension...
I guess I can go with creating a 3.x Plug-in project, but I keep wondering why I can't simply develop IDE extensions using the new Eclipse 4 application model (which I kinda like...)
What I'm missing here? Any ideas? Is it not possible (yet) to develop IDE extensions using Eclipse 4?
Thanks!
You can use the normal New Plug-in Project to create a plug-in for Eclipse E4. Be sure not to select the 'This plug-in will make contributions to the UI' check box as that will introduce Eclipse 3 dependencies.
Use 'New / Eclipse 4 / New Model Fragment' if you want to add an Eclipse 4 model fragment to the plug-in.
I've just downloaded the FDT IDE Free version from its website. I wanted to use it for Haxe development so at first startup I chose to develop Haxe projects only. However in the "New FDT Project" window I cannot find the Haxe project templates:
I added the Haxe and Neko paths in the preferences but it didn't solved it. I also tried to add them in the "Installed SDKs" tab but I got an error stating that it couldn't find SDKs in that given folder. My last desperate try was to extract a new FDT application and set it that I want to develop AS and Flex applications too but no luck. I still cannot create Haxe projects.
However what is wierd that the version of FDT is around 1.x.x.x:
But as far as I know the latest version is 5.5. Does the free version have separate versioning or I managed to download an outdated version? If the last is true then I don't really know where could I get the latest release since as mentioned above, I downloaded it from the official site.
The same goes for using FDT as a plug-in in an Eclipse Juno installation. Haxe projects are missing there too.
Checked the AppData folder of FDT, and there are Haxe project templates but no Haxe project type:
I originally downloaded the win64 version, but already tried the win32 version and still no Haxe project.
Chatted with tech support at FDT. Apparently, minor bug in the project template configuration files that will be fixed with an upcoming release.
Unsure where they are on non OSX platforms, but for the mac, they are in:
~/Library/Application Support/FDT/projectTemplates2/haxe/*/description.xml
Edit the files and change the 'version' tag from 2.7 to 2.8. Then relaunch FDT and the Haxe project templates will display.
I checked in eclipse/java plugin project from svn repository.
Eclipse automatically builds the code to show hundreds of errors.
It seems like that eclipse doesn't properly link to the plugin libraries. Googling to find this site that I need dependencies and other tabs in plugin.xml.
What might be wrong? I use Indogo(3.7) on Mac OS X 10.7.4
I used Indigo (3.7) for my Mac, but it happened so that the plugin was built on Helios (3.6). When I run the plugin using Helios, I got the project compiled without errors.
It seems like that some of the plugins are (heavily) version dependent.
Looks like you got the base XML editor instead of the plugin.xml editor.
This is probably caused by your not having the eclipse plugin development environment (PDE) enabled in a new workspace.
Try creating a new plugin project (this will enable the necessary plugin tools), or go to the preferences and enable the "correct" capability. Since the capabilities seem to change from release to release, I always use the first method and then delete the new project.