Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-ui-dev] Understanding the value of a lower BREE if plug-in depends on a plug-in with higher BREE

See also https://wiki.eclipse.org/Execution_Environments#I_have_prerequisites_that_require_version_X_to_run.2C_so_shouldn.27t_I_require_version_X_too.3F

"Value" is maybe the wrong word but "money" is definitely a factor as Markus pointed out: there are tons of bundles with BREE lower than 1.5 or even 1.3 and they work just fine. We all know that changing the BREE requires more work than just changing the manifest (blame it on our tools). The compiler settings need to be adjusted correctly and often one also wants (or has) to get rid of the newly introduces warnings or errors.

Dani



From:        Markus Keller/Zurich/IBM@IBMCH
To:        "Eclipse Platform UI component developers list." <platform-ui-dev@xxxxxxxxxxx>
Date:        06.08.2014 18:24
Subject:        Re: [platform-ui-dev] Understanding the value of a lower BREE if plug-in depends on a plug-in with higher BREE
Sent by:        platform-ui-dev-bounces@xxxxxxxxxxx




If "A" is in maintenance mode, one advantage is that you don't have to waste time updating the BREE, adjusting associated settings, adding @Override, etc.

Another reason can be that "A" still works fine with a previous release of "B" that only required 1.4. Why create a new version of "A" without need? It works perfectly fine. But if "B" starts to expose 1.6 types in old APIs, then "A" suddenly doesn't compile any more against the latest "B".


Maintenance burden is not a big deal if you just see your closed world with a few projects in your workspace. But it's a big deal if you work on a successful platform project that has thousands of unknown projects that depend on "B". Causing ripples is not necessarily a good thing. Even if the direct cost of the ripples is not on your end.


Related bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=234331

Markus




From:        
Lars Vogel <lars.vogel@xxxxxxxxx>
To:        
"Eclipse Platform UI component developers list." <platform-ui-dev@xxxxxxxxxxx>
Date:        
2014-08-06 18:00
Subject:        
[platform-ui-dev] Understanding the value of a lower BREE if plug-in depends on a plug-in with higher BREE
Sent by:        
platform-ui-dev-bounces@xxxxxxxxxxx




What is the value to keep a bundle A on a BREE level lower than a required bundle B?  

For example assume I have two bundles, A and B. A depends on B.  A has a BREE of Java 1.4 and B a BREEE of Java 1.6.

IMHO A can never be used on a JRE 1.4. As B requires 1.6, it will not resolve on on a 1.4 JRE and A cannot resolve, as B cannot be resolved.

I can only see two "values" for A (one of them is negativ):

1.) Keeping A on a BREE 1.4 prevents source code in it from using Java 1.5 or Java 1.6 language and library constructs. In other words "A" has less options. This is a negative value IMHO for A.
2.) Generics warning are not visible in A (could also be solved on a BREE 1.6 and corresponding project settings)

Is there more value for keeping A on a lower BREE than B? Or is there even a scenario in which A could actually work on a 1.4 JRE with a version B requiring 1.6?




_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

https://dev.eclipse.org/mailman/listinfo/platform-ui-dev _______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-ui-dev

Back to the top