Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Default Platform created by buckminster
Default Platform created by buckminster [message #527955] Sat, 17 April 2010 06:53 Go to next message
Matthias Kappeller is currently offline Matthias Kappeller
Messages: 54
Registered: July 2009
Member
Hello,

I've wondered about the target platform configuration created by
buckminster if no platform (or at least only the runtime platform) is
available.
There is not only a new directory (.buckminster/tp) added but also the
running eclipse platform.

While looking at the Buckminster 3.6 code I've found the following lines.

org.eclipse.buckminster.pde.internal.PDETargetPlatform

getDefaultPlatform()
....
if (dflt == null) {
...
dflt = ((TargetPlatformService)
service).newDefaultTargetDefinition();
IBundleContainer runningInstance =
dflt.getBundleContainers()[0];
IBundleContainer directory =
service.newDirectoryContainer(tpFolder.getLocation().toOSStr ing());
dflt.setBundleContainers(new IBundleContainer[] {
directory, runningInstance });
dflt.setName(defaultTP);
service.saveTargetDefinition(dflt);
}
....

I wonder why? Why is also the 'runningInstance' added? Maybe someone can
give me an advise why this is required.

thx and greetings

Matthias
Re: Default Platform created by buckminster [message #527956 is a reply to message #527955] Sat, 17 April 2010 07:58 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3208
Registered: July 2009
Senior Member
Hi Matthias,
If you install an IDE and check out things into your workspace, they will be built against the IDE runtime itself.
That's the default behavior of Eclipse. Buckminsters default behavior is to mimic this as much as possible in order to
keep downloads to a minimum. The runtime is sufficient for a large number of builds. When it isn't, then Buckminsters
behavior is annotate the runtime with whatever extras that is needed (hence the copy). This behavior keeps the entry
level for new Buckminster users fairly low. They don't need to worry about the concept of a target platform until they
get a bit warmed up. I think that's the general idea with the IDE default behavior too.

More advanced users will most likely choose not to use the default behavior but instead define a specific target
platform. That's also what we recommend as soon as your build process reaches beyond the very basic things.

HTH,
Thomas Hallgren



On 04/17/2010 12:53 PM, Matthias Kappeller wrote:
> Hello,
>
> I've wondered about the target platform configuration created by
> buckminster if no platform (or at least only the runtime platform) is
> available.
> There is not only a new directory (.buckminster/tp) added but also the
> running eclipse platform.
>
> While looking at the Buckminster 3.6 code I've found the following lines.
>
> org.eclipse.buckminster.pde.internal.PDETargetPlatform
>
> getDefaultPlatform()
> ....
> if (dflt == null) {
> ...
> dflt = ((TargetPlatformService) service).newDefaultTargetDefinition();
> IBundleContainer runningInstance = dflt.getBundleContainers()[0];
> IBundleContainer directory =
> service.newDirectoryContainer(tpFolder.getLocation().toOSStr ing());
> dflt.setBundleContainers(new IBundleContainer[] { directory,
> runningInstance });
> dflt.setName(defaultTP);
> service.saveTargetDefinition(dflt);
> }
> ....
>
> I wonder why? Why is also the 'runningInstance' added? Maybe someone can
> give me an advise why this is required.
>
> thx and greetings
>
> Matthias
Re: Default Platform created by buckminster [message #527968 is a reply to message #527956] Sat, 17 April 2010 10:44 Go to previous messageGo to next message
Matthias Kappeller is currently offline Matthias Kappeller
Messages: 54
Registered: July 2009
Member
Thank you Thomas for clarification.

greetings Matthias

On 04/17/2010 01:58 PM, Thomas Hallgren wrote:
> Hi Matthias,
> If you install an IDE and check out things into your workspace, they
> will be built against the IDE runtime itself. That's the default
> behavior of Eclipse. Buckminsters default behavior is to mimic this as
> much as possible in order to keep downloads to a minimum. The runtime is
> sufficient for a large number of builds. When it isn't, then
> Buckminsters behavior is annotate the runtime with whatever extras that
> is needed (hence the copy). This behavior keeps the entry level for new
> Buckminster users fairly low. They don't need to worry about the concept
> of a target platform until they get a bit warmed up. I think that's the
> general idea with the IDE default behavior too.
>
> More advanced users will most likely choose not to use the default
> behavior but instead define a specific target platform. That's also what
> we recommend as soon as your build process reaches beyond the very basic
> things.
>
> HTH,
> Thomas Hallgren
>
>
>
> On 04/17/2010 12:53 PM, Matthias Kappeller wrote:
>> Hello,
>>
>> I've wondered about the target platform configuration created by
>> buckminster if no platform (or at least only the runtime platform) is
>> available.
>> There is not only a new directory (.buckminster/tp) added but also the
>> running eclipse platform.
>>
>> While looking at the Buckminster 3.6 code I've found the following lines.
>>
>> org.eclipse.buckminster.pde.internal.PDETargetPlatform
>>
>> getDefaultPlatform()
>> ....
>> if (dflt == null) {
>> ...
>> dflt = ((TargetPlatformService) service).newDefaultTargetDefinition();
>> IBundleContainer runningInstance = dflt.getBundleContainers()[0];
>> IBundleContainer directory =
>> service.newDirectoryContainer(tpFolder.getLocation().toOSStr ing());
>> dflt.setBundleContainers(new IBundleContainer[] { directory,
>> runningInstance });
>> dflt.setName(defaultTP);
>> service.saveTargetDefinition(dflt);
>> }
>> ....
>>
>> I wonder why? Why is also the 'runningInstance' added? Maybe someone can
>> give me an advise why this is required.
>>
>> thx and greetings
>>
>> Matthias
>
Re: Default Platform created by buckminster [message #527974 is a reply to message #527956] Sat, 17 April 2010 13:09 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2492
Registered: July 2009
Senior Member
Cojld you please log a documentation issue for "working with target
platform" (with the info you posted) - this is currently not explained
very well in the documentation (if I remember correctly). Even if the
details are there, the higher level text just touches on the topic.

- henrik
Thomas Hallgren <thomas@tada.se> wrote:
> Hi Matthias,
> If you install an IDE and check out things into your workspace, they
> will be built against the IDE runtime itself. That's the default
> behavior of Eclipse. Buckminsters default behavior is to mimic this as
> much as possible in order to keep downloads to a minimum. The runtime
> is sufficient for a large number of builds. When it isn't, then
> Buckminsters behavior is annotate the runtime with whatever extras
> that is needed (hence the copy). This behavior keeps the entry level
> for new Buckminster users fairly low. They don't need to worry about
> the concept of a target platform until they get a bit warmed up. I
> think that's the general idea with the IDE default behavior too.
>
> More advanced users will most likely choose not to use the default
> behavior but instead define a specific target platform. That's also
> what we recommend as soon as your build process reaches beyond the
> very basic things.
>
> HTH,
> Thomas Hallgren
>
>
>
> On 04/17/2010 12:53 PM, Matthias Kappeller wrote:
> > Hello,
> >
> > I've wondered about the target platform configuration created by
> > buckminster if no platform (or at least only the runtime platform)
> > is
> > available.
> > There is not only a new directory (.buckminster/tp) added but also
> > the
> > running eclipse platform.
> >
> > While looking at the Buckminster 3.6 code I've found the following
> > lines.
> >
> > org.eclipse.buckminster.pde.internal.PDETargetPlatform
> >
> > getDefaultPlatform()
> > ....
> > if (dflt == null) {
> > ...
> > dflt = ((TargetPlatformService)
> > service).newDefaultTargetDefinition();
> > IBundleContainer runningInstance = dflt.getBundleContainers()[0];
> > IBundleContainer directory =
> > service.newDirectoryContainer(tpFolder.getLocation().toOSStr ing());
> > dflt.setBundleContainers(new IBundleContainer[] { directory,
> > runningInstance });
> > dflt.setName(defaultTP);
> > service.saveTargetDefinition(dflt);
> > }
> > ....
> >
> > I wonder why? Why is also the 'runningInstance' added? Maybe someone
> > can
> > give me an advise why this is required.
> >
> > thx and greetings
> >
> > Matthias
>
>


--
- henrik
Re: Default Platform created by buckminster [message #527996 is a reply to message #527974] Sun, 18 April 2010 06:22 Go to previous message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3208
Registered: July 2009
Senior Member
On 04/17/2010 07:09 PM, Henrik Lindberg wrote:
> Cojld you please log a documentation issue for "working with target
> platform" (with the info you posted) - this is currently not explained
> very well in the documentation (if I remember correctly). Even if the
> details are there, the higher level text just touches on the topic.
>

https://bugs.eclipse.org/bugs/show_bug.cgi?id=309586

- thomas
Previous Topic:Call jdt.ant from buckminster.prebind?
Next Topic:Unable to update a feature
Goto Forum:
  


Current Time: Sat Apr 19 06:04:52 EDT 2014

Powered by FUDForum. Page generated in 0.02449 seconds