Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add test case for ivy customization

Browse Source 
A bug in ivy (tickled by maven leaving a pom
but no jar in the local repo) would make the
default Grapes ivy config fail (cannot grab...).
Phil's workaround now has a test case.
This commit is contained in:
Dave Syer
2013-08-21 08:43:31 +01:00
committed by Phillip Webb
parent 39aea5d944
commit d88e1b4b7a
4 changed files with 187 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
spring-boot-cli/src/main/java/org/springframework/boot/cli/compiler/GrapeEngineCustomizer.java
View File

@@ -48,14 +48,18 @@ import org.apache.ivy.plugins.resolver.ChainResolver;
import org.apache.ivy.plugins.resolver.DependencyResolver;
import org.apache.ivy.plugins.resolver.IBiblioResolver;
import org.apache.ivy.util.AbstractMessageLogger;
import org.apache.ivy.util.Message;
import org.apache.ivy.util.MessageLogger;
import org.springframework.boot.cli.Log;
/**
* Customizes the groovy grape engine to download from Spring repos and provide simple log
* progress feedback.
* Customizes the groovy grape engine to enhance and patch the behaviour of ivy. Can add
* Spring repos to the search path, provide simple log progress feedback if downloads are
* taking a long time, and also fixes a problem where ivy cannot use a local Maven cache
* repo.
*
* @author Phillip Webb
* @author Dave Syer
*/
class GrapeEngineCustomizer {
@@ -300,6 +304,7 @@ class GrapeEngineCustomizer {
@Override
public void log(String msg, int level) {
logDownloadingMessage();
Message.getDefaultLogger().log(msg, level);
}
@Override