Classpath not generated for (non-jsw) daemons.
----------------------------------------------
Key: MAPPASM-92
URL: http://jira.codehaus.org/browse/MAPPASM-92
Project: Mojo AppAssembler Plugin
Issue Type: Bug
Affects Versions: 1.0
Reporter: David Stenglein
Attachments: appassembler-maven-plugin.patch
The scripts for a simple daemon do not include the right (or any) classpath.
I had some fun with debugging maven itself in eclipse and I tracked down the
issue (I'd have given up if I couldn't set breakpoints in the plugin code to
see how things were working). It seems that the creation of the classpath is
done different ways in different places. I did a very quick hack that got it
working.
I took the classpath creation code in AssembleMojo and made it a static method
that I could call from GenerateDaemonsMojo.
I've attached the patch I made.
If I have some time off in January, I'd like to explore refactoring the plugin
to unify the code for programs and daemons more completely. The first thing to
do would be to create some functional tests and sample scripts to compare to.
If this patch is something one of you could rework into something that could be
released, that would be great!
I love this plugin. I think it is a great tool for presenting polished packages
to sysadmins to deploy (being a former sysadmin myself).
Thanks,
Dave
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
