Facet Generation generates duplicate entries - breaks RAD/RSA support

As a follow up, RSA V7 reports an error when editing the facets that:

EJB Module 2.1 and Utility Module 1.0 cannot both be selected.

As a further follow up:

The pom of this project (which is an EJB project) had a packaging of type: JAR, not EJB.

Once that was done, the generated facet settings files was:

<faceted-project>
<fixed facet="jst.java"/>
<fixed facet="jst.ejb"/>
<installed facet="jst.ejb" version="2.1"/>
<installed facet="jst.java" version="5.0"/>
<installed facet="com.ibm.websphere.extended.ejb" version="6.1"/>
</faceted-project>

Which removes my concerns about the utility project.

This is the build section from the pom is now:

<build>
<plugins>
<plugin>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<wtpversion>1.5</wtpversion>

<additionalBuildcommands>
<buildcommand>org.eclipse.wst.validation.validationbuilder</buildcommand>
<buildcommand>org.eclipse.wst.common.project.facet.core.builder</buildcommand>
</additionalBuildcommands>

<additionalProjectnatures>
<projectnature>org.eclipse.wst.common.project.facet.core.nature</projectnature>
<projectnature>org.eclipse.wst.common.modulecore.ModuleCoreNature</projectnature>
</additionalProjectnatures>

<classpathContainers>
<classpathContainer>org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/WebSphere v6.1 JRE</classpathContainer>
<classpathContainer>org.eclipse.jst.server.core.container/com.ibm.ws.ast.st.runtime.runtimeTarget.v61/was.base.v61</classpathContainer>
<classpathContainer>org.eclipse.jst.j2ee.internal.module.container</classpathContainer>
</classpathContainers>

<additionalProjectFacets>
<com.ibm.websphere.extended.ejb>6.1</com.ibm.websphere.extended.ejb>
</additionalProjectFacets>

</configuration>
</plugin>
</plugins>
</build>

The problem is not localized only on IBM RSA V7.0.0.6.
Also Eclipse 3.3 / 3.4 duplicate entry using <additionalProjectFacets>.
For me:

<additionalProjectFacets>
<jst.web>2.3</jst.web>
</additionalProjectFacets>

give the following result:

<faceted-project>
<fixed facet="jst.java"/>
<fixed facet="jst.web"/>
<installed facet="jst.web" version="2.4"/>
<installed facet="jst.java" version="5.0"/>
<installed facet="jst.web" version="2.3"/>
</faceted-project>

Regards
Ale.

I have the same issue when creating a new web module. Adding "jst.jsf" in version 1.2 automatically adds "jst.web" in version 2.4 what is not supported by Eclipse. When i include "jst.web" in correct version 2.5 it looks like:

<configuration>
<additionalProjectFacets>
<jst.jsf>1.2</jst.jsf>
<jst.web>2.5</jst.web>
</additionalProjectFacets>
<wtpversion>2.0</wtpversion>
</configuration>

The result is a duplicated entry of "jst.web" in both versions 2.4 AND 2.5. It works for me, deleting the 2.4 entry out of the file.
Affects current version 2.7.

This is a patch to this bug which checks whether the additional facets overwrite any of the hard-coded installed facets. Also the patch contains a test case which should show the replacement.

The cause of this bug is the creation of the facet file for WTP 1.5 and above. This file contains entries for fixed facets, the server runtime and installed facets of a project. The fixed facets depend on the project type and can easily be added during the creation. For the installed facets the handling currently uses the dependencies and looks for the servlet-api to determine the version of the jst.web facet. So one solution is to add the dependency javax.servlet:servlet-api:2.x to the pom and it works or e.g. use the patch and override the installed facets using the additional facets configuration element.

There is still a bug when working with RAD because the extended and coexistence facets are only added to ear-projects but also need to be added to war-projects and the handling of the server runtime is somewhat buggy.

Can anyone post a status update on this? I can try to fix it if it's not been done yet.

KP, this bug still hasn't been fixed and meanwhile I'm usign a workaround

        <dependency>
            <groupId> javax.servlet</groupId>
            <artifactId>servlet-api</artifactId>
            <version>2.5</version>
            <scope>provided</scope>
        </dependency>

so it doesn't buggy my applications;

@Diego: Can you attach an example POM and the created Eclipse files? This would help us out.

Two attachments:

• sample-error.zip: contains the files generated by eclipse:eclipse and the pom for error sample
• sample-noerror.zip: contains the files generated by eclipse:eclipse and the pom for the workaround version

Bug reproduced here.

removed fixed version as no one has taken ownership to look into it.