Slim this guide down to a page or so to show the minimum about gs-convert-jar-to-war HOT 6 CLOSED

Note the related information in the Spring Boot reference docs:

http://docs.spring.io/spring-boot/docs/1.0.2.RELEASE/reference/htmlsingle/#build-tool-plugins-maven-packaging

http://docs.spring.io/spring-boot/docs/1.0.2.RELEASE/reference/htmlsingle/#howto-create-a-deployable-war-file

from gs-convert-jar-to-war.

Now that we have a separate guide for Maven, I think this one can be reduced and cleaned up to focus on Gradle. See http://spring.io/guides/gs/convert-jar-to-war-maven/

from gs-convert-jar-to-war.

I really don't get why all the guides still lead with gradle and there is no way for a user to choose the other path. Why are we doing this? The default should have always been maven if you ask me, but I'm happy either way as long as there's a choice. Why are we not providing the choice?

from gs-convert-jar-to-war.

All the guides include POMs, but the text generally only describes Gradle configs. We've discussed including both within the text, but there is some effort involved in reworking all the guides and building some client-side code to handle switching back and forth between Maven and Gradle. It simply hasn't been prioritized yet. Ultimately, we'd like to see something like the slider option on the Spring project pages.

from gs-convert-jar-to-war.

@olivergierke is suggesting this guide might be better moved into an Understanding page and NOT a guide. Not a bad idea.

from gs-convert-jar-to-war.

Resolved via dc9c9e6

from gs-convert-jar-to-war.