- This topic has 7 replies, 4 voices, and was last updated 16 years, 2 months ago by
.
-
Posts
-
I downloaded MyEclipse 7.0 M2, created a new folder with a basic pom.xml, called mvn eclipse:eclipse, imported it into myeclipse, and don’t see add project capabilities for Maven4MyEclipse.
Does 7.0m2 not support existing maven projects (without having to edit .project)?allenparslow,
I have asked some one from the dev team to look into this issue. He will get back to you with an update asap.Did you import it using m2eclipse wizard (Import->General/Maven Projects)? Note: you should enable m2eclipse features on Maven4MyEclipse preference page to be able to use the wizard.
If yes – you do need to do any configuration for that projects – they are treated as MyEclipse Java Maven Projects.Yes, “Enable all m2eclipse features” (on the Maven4MyEclipse preference page) added the option “menu /file/Import->General/Maven Projects”, which seems to work correctly for projects created with mvn eclipse:eclipse.
Is there a reason why this setting is not the default (besides the disclaimer that “some features are not compatible with MyEclipse projects”)?
I’m also really happy when mvn eclipse:eclipse projects have <packaging>war</packaging, that it automatically added web-project capabilities :).
Also looks like <scope>provided</scope> is correctly filtering server-deploys (although after a change to scope-provided, it seems that a /project/clean is required for the scope-provided lib to be filtered on re-deploy).
@allenparslow wrote:
Yes, “Enable all m2eclipse features” (on the Maven4MyEclipse preference page) added the option “menu /file/Import->General/Maven Projects”, which seems to work correctly for projects created with mvn eclipse:eclipse.
You don’t need to run eclipse:eclipse goal. It is meant to create generic Eclipse project (the one that is usable in Eclipse SDK) – web capabilities, m2eclipse support, etc. are added by IDE at import time.
@allenparslow wrote:
Is there a reason why this setting is not the default (besides the disclaimer that “some features are not compatible with MyEclipse projects”)?
That is the primary reason. m2eclipse UI does not fit into MyEclipse UI and may confuse users.
Your question “Is there a reason why this setting is not the default ?” is exactly as you specified – it really is a choice for us between two imperfect situations. If we enable this by default, it could confuse a whole lot of users.
This forum would fill up with questions like “Why did you set me up with UI options that allow me to create projects which don’t even work [deploy etc] with your own tooling.
So it was a question of slightly aggravating a very few users who use both, versus completely aggravating a very large number of users. We chose the former.
You don’t need to run eclipse:eclipse goal
I see, “menu /file/Import->General/Maven Projects” only requires a pom.xml (does not need a .project) to import an existing maven project.
@allenparslow wrote:
Is there a reason why this setting is not the default (besides the disclaimer that “some features are not compatible with MyEclipse projects”)?
The reason why I asked this question was that current maven users may not know to go to this location to enable existing maven project imports.
On the other hand, I get that it is undesirable to add other features which may not function as expected.
Maybe when 7.0 goes live, a note could be put in the known issues or faq section to help existing maven users?
