How strictly should I follow the standard Maven project structure?
what's with a Java project folder structure ?
It depends on the build system in use for the project.
In the days of Ant or if you let the IDE set it up for you without specifying a build, it was mostly:
src/ bin/
Maven and Gradle use the Maven Standard Directory Layout ( https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html )
src
main
{lang}
packages
resources
test
{lang}
packages
resourcesYou can see that when using Gradle for groovy - https://docs.gradle.org/current/userguide/groovy_plugin.html#sec:groovy_project_layout the lang for the groovy sources is 'groovy'. This is important if you mix groovy, scala, kotlin, and java all in one project. For example (not my project, just one I found out there) https://github.com/bellingard/sample_multi-language-project
More on reddit.comMaven / project structure question.
Getting Started with JavaFX 11
JavaFX is a great framework for that use case but it needs some marketing love. At last JUG meeting people was genuinely convinced that Oracle killed it by popping it out the JDK.
More on reddit.comVideos
Hi
I am learning Maven from the official docs. I see that it wants a src/main/java/com/mycompany/appname directory structure. So I did some googling on java packages and I see why these are useful. But my question is, is the java/com/ really necessary?
I really don't like all these nested folders. How about something like src/main/mycompany/appname? It's still a package right? However I am only a java novice so if there is a good reason for structuring it like this, I'd like to know.