Hi Nick,
On Sep 9, 2008, at 2:29 PM, Nick Evgeniev wrote:
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?
Yes
If so, is it on todo list?
Yes
when?
We plan to release 0.4 today or tomorrow. We want to improve the
support for Maven Repos in 0.5. It is a top priority feature as one
of my customers requires this. What we want to provide is the
possibility to deploy poms with any Ivy resolver, including deploying
snapshots. Our plan is to do this on the Ivy level and want to
contribute this to the Ivy project once it is ready.
our short requirements list for build system looks like:
1. build by convention for multimodule project
Yes
2. easy dependency management between modules in mm project
Yes
3. easy build customization for individual modules (here maven just
falls short, as I don't like the idea of writing maven plugins)
Yes
4. ide support.
4.1 execute particular build task from within IDE (intellij, eclipse)
Only via the external task support of the IDE's. It would be very
nice to have specific Gradle IDE plugins, but AFAIKT the current
Gradle developers don't plan to implement this themselves in the
foreseeable future. We hope for contributions here.
4.2 create IDE project file from build script (with correct
dependencies intellij, eclipse)
In 0.4 this is provided for Eclipse projects. We want to provide it
for IntelliJ soon. Contributions are welcome :)
4.3 assisted editing of build scripts in IDE
In IntelliJ the support is already very good. See also Appendix B in
the user's guide.
5. resolve project dependencies on 3rd party libs (against mavenrepoo)
6. freeze (remember) versions of 3rd party libs on project release
(repeatable build)
I don't understand 5 and 6.
7. publish build artifacts to repository (maven)
See above.
As a general remark. The more customization you plan, the more
serious you are about project automation, Gradle will already pay off
in its current incarnation compared to Maven.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
