Re: [m2e-users] Multi Project Dependency

[Anton Tanasenko <atg.sleepless@xxxxxxxxx>]

Both false.

'Maven build' and 'Java application' are just two types of eclipse launch types (you can see all available launch types in the run/debug dialog). Each eclipse launch type has its own logic of what to do when the run/debug button is pressed.

'Maven build' will execute a maven runtime in a separate process using specified project's dir as working dir. It's basically the same as running 'mvn install' on cmd line in that directory, so it does not consult project's build path whatsoever (It does, however, perform some magic when a 'resolve workspace projects' checkbox is enabled, but it's not related to the eclipse project classpath).

'Java application' launch type forks a java process with all classpath containers and/or entries, including maven dependencies and any external jars/projects you might add to the project.

Those project classpath containers might be contributed by an arbitrary eclipse plugin and m2e happens to be one such plugin.

2016-01-03 21:35 GMT+02:00 Sony Antony <sonyantony900@xxxxxxxxx>:

Thank you Anton :

Read your response carefully. Some more questions inline below

On Sun, Jan 3, 2016 at 6:54 AM, Anton Tanasenko <atg.sleepless@xxxxxxxxx> wrote:

Hi,

M2e has a separate project classpath container for repository jars and workspace projects (Java Build Path -> Libraries -> Maven dependencies).

Does this mean that when I choose 'Run As-> Maven install' only Maven dependencies ( which came from pom.xml ) will be in the classpath ( And that all other jar files -Add Jars/Add External Jars - will be ignored ) ?

Similarly :

If I run a java file directly from the editor, Maven Dependencies will be ignored, but Add Jars/Add External Jars/Projects will be in the classpath

Is the above true ?

--sony

 

'Referenced projects' mechanism is meant to be modifiable by users, while m2e derives project's classpath from pom.xml. And it also cannot be used since it includes linked projects' classpath as-is, while in pom.xml one might redefine dependency versions and/or specify excludes.

 

2016-01-03 12:13 GMT+02:00 Sony Antony <sonyantony900@xxxxxxxxx>:

I created a root pom ( r ) with 2 modules ( M1 & M2 )

M1 depends on M2

In Eclipse Work Space I have 3 Projects - R, M1 & M2

Everything works fine.

However :

1.  I was expecting Project M1 to list M2 unde Projects ( Properties for M1->Java Build Path -> Projects )

..but found no reference to M2

Am I supposed to see a reference to M2 here ?

2. When I do source browsing ( 'Open Declaration'/F3 ) on a call to M2 method from M1, Im able to see the declaration as expected.

How is exclipse storing teh inter project references, in this case

--sony

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users

--

Regards,

Anton.

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-users

--

Regards,

Anton.