For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 3 replies, 2 voices, and was last updated 21 years, 12 months ago by
.
-
Posts
-
I just started using the I20040226 release of Eclipse instead of the 3.0M7 release of Eclipse. I am hoping that you are designing the 3.7 release of ME to work with post M7 integration builds like the 3.7RC2 release did with integration builds post M6.
Andy
p.s. I am finding that this integration build works much nicer with 3rd party plugins than the M7 release does.
Andy,
We can’t intentionally design MyEclipse to work with releases that don’t exist at the time of our testing, but if Eclipse doesn’t introduce major breakage between M-release and integration releases, then a side effect will be that it works.As an aside, I imagine it will work fine with the integration builds as M7, M8, M9 are marked as stablization releases in the project roadmap, so I imagine no major breakage will be introduced.
@support-rkalla wrote:
Andy,
We can’t intentionally design MyEclipse to work with releases that don’t exist at the time of our testing, but if Eclipse doesn’t introduce major breakage between M-release and integration releases, then a side effect will be that it works.🙂 I disagree. As long as the ME team continues to design ME so that it uses the links folder, I will be able to use the latest M-releases without any problems. Thus, you can intentionally design it to work for future M-releases by maintaining your existing design. That is all I am asking for.
Andy,
We are on talking about two separate things. If all you are worried about is the usage of ‘links’ you will be fine to *try* ME with future integration builds. If there are any major API changes introduced by the Eclipse team that effects MyEclipse, wether its linked or not will cause the ME plugins to break… this is what we cannot future-proof our product against.
