|
| Re: Materializing a target platform [message #381338 is a reply to message #381336] |
Sat, 29 November 2008 21:35   |
|
Hi Abel,
Assembling platforms is not Buckminsters biggest strenght as things
stands right now. We will become very good at it once our P2 integration
is finished and we're working hard on making that happen.
My suggestion is that you use the static, pre-assembled TP's that are
available from the platform project as a base and import everything else
that you don't need the source for into your workspace using the
Buckminster "eclipse.import" reader type. That vouches for fairly static
set of immutable TP's that you don't need to download for each build.
One other advice is to maintain separate workspaces for your builds so
that you never expose one workspace to more then one TP.
Regards,
Thomas Hallgren
Abel Muiño wrote:
> Hello,
> I'm exploring the use of buckminster to assemble the target platform for
> Eclipse IAM [1], as a first step towards being able to make automated
> builds of the project after that.
>
> I could not find specific documentation about this (I have found some
> files to materialize an 3.3 RCP + EMF + Orbit [2] that seems like a good
> start).
> Is there any more information that I can use for materializing the
> target platform? Ideally we would like to have target platforms for
> different Eclipse versions (3.3, 3.4, 3.5), so if there is some
> difference that I need to pay attention to, advice is welcome (I'm
> wondering if P2 in >=3.4 would make materialization any different).
>
> [1] http://www.eclipse.org/iam
> [2]
> http://dev.eclipse.org/newslists/news.eclipse.technology.buc kminster/msg00516.html
>
>
> Thanks!
> Abel Muiño
>
|
|
|
| Re: Materializing a target platform [message #381437 is a reply to message #381338] |
Sat, 06 December 2008 22:24 |
Eclipse User |
|
|
|
Originally posted by: jconlon.apache.org
Hi Thomas,
I want to change my manual process of picking the correct Features and
installing them in my Eclipse IDE to a declarative (Buckminster)
approach so I can easily offer new dev collaborators a common way to
easily instantiate both workspace and target platform so they can
quickly be
productive.
Some Noob Questions follow your answers to Abel...
Thomas Hallgren wrote:
> Hi Abel,
> Assembling platforms is not Buckminsters biggest strenght as things
> stands right now. We will become very good at it once our P2 integration
> is finished and we're working hard on making that happen.
What is the difference between materializing a targetPlatform and
assembling one?
Abel included a link to a project file that you created for Wayne Beaton
last year that demonstrated creating a targetPlatform with Buckminster.
The zip as well as the link 'Realize an RCP target with Buckminster'
suggests to me that we can do this. How have things changed since then
regarding building targetPlatforms?
Is there documentation/usecase/or typical example on the targetPlatform
materializer?
>
> My suggestion is that you use the static, pre-assembled TP's that are
> available from the platform project as a base and import everything else
Where can I find these pre-assembled TPs?
> that you don't need the source for into your workspace using the
> Buckminster "eclipse.import" reader type. That vouches for fairly static
> set of immutable TP's that you don't need to download for each build.
> One other advice is to maintain separate workspaces for your builds so
> that you never expose one workspace to more then one TP.
>
> Regards,
> Thomas Hallgren
>
thanks,
John
>
> Abel Muiño wrote:
>> Hello,
>> I'm exploring the use of buckminster to assemble the target platform
>> for Eclipse IAM [1], as a first step towards being able to make
>> automated builds of the project after that.
>>
>> I could not find specific documentation about this (I have found some
>> files to materialize an 3.3 RCP + EMF + Orbit [2] that seems like a
>> good start).
>> Is there any more information that I can use for materializing the
>> target platform? Ideally we would like to have target platforms for
>> different Eclipse versions (3.3, 3.4, 3.5), so if there is some
>> difference that I need to pay attention to, advice is welcome (I'm
>> wondering if P2 in >=3.4 would make materialization any different).
>>
>> [1] http://www.eclipse.org/iam
>> [2]
>> http://dev.eclipse.org/newslists/news.eclipse.technology.buc kminster/msg00516.html
>>
>>
>> Thanks!
>> Abel Muiño
>>
|
|
|
| Re: Materializing a target platform [message #381442 is a reply to message #381437] |
Sun, 07 December 2008 11:59 |
|
John E. Conlon wrote:
> Hi Thomas,
>
> I want to change my manual process of picking the correct Features and
> installing them in my Eclipse IDE to a declarative (Buckminster)
> approach so I can easily offer new dev collaborators a common way to
> easily instantiate both workspace and target platform so they can
> quickly be
> productive.
>
> Some Noob Questions follow your answers to Abel...
>
>
> Thomas Hallgren wrote:
>> Hi Abel,
>> Assembling platforms is not Buckminsters biggest strenght as things
>> stands right now. We will become very good at it once our P2
>> integration is finished and we're working hard on making that happen.
> What is the difference between materializing a targetPlatform and
> assembling one?
>
What I have in mind when I wrote "assembling" is in fact materializing
into a target platform, so there's no real difference. We're using the
old update manager (the one present in Europa) which works for most
cases but in order for it to be really good, we must shift to using the
new P2 based update manager. That work is in progress.
Buckminster has no problems assembling a target platform like this but
it has problems tracking changes in the target platform that occurs over
time.
>
> Abel included a link to a project file that you created for Wayne Beaton
> last year that demonstrated creating a targetPlatform with Buckminster.
> The zip as well as the link 'Realize an RCP target with Buckminster'
> suggests to me that we can do this. How have things changed since then
> regarding building targetPlatforms?
>
No. Nothing has changed.
> Is there documentation/usecase/or typical example on the targetPlatform
> materializer?
>
I think the typical use-case is that you'd download a classic IDE and
use it as the TP for your resolutions and builds. Perhaps you have one
Europa (i.e. 3.3 based) IDE and one for Ganymede (3.4 based). If you're
doing bleeding edge development, perhaps it's of interest to use a 3.5
milestone release.
>>
>> My suggestion is that you use the static, pre-assembled TP's that are
>> available from the platform project as a base and import everything else
> Where can I find these pre-assembled TPs?
>
I'm referring to all installable packages that you can find on
http://download.eclipse.org. You would typically download and install
the relevant one(s) without using Buckminster (as you would with the
relevant JVM's for instance) and then appoint one of them prior to
resolution and build, using the targetPlatformPath preference.
Regards,
Thomas Hallgren
|
|
|
Powered by
FUDForum. Page generated in 0.03326 seconds
] 
Search
Help
Register
Login
Home
