Developing Blackberry application using NetBeans Plugin - part 2, fixing debug issue

On my previous post, I reviewed the new blackberry Netbeans Plugin. Latre I found Shai also published his post about how to use the new plugin in developing the LWUIT blackberry application.
But I found the new plugin could not debug the blackberry application.

Reason
The reason is if you want to debug your blackberry application, you have to copy all the .debug files into the blackberry simulator folder, include xxx.debug, xxx-1.debug, xxx-2.debug, ... etc. From the generated build-impl.xml script file, we know that blackberry plugin only copied the xxx.debug file and missing all other debug files.

Solution
Add the following targets in the build.xml, which will override the same target in the build-impl.xml:
1.  Update target blackberry-pre-debug, it will copy all the debug files into the simulator folder.

	<target name="blackberry-pre-debug" depends="blackberry-load-setings" if="blackberry.trigger">
	<copy todir="${platform.home}/simulator">
	<fileset dir="${dist.dir}" includes="${name}.*"/>
	<fileset dir="${dist.dir}" includes="*.debug"/>
	</copy>
	<condition property="jpda.port" value="${JDWPPort}" else="8000">
	<isset property="JDWPPort"/>
	</condition>
	</target>

view raw blackberry-pre-debug hosted with ❤ by GitHub

2.   Update target clean-blackberry, it will delete all the files of the application in the simulator folder.

	<target name="clean-blackberry" if="blackberry.trigger">
	<delete file="${dist.dir}/${name}.cod" failonerror="false"/>
	<delete file="${dist.dir}/${name}.cso" failonerror="false"/>
	<delete file="${dist.dir}/${name}*.debug" failonerror="false"/>
	<delete failonerror="false">
	<fileset dir="${platform.home}/simulator">
	<include name="**/${name}*.*"/>
	</fileset>
	</delete>
	</target>

view raw clean-blackberrty-target hosted with ❤ by GitHub

3.  If you want to build BlackBerry CLDC application, you need to add the target create-cod:

	<target name="create-cod" if="blackberry.trigger">
	<exec dir="${dist.dir}" executable="java" failonerror="true">
	<arg value="-cp"/>
	<arg value="${platform.home}/bin/rapc.jar"/>
	<arg value="net.rim.tools.compiler.Compiler"/>
	<arg value="import=${platform.bootclasspath}"/>
	<arg value="codename=${name}"/>
	<arg value="-cldc"/>
	<arg value="jad=${basedir}/${dist.dir}/${dist.jad}"/>
	<arg value="${basedir}/${dist.dir}/${dist.jar}"/>
	</exec>
	<property file="${dist.dir}/${dist.jad}"/>
	<echo file="${basedir}/${dist.dir}/${name}.alx">
	&lt;loader version="1.0"&gt;
	&lt;application id="${name}"&gt;
	&lt;name&gt;
	${MIDlet-Name}
	&lt;/name&gt;
	&lt;description&gt;
	${MIDlet-Description}
	&lt;/description&gt;
	&lt;version&gt;
	${MIDlet-Version}
	&lt;/version&gt;
	&lt;vendor&gt;
	${MIDlet-Vendor}
	&lt;/vendor&gt;
	&lt;copyright&gt;
	${MIDlet-Copyright}
	&lt;/copyright&gt;
	&lt;fileset Java="1.0"&gt;
	&lt;directory/&gt;
	&lt;files&gt;${name}.cod&lt;/files&gt;
	&lt;/fileset&gt;
	&lt;/application&gt;
	&lt;/loader&gt;
	</echo>
	</target>

view raw create-cod hosted with ❤ by GitHub

The only difference with build MIDlet application is in <arg value="-cldc"/>, by default, the Blackberry plugin already choose MIDlet by using <arg value="-midlet"/>.