I am curious whether a convention or best-practice has emerged yet for Gradle in terms of handling private repositories in relation to public projects.
For example, in Hibernate I have a series of databases I need to run integration tests against. Some of these databases (oracle, db2, etc) require jars that cannot be put into public repositories and cannot otherwise be made publicly available due to license issues. The Hudson environment has access to a private repository which makes these artifacts available. Seems bad practice to name this repositories in the build script. As far as I can tell the only real option at the moment is to utilize a ~/.gradle/init.gradle init script to inject a repository (seems you can only append a repository, not replace, pre-pend, etc). Any others I am missing? Any others planned? -- Steve Ebersole <[email protected]> http://hibernate.org --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
