- This topic has 3 replies, 2 voices, and was last updated 18 years, 8 months ago by
.
-
Posts
-
I’m running the trial version of MyEclipse Enterprice Workbench Version: 5.1.0 GA Build id: 20061111-5.1.0-GA with Eclipse 3.2.1
The follwing steps were taken during the installation:
1. Install Eclipse
2. Update Eclipse
3. Install MyEclipse
4. Update MyEclipse
5. Install Callisto (As expected: No option to install JST/WST
according to issue http://www.myeclipseide.com/modules.php?op=modload&name=PNphpBB2&file=viewtopic&t=15065#68791)
When applying this MyEclipse application on a workspace containing JST/WST projects I got the problems:
“Target runtime Apache Tomcat v5.5 is not defined. <my JST/WST Project> Unknown 1163753167120 269”
for each JST/WST project (“<my JST/WST Project>” is a placeholder for any of the JST/WST projects)/Harald
Harald,
The “Target runtime” nomenclature is from WTP, not MyEclipse. We have a different mode of deployment and server management. So if you are trying to mix WTP and MyEclipse, it will not likely work well.I can’t tell from your post if this is a mistake, or if you already know this and just prefer to use the products in this way… it’s just a tricky situation. I would encourage you to stick to using the MyEclipse manner of configuring connectors and deploying your projects to those app servers using our deployment tools and connectors.
Hi again,
actually I’m having a bunch of JST/WST projects that I would like be able to transfer (there and back) as effortless as possible between non-MyEclipse-enabled and MyEclipse-enabled environments.
So if we could find a convenient procedure for this issue I would be happy./Harald
Harald,
I think for the most part the projects should be fine… in WTP they will be treated as Dyanmic Web Projects, and in MyEclipse, you can add Web Capabilities to them s othey will be treated like Web Projects. As long as you are using clean installs of both in separate Eclipse instances, they should simply ignore the invalid Nature references.NOTE: Moving forward we will be building ontop of WTP’s project structure and so on, we have not done this yet because the functionality we require hasn’t been there yet and the work flow is constantly getting adjusted and refined (for the better). So we are being cautious before moving over. Hopefully in the 6.0 release we could look at having completely compatible project layouts.
