I was having some issues where I was unable to get a build on a separate springBoot project. I read an online forum that recommended updating to the latest so I bumped it and immediately Intellij stopped recognizing the build.gradle and it was no longer recognized as a build tool. I attempted opening the build.gradle files and invalidating the caches and restarting, but Intellij wouldn't recognize it.
I attempted cloning the gradle spring-boot starter project and I saw the same thing (https://github.com/spring-guides/gs-spring-boot.git). It did, however, work when I just open the complete subfolder as it's own project. Are there specific steps I should be taking to allow Intellij to mark subprojects and use gradle as my build tool?
Update: I was running MacOS High Sierra and there were issues with the latest versions of openJDK and Gradle running on the machine. I ended up having to do a factory reset and getting up to the latest OS to make it work.
Related
I need to open a gradle project, but IntelliJ doesn't support gradle versions below 3 (this one is in 2.7). I tried clicking the upgrade gradle version and reimport project link in the console, but that didn't work. I then tried to switch the boot JDK to java 8, but it says i can't go below 11. I have seen other people post in having the same problem in the same project, so I'm confident that switching the boot JDK will work. How do I do that?
I am trying to use the FontAwesomeFX library in my non-Maven project. However, it seems Maven is the only way the developer has chosen to provide the latest version of the library (9.1.2).
How do I get this imported into my IntelliJ IDEA project? The 9.1.2 version is not in the Maven repositories...
I have never used Maven, so I wouldn't know where to start.
I have a Gradle Intelij (community edition) project.
I want to use Vaadin plugin (CSValidationWidgetset), but I am lost how I can install this.
As I am using Spring Boot I am managed to set up this plugin in widget list. I've added following line to app.prop:
server.context_parameters.widgetset=com.vaadin.csvalidation.widgetset.CSValidationWidgetset
But now I can see that during server startup it is trying to get some resources related to this plugin. What files exactly should I provide? Is there any gradle task to do such kind of activity?
Thanks
Pawel
I'm working with Android Studio (Beta) 0.8.14.
I wanted to update the Gradle distribution and the Gradle plugin in my project, so I started manually changing the lines:
classpath 'com.android.tools.build:gradle:0.13.+' (in build.gradle)
distributionUrl=https\://services.gradle.org/distributions/gradle-2.1-all.zip (in gradle-wrapper.properties)
by upgrading to, respectively, 1.0.0 and 2.2.1. Then I tried to use different combinations found here on SO, e.g. 0.14.4 and 2.2, as none of these seemed to work. For each combination I got (after syncing and downloading what needed) some error, like:
AssertionError: null
AssertionError: com.android.tools.idea.gradle.project.AndroidGradleProjectComponent#71c8dfe3
UnsupportedMethodException
Unsupported method: SourceProvider.getJniDirectories().
The version of Gradle you connect to does not support that method.
After some research I thought this might be related to AS itself. Looking for updates in different channels brings me either to AS 0.9.9
This patch will allow you to update from 0.x to 1.x. After updating,
please check for updates again to install 1.x.
or to AS 1.0.2.
When trying to update, I get hundreds of errors related to Android Studio not deleting some files in android_SDK_folder/sources/android-21 , mainly.
This issue has some references here on SO. Known fixes are killing java processes during the update, which was unsuccessful for me, and launching Android Studio as admin, which doesn't look like a great idea to me (and I wouldn't know how to on OS X).
I'm stuck. My questions are:
are the Gradle syncing errors due to my old build of Android Studio?
if so, what can I do to update? I don't think I should uninstall and then get 1.0.2, as the message I reported says I can patch to 0.9.9 and then to 1.x. Is this the only thing to do?
Yes, your Gradle syncing errors are due to a mismatch between the plugin and the version of Android Studio. If you want to use v1.0.0 of the plugin, you need to be running Android Studio 1.0 or later.
As for upgrading, my advice would be to do a clean reinstall of 1.0; it will be easier than trying to spend a lot of time figuring out why the upgrade isn't working. I forget where the SDK is installed in 0.8.14, but we're encouraging/requiring users to have the SDK located outside the application directory itself, so it should help avoid future SDK woes with upgrading/reinstalling Android Studio itself.
If the SDK is currently installed inside Android Studio's directory and you don't want to re-download it, you could move it out to a more sensible place before reinstalling, and point the new installation at it.
I'm running OS X Mavericks. Then I:
Downloaded / installed NetBeans 8.0 IDE ("All" download).
Opened my maven project in the IDE.
Select project name.
Attempted Clean and Build. No go.
Attempted to generate dependency tree from maven. No go.
It appears the version of maven bundled with NetBeans 8.0 is not working.
Preferences shows the v. 3.0.5 of maven is bundled with the IDE. Here is
the path, I think, to the bundled version:
/Applications/NetBeans/NetBeans\ 8.0.app/Contents/Resources/NetBeans/java/maven
To confirm the project is valid, I then downloaded / installed my own, local
instance of Maven (v. 3.2.3). From the shell, I am able to clean / build
install fine. IE, the project is sound.
Something is awry with the IDE. I've searched Google and Yahoo, to no avail.
So, I think the short explanation of what is going on is that there is
an initialization bug in NetBeans 8.0. Here is what I did to get my
instance of the IDE to start using the bundled version of maven:
Downloaded / installed Apache Tomcat 7.x.
In the NetBeans IDE, went to Services>Servers, and added Tomcat.
In the NetBeans IDE, went to Projects, selected my project, right-clicked, and chose Properties.
In the Project Properties dialog, I selected Run, and chose Apache Tomcat for the Server, added a Context Path, and pressed OK.
Then I added a suitable custom-context to /path/to/apache-tomcat-7/conf/Catalina/localhost/myproject.xml, where I specified a reference to my workspace-instance of my project's war-file.
In addition to all of these steps, I also had to make certain permission-changes for Tomcat configuration files. You will have to figure this step out depending on your installation.
Finally, in the Projects window, I selected my project, right-clicked and selected Run.
Mysteriously, the bundled instance of maven started working.
I hope these steps can help others, as well as the NetBeans team resolve the initialization issue.