Hello Frank. Using too many tools could make project too complicated. I saw a project with maven, ant and .bat files. It was tricky:) If something could be solved using maven only -- we should do so. Ant-script at least requires ant to be installed on platform. If something cannt be solved using existing maven plugins -- we should make decision between creating maven plugin and using ant script, because ant script is better than shell script for example (because of its cross-platform nature). But I am sure that 99% of our issues could be solved using maven only. But that’s my imho, and its probably not a best practice.
-----Original Message----- From: Gorham-Engard, Frank [mailto:frank_gorham-eng...@cable.comcast.com] Sent: Monday, February 01, 2010 7:20 PM To: Maven Users List Subject: RE: Plugin for updating external XML file content What do you see as the value of completely eliminating ant use from your Maven project. I see ant as a tool that is supported and may be appropriate for some situations. To have a policy that rules out a useful tool seems counterproductive. <!-- Frank Gorham-Engard → -----Original Message----- From: Ilya Kazakevich [mailto:kazakev...@devexperts.com] Sent: Monday, February 01, 2010 10:57 AM To: 'Maven Users List' Subject: RE: Plugin for updating external XML file content Thanks. Actually, I wanna get rid of ant in our project, ... --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
