[mtrtm]

Hi,

I have searched and can’t seem to find any way to change the Deploy Location for a project. I currently have MyEclipse 5.1.

If I Manage Deployments for a certain server and click Add, I can select a project but the Deploy Location is uneditable. Is there any way to change this?

Thanks,

Mario

[Riyad Kalla]

Mario,
No worries, instead of selecting your app server, select “Custom Location” as the deployment and you can specify whatever directory you would like.

[mtrtm]

Riyad,

Thanks for the suggestion. My problem is that I need to deploy to a directory that contains another web project – my web project is an addition to the existing one.

If I use the “Custom Location” option, it overwrites the project that is currently there. What I need it to do is just add all of its files to the existing deployment.

Is there any way to use MyEclipse when having to do specific deployment like this?

Thanks in advance,

Mario

Mario

[Riyad Kalla]

Mario,
When you get a conflict with an existing deployment location, MyEclipse will prompt you if you want to Replace/Backup/Overlay the new deployment with the old one. I suppose you want to choose Overlay (or Overwrite… I forget the exact verbage).

[mtrtm]

Riyad,

Overwrite does what you are talking about – thanks for the help on that one.

I have a new problem now – Every time I try to deploy to a “Custom Location – Suffixed” with a Deploy Type of Archived and choose to “Overwrite remote resources” I get an error popup. The error pop up only says Error, has a red circle with a white X in it and has an OK button. Could you tell me what this error means? Maybe you could search where you are throwing an error with no message?

I also can’t seem to get MyEclipse to deploy any class files at all after this error is encountered. Is this related or a different issue?

Any help would be appreciated. Thanks,

[Riyad Kalla]

That error is usually the side effect of some weird state either of the project, or of the deployment location and almost always throws an exception to the log file, can you check for it?

(<workspace dir>\.metadata\.log) is the location of the log file, look near the bottom.

[mtrtm]

Riyad,

Thanks for the quick reply. This has happened both with a copied project and one I tried building (kind of) from scratch.

To make sure I was capturing the correct error in the .log file, I opened it up and put a marker in at the very bottom of the file, then reproduced the error. I then opened the log file up again and nothing was written to the file.

Any more ideas?

[Riyad Kalla]

Try and shut down your app server, remove all the deployments, then right-click on each project at the root and do a Refresh. Then clean all the projects and re-create the deployments.

Did that work?

[mtrtm]

Riyad,

Sorry, that didn’t fix it. I looked in the log and just seem to see a lot of MyEclipse validation errors (javascript exceptions mostly)

[Riyad Kalla]

If you create a new workspace temporarily, say File > switch workspace > C:\tempworkspace. Then import your two projects into it, and configure Tomcat… do they deploy without a hitch?

[mtrtm]

Still the same error (with no error message)

[Author]

Posts