Right now (EA2) we don’t do anything to facilitate deployment when using this “utility project” model. However, we do recognize how useful it is and we do plan on supporting it soon.
A workaround for the current version would be to have Eclipse create and save jar export tasks for the library projects and then run the jar exports upon modification. The export would save the revised versions of the jar to the <webroot>/WEB-INF/lib directory of your web project. Our deployer would then note the change and send it to all the application servers upon which the project is deployed.
However, we will be supporting this model very soon, but most likely after the GA date of 7/15. We plan on introducing a “utility project” concept with each project. Any utility project artifacts that are modified will automatically be deployed / redeployed to all deployed projects that use it. It’s basically an enhancement to our Sync-On-Demand deployer, but like I said, given the feature list for GA it will most likely slip into the next dot release in early August.
–Scott
MyEclipse Support