peterdnight wrote:
Overall - I heavily rely on functionality provided by maven plugin and think
the new pom editor rules!!!
I have noticed a couple of glitches with the new pom editor, like ctrl-s
does not remove the asterisk on the editor tab after changes have been made.
I am prompted to save however on exit, and changes do persist.
Running on eclipse 3.4 ;)
Also - there a couple of issues with wtp integration:
org.eclipse.wst.common.project.facet.core.xml
changing facet to jst.web to 2.5 causes hiccups with new maven project using
archetypes:
- after creating the project, the compiler gets set to "override project
defaults" which in my case switches from a 1.6 (or 6.0 ) compiler to a 1.5
compiler.
This is standard WTP behaviour, it configures java compiler compliance
level to match requirements of servlet specification specified in
web.xml. I am not sure if m2e can do anything about it, but please open
JIRA bugreport with sample project and we will have a look. Also note
that generally m2e honours java source/target version specified in
pom.xml and if I remember correctly, it never uses workspace defaults.
--
Regards,
Igor
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
