{"action":"created","issue":{"url":"https://api.github.com/repos/spring-projects/spring-boot/issues/5457","repository_url":"https://api.github.com/repos/spring-projects/spring-boot","labels_url":"https://api.github.com/repos/spring-projects/spring-boot/issues/5457/labels{/name}","comments_url":"https://api.github.com/repos/spring-projects/spring-boot/issues/5457/comments","events_url":"https://api.github.com/repos/spring-projects/spring-boot/issues/5457/events","html_url":"https://github.com/spring-projects/spring-boot/issues/5457","id":142380248,"number":5457,"title":"Support starting/stopping the JAR/WAR file with the Spring Boot Maven plugin","user":{"login":"mrumpf","id":1191530,"avatar_url":"https://avatars.githubusercontent.com/u/1191530?v=3","gravatar_id":"","url":"https://api.github.com/users/mrumpf","html_url":"https://github.com/mrumpf","followers_url":"https://api.github.com/users/mrumpf/followers","following_url":"https://api.github.com/users/mrumpf/following{/other_user}","gists_url":"https://api.github.com/users/mrumpf/gists{/gist_id}","starred_url":"https://api.github.com/users/mrumpf/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrumpf/subscriptions","organizations_url":"https://api.github.com/users/mrumpf/orgs","repos_url":"https://api.github.com/users/mrumpf/repos","events_url":"https://api.github.com/users/mrumpf/events{/privacy}","received_events_url":"https://api.github.com/users/mrumpf/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/spring-projects/spring-boot/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-03-21T15:18:01Z","updated_at":"2016-03-30T07:00:26Z","closed_at":null,"body":"When there is a separate Maven sub-modules with integrations tests which runs after the Maven module where the JAR or WAR file has been created, the classpath has to be re-created for the Spring Boot Maven plugin top work.\r\nThere should be an easy way to run the JAR (or WAR) file instead of having to re-assemble the classpath in the integration test Maven sub-module.\r\n\r\nI'm currently struggeling with trying to make the classpath of the integration test Maven project look the same as the classpath that has already been assembled as part of the full JAR file.\r\n\r\nThe Spring Boot Maven plugin should have 2 modes:\r\n\r\n* Run the tests in the same location where the full JAR file is packaged: Use the classpath, as defined by the Maven POM of the current project\r\n* Run integration tests as part of another Maven module: Just run the JAR file, that has been built before, no need to specify a classpath because the JAR file contains everything needed to run the application.\r\n"},"comment":{"url":"https://api.github.com/repos/spring-projects/spring-boot/issues/comments/203280397","html_url":"https://github.com/spring-projects/spring-boot/issues/5457#issuecomment-203280397","issue_url":"https://api.github.com/repos/spring-projects/spring-boot/issues/5457","id":203280397,"user":{"login":"snicoll","id":490484,"avatar_url":"https://avatars.githubusercontent.com/u/490484?v=3","gravatar_id":"","url":"https://api.github.com/users/snicoll","html_url":"https://github.com/snicoll","followers_url":"https://api.github.com/users/snicoll/followers","following_url":"https://api.github.com/users/snicoll/following{/other_user}","gists_url":"https://api.github.com/users/snicoll/gists{/gist_id}","starred_url":"https://api.github.com/users/snicoll/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/snicoll/subscriptions","organizations_url":"https://api.github.com/users/snicoll/orgs","repos_url":"https://api.github.com/users/snicoll/repos","events_url":"https://api.github.com/users/snicoll/events{/privacy}","received_events_url":"https://api.github.com/users/snicoll/received_events","type":"User","site_admin":false},"created_at":"2016-03-30T07:00:26Z","updated_at":"2016-03-30T07:00:26Z","body":">  even manually executing the shutdown operation did not shutdown the VM.\r\n\r\nThere's not much we can do at the level of the plugin I am afraid. You should have something in your context that prevents the context to shutdown gracefully. Calling `close` several times has no effect so a `maxAttempt` won't help either."}}