> From: Rodney Schneider <[EMAIL PROTECTED]> > > On Fri, 11 Oct 2002 18:19, you wrote: >> Rodney, >> >> This sounds great. How about moving to a maven build process at the same >> time? This will to a certain extent dictate your directory structure. > > OK, I can give this a go... but this will be the first time I have used > maven, so it might take me a while to get the hang of it. Have you built torque, fulcrum, tdk, turbine-2 or turbine-3 before? If so then you have used maven ;-)
> The standard build scripts and properties files that are generated by > TDK-2.2b3 are not yet mavenized, so would this make the migration howto more > confusing and possibly less useful? Possibly. There have been a few small posts over on maven-user discussing the best way to mavenize a turbine project, but I am not sure how conclusive they have been. There has also been discussion of a torque plugin for maven, but again I am unsure of the status. > Should I wait until the TDK is mavenized before I migrate over to using maven > for the migration howto? > > To mavenize or not to mavenize, that is the question :) The migration howto is really important. If considering maven is going to slow you down in any way I would say don't bother - we can address the mavenization process at a later date. That said, if you need to juggle directory structures, heading in the direction of the structure dictated by maven will make things easier in the long run. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
