thanks for replies. they really helped me. but still have problem. first, modifying web.xml is not good as much as modifying JSP files. because about twenty projects use that taglib, so if taglib changed, I must change twenty web.xml. in fact, it isn't difficult job, but it seems bad job. taglib will be developed day after day, and other web developers want to know just one name for one product. notifying difference of both versions is easier than changing filename because all products are in-company project.
second, putting tld into jar seems good idea. and it solved my case. but one jar may need two or more tld files like JSTL or Struts. how can I solve a case like these? third, I have another requirement that need simple copying deployment. our web projects have some categories, and in same category projects have common web resources like jsp and html. so we extract that common resources and make a seperated project. for example, project A, B, C are in same category CAT1, 4 project are needed: common-CAT1, CAT1-A, CAT1-B, CAT1-C. at build time, common-CAT1's resources should be copied to CAT1-A, CAT1-B, CAT1-C. of source all associated project must be checked out to local workspace. we have used Ant for this job, and I want to use Maven for this. I think if I can deploy common-CAT1 in webapp form, CAT1-A can use it as dependency. making war for this job is not good because it should do unnecessary job. if I could build common-CAT1 using war:webapp and deploy the built webapp directory, it'll be great. how do you think about this?
