Using Maven to build BrailleBlaster is fine. Users, however, will be more comfortable with BrailleBlaster if it is directly executable, as Eclipse is. They just want to seloect a program or shortcut and have it runj, not requiring anything except the jre. Incidentally, hhow about setting up Maven in the BrailleBlaster repository and setting up the brailleblaster directory with the structure Maven requires. John B. On Sat, Aug 07, 2010 at 03:53:31PM +0100, Michael Whapples wrote: > Hello, > I said in a previous message that the proposed way of starting > BrailleBlaster java code was just complicated and that I thought much > better and simpler solutions existed which would fit in with using maven > as a build system. I have now done a quick look and here are two options. > > 1. Use the built in maven assembly plugin: This possibly is the most > flexible option as the assembly plugin is really a general plugin for > allowing you to assemble archive files from maven projects and create > custom descriptors. For this I think we would need to provide the start > up scripts (shell script for unix and batch file for windows) and then > just get the assembly plugin to copy these into the correct location. > 2. The AppAssembler plugin from codehaus > http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/: This > plugin seems to be more targeted at creating application bundles which > is what we are looking at here. It has a mechanism for it to generate > these start up scripts for us, however it may be limiting should we want > to do something very advanced. > > At the moment I have no strong view for one of these options over the > other, but these both are better than having to write custom C code to > use JNI, just to start the JVM in a particular class. > > Michael Whapples -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities