Problem using YAML instead of Properties with spring-boot-starter-parent 1.4.0.RELEASE

[Panciz]

Form the reference guide

 The SpringApplication class will automatically support YAML as an alternative to properties whenever you have the SnakeYAML library on your classpath.

[Note]
If you use ‘Starters’ SnakeYAML will be automatically provided via spring-boot-starter.

anyway if I use in my pom.xml

<parent>
        <groupId>org.springframework.boot</groupId>
        <artifactId>spring-boot-starter-parent</artifactId>
        <version>1.4.0.RELEASE</version>
    </parent> 

The application keeps looking for application.properties and ignoring the .yml file.
I need to downgrade to 1.4.0.RELEASE or adding the dependency snakeyaml 1.16

    <dependency>
                <groupId>org.yaml</groupId>
               <artifactId>snakeyaml</artifactId>
              <version>1.16</version>
        </dependency>

[Panciz]

It's easy to replicate just start from this boilerplate https://github.com/hoserdude/spring-boot-sample-yaml-config change the pom.xml to use 1.4.0.RELEASE

[wilkinsona]

The repository you've referenced builds and runs fine for me with both 1.2.0.RELEASE and 1.4.0.RELEASE. What do we need to do to replicate the problem? Also, snakeyaml remains a dependency of spring-boot-starter in 1.4.0.RELEASE so there should be no need to add an explicit dependency.

If you'd like us to investigate further we're going to need a sample and the exact steps required to reproduce the problem.

[wilkinsona]

This has been posted on Stack Overflow too with a little bit more information: http://stackoverflow.com/questions/39474133/spring-boot-using-yaml-instead-of-propeties-file

@Panciz If you really must cross-post please make it clear that you've done so. You're just wasting people's time otherwise.

I'd guess that the Snake YAML 1.17 jar is corrupted which is why it works when 1.16 is used instead.

[Panciz]

The repository you've referenced builds and runs fine for me with both 1.2.0.RELEASE and 1.4.0.RELEASE.

Sorry I was not precise enough. Actually the project runs with both the configuration but I get a different output:

With 1.4.0.RELEASE

AutoConfiguration should have wired up our stuff
Let's see if we are doge-worthy...
No Doge for us :(

with 1.2.0.RELEASE

AutoConfiguration should have wired up our stuff
Let's see if we are doge-worthy...
(A nice ascii art dog)

That's because in the with1.4.0.RELEASE

if (dogeService.requiresDogeness()) {

return false in com.hoserdude.samples.boot.config.SuchApplication run method, since the configuration is not loaded.

As I wrote on stack overflow I need to add snakeyaml 1.16 in the classpath to get everything work also on 1.4.0 RELEASE

I try with windows 10 JVM

java version "1.8.0_102"
Java(TM) SE Runtime Environment (build 1.8.0_102-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.102-b14, mixed mode)

[wilkinsona]

I get the exact same output with both 1.4.0.RELEASE and 1.2.0.RELEASE (ASCII art in both cases). The problem appears to be specific to your environment, and I strongly suspect that's because the Snake YAML 1.17 jar in your Maven cache is corrupted.

[Panciz]

Ok that was the problem. I'm really sorry that I waste your time.
The fact that I do not recieve any error at build not at run time mislead me.

[mingzhi5626]

@Panciz Hi Panciz, I have same issue and after change to snakeyaml 1.16 solved this problem. Do you find out why snakeyaml 1.17 is corrupted? I cleaned my maven cache and re-installed snakeyaml 1.17 in my .m2. But still have this issue.

I am using spring boot 1.4 and my project is just a central integration test project which means there are only test cases in /src/test/java and /src/test/resources. this is snippet of my project pom.xml, parent pom is org.springframework.boot

<dependencies>
	<dependency>
		<groupId>org.springframework.boot</groupId>
		<artifactId>spring-boot-starter-test</artifactId>
	</dependency>
	<dependency>
		<groupId>io.rest-assured</groupId>
		<artifactId>rest-assured</artifactId>
	</dependency>
</dependencies>

[Panciz]

My solution was clean almost my entire maven cache. I do not only clean the <maven_directory>/org/springframework/boot/spring-boot-starter-test dire but the entire /org/ directory.
I think the problem was with a different dependent jar, that I not exactly identified!