Description Jason Sholl 2010-09-23 16:38:48 EDT

When tagging classpath entries for inclusion using the deployment assembly pages, the defaults ought to always place the tagged entries into the EAR's lib folder if one exists when the module is not a Web module.  e.g. if the module is already in the lib folder the tag should be '../', if the module is in the root and the ear has a default lib folder, the tag should be '../lib/', if the module is in the foo directory and the ear's lib folder is the bar directory, the tag should be '../../bar', etc.

The attached patch handles the above.