- This topic has 5 replies, 3 voices, and was last updated 18 years ago by
.
-
Posts
-
Hi all,
I’ll of course say “sorry if this has already been mentioned” …
We’re having a few annoyances with the fact that a few MyEclipse specific properties aren’t checked in to our repository along with the rest of the project properties:
This means that each time we check out the project from scratch and deploy, we always go through the “This doesn’t frickin work” phase, followed by the “Hey Mike! Why can’t I deploy” phase, followed by “Shit if I know!” followed by “Wait. That property isn’t checked in. Go to the MyEclipse properties for the project and change …”
Case in hand:
My Eclipse | EJB dependency policy
My Eclipse | Web | DeploymentIt would be REALLY nice to have this checked in.
Thanks.
You are absolutely right, We started a dialog about this a while ago (internally) and I forgot what the resolution was. I’ll bring this up again to make sure this is still ontrack for a future release.
Ahh ok update on this, we never changed it or backward compatibility reasons. We *have* plans to fix this moving forward, possibly as early as our 6.0 release if all goes well, but there is a huge responsibility of backward compatibility that we have to honor first and foremost.
Can’t this easily be solved by having one master setting for legacy / extended storing of settings in the .myeclipse properties file (or any other file in the workspace which holds myeclipse settings)?
This single master setting would default to “legacy”, so no one would be caught by this by suprize. When set to “extended store”, more myeclipse properties will be stored in project file. It would be nice if the settings dialog would somehow show that a specific property is under version control or strictly personal.
One of the settings I would like to have under version control is whether libraries not in WEB-INF/lib are deployed. I just added a directory in my project (under version control), put a lib in it (under version control) added this to the project’s classpath (under version control) and excluded this lib from being deployed (not under version control).
So, when I check in these changes, I have to communicate to everyone on the team that they change this single setting. Of course, new people will check out the project eventually and don’t know about this setting.
