Hi, Just want to know if it's possible to use maven repositories with gradle (read & publish). we're reconsidering project build infrastructure in our company. So far we've evaluated maven, ivy, maven ant tasks as a replacement for homegrown ant scripts. Unfortunately every evaluated solution has it's own shortcomings.
For example with ivy I can resolve deps against maven repositories but can't publish to. Even if we don't use maven as a build system, I see no reason not to use local (company wide) maven repository for cross project deps. with ivy it's not possible (or I have to use both ivy + maven ant tasks, maintain ivy.xml & pom.xml i.e. it's a bug prone approach). as gradle is based on ivy I suspect that there is no native support for maven repos? Is it correct? If so, is it on todo list? when? our short requirements list for build system looks like: 1. build by convention for multimodule project 2. easy dependency management between modules in mm project 3. easy build customization for individual modules (here maven just falls short, as I don't like the idea of writing maven plugins) 4. ide support. 4.1 execute particular build task from within IDE (intellij, eclipse) 4.2 create IDE project file from build script (with correct dependencies intellij, eclipse) 4.3 assisted editing of build scripts in IDE 5. resolve project dependencies on 3rd party libs (against mavenrepoo) 6. freeze (remember) versions of 3rd party libs on project release (repeatable build) 7. publish build artifacts to repository (maven) What can't be done withgradle? -- View this message in context: http://www.nabble.com/using-maven-repos-with-gradle-tp19391276p19391276.html Sent from the gradle-user mailing list archive at Nabble.com.
