[stchome]

Because of changes to the way MyEclipse recognizes certain things in a project (previously I didn’t have to have web capabilities to get tag code assist in MyEclipse JSP editor), I had to add web capabilities to my project (was previously a Java Project in Eclipse). I quickly discovered that MyEclipse not only added various folders to my project, it changed (without asking) my output directories for compiled code (we do not want our code compiled into the WEB-INF\classes directory).

If the user adds web capabilities and MyEclipse needs to add folders that do not currently exist, they user should be prompted with whether or not they want to add the folder/file/whatever. If the user declines to add a certain item, they should also be warned if this will cause certain functions of MyEclipse to break. It should not change any current configurations without a warning.

For instance, I do not want / need a META-INF folder and manifest in my project. We also use a shared library project, rather than keeping the libs redundantly in each project, so I do not need / want a lib folder in my WEB-INF. If by not having those folders, MyEclipse can’t deploy my project, that’s ok as its not a feature I need or use. If by not having those folders, I can’t get code assist in my JSP editor, I want to know that (not saying that happens, its just a fictional example).

[Riyad Kalla]

Charles,

(previously I didn’t have to have web capabilities to get tag code assist in MyEclipse JSP editor)

You still don’t *have* to, but then MyEclipse requires that you have your app in a VERY specific format so it can find everything… we suggest adding web caps though, makes everyone’s life easier.

I quickly discovered that MyEclipse not only added various folders to my project

The .myeclipse dir is a scratch dir it needs for compilation, the WebRoot is the dir it creates based on the settings you give it, same goes for the /src dir and it implicitcly adds the WEB-INF and WEB-INF/classes dir off of your WebRoot dir because it needs them.

they user should be prompted with whether or not they want to add the folder/file/whatever.

I agree, changing a project behind the scenes is annoying. I think the reason we don’t prompt is that we NEED those dirs to work correctly… so if the user Says No… then its the same as cancelling adding WEb Caps; but ultimately I agree.

Overall I see your points (good ones) and we are currently in discussions about this model of “adding capabilities” for everything. Thank you for your additional feedback in this area, it will help us decide where to go in the future.

[Author]

Posts