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.
Related
I downloaded J2ME plugins from here: https://www.oracle.com/java/technologies/javame-sdk-downloads.html
I can't install the plugins, this is the error:
Some plugins require plugin Java Profiler Core to be installed.
The plugin Java Profiler Core is requested in version >= 2.1.1 (release version 2) but only 3.41 (of release version different from 2) was found.
The following plugins are affected:
Java ME SDK CPU Profiler Snapshot Viewer
Profiler (Java ME Projects Support)
Please help me, thank you
First a couple of basic points:
I don't know whether Java ME works with NetBeans using a JDK version > 8 so I first set the default platform for NetBeans to JDK 8. This step may not be necessary, but it definitely works.
Do not download the NetBeans plugins from the Oracle page you linked to. Instead, use the approach detailed below to use older plugins which are compatible.
In NetBeans 12.4:
Go to Tools > Plugins > Settings and click Add to add http://updates.netbeans.org/netbeans/updates/8.2/uc/final/distribution/catalog.xml.gz as an Upgrade Center, then check the Active column for its entry.
Click the Available Plugins tab. You should see four entries for Java ME. Click the Install checkbox for all four, then click the Install button to install those plugins:
Next download oracle-jmesdk-8-0-rr-win32-bin.exe from the Oracle page you linked to, then run the downloaded executable to install the Java ME SDK to a location of your choice (if you haven't already done that).
Add the ME JDK you just installed as a Java Platform within NetBeans using Tools > Java Platforms > Add Platform.... The exact steps are detailed in the update at the end of this answer to How to fix Netbeans 8.0 not detecting Java ME.
So Java ME SDK has been added as a Java Platform, and the older Java ME... plugins have been installed. The final step is to verify that you can now use the Project Wizard to create a Java ME Embedded Application in NetBeans 12.4:
Select Files > New Project... and you should see a new entry in the list of Categories list titled Java ME Embedded. In the Projects list there will be a single entry titled Java ME Embedded Application:
Click Next >, and you should see a screen similar to this:
Set the Project Name field, and any other fields, as necessary.
Finally, click Finish to create the Java ME project.
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.
I have the task to do some work on our GWT 2.2 code base with
the GWT Config, etc, used, is long gone. And I must use Eclipse Kepler.
Does current GWT provide backward compatability that far?
Any thoughts?
The version of the Eclipse plugin is independent of the version of the SDK you use in your project. You can use the newest plugin with GWT projects that needs older versions of the SDK.
You have to set this up in the project properties.
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.
I have an Eclipse/Maven web project. I'm trying to update the facets to support JSF2. However I can't update the dynamic web module to 3.0 (or even 2.5) because Eclipse refuses to recognize that I'm using Java 1.6. It shows Java 1.6 in the facet properties, but every time I try to change the dynamic web module to 2.5 or 3.0, it tells me I must use Java 1.6 even though that is selected. How can I solve this?
I'm not sure if and how Maven plays a role here, but ignoring that, you can alternatively also change the project facets by editing the .settings/org.eclipse.wst.common.project.facet.core.xml file. You can find the file when you browse in Navigator view (instead of Project Explorer). To set the dynamic web project facet version to 3.0, edit the following entry (with an unknown version, represented by ...)
<installed facet="jst.web" version="..."/>
to
<installed facet="jst.web" version="3.0"/>
If that doesn't solve the concrete problem, then most probably some Maven plugin has forced the facet versions based on a pom.xml or so.
Had the same problem, looked at the .project file of my maven/eclipse project.
Turned out, that you have to first make the Project a Java project in your Project facet project preferences page!
Unfortunately, as of right now, Eclipse Java EE tooling does not support changing spec versions on module facets (ear, ejb, web, etc.). You can edit the metadata file directly as BalusC has described and patch up any other source compatibility issues. Alternatively, you can create a new project with the appropriate spec version and copy you source into it.
If like me you find that only your Dynamic Web projects have this problem, try checking whether the server you are deploying to is configured for the JRE version you want. (Global Preferences -> Server -> Runtime Environments; then edit the server runtime environment in question.)
You may also need to manually edit your Eclipse settings, as suggested by BalusC and Konstantin. If you do, after restarting Eclipse re-open the Facets preference pane and click OK or Apply. This lets Eclipse sanity check your new setting.