Comments on: Maven2 And Mobile Java http://codeforfun.wordpress.com/2008/04/07/maven2-and-mobile-java/ Java development with an iPhone touch pad for the Atari 2600 from an urban hip-hop perspective Thu, 03 Dec 2009 06:18:31 +0000 http://wordpress.com/ hourly 1 By: Cliff http://codeforfun.wordpress.com/2008/04/07/maven2-and-mobile-java/#comment-15476 Cliff Fri, 18 Apr 2008 20:46:30 +0000 http://codeforfun.wordpress.com/?p=381#comment-15476 Well I'll tell you. There are a whole bunch of reasons primarily tied to production build. In experience I found that you can't/shouldn't use IDE wizards unless your project is simple and your dev team consists of 1. Why? Well, what do you do when you publish your product? With a team greater than one and a product slightly more sophisticated than client only logic you'd face some integration issues. (I'm using Eclipse 3.3 and he's on Eclipse 3.2 I run Ant-1.6.5 and he uses Ant-1.7.0). If there's a server component then you'd also have additional deployment concerns. The wizards fall apart here. Plus add in a CI server to help with developer change integration of course and now you have the need for a build system. Maven brings uniformity to the entire development process which eliminates that bugs that come from point release differences in a component or tool involved in the build or used by the application. We took the approach of wrapping Maven around an Ant build and while it works it has it's issues. While most would shake the finger at Maven, a seasoned developer would immediately see the root cause as a build tool integration issue. (The re-invented build life cycle doesn't match the Maven build life cycle.) The short answer is because we're an agile shop we need all of the Agile features available from the Maven build system which are currently mis-understood or mis-implemented in the Ant component of our client build. Well I’ll tell you. There are a whole bunch of reasons primarily tied to production build. In experience I found that you can’t/shouldn’t use IDE wizards unless your project is simple and your dev team consists of 1. Why? Well, what do you do when you publish your product? With a team greater than one and a product slightly more sophisticated than client only logic you’d face some integration issues. (I’m using Eclipse 3.3 and he’s on Eclipse 3.2 I run Ant-1.6.5 and he uses Ant-1.7.0). If there’s a server component then you’d also have additional deployment concerns. The wizards fall apart here. Plus add in a CI server to help with developer change integration of course and now you have the need for a build system. Maven brings uniformity to the entire development process which eliminates that bugs that come from point release differences in a component or tool involved in the build or used by the application. We took the approach of wrapping Maven around an Ant build and while it works it has it’s issues. While most would shake the finger at Maven, a seasoned developer would immediately see the root cause as a build tool integration issue. (The re-invented build life cycle doesn’t match the Maven build life cycle.)

The short answer is because we’re an agile shop we need all of the Agile features available from the Maven build system which are currently mis-understood or mis-implemented in the Ant component of our client build.

]]> By: Allan http://codeforfun.wordpress.com/2008/04/07/maven2-and-mobile-java/#comment-15472 Allan Wed, 16 Apr 2008 08:41:20 +0000 http://codeforfun.wordpress.com/?p=381#comment-15472 congrats. I'm thinking of using maven as well...I presently use it for my web applications. But the Sun WTK emulator/build tool does a pretty good job of organizing/compiling/obfuscating/running the code. What was your motivation to get your J2ME builds on Maven? congrats.

I’m thinking of using maven as well…I presently use it for my web applications. But the Sun WTK emulator/build tool does a pretty good job of organizing/compiling/obfuscating/running the code.

What was your motivation to get your J2ME builds on Maven?

]]>