[Jagov]

We are trying to import existing maven projects into myeclipse blue. myeclipse creates a JEE6 project when we import a EJB 3.0 project, this should be a JEE5 project. We can’t change it anywhere as myeclipse does not create a ..mymetadata file.

This is really a blocking issue for us, as we need to deploy onto WebSphere 6.1 (with ejb feature pack). And myeclipse blocks the deployment of the JEE6 application onto the WebSphere server.

We have found a workaround but it is not very viable for many projects
1. Create a EJB project for the IDE.
2. Copy the contents of the original project into the new project. (except eclipse settings etc)
3. Refresh the project.
4. Enable dependency management on the project.

This pom should be enough to reproduce the problem.

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.poc</groupId>
    <artifactId>HelloWorldEJB</artifactId>
    <packaging>ejb</packaging>
    <name>HelloWorldEJB</name>
    <version>1.0-SNAPSHOT</version>
    <description>HelloWorldEJB</description>

    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-ejb-plugin</artifactId>
                <version>2.2</version>
                <configuration>
                    <ejbVersion>3.0</ejbVersion>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <source>1.5</source>
                    <target>1.5</target>
                    <encoding>UTF-8</encoding>
                </configuration>
            </plugin>
        </plugins>
    </build>

    <dependencies>
        <dependency>
            <groupId>javax.ejb</groupId>
            <artifactId>ejb-api</artifactId>
            <version>3.0</version>
            <scope>provided</scope>
        </dependency>
    </dependencies>
</project>

We are using the myeclipse blue plugin.

[support-tomasz]

Can You please describe that type of import are You using? What is Your version of MyEclipse Blue?

[Jagov]

We are using the MyEclipse Blue version 9 Eclipse plugin. And we use File -> import -> Maven4MyEclipse -> Existing Maven Projects

[support-tomasz]

After import please rightclick on the Project and then go to the properties and then plase go the location specified under Resources, please make sure that in mymetadata is j2ee-spec=”5.0″ if exists, if not please send me on my e-mail [email protected] the error log file from Your workspace.

[Jagov]

I have send an email to tomasz[at]genuitec[dot]com on 7/7/2011 with the log file and a hello world project to reproduce the problem. It also contains the steps to reproduce the problem. could you verify that you have received the email.

[support-tomasz]

Thanks for Your e-mail. In Your example You are importing Maven project and in the result You would like to have an EJB project with Maven support. At this moment You will still retrieve a Maven Project so in this case Your way around is absolutely correct.

[Jagov]

Is it a known bug or is it now reported as a bug and when is this possibly fixed?

The email described that there are problems in all the modules (web/ejb and ear) how about those?

[support-tomasz]

Maven Projects in MyEclipse has dual natures and this features are not implemented now.

[Author]

Posts