Hi Alexey, > So I want to ask some questions to see if Maven can help in > our particular case. First of all I briefly describe the > situation. We have large website content management system > comprising of dozens of small modules doing their atomic > tasks. Each of these modules have it's own ant building > script which produces versioned jar-file. The deployment > process is pretty difficult, because it may include the > following steps: > 1) copying new jar and deleting old one -- fairly simple :) > (no problems!)
Do you mean something similar to maven clean maven jar:install ???? > 2) updating mysql database on the hosting server (needed sql > scripts are stored in cvs) Mhm. I guess you have to write your own goal with jelly for that in your maven.xml script. Jelly supports JDBC for fireing SQL statments to a database server: http://jakarta.apache.org/commons/sandbox/jelly/tags.html#jelly:sql There are also some samples in CVS so you will see if you can apdopt it. > 3) copying dependency files such as XSL templates and binary > stuff (binary stuff is NOT stored in cvs) this could be done with an ant task inside the maven.xml jelly script. For jar files you have the abiltly to attatch resources with a couple of filesets in the project descriptor e.g. <build> . . . <resources> <includes> <include>*.xsl</include> <include>log4j.properties</include> </includes> </resources> <jars/> </build> > 4) updating property files with modules' settings that are > differ from one hosting server to another. > > So, the questions that arise are: > 1) Can Maven perform database operations? If yes, please give > an example code Yes, see jelly:sql. > 3) Is there a possibility in Maven to verify the validity of > deploy? (compare size of directories, for instance) Maven have some Jelly tags to verifiy a war file's structure if you mean that. > 4) And finally, is there any In-Depth Maven tutorial? Not yet. It helps if you study the goal and properties documenation, asking questions to the mailing list (relly nice guys out there), consult the jelly documenation, look into the jakarta cvs dirs and spying and get familar with ant.... :-) I guess the "problem" is that maven has a very fast evolution cycle right now. The documenation will grow when the first peak is reached (maybe when version 1.0 is avialable ???). This is not the problem of Maven. Nearly every software projects struggles to keep the documenation up-to-date.... Hope this helps. Toby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
