Using LookAndFeelAddons to manage non-SwingX addons
I am using LookAndFeelAddons to manage custom components with UI delegates for non-SwingX components. It works extremely well. Thank you. Having a well-written and reusable manager is great (especially when I didn't have to write it).
I would like to be able to distribute, just the portions of SwingX that I need with my project. I do not understand the licence enough to know if I am able to package, just some of the classes in a seperate jar for download. Can anyone clue me in on this?
I have, to test the feasibility of doing so, created an addons.jar that I am currently testing with. This jar is ~14K and contains only the LookAndFeelAddons code. I have discovered that I am required to include org.jdesktop.swingx.plaf.resources.swingx.properties in the jar to prevent errors from the call to LookAndFeelAddons.addDefaultResourceBundle in the LookAndFeelAddons static initializer.
Just in case anyone is wondering here are the files that I included in my custom addons.jar. This seems to be the complete set necessary to utilize LookAndFeelAddons outside of SwingX.