I'm running Eclipse Neon (tried with Mars too) and Liferay 6.2
I try to run the service builder but:
If I run with java 8 (unsupported, I know), it says it requires a 1.6 compliant JVM. Correct.
If I run with java 7, it says "Unsupported major.minor version 52.0". That's my nightmare.
Yes, I've cleaned everything before. In fact, I created a brand new project, in an Eclipse with only jre7 installed, pointing all to jre7 (compiler, facets...)
Eclipse is running over jre8, but can't run on jre7 because some of the plugins requires jre8. Anyway, some days ago it do worked in this Eclipse, so it's not the problem.
Service Builder might pull code from more than your Eclipse project setup - e.g. from the running Liferay installation that the plugin sdk points to.
I've not heard of a com.aspr.seu package in Liferay - is that your own, or unknown to you as well?
If service builder ran in the past (e.g. with Java 8), it created a yourprojectname-service.jar - that might be one that is pulled into the build process and that you might not have cleaned yet. You definitely have a class that was built with Java 8 on the classpath, you'll just need to find it. It might help to know that servicebuilder is executed through an Ant task outside of Eclipse, thus it might not be enough to search through all of the files that Eclipse has configured on its classpath, but rather on what's configured for the Plugins-SDK
Related
I am currently having an issue with setting up a Tomcat server to run a Java 8 servlet. I've included snippets of the settings that are relevant to the issue. As you can see, I have jdk-1.8 installed and bound to the project build path. I have spent hours trying to figure out why Eclipse keeps saying Java 1.8 is not supported by Tomcat 9. If you look in at the project facets runtimes, you'll see that the server shows jre-1.7 even though I have set the path to the jre-1.8. I'm convinced this is where the issue is, but I have no idea how to fix it. I've tried setting the same Tomcat server up on another machine with no problems so I'm confused as to why it isn't working on this one. The major difference between the two is that the one that works properly shows jre-1.8 in the runtimes.
I am using Eclipse Oxygen on Windows 10
So it looks like I had Java 1.7 still installed in my machine (Java 1.8 was there too) so I went ahead and uninstalled the older version and then I reinstalled Eclipse Oxygen. Everything works now. The runtimes are showing jre-1.8. I have not a single clue exactly why it wasn't working before; but if you have this same issue, try giving this a shot.
I am trying to configure Grails in Netbeans.
Grails version:3.2
Netbeans: 8.2
JDK: 1.8
OS: Windows 10
I have install and configured environment path and other stuffs. I can create and run project from the Command Prompt. But I can not create project from netbeans.
Warning |
Unrecognized flag: non-interactive.
Error |
Specify an application name or use --inplace to create an application in the current directory
This error is showing, to create project from Netbeans. I can run the created project though. I have already added Groovy plugin.
How can I solve this problem?
I don't think you are doing anything incorrectly. I have an environment very similar to yours (Grails version: 3.3.2, Netbeans: 8.2, JDK: 8u151, OS: Windows 10) and I see the same error: Specify an application name or use --inplace...
This is a known issue with NetBeans 8.2 that has already been bug reported; see Bug 258407 - Error when creating a Grails 3.1.x project. The problem has been confirmed to exist in Grails releases 3.1.0 up to 3.1.4, but I see the same issue in 3.3.2, and there is no fix for NetBeans 8.2.
However, I successfully created a Groovy/Grails application using JDK 8u151 with a DEV release of NetBeans which you can download from here: http://bits.netbeans.org/download/trunk/nightly/latest/
Note the caveat that comes with using DEV releases of NetBeans:
These builds are still under development and could contain defects
that lead to data loss. They are meant for evaluation of new features.
As always, be sure to back up your changes if you use these builds on
your production code.
As long as you can you can live with that situation, using a DEV release is your (only) solution for creating Grails 3.x applications in NetBeans.
One final point: unlike NetBeans 8.2, DEV releases of NetBeans support Java 9 as well as Java 8, but don't use Java 9 when creating a Groovy/Grails applications. It won't work for a completely unrelated reason.
I'm using Windows 8 and Grails 3.3.8, but the following worked for me:
Create the project using system command line (I used instructions in this page: how to create grails project through windows command promt).
Import the project to Netbeans 8.2 by clicking on File > Open Project... and selecting the project folder.
This solution works for me (Mac OS)
1) Open de console inside Netbeans
2) Navigate to your GRAILS_HOME/bin
3) Type grails create-app [YOUR_NAME_APP] --profile=web (rest-api, etc)
4) The project must be created at GRAILS_HOME/bin/[YOUR_NAME_APP]
5) Do not try to import into Netbeans instead of it Open the project
6) Start coding!
You can move the folder GRAILS_HOME/bin/[YOUR_NAME_APP] to the Netbeans workspace before open the project.
FYI, I am using netbeans 9 and grails 3.3.8 (dont use 3.3.9, its broken), and it works like a dream. I can create domain classes etc. from the menus in netbeans, run, debug etc. THe only thing I had to do was manually install the grails plugin for netbeans, and configure my grails paths etc. The answer on how to set this up is here: how to open a grails 3.3 app in netbeans 9?
The only thing I cant get to work (and its a bit of a show stopper), is multi-module projects (i.e. a grails app which depends on a grails plugin). I can run them, but netbeans does not recognise any of the imports so there is no code completion and it shows all files are having errors. What a shame, as appart from this, netbeans has very good grails support.
Note, I always create projects on the command line, e.g. "grails create-app myapp ...", then simply use the open project menu in netbeans and it instantly recognises them as grails.
Ensure you have gradle plugin installed for netbeans. Then go to File -> Open Project.
You should see the project shown by netbeans as a gradle project.
I've developed an IntelliJ plugin in Java 8 on OSX. During the development everything worked, I was able to run a test instance of IntelliJ with my plugin preloaded without any issues.
However, after I've built my plugin and tried to install it in the real IntelliJ I get an error saying "Unsupported major.minor version 52.0", which clearly means that IntelliJ is running on some older Java. Indeed it seems it's running on Java 6.
I tried changing JVMVersion in Info.plist, but the application wouldn't start afterwards. What I can't understand is that the test instance would run smoothly so it would seem running IntelliJ on Java 8 is perfectly possible.
But how to do it?
You should be editing idea.properties instead of the plist. More info at IntelliJ support: https://intellij-support.jetbrains.com/entries/27854363-IDE-doesn-t-start-after-updating-to-Mac-OS-Yosemite-or-Mavericks
I'm trying to install the PMD source code analyser plugin for Eclipse. It's available through Eclipse Market Place, but I'm getting following problem in the phase of installation :
Why am I getting this problem ?
EDIT
I do not have this menu even though I have added the ruleset configuration file
I'm the creator of eclipse-pmd, the plugin you are trying to install. I tried to install it myself just now and it worked without any problems. So I can only guess what could be the problem in your case:
The repository was temporarily not available
Simply try again.
You are using a (very) old version of Eclipse
The plugin requires Eclipse Indigo (3.7) or later. I tried to install eclipse-pmd with Indigo and Luna just now and it worked both times.
Run Eclipse with Java 7
You need to run Eclipse with a JRE 7 or later. There have been problems during the installation with people using an older JRE in the past. However they could finish the installation but Eclipse silently refused to load the plugin (this has been fixed a few versions ago though).
Proxy configuration
Although unlikely as you came this far, please open the proxy configuration in Eclipse and check if the settings are correct and the domain is accessible.
If you tried everything I suggested above and are still not able to install the plugin, please head over to the project's Github page and open an issue.
I have a clean, vanilla system (Mac OS 1.5) with Java 6 installed - I have also installed the latest version of Grails (2.0.0.RC3) and STS (2.8.1), together with appropriate extensions:
Grails Support
Groovy 1.8 Compiler
Within STS I have navigated to Peferences -> Groovy -> Compiler and changed it to use version 1.8 compiler (rather than 1.7).
I have then created a blank Grails project from the command-line (using "grails create-app", etc) and everything works fine - I can compile/test/run it.
However, when I access the problem via STS/Eclipse I get a Bad version number being reported on conf/ApplicationResources.groovy; nevertheless, the project still works - I can still compile and run from within STS, but the auto-build feature keeps kicking in and reporting the same compilation problem on this file...
Can anyone shed any light on why this might be and how to solve it?
I have done various clean operations, such as "grails clean" and removed the ~/.grails and ~/.groovy directories in case of a stale class file, but it's made no difference so far...
Any help much appreciated!
It seems my answer to Eclipse problems (not specific to STS) was usually do clean install. You likely have already heard this and perhaps I should not post as an 'answer' (I'm new to stackoverflow) but my team uses IntelliJ IDEA across the board. Some start with STS for familiarity but eventually that gets overridden by IntelliJ's Grails support. It is worth giving it a try over Christmas break. You can try the Ultimate edition (has Grails support) for free for at least 30 days and if you like, you can probably get an extension (I did for several months until my boss stepped up).
Removed comment as issue returned