grails-2.2

Grails 2.2.4 unresolved dependencies commons-imaging

99封情书 提交于 2019-12-04 17:11:08
So I'm kinda lost here. I've had the same BuildConfig for over a month, and since the beginning of the week I have the following problem: I'm trying to use the Apache commons-imaging 1.0-SNAPSHOT in my grails 2.2.4 project using the following configuration: BuildConfig.groovy repositories{ ... mavenRepo 'http://repository.apache.org/snapshots' ... } dependencies{ ... compile 'org.apache.commons:commons-imaging:1.0-SNAPSHOT' ... } But every now and then, after running the grails clean command (I've tried from the terminal and from GGTS ), I get an unresolved dependencies error. At the very

Custom Plugin transitive Dependency resolution in BuildConfig.groovy Grails 2.2.3

可紊 提交于 2019-12-04 14:32:18
tl;dr version Dependencies of my custom grails plugin weren't getting inherited and resolved by projects I installed the plugin to. Install the latest version of the release plugin to your plugin (fixes the issue for jar dependencies) Clear out any references to plugins that might exist in your BuildConfig.groovy file (fixes the issue for plugin dependencies) grails maven-install to make the plugin available in the mavenLocal() source Long version So, I've been trying to create a custom grails plugin for internal use at my University. I'd really like it if putting the plugin in your

Grails 2.2.x unresolved dependencies without any changes to previously working build

ε祈祈猫儿з 提交于 2019-11-29 15:19:58
We have a Grails 2.2.4 project that I was looking to do some work on. There has been no work done on it for six months, but it built just fine back then. When I try to run grails clean now I get a host of UNRESOLVED DEPENDENCIES errors. This is despite all dependencies working just fine a few months ago. Has something changed within that time on the repository side? I have changed the log level within BuildConfig.groovy to log "warn" as suggested by the error message. The interesting thing from this is when I try to download via a browser some of the URLs that the build tries to resolve, they

Grails 2.2.x unresolved dependencies without any changes to previously working build

ぐ巨炮叔叔 提交于 2019-11-28 09:00:04
问题 We have a Grails 2.2.4 project that I was looking to do some work on. There has been no work done on it for six months, but it built just fine back then. When I try to run grails clean now I get a host of UNRESOLVED DEPENDENCIES errors. This is despite all dependencies working just fine a few months ago. Has something changed within that time on the repository side? I have changed the log level within BuildConfig.groovy to log "warn" as suggested by the error message. The interesting thing