Re: Chainsaw harmonization, branding, etc.
2007-07-01 22:27:56 GMT
> > I used the assembly:assembly plug to create a distribution, however > the descriptor (src/assembly/bin.xml) needs to be tweaked to drop > out non-re-distributable jars. Hopefully, all the non-(Continue reading)
re- > distributable jars are not essential to operation, at least not on > JDK 1.5. Currently, you can do java -jar on apache-chainsaw.jar and > the app launches. I added the main-class and path entries to the > chainsaw jar, wouldn't do that on a library jar but hopefully is a > good thing for an application jar. > I've never found that main-class much use because of the external reference to jars. Personally I like the appassembler distribution that maven can build, plus the Mac-specific one. The external referenced jars are the crux of the problem with Chainsaw. Out-of-the-box, Chainsaw is useful for socket-based operations and local file reading. For JMS, DB, and VFS style operations, the 3rd-party requirements make it a tricky distribution problem. Which exactly are the non-redistributable jars? Xstream and jmdns are the only listed dependencies in the pom, both of which are ASL licensed. JSch (for ssh-based stuff like vfs) used to LGPL but is now BSD licensed, but we don't actually need to depend on that per-se (they can go in the plugins directory). > I will probably need to get my head around the distribution > mechanisms. I think we do need a classic distribution tarball that > is farmed out to the distribution mirrors. Keeping the WebStart is