[
http://jira.codehaus.org/browse/MECLIPSE-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114500
]
aheritier edited comment on MECLIPSE-346 at 11/22/07 7:59 AM:
--------------------------------------------------------------------
Your solution is quite good, but in theory we shouldn't have to use
MavenProject.getDependencies, MavenProject.getArtifacts or
MavenProject.getProjectReferences to be sure that we don't ask to maven to
resolve itself the dependencies (or we will have some problems, for example to
create the eclipse config if the project has some dependencies not yet built).
That's why we have some methods like
AbstractIdeSupportMojo.doDependencyResolution()
I wouldn't break something by using this method....
was (Author: aheritier):
Your solution is quite good, but in theory we should have to use
MavenProject.getDependencies, MavenProject.getArtifacts or
MavenProject.getProjectReferences to be sure that we don't ask to maven to
resolve itself the dependencies (or we will have some problems, for example to
create the eclipse config if the project has some dependencies not yet built).
That's why we have some methods like
AbstractIdeSupportMojo.doDependencyResolution()
I wouldn't break something by using this method....
> 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
