What are the best practices for using third-party libraries in enterprise
build automation?
We use third-party libraries as:
1. Dependencies of our applications.
Examples:
compile 'commons:commons-logging:1.0.4'
compile 'junit:junit:4.11'
2. Dependencies of our build script.
Examples:
repositories {
mavenCentral()
maven { url 'http://kercheval.org/mvn-repo/releases' }
}
dependencies { classpath
'org.kercheval:GradleCMPlugin:1.14-20130611.134348' }
I assume that we don't want our build depend on availability of repositories
we don't control. Therefore, our build script should only reference our
internal repository. That means that we should remove references to
mavenCentral and kercheval.org repositories.
Questions:
1. How do we migrate from references to outside repositories to internal
repositories? Do I have to manually upload all JARs to our artifactory
server?
2. How do we migrate reference to GradleCMPlugin? Do I download the plugin
JARs, than upload them to the artifactory server?
3. Should we configure the artifactory server to never retrieve the JARs
from outside repositories?
--
View this message in context:
http://forums.jfrog.org/Best-practices-for-using-third-party-libraries-in-enterprise-build-automation-tp7579503.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
