You can borrow some code from maven-dependency-plugin to pull artifact down on the fly. I doubt you need a profile since you can poke around with system property to find what OS you are on. You can even ask user to pass luncher type at runtime
Licensing is a headache, since apache/codehaus folks are very nervous about GPL :-). Oh please dont flame me. -D On 10/13/06, pjungwir <[EMAIL PROTECTED]> wrote:
Hi Dan, Ask all the questions you like. :-) Only grabbing the necessary binary bundle is a nice idea. I'll think about that one. So that means the plugin would have a variable dependency based on platform. I'm not sure how to do that, but it sounds fun to figure out. Profiles? I need an excuse to try those out. Can a plugin declare profiles so that one is chosen whenever the plugin is used? I would like to license the plugin the same way that launch4j is licensed: gpl for the tool itself; lgpl for everything linked to the executable it produces. Since the plugin is hardly more than a repackaging of the launch4j distro, that seems most appropriate. Paul -- View this message in context: http://www.nabble.com/plugin-naming-advice-tf2439526.html#a6805328 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
