Zoltan Baji [http://community.jboss.org/people/zzzooo] created the discussion "Re: Eclipse indigo JBoss AS 7 deploy problem" To view the discussion, visit: http://community.jboss.org/message/635936#635936 -------------------------------------------------------------- We have found the issue. The problem was: I imported all my projects as "existing maven project". Then - somehow -, the org.eclipse.wst.common.component file under the ear project's .settings directory referenced for the projects - which should have been packaged (zipped) into the ear's lib directory - as resource instead of maven reference. Problem: <dependent-module archiveName="wicket-core-2.0.1-SNAPSHOT.jar" deploy-path="/lib" handle="module:/resource/com.doctusoft.web.wicket-core/com.doctusoft.web.wicket-core">             <dependency-type>uses</dependency-type>         </dependent-module> Solution: I replaced it to this: <dependent-module archiveName="wicket-core-2.0.1-SNAPSHOT.jar" deploy-path="/lib" handle="module:/classpath/var/M2_REPO/com/doctusoft/web/wicket-core/2.0.1-SNAPSHOT/wicket-core-2.0.1-SNAPSHOT.jar">             <dependency-type>uses</dependency-type>         </dependent-module> No it's packed correctly and works fine! Thanks a lot! z. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/635936#635936] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Zoltan Baji [http://community.jboss.org/people/zzzooo] created the discussion "Re: Eclipse indigo JBoss AS 7 deploy problem" To view the discussion, visit: http://community.jboss.org/message/635953#635953 -------------------------------------------------------------- I also tried that many times - it didn't help. The situation: I had too different repository under the svn. Both of them had a (maven) parent project: let it parent1 and parent2. We group the versions and repository references in these parent projects' pom files. Under these parent projects has many different projects. Under the parent1 we had projects, which are a kind of company framework elements. Under the parent2 we had projects, which are specific for a customer, and they references for the framework projects (here I have the deployable ear project as well). I checked out these parents and it's child projects, and build them from command line with maven (3.0.3) (java version: 1.6.0_26). I have Ubuntu 10.10. After this, I imported them as existing maven projects into eclipse. First, the parent1 with it's child projects and then the parent2 with it's child projects. After this, I created a new server instance - JBoss 7 - referencing to my own JBoss. Then I deployed, and the mentioned problem happend... We tried this in 3 different computer with the same environment except the op. sys. (Ubuntu 10.04, Ubuntu 11.10, Mac - OSX). The Ubuntu 10.04 was mine, and the Mac had the same issue. But on the Ubuntu 11.10 was ok. After this, we compared the differences, and realized the solution. I don't think the op.sys is the responsible for this problem, but I tried to import the projects more times, and the same issue happend - also on the Mac. I really don't know what would cause this, but after when I fixed the org.eclipse.wst.common.component file manually it worked fine. So I guess the problem was with the m2eclipse or with the wst. Maybe the our settings were different - I don't know. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/635953#635953] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Zoltan Baji [http://community.jboss.org/people/zzzooo] created the discussion "Re: Eclipse indigo JBoss AS 7 deploy problem" To view the discussion, visit: http://community.jboss.org/message/636003#636003 -------------------------------------------------------------- I did "Update Project Configuration" and the problem wasn't recreated. So after I manually fixed that file - everything is ok. Unfortunatelly, I can't send you the poms :( . -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/636003#636003] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]