Remove config server monitor for this release

A bug in spring-cloud-config makes the generetaed jar blow up
if it is using the default classpath:/launcher/ location for
config files. We can fix that in 1.2.1.
This commit is contained in:
Dave Syer
2016-10-13 11:58:04 +01:00
parent 16a9c6890f
commit 5facdb5e55
2 changed files with 0 additions and 10 deletions

View File

@@ -33,10 +33,6 @@
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-config-server</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-config-monitor</artifactId>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-test</artifactId>

View File

@@ -17,15 +17,11 @@
package org.springframework.cloud.launcher.configserver;
import java.io.IOException;
import java.nio.file.FileSystems;
import java.util.Collections;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.cloud.client.discovery.EnableDiscoveryClient;
import org.springframework.cloud.config.server.EnableConfigServer;
import org.springframework.core.io.ClassPathResource;
import org.springframework.core.io.Resource;
/**
* @author Spencer Gibb
@@ -36,8 +32,6 @@ import org.springframework.core.io.Resource;
public class ConfigServerApplication {
public static void main(String[] args) throws IOException {
Resource resource = new ClassPathResource("/launcher");
FileSystems.newFileSystem(resource.getURI(), Collections.<String,Object>emptyMap());
SpringApplication.run(ConfigServerApplication.class, args);
}
}