Hi, I've just started using the appassembler-maven-plugin and really appreciate its capabilities. Thanks to all who have contributed.
I have some applications that expect file/directory paths as cmdline arguments. Relative paths fail with the scripts generated by appassembler-maven-plugin v1.0-alpha-2, because the current directory is changed to the BASEDIR - i.e. the parent of the location of the script - before invoking the JVM. Looking at the current trunk versions of the appassembler-maven-plugin/resources/.../script/*BinTemplate files, and according to http://jira.codehaus.org/browse/MOJO-565 , this has been fixed. Is there a release schedule for appassembler-maven-plugin? (I assume not, as these things tend to go...) Here's my (totally, like, non-binding) +1 for releasing v1.0-alpha-3. I can see from JIRA and fisheye that there are other new capabilities being baked in, and I'd be cool with waiting until these stabilize, of course. Is there anything I can do to help? Separate question: why are the script templates located under "daemon" in the resources/ directory? Although they could be used that way, I suppose, there is nothing about the generated scripts that requires that they be run as daemons (i.e., processes that run in the background and can live beyond their parent process's lifespan). Thanks, Steve --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
