Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Only Dependencies from top level pom.xml in classpath

What m2eclipse version are you using?

It sounds like you are on 0.10.0 and imported multi-module maven project
as single Eclipse workspace project. This is no supported starting with
0.12.x. Please upgrade to 0.12.1 and reimport the project, ideally into
a new workspaces. This will automatically create separate workspace
project for each maven module, and each project will have proper classpath.


On 11-01-29 04:19 PM, Billy N wrote:

Sorry for the confusion, this is an already existing project and I
cannot break it into multiple projects at this time. Nor can I checkout
each module as its own project. Unfortunately the top level project has
all the attached source (coming from different modules).

I.E (three source folders for the project):
jar/main/java/src for the jar
ear/main/java/src for the ear
war/main/java/src for the war

So the top level pom contains the modules:

But this pom does not contain the dependencies for each of those
modules, each module has at least one more pom file, ie under the jar
folder the is a pom that contains the dependencies for the jar stuff.

This is an old project and I really cannot break it apart at this point.
So I am stuck, basically I am adding in each jar file to the classpath.
the problem is that whenever I need a new dependency or a newer version
I have to update the correct pom file and I have to remove the old
version of the jar from the classpath and add the new version to the
classpath. I would really like to just update the pom and have the
plugin deal with my classpath.

Do anyone have any other ideas that might work??


m2e-users mailing list

Back to the top