If it's a feature, I need to know how to work around it :)
I've got the following project defined in my build.gradle:
> project(':api:pricing') {
> version = 1.0
>
> dependencies {
> compile project(':api:util')
>
> compile 'org.springframework:spring:2.5.6.SEC01'
> compile 'org.drools:drools-core:5.0.1'
> compile 'org.drools:drools-api:5.0.1'
> compile 'org.drools:drools-compiler:5.0.1'
> }
>
> task copyDatasource(type: Copy) {//copy our <datasource>.xml into
> dpu-datasource.xml
> from('/datasource/')
> into('src/main/resources/')
> include(datasource + '.xml')
> rename(datasource + '.xml', 'pricing-datasource.xml')
> }
>
> jar.dependsOn task('copyDataSource')
> }
>
The datasource variable is defined in gradle.properties with a default value
of "localhost", this is used to enable build-time configuration of which of
our databases we want hibernate to interact with for the project.
Here's the part that I think might be a bug: When I run
gradle :api:pricing:copyDatasource -Pdatasource=datasource
this copies the datasource file as I intend; however if I run
gradle :app:IQ:war -Pdatasource=datasource
the :api:copyDatasource task reports UP-TO-DATE even if I manually delete
pricing-datasource.xml beforehand. Is this expected behavior? Does anybody
know of a workaround?
Thanks in advance,
~Brian
--
View this message in context:
http://gradle.1045684.n5.nabble.com/Bug-or-feature-tp4459390p4459390.html
Sent from the gradle-user mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
