Java Reference
In-Depth Information
<copy todir="${build.directory}">
<fileset dir=".">
<include name="bsh/commands/*.bsh"/>
<!-- and so on... -->
</fileset>
</copy>
The resource files can now be found on the build class path. Rebuild, and run jEdit
again:
$
ant dist
...
[bnd] # org.gjt.sp.jedit (jedit.jar) 1003
$
java -jar jedit.jar
Bingo! You should see the main jEdit window appear, as shown in figure 6.7.
Figure 6.7
Main jEdit window
Your bundle works as a classic
JAR
file, but will it work as a bundle? Let's review the
manifest.
Listing 6.2 jEdit mega bundle manifest
Manifest-Version: 1.0
Created-By: 1.6.0_13 (Sun Microsystems Inc.)
Bnd-LastModified: 1250524748304
Tool: Bnd-0.0.384
Main-Class: org.gjt.sp.jedit.jEdit
Bundle-ManifestVersion: 2
