[paskos]

This message has not been recovered.

[paskos]

This message has not been recovered.

[Loyal Water]

MyEclipse does not handle such a long chain of dependencies. It handles dependencies just one level down.

[joehuangathome]

Any new development on Maven transitive dependences from MyEclipse? I have a Mavenized application where A –> B, A–>C, both B and C depends on D. Maven build(compile, install) has no problems resolving it but when an MyEclipse project is bult on it. MyEclipse complains about D that “both path contains duplicate entry”.

Maven pom files are provided for all A, B, C and D.

[support-eugene]

@joehuangathome wrote:

Any new development on Maven transitive dependences from MyEclipse? I have a Mavenized application where A –> B, A–>C, both B and C depends on D. Maven build(compile, install) has no problems resolving it but when an MyEclipse project is bult on it. MyEclipse complains about D that “both path contains duplicate entry”.

Maven pom files are provided for all A, B, C and D.

Thank you for reporting the issue. We will look into it in our next releases. Unfortunately I can’t suggest a walkaround other then changing your dependencies…

[support-eugene]

@joehuangathome wrote:

Any new development on Maven transitive dependences from MyEclipse? I have a Mavenized application where A –> B, A–>C, both B and C depends on D. Maven build(compile, install) has no problems resolving it but when an MyEclipse project is bult on it. MyEclipse complains about D that “both path contains duplicate entry”.

Maven pom files are provided for all A, B, C and D.

Can you better describe the problem?

I have web project that depends on:

    <dependency>
        <groupId>org.springframework</groupId>
        <artifactId>spring-tx</artifactId>
        <version>2.5.6</version>
    </dependency>
    <dependency>
        <groupId>org.springframework</groupId>
        <artifactId>spring-context</artifactId>
        <version>2.5.6</version>
    </dependency>

So it indirectly depends on spring-core twice. I can deploy the web project and export as war.

Please provide detailed description so we can fix the problem ASAP.

[joehuangathome]

Eugene:

From my last post, there are 3 levels along the dependency hirarchy, A as the very top. B and C just below it, and D at the very bottom. Pom files are provided at all level and for all jars. I am not an expert at pom file but I think pom for A.jar is the master pom file. In order to mount(make a new project out of) MyEclipse on A, the command mvn eclipse:eclipse is executed at directory level where pom file for A resides. When I do File->New Prject->Java Project and hit Finish, I was bombed with this duplicate entry error message I quoted in the last post. I verified it by going to Build Path for A project and I did see D listed twice in MyEclipse’s buildpath window.

My D is a private jar while your example is a Spring jar.

Not sure if it is detailed enough for your analysis.

FYI:MyEclipse is THE IDE for our company and Maven is our build tool. And if they don’t integrate merrily, we’ll have to scratch more on our heads, some of which are already sparsely hair popluated.

Joe

[support-eugene]

My understanding:

1. A, B, C, D are POMs in your repository. They are not projects in the workspace.
2. You do mvn eclipse:eclipse for A and import the result into MyEclipse workspace. Does it have source folders?

Thus project A is a regular Java project. It doesn’t have “Maven Dependencies” classpath container (see picture attached).

Attachments:

You must be logged in to view attached files.

[joehuangathome]

@support-eugene wrote:

My understanding:

1. A, B, C, D are POMs in your repository. They are not projects in the workspace.
2. You do mvn eclipse:eclipse for A and import the result into MyEclipse workspace. Does it have source folders?

Thus project A is a regular Java project. It doesn

1. A, B, C, D are POMs in your repository. They are not projects in the workspace.
2. You do mvn eclipse:eclipse for A and import the result into MyEclipse workspace. Does it have source folders?

1. That is right.
2.Maven directory structure is followed. source/main/java and source/main/resources are the source file folders.

I think what I missed is that I did not check “Enable all m2features” box in Maven4MyEclipse Preference screen since the words “some feautures are not compatible with MyEclipse projects” label turned me away. Now it works!

Thanks for the great help!

Joe

[support-eugene]

Ok, now I see.

The problem is that currenttly MyEclipse doesn’t support projects created outside of it. So if you want to use MyEclipse Maven support you will need to create appropriate project type (web/EJB (with Maven support selected on the first page) or Java Maven Project). Then you will have to manually copy the project contents to it. Afterwards you will be able to use MyEclipse support for Maven projects – i.e. classpath built from dependencies list, deployment and debug.

[Author]

Posts