Facing issue while importing a Liferay project into eclipse
Saying :
'Creating SDK Projects' has encountered a problem.
Failed while installing Liferay Theme 6.0
Related
I installed Netbeans 11.3 under Ubuntu 18.04 and created in the following a new Groovy project.
Choose File > New Project (Ctrl-Shift-N;\u2318-Shift-N on Mac) from the main menu to open the New Project wizard.
Select Java Application in the Java category. Click Next.
Type GroovyJavaDemo as the Project Name and specify the folder where you want to create the application in the Project Location field.
Deselect the Create Main Class checkbox. Click Finish.
Next, I created a Groovy Script file with only this content println "Hello" and it caused the following problems:
ant -f /home/ubuntu/NetBeansProjects/GroovyJavaDemo -Djavac.includes=Hello.groovy -Drun.class=Hello run-single
init:
deps-jar:
Created dir: /home/ubuntu/NetBeansProjects/GroovyJavaDemo/build
Updating property file: /home/ubuntu/NetBeansProjects/GroovyJavaDemo/build/built-jar.properties
Created dir: /home/ubuntu/NetBeansProjects/GroovyJavaDemo/build/classes
Created dir: /home/ubuntu/NetBeansProjects/GroovyJavaDemo/build/empty
Compiling 1 source file to /home/ubuntu/NetBeansProjects/GroovyJavaDemo/build/classes
/home/ubuntu/NetBeansProjects/GroovyJavaDemo/nbproject/build-impl.xml:1120: The following error occurred while executing this line:
/home/ubuntu/NetBeansProjects/GroovyJavaDemo/nbproject/groovy-build.xml:26: Error running forked groovyc.
BUILD FAILED (total time: 1 second)
What did I miss?
Thank you in advance,
I don't think you missed anything, since I can reproduce your problem with JDK 11 on NetBeans 11.3.
However, there is a (somewhat unsatisfactory) workaround that worked for me:
Install JDK 8 (if necessary).
Edit the NetBeans file etc/netbeans.conf and set the JDK that NetBeans uses to JDK 8. In my case I added the line netbeans_jdkhome="C:\Java\jdk1.8.0_221" to netbeans.conf.
Restart NetBeans then rebuild your project. It should compile now:
Notes:
You could bug report this issue to the NetBeans team if you wish.
I also tried using JDK 14 as the default Java platform for NetBeans and got a different error: NoClassDefFoundError: Could not initialize class org.codehaus.groovy.vmplugin.v7.Java7. See the Gradle bug JDK 14 support #10248 for more information on that.
Setting JDK 8 as the default platform for NetBeans doesn't prevent you from adding other Java platforms (Tools > Java Platforms > Add Platform...) such as JDK 11 and JDK 14 for your individual projects.
Edit the groovy-build.xml and replace <groovyc javahome="${platform.home}" with <groovyc javahome="${jdk.home}" it works for me on JDK 1.8
Please find here the solution for Open-JDK-13
I am facing an issue when I publish my .NET Core 2.1.1 app to IIS and this has started to happen after upgrading from .NET Core 2.1 to 2.1.1.
I am getting Cannot find compilation library location for package 'Microsoft.NETCore.App'.
I tried to reinstall/uninstall/install the SDK 2.1.301 and the related runtime but no success.
This works fine on my dev PC but not on the IIS server.
I fixed my issue by setting MvcRazorExcludeRefAssembliesFromPublish to false in my .csproj file.
I updated Xamarin Mvvmcross 3.2.2 project to 3.5 for Unified API support.
Mvvmcross.HotTuna 3.5 package is added in project.
So there are Mvvmcross.HotTuna.CrossCore and Mvvmcross.HotTuna.MvvmCrossLibraries packages can be seen under Package folder.
But cannot find binding assemble, so "using Cirrious.MvvmCross.Binding;" is not resolved.
And MvxTouchSetup is also not resolved
The project worked well with Mvvmcross3.2.2.
Now what other nuget packages should be added in the project?
No package is added newly.
The 3.5 libraries package has been updated to include the new MvvmCross.Touch.dll for lib\Xamarin.iOS10\ - see https://github.com/MvvmCross/MvvmCross/blob/3.5/nuspec/MvvmCross.HotTuna.MvvmCrossLibraries.3.0.1.nuspec#L72
The 3.5 crosscore package has bee update to include the new MvvmCross.Binding.Touch.dll for lib\Xamarin.iOS10\ - see https://github.com/MvvmCross/MvvmCross/blob/3.5/nuspec/MvvmCross.HotTuna.CrossCore.3.0.1.nuspec#L91
If the update isn't working for you:
read the advice on http://kerry.lothrop.de/unified-api-for-xamarin-ios/ about how to update the unified
check you have updated your own project to Xamarin iOS unified
check you have up-to-date nuget installed
clean, rebuild, swear and retry until it all works
I'm having an issue with a custom hook I'm deploying in Liferay.
I've created both a hook and a theme using Liferay Plugins SDK 6.2.0
I create a .war (with Eclipse's built in Liferay -> SDK -> war command) for my theme, and deploy it onto my server running Liferay EE 6.2, which works fine.
However, I repeat the same process with my hook and I get this error:
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.UnsupportedClassVersionError: com/bofa/UserLoginImpl :
Unsupported major.minor version 51.0 (unable to load class com.bofa.UserLoginImpl)
at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassL
oader.java:2908)
I'm not sure if this could be a Java Compiler version error like I've read about, because my theme uses the same exact settings and works properly.
Any ideas?
Its because of different JDK at compile time and runtime, make sure you are using same JDK version to compile and run it.
It generally occurs if a higher JDK version is used to compile the java file and a lower JDK version is used at runtime
I installed Visual Studio 2012 Update 1 and now I can't add a reference to any project.
The Add Reference dialog does not open at all.
The ActivityLog.xml contains these errors :
550 Begin package load [ReferenceManagerPackage] {48D4A2C1-02AD-4F18-9153-620511BACB7B} VisualStudio 2012/12/09 00:39:58.544
551 ERROR CreateInstance failed for package [ReferenceManagerPackage] {48D4A2C1-02AD-4F18-9153-620511BACB7B} 80131522 VisualStudio 2012/12/09 00:39:58.575
552 ERROR End package load [ReferenceManagerPackage] {48D4A2C1-02AD-4F18-9153-620511BACB7B} 80004005 - E_FAIL VisualStudio 2012/12/09 00:39:58.575
I'm on VS2012 Professional.
Following a suggestion from the Visual Studio Setup and Installation forums, I uninstalled and reinstalled Visual Studio and the problem is gone for now ...
Note that I had difficulties uninstalling Visual Studio, I guess the install had been corrupted but by what ?