Niklas,

M2E is expected to resolve dependencies from workspace projects by default, so your changes are expected to become available immediately without any special configuration.

To check if m2e properly resolved workspace dependencies, you can open "Maven Dependencies" classpath container in Package explorer. You should see something similar to [1] (note three dependencies resolved from other workspace projects).

[1] http://imagebin.org/36790



Pettersson, Niklas wrote:
Thank you for your quick reply...

I have tried with workspace resolution both on and off but the problems still 
exists. It is very difficult to get code changes to be picked up by the Eclipse 
classpath. Usually it takes a restart of Eclipse which leads me to belive that 
Eclipse somehow caches the classes in the dependencies and that M2Eclipse fails 
to purge/reload them when code in modules changes.

Can you describe how I should work if we pretend that everything works as 
supposed.

// Niklas P

________________________________________
Från: Eugene Kuleshov [[email protected]]
Skickat: den 23 januari 2009 18:07
Till: [email protected]
Ämne: Re: [m2eclipse-user] Eclipse not picking up changes in m2eclipse managed 
dependencies

Niklas,

  Please verify that those projects that picking changes have workspace
dependency resolution enabled. Otherwise dependencies are resolved from
the Maven local repository and you would have to run Maven install
command after every change. You can also see if projects are resolved
from workspace in the "Maven Dependencies" container (jar vs. project
entry). So, if you see jars there even if workspace dependency
resolution is enabled, please check that referenced dependency version
matches with the version of the project in workspace and then run Maven
/ Update Dependencies action.

  Another reason when changes may not be seen is if you have Project /
Build automatically turned off.

  Hope that helps.

  regards,
  Eugene


Pettersson, Niklas wrote:
We are experiencing problems with Eclipse and M2eclipse not picking up
changes to code in dependent modules. Our project is a large Maven
based project which constist of seven modules declared as snapshots.
We use Eclipse 3.4.1 with M2Eclipse 0.9.6.

When I change code in one of the modules, like changing method
names, making new classes etc, and then to try to use it in another
the changed code is not presented by Eclipse content assist. It seems
like Eclipse is not aware of that the code has been changed.

I have tried all commands that is available in m2eclipse
(like "Update dependencies", "Update snapshots" etc.) but I can't get
Eclipse to pick up the changes. Cleaning the project does not fix the
problem, only if I restart Eclipse the changed code is present.

What is wrong?? Have I set up my project in the wrong way? Does
anybody else have this problem?


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email




---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to