[
http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103194
]
Michael Schnake commented on MECLIPSE-264:
------------------------------------------
What changed with WTP 2.0 IMHO is the way J2EE module dependencies are
declared. They no longer to are declared inside
.settings/org.eclipse.wst.common.component, but as a classpath entry attribute
in .classpath instead.
So, currently (for WTP 1.5) there is an entry in
.settings/org.eclipse.wst.common.component created, like
<dependent-module deploy-path="/WEB-INF/lib"
handle="module:/classpath/var/M2_REPO/org/springframework/spring-core/2.0.5/spring-core-2.0.5.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
For WST 2.0 the following entry must be created in .classpath instead:
<classpathentry kind="var"
path="M2_REPO/org/springframework/spring-core/2.0.5/spring-core-2.0.5.jar">
<attributes>
<attribute name="org.eclipse.jst.component.dependency"
value="/WEB-INF/lib"/>
</attributes>
</classpathentry>
The issue of supporting classpath entry attributes is also relevant for
MECLIPSE-270
Currently after an "mvn eclipse:eclipse" when using WTP 2.0 I have to manually:
1. Drop the dependency entries from .settings/org.eclipse.wst.common.component
(either by unchecking them via Eclipse "J2EE Moduie" GUI, or by editing the
file directly).
2. Add the "org.eclipse.jst.component.dependency" attribute to the classpath
entries in .classpath (again by checking them via Eclipse "J2EE Moduie" GUI, or
by editing the file directly).
3. (MECLIPSE-270 related) Add my spring-aspects.jar to the AspectJ Path (via
GUI or editing .classpath)
> Support for WTP2.0
> ------------------
>
> Key: MECLIPSE-264
> URL: http://jira.codehaus.org/browse/MECLIPSE-264
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: WTP support
> Reporter: Geir Pettersen
>
> As far as I can see this plugin only supports WTP version 1.0 and 1.5. while
> WTP 2.0 is already released in milestone 6
--
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
