Hi David
You can configure the artifactory closure to not publish the pom and ivy
files by adding the default closure:
defaults {
publishConfigs('published')
*publishPom = false* //Publish generated POM files to Artifactory (true by
default)
*publishIvy = false* ////Publish generated Ivy descriptor files to
Artifactory (true by default).
}
This will prevent the deployment of the pom and ivy files. Also, you can
add:
def f1 = file("test.rpm")
rootProject.artifacts {
println "artifacts"
println f1.toString()
println f1.getName()
//File = Path to the file, GetName= Will get the filename for this example
test.rpm and the type is “rpm”
published file: f1, name: f1.getName(), type: 'rpm', classifier:
"classifier"
}
to publish an RPM file named “test”.
Hope this helps,
Alex
--
View this message in context:
http://forums.jfrog.org/Suggestion-for-publishing-pure-RPM-s-to-Artifactory-Pro-YUM-repository-using-Gradle-tp7580347p7580350.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
