//In gradle multi-project build; top-level build file
apply plugin: 'Java'
apply plugin: 'Artifactory'
...
artifactory {
...
publish {
...
defaults {
publishConfigs('archives')
}
}
}
//In subproject; build.gradle file
dependencies {
compile ...
someOther ...
}
task onlyTask(type:JavaExec) {
... <outputs artifacts to buildDir\some-folder>
}
artifacts {
archives onlyTask
}
cmd> gradle artifactoryPublish
execution failed for task..
cause: failed to calculated checksums for artifact:
<file-path-to-buildDir\libs\my-project-name.jar>
How can I override the behaviour (from sub-project) such that artifactory
does not look for a subprojectName.jar file in buildDir\libs? I've tried
artifactoryPublish { publishConfigs ('configName')} but that didn't seem to
help.. is there any other way to do this? Any help would be appreciated.
--
View this message in context:
http://forums.jfrog.org/Gradle-artifactoryPublish-expects-jar-file-in-buildir-libs-jar-tp7375684p7375684.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
