Maybe I don't understand exactly what you are asking correctly - but, Can't you just keep the old maven files and customise the deployment process so that it also copies the pom files to the deployment target?
I mean isn't that one of the points of Gradle - that it's highly customisable? The drawback of this approach is that you will have to maintain your maven poms by hand until you are completely migrated. Marko Bauhardt-3 wrote: > > hi all, > we have a project that contains about 20 subproject. but it is no > multiproject. and some modules are builded it with maven 1 and some > modules with maven 2. > so i plan to replace the complete maven build with gradle. but i have > todo this step by step because it is a project which is in production > and i have todo this carefully. > > So my 'problem' is that only the ivy.xml files with the jar files are > deployed to our maven repository. but we need the pom files in our > repo because the rest of the projects is build with maven and need to > download the jars via maven. > > So my question is: is it possible or exists a workaround that the > deploy process deploy > > 1) the jar file > 2) the ivy file > 3) the maven2 pom file > 4) and the maven1 pom file > > to our maven repo. > > thanks for help or any hints > marko > > > > > > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > ----- ___________________________ http://stubbisms.wordpress.com http://stubbisms.wordpress.com -- View this message in context: http://www.nabble.com/deploy-ivy.xml-and-pom.xml---tp18280143p18436438.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
