[ http://jira.jboss.com/jira/browse/JBIDE-759?page=comments#action_12375777 ] Rob Stryker commented on JBIDE-759: ----------------------------------- This is a problem with both WTP and the Seam plugins. The issue here is as follows. When you make a new Seam Project, 3 projects are created, Seampro, Seampro-ear, and Seampro-ejb. Theoretically eclipse should interpret these all as different "Modules", and normally they would. However, after browsing the org.eclipse.wst.common.component in each of the projects, I found the following lines: <wb-module deploy-name="Seampro"> (in the ear) <wb-module deploy-name="Seampro"> (in the war) <wb-module deploy-name="Seampro-ejb"> (in the ear) What this causes is the following: Both the ear and the war *think* their module ID is Seampro,org.eclipse.jst.jee.server:Seampro So when you go to add/remove a project from a server, or if you deploy the EAR but restart your eclipse installation, WTP will think it is the WAR, NOT THE EAR. Further attempts to publish will assume it's the war. A user in IRC also experienced similar behavior, where without restarting, he tried to full-republish his ear and it instead tried to publish the war. I am filing a bug in eclipse for allowing two different projects in the same ModuleFactory to keep the same id. I am also going to post about this on JBossTools-dev so that it gets maximum exposure. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira