Д«esides that index.jsp is not necessary, just delete it. By default the 'pom.xml' will include locked down versions for maven plugins, you could safely get rid of those since we won't personalize the entire Maven lifecycle, just a couple of hooks. Now you should be able to open your project in any IDE. In the end you should have the following structure as result: demo-angular-8$ tree The interactive shell will ask you for you project characteristics including groupId, artifactId (project name) and base package. To bootstrap the Java project, you could use the plain old maven-archetype-webapp as basis: mvn archetype:generate -DarchetypeGroupId= -DarchetypeArtifactId=maven-archetype-webapp -DarchetypeVersion=1.4 Allows you to distribute a minified and ready for production project.Allows you to combine Java(Maven) and JavaScript(Webpack) build systems.Allows you to create a SPA modern application (With all npm, ng, cli stuff).Allows you to use the IDEs as JavaScript development IDEs.Is compatible with the big three Java IDEs (NetBeans, IntelliJ, Eclipse) and VSCode.To demonstrate this I will create a project that: Creating a POC with Angular 8 and Java War IT people is reluctant to publish a plain old web serverДЄnyway, and as described in Oracle's documentation one of the benefits of using war files is the possibility to include static (HTML/JS/CSS) files in the deployment, hence is safe to assume that you could distribute any SPA application using a war file as wrapper (with special considerations).You're dealing with rigid deployment standards.You don't have control over deployment infrastructure.From time to time it is necessary to distribute SPA applications using war files as containers, in my experience this is necessary when:

Angular cli intellij ultimate