ChrisGWarp wrote:
So, your "update project configuration" is similar in function to the
maven-eclipse-plugin code? In that it creates the necessary eclipse
.settings files/.project/.classpath files based upon the contents of the
POM?
Yes. But m2eclipse is using proper API, so it would be WTP code or
other projects that actually create those settings.
Also, project configurator is capable of updating settings when other
projects changed in workspace, e.g. dynamically update dependencies or
deployed modules when dependency version changed in workspace.
I've put a good deal of working in getting the POM to work with the
maven-eclipse-plugin. Why not, use some of their code? It seems to me that
it would solve what you want?
As a matter of fact, maven-eclipse-plugin is executed while updating
project configuration, which is done by special configurator. However,
this configurator can't update project configuration when workspace
project change.
Also note that WTP configurator is executed after maven-eclipse-plugin
configurator and it would overwrite project configuration. If you want
to use only plugin configurator, then you would need to uninstall WTP
configurator. However our goal is to make it unnecessary to "put a good
deal of working in getting the POM to work with the
maven-eclipse-plugin", so projects created by plain Maven archetypes
could be imported into Eclipse and ready to go. See for example WTP
howto. http://docs.codehaus.org/display/M2ECLIPSE/WTP+mini+howto
But that is is another way of saying: I don't understand what you are trying
to achieve with the m2eclipse plugin where there are others that do
_similar_ features.
Please note that maven-eclipse-plugin is actually using reverse
engineering and not using Eclipse APIs to create config files. This is
more fragile and less robust approach, which also requires explicit
project refresh, that slows down the whole process.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
