I presented my views on why we should use Maven over Ant today in a meeting. My basic reasons are simple: 1) the ability to download jars (and have a central repository for all projects) and 2) to have a standard directory structure and build/test/deploy mechanism. It's going over like a fart in a crowded room so far. The major pushback is because supposedly you can convert JBuilder's .jqx files to Ant build files. Has anyone does this? How does it work? They mentioned that if there is a converter for .jqx -> maven build files, then they'd be happy to try it.
If we do use Ant (high probability), now begins the arduous task of standardizing across projects, as well as creating a "lib" module in CVS to store all the jars for the different projects. Good thing I'm on vacation next week! ;-)
I have a former client that has a customer. This customer asked them - "so when are you migrating from Java to PHP?" So evidently this person has the impression that the next wave of web applications will be written in PHP. My former client has asked me to provide an answer for their customer. If I translate it, I think they mean to ask "what is different between Java and PHP and why should we use Java over PHP." Here are my opinions - please add yours as you see fit. I must admit I don't know a whole lot about PHP, except that it's widely popular among the Linux/Apache/MySQL crowd and that it's similar to ASP in it's lack of a MVC architecture (yes, I know about the PHP MVC project).
- I think Java is more of an industry standard, whereas PHP seems to be popular among hackers and hobbyists.
- Java provides better separation of layers - key for testability. PHP has all the code embedded in the page, so you have to run it through a browser to test if database connections work (for instance).
- Java is more scalable.
- More folks know Java and it's easier to qualify someone's Java skills. How do you test someone knows PHP? Is there a certification?
- More for-profit organizations use it.
If you're a Java or a PHP-lover, I'd love to hear your opionions (facts are always better). I'm going to point my client to this post, so keep it clean.
I can't seem to subscribe to the Maven User Mailing List for the life of me, so I'll ask my questions here, and hopefully get some answers. The first question is regarding local repositories. Ideally, I'd like to put this on a network drive, so all developers can get to it by mapping a drive or something. When I try to use a network drive, I get the following error (WinXP, Maven CVS pull from yesterday):
Artifact '\\server\share\repository\velocity\jars\velocity-1.4-dev.jar'
not found to add to classpath
java.lang.ClassNotFoundException: velocity
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
The reason I'd like to use a network share (over an FTP server or HTTP server) is because then we can easily add the .jar files to the classpath in Eclipse or JBuilder. If Maven downloads the files to each user's local hard driver - then we can use an FTP server. Another option is to use the default (~/.maven/repository), but then each developer has to copy javamail and our custom jars onto their hard drive.
My second question is regarding webapp best practices with Maven. The Maven Tomcat Plugin seems nice, but it mangles my server.xml file. I'd like a solution similar to the way I've done it with Ant. I use a context.xml file and place this in $CATALINA_HOME/webapps and then I "deploy" the expanded war into Tomcat. Tomcat detects when any files change under WEB-INF/ and reloads the app. Works great. A better solution would be to point the docBase to target/webappName. So I guess what I'm saying is - should I just create a context.xml file and make my own custom "setup-tomcat" task (which does an ant:copy)? Then use war:webapp to refresh the app's files from source? How are you experts doing it?
