Closed
Description
Overview
Conditions that matches this issue
If following all conditions are matched, the SpringBootVFS
cannot scan classes correctly.
- Run without executable jar(e.g. Maven/Gradle Plugin, IDE, etc...)
- Scanning target classes are stored in jar file under maven local repository (e.g.
${HOME}/.m2/repository
) - Specified scanning base package is matched with prefix of groupId
In this case, all conditions are matched as follow:
- Run without executable jar because it use spring-boot-devtools
- Scanning target classes are stored in
$HOME/.m2/repository/com/bee/kuna/kuna-server-db/0.1.1-RELEASE/kuna-server-db-0.1.1-RELEASE.jar
- Specified scanning base package is
com.bee
- GroupId of artifact that stared target classes is
com.bee.kuna
-> the groupId prefix is matched with scanning base package(com.bee
)
Fix version
- 2.0.1
- 1.3.4 (backport) Fix resources scanning bug on SpringBootVFS #305