I don't know if this is of interest to anyone, but I thought I'd just record it for the archives in case anyone does have the same itch I've just had.
I like to use maven for everything now. The site is only worthwhile for a project of components, or larger project, but having a standard project.xml even in tiny 1->3 class projects is worth it. However, this causes me pain. With a component project, the target of the output is a set of jar files. With the tiny projects it is normally just one or more main methods. I could build these into jars and execute these, but in this I hit an issue in that the jar still needs its supporting jars to be available. In the future I can see a tool which runs a jar, checks the dependencies inside the MANIFEST and then talks to the maven repo [cjan] to get those jars if need be. However I want something small and tiny. So I've a 'RunMaven' Java 'script' which assumes it is run in the same directory as the project.xml and creates a suitable classpath to run against. I'll then setup a mavenrun alias to invoke this and just type mavenrun <java package name>. If anyone is interested, I can submit it somewhere. Currently it builds against my own commons library, but all the methods are available in Jakarta Commons. Or if anyone knows of a better way to do this, I'm all ears. Hen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
