- This topic has 3 replies, 2 voices, and was last updated 11 years, 6 months ago by
.
-
Posts
-
I found a missing builer in MyEclipse 2013.
So I want to know it is a problem or not.
Details:
When I created a ‘Web Project’ in MyEclipse Enterprise 10.7.1,
(Through this way : File -> New -> Project (New Project) -> Select ‘Web Project’ in Wizrard: -> Setting Web Project details)
I could see ‘WebClasspathBuilder’ is included. (in Project Properties -> ‘Builders’)However, when I made a project through the MAVEN in MyEclipse 2013,
the ‘WebClasspathBuilder’ was presenting ‘Missing builder’ on the same properties page with 10.7.1′
(I am attaching a screenshot of this.)In addition, when I made a web project, ‘WebClasspathBuilder’ was not even included in 2013.
Please let me know what is changed in the newest version.
francsue,
WebClasspath builder was removed, because we have moved to a “smarter” solution, that is, a container for JARs from lib folder – Web App Libraries (org.eclipse.jst.j2ee.internal.web.container) and a container for JARs referenced from EAR – EAR Libraries (org.eclipse.jst.j2ee.internal.module.container). The last one requires to add referenced JARs names to MANIFEST.MF, using MyEclipse -> Deployment Assembly property page of the project.
The migration process ensures that the project is correctly configured for ME 2013. So it is not a problem.
Let us know if you have any further questions.
@support-swapna wrote:
francsue,
WebClasspath builder was removed, because we have moved to a “smarter” solution, that is, a container for JARs from lib folder – Web App Libraries (org.eclipse.jst.j2ee.internal.web.container) and a container for JARs referenced from EAR – EAR Libraries (org.eclipse.jst.j2ee.internal.module.container). The last one requires to add referenced JARs names to MANIFEST.MF, using MyEclipse -> Deployment Assembly property page of the project.
The migration process ensures that the project is correctly configured for ME 2013. So it is not a problem.
Let us know if you have any further questions.
So according to you, current verson of MAVEN (or mvn goals)cannot configure a complete project automatically through ‘eclipse:myeclipse’.
It is because that there is one needed to be configured manually (something to be add, MyEclipse -> Deployment Assembly property)I want to know that there is a plan to provide a MAVEN goal configuring a project automatically for example, mvn eclipse:me2013.
francsue,
Maven projects are automatically configured as well. You just need to use Import -> Maven Project. Running any mvn goal will not help, as this is done by a non-maven code which synchronizes Maven metadata specified in pom.xml with eclipse project metadata.
You can refresh configuration of a project by right clicking project > Maven4MyEclipse -> Update project.
Let us know if you have any questions.
