Recommend two subprojects - one for the tag library and one for the example web application, with the web application having a dependency on the tag library. This would make repository management easier, too.

Matt Raible wrote:

I am using Maven to build struts-menu (http://sf.net/projects/struts-menu). Since this is a tag library - I want to build the struts-menu.jar from my target/struts-menu/classes directory, but I don't want to include net/sf/navigator/example/* classes. I want the example classes to remain in WEB-INF/classes and move the rest to WEB-INF/lib/struts-menu.jar before deployment. This will allow the struts-menu.war (example app) to use the same setup that users will use. What is the best place to do this - in a <preGoal> of webapp:war? Does anyone have any samples of this lying around?

Thanks,

Matt


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to