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.
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 recently got on a new team and trying to setup the project requirements. Currently, I had Maven 3.1.1 on my system and I need Maven 3.3.9. If any one can tell me how to upgrade the version of maven, I would appreciate it. (I'm working on windows 10)
It's pretty simple - download maven from the official distribution archive
that is available at https://archive.apache.org/dist/maven/maven-3/3.3.9/binaries/. After that follow installation guide from maven documentation available at https://maven.apache.org/install.html.
Just remember that Maven 3.3.9 requires at least Java version 7.
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 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.