FWIW,

so far this issue was reported in two platform error reports by ~500 users each 
[1,2]. I added a comment to these problem reports which informs users that the 
early startup extensions they use, stopped working properly in Eclipse Mars and 
that they should inform their plugin providers about this to allow them taking 
care of this in their code.


At least there is an (indirect but focused) way informing 3rd party plugin 
providers about this breaking change before Eclipse Mars is released.


Marcel


[1] 
https://dev.eclipse.org/recommenders/committers/confess/#/problems/551194a2e4b0b71121dad676/details
[2] 
https://dev.eclipse.org/recommenders/committers/confess/#/problems/54c4f0a7bee810030da08462/details




> On 11 Apr 2015, at 18:30, Konstantin Komissarchik 
> <[email protected]> wrote:
> 
> I appreciate Lars’s response on the bug with a pointer to the change in 
> question along with the rationale.
>  
> I do want to state that communication regarding this was lacking. Evidence:
>  
> 1.       WTP 3.7 M6 (Mars) milestone build is affected by this issue. 
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=459620
> 2.       A number of third party plugins are similarly affected.
>  
> Plugin developers rely on Eclipse Platform maintaining rock-solid backwards 
> compatibility. As such, instances where compatibility will be broken, should 
> be announced at the highest volume possible and with much repetition. In this 
> case, the particular extension point usage pattern was apparently deprecated 
> in Eclipse 4.2 before being removed in 4.5. It would have been good to add a 
> deprecation warning to the error log starting in 4.2 in order to ensure that 
> the affected plugin maintainers notice that they need to take action while 
> there is still plenty of time to plan for this. The final removal should have 
> also been announced on cross-project.
>  
> Thanks,
>  
> - Konstantin
>  
> From: Konstantin Komissarchik [mailto:[email protected]] 
> Sent: Friday, April 10, 2015 2:58 PM
> To: 'Cross project issues'
> Subject: Bug 456909 - Implementing Early Startup IStartup causes 
> org.eclipse.core.runtime.CoreException
>  
> Could someone from the platform team comment on this issue?
>  
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=456909
>  
> Plugins that have an IStartup extension and worked fine on 4.4 are causing 
> exceptions to be logged when used on 4.5 milestones. This appears to be an 
> API behavior regression. The bug was filed in January and the platform team 
> has yet to comment on it…
>  
> - Konstantin
> _______________________________________________
> cross-project-issues-dev mailing list
> [email protected]
> To change your delivery options, retrieve your password, or unsubscribe from 
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-179-131-7721
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940

_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to