I am coming to springboot after using Grails for a couple years. It seemed like a good way to replicate the really great CLI that Grails provides. One thing that seems to be missing, though, is "grails war"; if you're not familiar, this simply builds a WAR out of your grails project, the same way that "grails run-app" or "spring run" kicks off a Tomcat container for your project.
I may be missing something here, not from a strong Java / Spring background, but it would greatly increase the usefulness of springboot, for me at least, to provide a "spring war" that would wrap up whatever would go into the Tomcat container with "spring run" into a war file.
(in case you're about to suggest it, I have seen http://spring.io/guides/gs/convert-jar-to-war/ and it of course accomplishes this in a roundabout way, but I'm really looking for something simpler)
The text was updated successfully, but these errors were encountered:
We have "spring jar ..." for packaging. I don't always want to encourage people to use WAR files, but I guess if you want to implement the WarCommand it might be straightforward enough to crib from JarCommand and change the file structure. Pull requests welcome.
I am coming to springboot after using Grails for a couple years. It seemed like a good way to replicate the really great CLI that Grails provides. One thing that seems to be missing, though, is "grails war"; if you're not familiar, this simply builds a WAR out of your grails project, the same way that "grails run-app" or "spring run" kicks off a Tomcat container for your project.
I may be missing something here, not from a strong Java / Spring background, but it would greatly increase the usefulness of springboot, for me at least, to provide a "spring war" that would wrap up whatever would go into the Tomcat container with "spring run" into a war file.
(in case you're about to suggest it, I have seen http://spring.io/guides/gs/convert-jar-to-war/ and it of course accomplishes this in a roundabout way, but I'm really looking for something simpler)
The text was updated successfully, but these errors were encountered: