We are currently running a
maven project setup, where we have a shared_resources project which is merged into 2 different web projects, via a maven build. The merge is done by defining the shared_resources project as a resource in the admin_portal and client_portal project pom files. We are trying to migrate from eclipse juno/tomcat 7 to netbeans 7.3.1/glassfish 3.2.11. The projects build and deploy fine. When we set the admin and client projects to compile and deploy on save, everything seems to work fine. However, the problem is that when we modify the shared project, the changes don't auto-push to the admin and client deployments. This causes us to have to build the 2 portal projects on every shared modification, which really slows down the development speed. Is there any clever way around this, or a better project structure we should be using?
I have included a sample file structure for the projects and resulting wars. Note that when the shared resources are added to the portal projects, it is more of a merge effect. There are overlapping folder structures, where the shared resources augments each of the portal's respective files.