What I did with maven 1 is write a custom goal that uses ant to call a bat file that calls make. That way, we only needed to export a make file from Visual Studio and all parameters are correct. Otherwise, you need to duplicate all parameters you have in your ide in the maven plugin.
regards, Wim 2005/11/3, David Jackman <[EMAIL PROTECTED]>: > > How does the maven-native plugin compare with the FreeHEP plugin Mark > Donszelmann talks about (http://java.freehep.org/freehep-nar-plugin for > the Maven1 version, Maven2 version in the works)? > Can we combine efforts to make a single native plugin faster (and > better), or are there really multiple approaches that are applicable in > different circumstances? > > ..David.. > > > -----Original Message----- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 03, 2005 7:49 AM > To: Maven Users List > Subject: Re: make -> maven > > Harnett, Brendan said: > > Hi > > > > > > > > We are currently responsible for developing and maintaining a large > > code base (mainly C++ but also Java) which is currently built using > > Make. We are considering replacing make with maven for our builds as > > it provides good support for distributed builds, release management > > and seems to handle dependencies well. > > > > > > > > It appears that we would need to use the Maven native plug-in, to > > build the C++ components. This plug-in exists for Maven 1.0 but > > doesn't seem to be available yet for Maven 2.0. Does anyone know when > > > this plug-in might be available or if there is another possible > approach. > > > > The plugin exists but it isn't released yet > https://svn.codehaus.org/mojo/trunk/mojo/maven-native/ > > > > > > > Any general advice from anyone who has ported an application from make > > > to Maven or has experience of building C++ applications using Maven > > would be greatly appreciated (i.e is this a good idea or not?) > > > > > > > > Thanks > > > > > > > > Brendan > > > > > > > > > > > > > > > > > > > > This e-mail and any attachment is for authorised use by the intended > > recipient(s) only. It may contain proprietary material, confidential > > information and/or be subject to legal privilege. It should not be > > copied, disclosed to, retained or used by, any other party. If you are > > > not an intended recipient then please promptly delete this e-mail and > > any attachment and all copies and inform the sender. Thank you. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
