Home » Archived » EPP » Buckminster team willing to committ
|
Re: Buckminster team willing to committ [message #1773 is a reply to message #1745] |
Mon, 18 December 2006 22:21 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: jkrause.innoopract.com
Hendrik,
That is great. There has been significant interest from multiple parties
over the last couple of days, and the install topic is consistently one
of high interest.
Can you point us to the technology that Buckminster provides in this area.
Best Regards,
Jochen
Henrik Lindberg wrote:
> Hi, we have now synced up internally, and Cloudsmith / i.e. the Buckminster
> team is very interested in helping out and becoming comitters on this
> project.
> It will be me, and one of Thomas Hallgren, Filip Hrbek, or Karel Brezina.
>
> Looking forward to discussing this project and requirments further.
> Best Regards
> Henrik Lindberg
>
>
>
|
|
| |
Re: Buckminster team willing to committ [message #1806 is a reply to message #1796] |
Tue, 19 December 2006 13:15 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) ![Go to next message Go to next message](theme/Solstice/images/down.png) |
Eclipse User![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=) |
|
|
|
Originally posted by: jkrause.innoopract.com
If you are willing to take it on ...
The original intent of the packaging proposal was to provide new entry
level bundles for users at download.eclipse.org.
From my point of view installers could still fit into the scope of
packaging, but it could as well be addressed by platform.
What we will not tackle is the kind of dynamic provisioning that many
people have in mind, and installer would just deliver a fixed set of
functionality. This might be a minimal install to be extended by update
manager (or a better technology) or a predefined package.
Jochen
Pascal Rapicault wrote:
> Don't that fall under the provisioning aspect as well?
>
> "Jochen Krause" <jkrause@innoopract.com> wrote in message
> news:em74ab$o9k$1@utils.eclipse.org...
>> Hendrik,
>>
>> That is great. There has been significant interest from multiple parties
>> over the last couple of days, and the install topic is consistently one of
>> high interest.
>>
>> Can you point us to the technology that Buckminster provides in this area.
>>
>> Best Regards,
>>
>> Jochen
>>
>>
>>
>> Henrik Lindberg wrote:
>>> Hi, we have now synced up internally, and Cloudsmith / i.e. the
>>> Buckminster team is very interested in helping out and becoming comitters
>>> on this project.
>>> It will be me, and one of Thomas Hallgren, Filip Hrbek, or Karel Brezina.
>>>
>>> Looking forward to discussing this project and requirments further.
>>> Best Regards
>>> Henrik Lindberg
>>>
>>>
>
|
|
|
Re: Buckminster team willing to committ [message #1810 is a reply to message #1773] |
Tue, 19 December 2006 18:16 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Henrik Lindberg![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=glashammer%40hotmail.com) Messages: 112 Registered: July 2009 |
Senior Member |
|
|
Hi,
You can read more about Buckminster in general on the Eclipse wiki
http://wiki.eclipse.org/index.php/Buckminster_Project
The functionality that I guess is could be of special interest to this
project is the Buckminster installer; a headless packaging of
Eclipse/Buckminster that can run from a command line, or soon be invoked via
Java Web Start. This installer is about 2M in size and includes the Eclipse
update manager.
Buckminster installs things based on a Bill of Materials that Buckminster
can produce based on transitive dependencies (such as the OSGi declared
dependencies found in Eclipse artifacts). A Bill of Materials can be
produced for concepts such as "latest" etc. which means it is possible to
create a "dynamic installer" that is not bound to a particular version (or
is partially bound to particular versions for some components, and
dynamically bound to others). Buckminster also materializes from different
repositories; naturally from Eclipse update sites, but also from other
repositories (web, ftp, svn, cvs, etc).
Finally, Buckminster has an action framework and can invoke actions on
components; (Eclipse internal, such as PDE builds, but also via ant). It is
thus easy to define actions that create packages based on things that are
fetched dynamically.
I hope that gives some ideas about what Buckminster technology can do for
this project, and we are also very open to improvment suggestions!
Regards
- henrik
"Jochen Krause" <jkrause@innoopract.com> skrev i meddelandet
news:em74ab$o9k$1@utils.eclipse.org...
> Hendrik,
>
> That is great. There has been significant interest from multiple parties
> over the last couple of days, and the install topic is consistently one of
> high interest.
>
> Can you point us to the technology that Buckminster provides in this area.
>
> Best Regards,
>
> Jochen
>
>
>
> Henrik Lindberg wrote:
>> Hi, we have now synced up internally, and Cloudsmith / i.e. the
>> Buckminster team is very interested in helping out and becoming comitters
>> on this project.
>> It will be me, and one of Thomas Hallgren, Filip Hrbek, or Karel Brezina.
>>
>> Looking forward to discussing this project and requirments further.
>> Best Regards
>> Henrik Lindberg
>>
>>
|
|
| | |
Re: Buckminster team willing to committ [message #572007 is a reply to message #1796] |
Tue, 19 December 2006 13:15 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Jochen Krause![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=jkrause%40innoopract.de) Messages: 72 Registered: July 2009 |
Member |
|
|
If you are willing to take it on ...
The original intent of the packaging proposal was to provide new entry
level bundles for users at download.eclipse.org.
From my point of view installers could still fit into the scope of
packaging, but it could as well be addressed by platform.
What we will not tackle is the kind of dynamic provisioning that many
people have in mind, and installer would just deliver a fixed set of
functionality. This might be a minimal install to be extended by update
manager (or a better technology) or a predefined package.
Jochen
Pascal Rapicault wrote:
> Don't that fall under the provisioning aspect as well?
>
> "Jochen Krause" <jkrause@innoopract.com> wrote in message
> news:em74ab$o9k$1@utils.eclipse.org...
>> Hendrik,
>>
>> That is great. There has been significant interest from multiple parties
>> over the last couple of days, and the install topic is consistently one of
>> high interest.
>>
>> Can you point us to the technology that Buckminster provides in this area.
>>
>> Best Regards,
>>
>> Jochen
>>
>>
>>
>> Henrik Lindberg wrote:
>>> Hi, we have now synced up internally, and Cloudsmith / i.e. the
>>> Buckminster team is very interested in helping out and becoming comitters
>>> on this project.
>>> It will be me, and one of Thomas Hallgren, Filip Hrbek, or Karel Brezina.
>>>
>>> Looking forward to discussing this project and requirments further.
>>> Best Regards
>>> Henrik Lindberg
>>>
>>>
>
|
|
|
Re: Buckminster team willing to committ [message #572037 is a reply to message #1773] |
Tue, 19 December 2006 18:16 ![Go to previous message Go to previous message](theme/Solstice/images/up.png) |
Henrik Lindberg![Friend of Eclipse Friend](/donate/web-api/friends_decorator.php?email=glashammer%40hotmail.com) Messages: 112 Registered: July 2009 |
Senior Member |
|
|
Hi,
You can read more about Buckminster in general on the Eclipse wiki
http://wiki.eclipse.org/index.php/Buckminster_Project
The functionality that I guess is could be of special interest to this
project is the Buckminster installer; a headless packaging of
Eclipse/Buckminster that can run from a command line, or soon be invoked via
Java Web Start. This installer is about 2M in size and includes the Eclipse
update manager.
Buckminster installs things based on a Bill of Materials that Buckminster
can produce based on transitive dependencies (such as the OSGi declared
dependencies found in Eclipse artifacts). A Bill of Materials can be
produced for concepts such as "latest" etc. which means it is possible to
create a "dynamic installer" that is not bound to a particular version (or
is partially bound to particular versions for some components, and
dynamically bound to others). Buckminster also materializes from different
repositories; naturally from Eclipse update sites, but also from other
repositories (web, ftp, svn, cvs, etc).
Finally, Buckminster has an action framework and can invoke actions on
components; (Eclipse internal, such as PDE builds, but also via ant). It is
thus easy to define actions that create packages based on things that are
fetched dynamically.
I hope that gives some ideas about what Buckminster technology can do for
this project, and we are also very open to improvment suggestions!
Regards
- henrik
"Jochen Krause" <jkrause@innoopract.com> skrev i meddelandet
news:em74ab$o9k$1@utils.eclipse.org...
> Hendrik,
>
> That is great. There has been significant interest from multiple parties
> over the last couple of days, and the install topic is consistently one of
> high interest.
>
> Can you point us to the technology that Buckminster provides in this area.
>
> Best Regards,
>
> Jochen
>
>
>
> Henrik Lindberg wrote:
>> Hi, we have now synced up internally, and Cloudsmith / i.e. the
>> Buckminster team is very interested in helping out and becoming comitters
>> on this project.
>> It will be me, and one of Thomas Hallgren, Filip Hrbek, or Karel Brezina.
>>
>> Looking forward to discussing this project and requirments further.
>> Best Regards
>> Henrik Lindberg
>>
>>
|
|
|
Goto Forum:
Current Time: Fri Aug 16 18:28:54 GMT 2024
Powered by FUDForum. Page generated in 0.04299 seconds
|