[ 
http://jira.codehaus.org/browse/MECLIPSE-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114835
 ] 

Arnaud Heritier commented on MECLIPSE-346:
------------------------------------------

I don't see which change can produce this problem.
Perhaps another patch I applied.
Yes, can you open a new issue for that.
We'll fix it ASAP.

> Transitive dependencies aren't used to resolve JEE/JSP/EJB/Servlet versions
> ---------------------------------------------------------------------------
>
>                 Key: MECLIPSE-346
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-346
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: dependency resolution, WTP support
>    Affects Versions: 2.4
>         Environment: maven-eclipse-plugin-2.5-SNAPSHOT with freshly applied 
> WTP-2.0 patch
>            Reporter: Siarhei Dudzin
>            Assignee: Arnaud Heritier
>             Fix For: 2.5
>
>         Attachments: MECLIPSE-346.patch, test-project-MECLIPSE-346.zip
>
>
> After using parent pom settings from test project 34 or 35 ( Revision 595865: 
> /maven/plugins/trunk/maven-eclipse-plugin/src/test/resources/projects/project-35
>  )
> I've generated the project. As a result I had an error "The deployment 
> descriptor of the module 'jboss-seam-2.0.0.GA.jar' cannot be loaded." (using 
> jboss seam as an ejb module). After checking facets I've found that the the 
> ear module had ear version 1.4 in 
> org.eclipse.wst.common.project.facet.core.xml:
> <installed facet="jst.ear" version="1.4"/> instead of 5.0. 
> After manually changing the facet version to <installed facet="jst.ear" 
> version="5.0"/> and re-adding the project to the workspace the problem go 
> resolved.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to