- This topic has 27 replies, 5 voices, and was last updated 21 years ago by
.
-
Posts
-
Hi!
After Moving my project to Myeclipse, deploying exploded as well as packaged archives worked great. (By removing the exploded one and adding a packaged ond)
Yesterday evening it was not possible to add a packaged archive. -The “deploy location” was empty and grey. After that even switching back to an exploded archive was not possible anymore. “undefined exploded archive location” is the errormessage. In Preferences – Tomcat 4 everything is still the same.
I assume that it has to do with the following: I used “Team”->”Change ASCII/Binary Property” -> “automatic”, “include files that are already shared in the repository” -> “finish” to correct the CVS handling of my files. After that I deleted my project-folder within eclipse and checked it out as webapp-project again.
Here my System Data:
os: Windows 2000 , sp 4
Eclipse: Version: 2.1.1, Build id: 200306271545
Eclipse was freshly installed for MyEclipse!
NO other external plugins are installed
How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*? ONE
MyEclipse 2.5.1
JDK 1.4.0-b92
What JDK version are you using to launch your application server? JDK 1.4.0-b92
Application Server Tomcat 4Regards,
Mario
It may be that the Deployment Manager is out of sync with your environment. You can inspect the deployment properties by viewing the following file, see <your workspace>/.metadata/.plugins/com.genuitec.eclipse.ast.deploy.core/pref_store.ini.
To reset the Deployment Manager just delete this file.Let us know what you determine.
Michael
MyEclipse SupportYou are the fastest support in the web. I’ve seen that suggestion in another posting, but there is no file in my “<your workspace>/.metadata/.plugins/com.genuitec.eclipse.ast.deploy.core/” folder.
My 1st thought is that your CVS actions should have no effect on you project’s deployment qualities. I would like to look more closely at you Tomcat4 connector preferences.
1) Can you reinspect the MyEclipse Tomcat4 location preferences and verify that the connector’s filesystem locations are specified correctly? Also make sure the connector is enabled (I assume it is).
2) Can you also manually inspect your Tomcat4 installation and verify that it has a webapps directory <tomcat home>/webapps. The MyEclipse Tomcat connector requires this directory to exist. Also check the directory for remnant deployed applications that should not be there and delete as needed.
3) If you have another appserver installed can you try a test deployment of your application to it see if the problem is Tomcat4 specific or more general?
4) I reviewed your environment info (good job specifying it) and noticed your PDE plugin count is 1 (one). The real count should be approximately 7. A count of 1 indicates that your Eclipse install is the basic Eclipse platform w/o the developer tools. I will assume this is a miscount if you are able to compile and build java classes. Are you experiencing other problems with MyEclipse?
Michael
MyEclipse Support1. The preferences are correct.
2. the webapps-dir exists and even contains the exploded archive from former times.
3. I will install Tomcat 5 for testing on monday
4. I’m sorry. Seven PDE plugins.Do me a favor and try deleting the former exploded archive from the Tomcat webapps. After doing that shutdown and then restart Eclipse. Then test the deployment manager on your project. Pleaes let us know how what you determine.
Michael
MyEclipse SupportDeleting the former exploded archive from the Tomcat webapps did not help unfortunately.
Even installing Tomcat 5 did not help.
If I create a NEW Project, the deployment works fine for that, but not for my old project.
After deleting my (old) project and checking it out again as web-module, the deployment works again. BUT when ckecking out as web-module from CVS, a message appears, saying that the project would exist already. Then you can only agree to get your files out of the repository. After that, the files “.mymetadata” in the projectfolder and the “META-INF”-folder in the webroot do not exist anymore. Do I need those files? Do they influence the deployment? Thank you.After that, the files “.mymetadata” in the projectfolder and the “META-INF”-folder in the webroot do not exist anymore. Do I need those files? Do they influence the deployment?
Yes, when using CVS, .mymetadata should be checked in with the project, just as the .project and .classpath files are. The META-INF directory should also be added to CVS. However the .myeclipse folder is just for temporary build files so it does not need to be in CVS.
Without the project meta-information, the project can’t be deployed, which is exactly what you’re seeing. Once .mymetadata and META-INF are added to CVS from a deployable configuration, you should be fine.
–Scott
MyEclipse SupportThe deployment does not work again. Even not after installing the folder “META-INF” as well as the file “.mymetadata”. By comparing the file “.mymetadata” with a new project, the following difference came to my attention: The ID in the line “type=”WEB” id=”myeclipse.1064934323894″>” differs. As I copied the file “.mymetadata” from another project, I’m afraid that the ID has to be changed. Where can I get the right ID for my project?
Staudt,
I reviewed this thread and noticed that your running MyEclipse 2.5.1? If yes, please update to MyEclipse 2.6.2. There are known deployment problems with pre-2.6.2 versions.
Michael
MyEclipse SupportSeveral deployment problems were r
The id attribute is a generated as “myeclipse.” + System.currentTimeMillis().
I updated now to 2.6.2. Unfortunately the problems are still the same. If I choose a new deployment, choose my project, click on “packaged archive” and back on “Exploded Archive”, in the line below “New Deployment” a line appears, saying “undefined exploded archive location”.
Let’s try resetting your environment:
0) For an exploded webapp deployment ensure that your project root-context is a single segment URL, such as /mywebapp. If it is a multiple segment URL such as /myapp/mywebapp it will not deploy in exploded or packaged format and must be shortened to a single segment URL.
1) Manually remove any MyEclipse deployed webapps from the Tomcat webapps directory. Remove both *.war files and exploded war directories.
2) Next, verify that your Tomcat configuration is correct by starting and stopping Tomcat from with in MyEclipse (see the toolbar actions). During MyEclipse Tomcat startup observer the console output for unusual error/warning messages.
3) With MyEclipse shutdown, remove the pref_store.ini file identified in the 2nd post of this thread. If it does not exists then don’t worry about it.
4) Start MyEclipse and attempt to deploy the webapp in exploded format.
Michael
MyEclipse SupportWhat does a typical <your workspace>/.metadata/.plugins/com.genuitec.eclipse.ast.deploy.core/pref_store.ini look like?
I have the odd problem that the New Deployments dialog does not seem to respond to typing (that is, I can’t type anything into Deploy Locations). Hence I want to edit <your workspace>/.metadata/.plugins/com.genuitec.eclipse.ast.deploy.core/pref_store.ini directly. It doesn’t exist however, so I need a template.
User specified deployment locations are not available. All deployments are to the default locations of the respective servers. Hope this helps.
Michael
MyEclipse Support
