| Home » Eclipse Projects » Eclipse Platform » Recommendations on Bundle-RequiredExecutionEnvironment manifest header?
 Goto Forum:| 
| Recommendations on Bundle-RequiredExecutionEnvironment manifest header? [message #327251] | Mon, 14 April 2008 11:51  |  | 
| Eclipse User  |  |  |  |  | Hi Everyone, 
 What is the recommendation in general for the
 "Bundle-RequiredExecutionEnvironment" manifest header?  In Eclipse 3.4, I
 get warnings from the PDE on all of my legacy plug-ins when it is not
 set.  However, it always recommends a value from my target environment
 which will undoubtedly match my installed product's configuration.  So, I
 guess what I am asking is, should I:
 
 1) Set Bundle-RequiredExecutionEnvironment for *all* of my plug-ins to a
 minimum required value such as "J2SE-1.5" (which is what we install with
 our product).
 2) Individually keep track of the minimum
 Bundle-RequiredExecutionEnvironment value for each plug-in, and track
 minimum required values for each plug-in (prone to error and a bit of a
 pain).
 3) Just avoid setting Bundle-RequiredExecutionEnvironment entirely, and
 live with the warning.
 
 I also noticed that when I specify a minimum value such as "J2SE-1.5", I
 still get a warning about the JRE container on my classpath (currently JRE
 1.6) not being a perfect match, so either way I get a warning that I must
 ignore.  I just am unsure of which warning is more "acceptable".  Is there
 an Eclipse standard related to this?
 
 Thanks,
 Mark.
 |  |  |  |  |  |  |  |  | 
| Re: Recommendations on Bundle-RequiredExecutionEnvironment manifest header? [message #327327 is a reply to message #327256] | Tue, 15 April 2008 11:06   |  | 
| Eclipse User  |  |  |  |  | On Mon, 14 Apr 2008 14:21:43 -0400, Chris Aniszczyk <zx@us.ibm.com> wrote: 
 > Mark Melvin wrote:
 >> 1) Set Bundle-RequiredExecutionEnvironment for *all* of my plug-ins to
 >> a minimum required value such as "J2SE-1.5" (which is what we install
 >> with our product).
 >
 > This may be the easiest way to start off with... and probably makes
 > sense for your product if you don't care and state that the minimum JVM
 > should be 1.5
 >
 >> 2) Individually keep track of the minimum
 >> Bundle-RequiredExecutionEnvironment value for each plug-in, and track
 >> minimum required values for each plug-in (prone to error and a bit of a
 >> pain).
 >
 > This is the approach that the Eclipse SDK takes as it's beneficial to
 > our consumers who use Eclipse plug-ins in various runtime environments.
 > In your case, it may be too much overhead if your product is only
 > "tooling based" and not really meant to run on other types of
 > environments.
 >
 
 I guess there is one more question I have on this.  You can currently
 specify a list of execution environments.  Is this recommended at all?
 For instance, if a plug-in is compatible with Java 1.4, should I add
 J2SE-1.4, J2SE-1.5, and JavaSE-1.6?  If not, what is the use case for
 allowing multiple values here?
 
 Thanks,
 Mark.
 |  |  |  |  | 
| Re: Recommendations on Bundle-RequiredExecutionEnvironment manifest header? [message #327336 is a reply to message #327327] | Tue, 15 April 2008 13:45   |  | 
| Eclipse User  |  |  |  |  | Originally posted by: zx.us.ibm.com 
 > I guess there is one more question I have on this.  You can currently
 > specify a list of execution environments.  Is this recommended at all?
 > For instance, if a plug-in is compatible with Java 1.4, should I add
 > J2SE-1.4, J2SE-1.5, and JavaSE-1.6?  If not, what is the use case for
 > allowing multiple values here?
 
 J2SE-1.4 implies it will work on >=J2SE-1.4
 
 The use case of multiple values is that EE's like Foundation aren't
 directly related to J2SE... for example, Foundation 1.1 is a subset of
 J2SE 1.3 so you may have a bundle that could run on both of those
 environments so you would list them both.
 
 If you look at the OSGi spec, you see this in more detail in the EE
 section. The Eclipse project makes heavy use of BREEs, I recommend
 checking this link out:
 
 http://www.eclipsecon.com/eclipse/development/eclipse_projec t_plan_3_4.html#Appendix1
 
 Hopefully that wasn't too confusing.
 
 Cheers,
 
 ~ Chris
 |  |  |  |  | 
| Re: Recommendations on Bundle-RequiredExecutionEnvironment manifest header? [message #327338 is a reply to message #327336] | Tue, 15 April 2008 15:05  |  | 
| Eclipse User  |  |  |  |  | On Tue, 15 Apr 2008 13:45:42 -0400, Chris Aniszczyk <zx@us.ibm.com> wrot= e:
 
 >> I guess there is one more question I have on this.  You can currently=
 =
 
 >> specify a list of execution environments.  Is this recommended at all=
 ?   =
 
 >> For instance, if a plug-in is compatible with Java 1.4, should I add =
 =
 
 >> J2SE-1.4, J2SE-1.5, and JavaSE-1.6?  If not, what is the use case for=
 =
 
 >> allowing multiple values here?
 >
 > J2SE-1.4 implies it will work on >=3DJ2SE-1.4
 >
 > The use case of multiple values is that EE's like Foundation aren't  =
 
 > directly related to J2SE... for example, Foundation 1.1 is a subset of=
 =
 
 > J2SE 1.3 so you may have a bundle that could run on both of those  =
 
 > environments so you would list them both.
 >
 > If you look at the OSGi spec, you see this in more detail in the EE  =
 
 > section. The Eclipse project makes heavy use of BREEs, I recommend  =
 
 > checking this link out:
 >
 >  http://www.eclipsecon.com/eclipse/development/eclipse_projec t_plan_3_4=
 ..html#Appendix1
 >
 > Hopefully that wasn't too confusing.
 >
 > Cheers,
 >
 > ~ Chris
 
 Thanks again.
 
 M.
 |  |  |  | 
 
 
 Current Time: Fri Oct 31 05:54:42 EDT 2025 
 Powered by FUDForum . Page generated in 0.03859 seconds |