Hi,
I have committed functionality to trunk for auto generating a Maven
pom descriptor file and deploying this pom to a repository. Not
everything we want to implement is implemented yet. We are going to
offer this code eventually to the Apache Ivy project. They have some
code for generating a pom out of ivy objects but this code is pretty
limited and was not usable for our purpose.
Here are the missing bits I'm aware of:
- Dealing with Snapshots (I want to implement this very soon)
- Dealing with the new 'override' functionality of Ivy (as a more
powerful equivalent to Maven's 'dependencyManagement' element).
- Dealing with Ivy artifact dependencies
- Fine grained customization
The last point I think is very important. Due to the more powerful
elements Ivy has and many differences, sometimes subtle differences,
how the domain is modelled auto generation can't always produce the
result that is needed. What we want to provide is that the user can
modify any property of an auto generated Maven dependency element.
Customization should also allow to remove auto generated elements as
well as add dependency elements. Our configuration to scope mapping
is already very customizable.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
