Yes, on reflection I realised that a combination of tools could do the job.
I can successfully do - java:compile - jar:install - site:deploy so I will get benefits from maven. It seems to be the distribution and release steps where I hit the really hard problems. So, question to maven guys - is there a maven ant task? Stephen ----- Original Message ----- From: "Joakim Erdfelt" <[EMAIL PROTECTED]> > Siegfried G�schl wrote: > > There is a third option - I just integrated MAVEN into an existing > > ANT build environment without giving up the "large existing build" > > (400 KByte of ANT scripts) and more than 100 subprojects. > > > > Basically I reap the report generation of MAVEN and everything else > > is done by the existing ANT build plus a few more ANT scripts for > > invoking MAVEN. The setup is not for the "faint hearted" but there > > was no other way doing it with the given timeframe of two weeks. > > Do you have any "Best Practices" or "Lessons Learned" type tips for this > kind of hybrid setup? We are also in the process of moving a large > corporate project into maven, and would greatly benefit from the > lesson's learned in your setup. > > /* joakim */ > > > --------------------------------------------------------------------- > 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]
