Part 1 - J2ME Development: Eclipse Pulsar, Maven2, TestNG, Subversion & Mockito
Article Series Overview
These series of articles is an example of how to setup both an Eclipse J2ME development environment and a command line only approach using Maven2. This is just one approach of doing things based on my personal experience and all the related online resources out there. Throughout the series I'll will justify why I've done things in certain way, that being said it may or may not be the best approach for you. Keep in mind there is assumption here you are a Java Developer, in otherwords I won't be going into unecessary steps like how to install Eclipse Pulsar. I have intentionally separated the Eclipse environment and the command line approach. The only sync up is when you actually commit to subversion via Subclipse in Eclipse Pulsar and then do a full checkout using Maven2. My reasoning (and yes there are pros and cons) is to a give a developer the choice to use either method or both. I personally typically like coding in Eclipse and then when necessary attempt a full build and a regression test (unit tests) against the entire code base. This as well allows for a group of developers to choose the IDE of of their choice like IDEA, Eclipse, NetBeans or just simple text editor. Whatever your choice is, it isn't tied to the command line approach. If aren't familiar with the tools used in this series please visit the following: Lets get started! On to Eclipse Pulsar! Go to Part 2 - J2ME Development: Eclipse Pulsar & other Wireless Dev Kits