- This topic has 1 reply, 2 voices, and was last updated 18 years, 6 months ago by
.
-
Posts
-
I know MyEclipse 5 will build on top of the functionality provided by WTP. The question on our minds is in what places is MyEclipse not using the functionality of WTP. Certainly in some cases it makes sense to disable WTP features and enable MyEclipse provided features that are superior. Perhaps even some functionality in ME releases previous to 5 have been disabled/deprecated in favor of WTP mechanisms. I’ve read in the ME 5 RC1 release notes that the ME J2EE project structure is not compatible with the WTP project structure. Perhaps there are ways I have been doing things in the past with ME that WTP provides a better/easier solution. Questions like: Are ME server connectors the same as WTP connectors? Are the debuggers consolidated? When should we use ME project structure vs WTP project structure? I don’t mind having multiple ways to do things, but I would like to know which way I am doing it, and the reasonings behind having multiple ways to do things. So would it be possible to get a feature list comparison where there are differences in WTP/MyEclipse would be great.
ThanksThe short answer is “don’t worry about it”. It sounds like the underlying concern here is project layout and the best answer is to keep your projects in the exploded WAR format that MyEclipse has liked since day one. This format is going to be compatible with every IDE out there and is easy to import/export and reuse even from the command line.
The flexi project support we were gunning for in WTP was not implemented in a fashion we were hoping for, for the immediate future we will be keepnig our project structure and connectors. Moving forward as WTP matures we will replace portions of MyEclipse as it makes sense. The “makes sense” part is hard to predict, each major update to WTP we evaluate and see where the major features stand. If it’s going to be a nightmare to pull them in or create a complete PIA for our users to transition over all their projects, we will ignore it until a better solution presents itself.
Trust us, we don’t like writing code for the sake of code. If WTP is doing something better than us, we’ll take it in a heart beat, that frees us up to do designers or other cool tools.
