This is what I see in the log file, an error that MANIFEST.MF cannot be found for the various WARS in the EAR: There is a yellow triangle showing in the deployment window, and the message is that the project has changed and needs to be refreshed.
When I try to deploy, either exploded or packaged, the deployment fails almost immediately and the only thing making it into the archive/folder is the META-INF folder and MANIFEST.MF inside the folder. home/tom.mccobb/MyEclipse/MyEclipse 10/configuration home/tom.mccobb/MyEclipse/MyEclipse 10/myeclipse Workspace=file:/home/tom.mccobb/Workspaces/ ME performs so much better on linux that it is usually worth the added aggravation.
#Jrun jar launcher update
(Fedora 20 update from F18 creamed ME10, also). Unfortunately 2014 has not behaved well on Fedora 19 or 20 (a redhat problem, not ME) so I am still on ME 10.7. It is useful to replicate with as simple a set up as possible. I’ve tried to replicate from what I understand but the deployment works as expected.Īgain, specific steps to replicate would help, as would trying to replicate it yourself using two simple Web projects with maven support. So are you saying that the deployment of Web1 (with the Web2 dependency) works fine when you don’t have the overlay configuration that you listed above but fails when you add that configuration? A clear description of the issue is always useful. This should happen even without a specific overlay configuration. MyEclipse will merge the two projects, in the same way as maven does, when deploying using MyEclipse. By default, maven for MyEclipse will satisfy dependencies from the workspace, if possible. You have added a maven dependency to Web1, which is the group, artifact and version specified in the Web2 project. As I understand it, you have two web projects, let’s say Web1 and Web2, which are both Maven projects. I’m sorry but I am still not sure exactly what and how you are trying to do your deployment.
0 kommentar(er)
