Hi all... I think I have found a theory to why our m2eclipse does not behave as expected. One of our projects use the jaxws-maven-plugin (currently ver 1.10) to generate web service artifacts from WSDL and this seems to crash when the Maven builder runs.
I'm getting this error message: Build errors for soa-jax-ws-artifacts; org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.codehaus.mojo:jaxws-maven-plugin:1.10:wsimport': Mojo execution failed. My theory is that this crash prevents the Maven builder to complete whatever it is supposed to be doing, hence the Eclipse classpath is not refreshed or purged. This is a major annoyance for our project. Is there a solution? Thank you for your assistance... // Niklas P ________________________________________ Från: Eugene Kuleshov [[email protected]] Skickat: den 26 januari 2009 16:36 Till: [email protected] Ämne: Re: [m2eclipse-user] Eclipse not picking up changes in m2eclipse managed dependencies Niklas, Have you checked that with workspace resolution enabled you see project reference under "Maven Dependencies" container? It has the same icon as projects, so should be easy to distinguish. If you don't see project there, please double check that you are referencing a correct dependency version, you can use "Maven / Show Dependency Hierarchy" action from popup menu on project jars that should show you where dependency came from and if there is version conflicts. Also, please check that build automatically is turned on and that project properties / Java compiler / Building / Scrub output folders is enabled on your projects. regards, Eugene 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 > > ________________________________________ > 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
