[csell]

Hello,

am I right in assuming that myeclipse imposes a fixed project layout and does not allow placing J2EE artefacts according to individual preferences or company standards? I would like to have one project, with different J2ee module types below it, but there seems to be no way..

Also, I would really like to avoid all the myeclipse artefact files to be spat all over the place (mymetadata, mystrutsdata, myumldata). I guess I am asking too much, right?

can anybody say whether plain WTP is better in this regard?

christian

[Riyad Kalla]

Christian,
MyEclipse 5.0 will relax the project layout quite a bit and you should be able to assign locations to artifacts but right now there is certain locations that MyEclipse will look for files (web.xml and so forth).

Also you can’t avoid the dot-files in your project, but this is the case with any eclipse-based product, they have to store their settings somewhere and they all use dot-files.

As far as WTP being better or not, MyEclipse 5.0 will be built ontop of WTP 1.5 so it will become a moot point as MyEclipse will continue to build value-add designers and tools ontop of the base WTP distrobution.

Now if the question is “Is WTP good enough for me”, I’m not sure. Have you tried using it in a separate install of Eclipse and seeing if it is all you need?

[csell]

Riyad,

can you say what version of WTP MyEclipse is currently based on? And does plain WTP impose the same kinds of restrictions with regard to project layout as ME does? I already have an ME license, so downgrading is not my goal

thanks,
Christian

[Riyad Kalla]

Christian,
We are currently based on a *heavily* modified version of the original WTP drop from quite a while back but in 1.5 the WTP team has really brought things together into a more functionality cohesive platform to build on and we already have Milestone 1 of MYEclipse 5.0 running ontop of it. It should be out shortly (and we appreciate your support and purchase of MyEclipse subscription)

Also I’m not terribly farmiliar with what WTP has normalized on for projects in 1.5, in 1.0 they had a really convoluded implementation of “flexi project support” that was a bit confusing but I heard in 1.5 they simplified it and I’m sure moving forward it will improve since all the major IDEs will be building ontop of it and getting enhancements pushed down into it so they can all be compatible.

[csell]

unfortunately, after looking into this a bit further, it seems there is no way to migrate our currently JBuilder-based projects and build system to MyEclipse (without completely disrupting the project, that is)

too bad
Christian

[Riyad Kalla]

Christian,
We are pushing to get the flexiproject support into MyEclipse 5.x, when that happens and then you get logical-to-physical mappings and assuming you had the time and willpower we’d appreciate it if you could try and port your project over again and just give us some feedback on what worked and what didn’t work.

When flexiproject support is added it should be a big line item in the release notes, we want to get it into 5.0 but it hasn’t been confirmed that it’s ready for prime time yet so it may slip to a later 5.x release.

[Author]

Posts