I'm using Maven 1 to build jars and wars. I also build windows dll's and InstallShield Merge Modules and InstallShield Installers through custom goals in my maven.xml. I will need to convert those things into plugins first. We also use the XDoclet plugin in 1 module which is not converted yet, so for the moment it is impossible to use m2 for that module.
As I see it, it will take some work to convert it all (lean how to write the plugins, write them, ...) so I would like to migrate a module at a time, starting with the pure java ones to Maven2. regards, Wim 2005/10/19, Jason van Zyl <[EMAIL PROTECTED]>: > > On Tue, 2005-10-18 at 08:29 +0200, Wim Deblauwe wrote: > > Hi, > > > > is it possible to build with Maven 1 and Maven 2? As I understand it, > Maven > > 2 uses pom.xml in stead of project.xml. So if I have a project.xml I can > > build with Maven 1 and if I add a pom.xml I can build the same project > with > > Maven 2. Correct? Or are there any extra's I need to consider? > > Yes, m1 and m2 can sit side by side but you probably don't want to do > this more long. It was meant for migration but if you have both systems > there one of them will naturally get out of date. We've been thinking > about creating an m2 -> m1 converter which might help with this as m2 > POMs are a superset of m1 POMs. > > If you are building a simple JAR you will probably be ok, but if you're > going to get into using plug-ins then it could get a little hard to > manage. What's your use case? > > > regards, > > > > Wim > -- > jvz. > > Jason van Zyl > jason at maven.org <http://maven.org> > http://maven.apache.org > > We know what we are, but know not what we may be. > > -- Shakespeare > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
