Yes, RAD 6 is based on Eclipse 3.2.1-xx and it honors WTP 1.5 resources.
RAD 7 provide backward compatability for RAD 6 projects, so by that
definition RAD 7 can also work with WTP 1.5 resources.
If memory serves me, WTP 1.0 resources are for the older Eclipse v2.x (?)
versions. Now I'm not sure what wtpversion=R7 is for..
Regards
Salman Moghal
----- Original Message -----
From: "Olivier Dehon" <[EMAIL PROTECTED]>
To: "Maven Users List" <[email protected]>
Sent: Tuesday, February 26, 2008 9:55 PM
Subject: Re: maven-eclipse-plugin 2.4 & versioned projects
Sorry to reply to your question with another question, but
does RAD6 really supports WTP 1.5 ?
I was under the impression that RAD7 only supported that version.
-Olivier
On Tue, 2008-02-26 at 12:38 -0800, Salman Moghal wrote:
Hello:
I'm using maven-eclipse-plugin v2.4 to generate WTP 1.5 resource for
Eclipse 3.2.x / RAD v6.x environment. The goal of this exercise is to
take advantage of Eclipse 3.2 / RAD v6.x
integrated development, debugging, and hot code deployment features. The
runtime environment is WebSphere Application Server v6.1. Eclipse / RAD
also have M2Eclipse plugin installed for dependency management, etc.
There is one slight issue that has me scratching my head for a few days.
It has to do with generated WTP v1.5 files.
Essentially, maven eclipse plugin goal "eclipse:m2eclipse" generates all
WTP 1.5 files correctly. However, once
<addVersionToProjectName>true</addVersionToProjectName> is added to
plugin config, .settings/org.eclipse.wst.common.component contains an
incorrect entry. The goal generates the .project WTP file properly with
a project name containing the POM version number, but the corresponding
.settings/org.eclipse.wst.common.component contains an incorrect value
for <wb-module deploy-name=".....">. The value of deploy-name= does not
contain a POM version number along with the project name.
The reason why having a version number in <wb-module deploy-name= entry
is important is because if the EAR / WAR module is deployed to WebSphere
runtime in "loose configuration" mode, the runtime complains about not
being able to locate corresponding modules. Loose configuration allows
the class files to reside in Eclipse / RAD workspace and speeds up the
EAR deployment process many folds since no real EAR is generated and
installed into WebSphere. Eclipse / RAD loose config file is located
under
WORKSPACE/.metadata/.plugins/com.ibm.etools.wrd.websphere/looseconfigurations/<EAR
NAME>/looseconfig.xmi.
Note that if I manually make the change to the generated
.settings/org.eclipse.wst.common.component file by adding version number
along with the project name, the runtime doesn't complain and everything
works well in loose configuration mode.
May be I'm missing something in maven-eclipse-plugin configuration.
Here's what I have:
<!-- maven-eclipse-plugin config for generating WTP 1.5 resources for WAR
and EARs -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<manifest>
${basedir}/src/main/resources/META-INF/MANIFEST.MF
</manifest>
<addVersionToProjectName>true</addVersionToProjectName>
<useProjectReferences>false</useProjectReferences>
<wtpmanifest>true</wtpmanifest>
<wtpapplicationxml>true</wtpapplicationxml>
<wtpversion>1.5</wtpversion>
<additionalBuildcommands>
<buildcommand>com.ibm.etools.common.migration.MigrationBuilder</buildcommand>
<buildcommand>org.eclipse.jdt.core.javabuilder</buildcommand>
<buildcommand>org.eclipse.wst.common.project.facet.core.builder</buildcommand>
<buildcommand>org.eclipse.wst.validation.validationbuilder</buildcommand>
</additionalBuildcommands>
<additionalProjectnatures>
<projectnature>org.eclipse.wst.common.project.facet.core.nature</projectnature>
<projectnature>org.eclipse.jdt.core.javanature</projectnature>
<projectnature>org.eclipse.wst.common.modulecore.ModuleCoreNature</projectnature>
<projectnature>org.eclipse.jem.workbench.JavaEMFNature</projectnature>
</additionalProjectnatures>
<classpathContainers>
<classpathContainer>org.eclipse.jst.j2ee.internal.module.container</classpathContainer>
</classpathContainers>
</configuration>
</plugin>
<!-- maven-eclipse-plugin -->
Is there any way to manipulate or affect entries in
.settings/org.eclipse.wst.common.component via maven-eclipse-plugin
configuration? to If you guys have any clues / pointers /
recommendations, please do share.
Regards
Salman Moghal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
