Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster dev » New version of Buckminster Book available (rev 0.5)
New version of Buckminster Book available (rev 0.5) [message #370444] Tue, 28 July 2009 21:31 Go to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2498
Registered: July 2009
Senior Member
New Draft of Buckminster Book is available at http://tinyurl.com/ncv4lq

This is version 0.5 of the book, and it is now getting near completion.
I (think) have one or two more examples to write, and then final editing
and polish.

Your feedback is much appreciated.

Regards
- henrik
Re: New version of Buckminster Book available (rev 0.5) [message #371941 is a reply to message #370444] Wed, 29 July 2009 04:01 Go to previous messageGo to next message
Johannes Utzig is currently offline Johannes Utzig
Messages: 329
Registered: July 2009
Senior Member
Henrik Lindberg schrieb:
> New Draft of Buckminster Book is available at http://tinyurl.com/ncv4lq
>
> This is version 0.5 of the book, and it is now getting near completion.
> I (think) have one or two more examples to write, and then final editing
> and polish.
>
> Your feedback is much appreciated.
>
> Regards
> - henrik

Hi Henrik,

thanks a lot for the new version of the book!
As for the feedback: maybe you should correct the advanced property
section after my issues in the 'dynamic property refs' discussion.

This one:

Here is another more advanced example:
<«element» format="/tmp/somewhere/${{0}}">
<«function» ...>
</«element»>
In this example an element that has a format where {0} is expanded to
the value of the first child
element, uses this value (i.e. {0}) as the name of a property that
should be expanded as the final value.
Re: New version of Buckminster Book available (rev 0.5) [message #373118 is a reply to message #371941] Wed, 29 July 2009 09:00 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2498
Registered: July 2009
Senior Member
Fixed in 0.6.
Thanks.
Johannes Utzig wrote:
> Henrik Lindberg schrieb:
>> New Draft of Buckminster Book is available at http://tinyurl.com/ncv4lq
>>
>> This is version 0.5 of the book, and it is now getting near
>> completion. I (think) have one or two more examples to write, and then
>> final editing and polish.
>>
>> Your feedback is much appreciated.
>>
>> Regards
>> - henrik
>
> Hi Henrik,
>
> thanks a lot for the new version of the book!
> As for the feedback: maybe you should correct the advanced property
> section after my issues in the 'dynamic property refs' discussion.
>
> This one:
>
> Here is another more advanced example:
> <«element» format="/tmp/somewhere/${{0}}">
> <«function» ...>
> </«element»>
> In this example an element that has a format where {0} is expanded to
> the value of the first child
> element, uses this value (i.e. {0}) as the name of a property that
> should be expanded as the final value.
>
RE: [buckminster-dev] New version of Buckminster Book available (rev0.5) [message #373613 is a reply to message #370444] Wed, 29 July 2009 11:13 Go to previous messageGo to next message
Eclipse User
Originally posted by: dieter.cailliau.barco.com

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA105F.220EE395
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

When talking about svn branches i read that one should use the =
versionOverride (1) in combination with the rmap (2) of this form (see =
below).
This is very slow because it seems like buckminster visits all branches =
in order to find the best match, which is useless as i typically want =
one single branch (no need to do a find-best-match).
So it's much faster to have a specific rmap for each branch this (3) =
(and leave the .cquery alone, without the advisor nodes).
Can you comment on this please? Is it okay to do so, or not?

(3) my faster branch-specific rmap

<rm:searchPath name=3D"bundle">
<rm:provider readerType=3D"svn" componentTypes=3D"osgi.bundle" =
mutable=3D"false" source=3D"true">
<rm:uri =
format=3D" http://.../svn/software/branches/branchname/{0}?moduleAfterB ran=
ch">
<bc:propertyRef key=3D"buckminster.component" />
</rm:uri>
</rm:provider>
</rm:searchPath>



(1) the example from the documentation

<cq:advisorNode namePattern=3D"com.mycompany.*" =
useTargetPlatform=3D"false" =
versionOverride=3D"raw:['branchname','branchname']/format(S):branchname,b=
ranchname"/>

(2)

<rm:searchPath name=3D"cspec">
<rm:provider readerType=3D"svn" componentTypes=3D"buckminster" =
mutable=3D"false" source=3D"true">
<rm:uri =
format=3D"http://.../svn/software/trunk/{0}?moduleAfterBranch">
<bc:propertyRef key=3D"buckminster.component" />
</rm:uri>
<rm:versionConverter type=3D"branch">
<rm:transform fromPattern=3D"^(.*)$" fromReplacement=3D"$1" =
toPattern=3D"^(.*)$" toReplacement=3D"$1" />
</rm:versionConverter>
</rm:provider>
<rm:provider readerType=3D"svn" componentTypes=3D"buckminster" =
mutable=3D"false" source=3D"true">
<rm:uri format=3D"http://.../svn/software/trunk/{0}?moduleAfterTag">
<bc:propertyRef key=3D"buckminster.component" />
</rm:uri>
<rm:versionConverter type=3D"tag">
<rm:transform fromPattern=3D"^(.*)$" fromReplacement=3D"$1" =
toPattern=3D"^(.*)$" toReplacement=3D"$1" />
</rm:versionConverter>
</rm:provider>
</rm:searchPath>


DISCLAIMER:
Unless indicated otherwise, the information contained in this message is =
privileged and confidential, and is intended only for the use of the =
addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.

------_=_NextPart_001_01CA105F.220EE395
Content-Type: application/ms-tnef;
name="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+IiAPAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcA GAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEASQAAAFJFOiBb YnVja21pbnN0ZXIt
ZGV2XSBOZXcgdmVyc2lvbiBvZiBCdWNrbWluc3RlciBCb29rIGF2YWlsYWJs ZSAocmV2MC41KQCF
GQEFgAMADgAAANkHBwAdABEADQAfAAMARAEBIIADAA4AAADZBwcAHQARAA0A HwADAEQBAQmAAQAh
AAAAQkFCNjlGRDY1RTlEOTc0NThEMDcyREIxOTFERTI4QzMAYwcBA5AGAIgM AAA5AAAAAwAmAAAA
AAADADYAAAAAAEAAOQCV4w4iXxDKAR4APQABAAAABQAAAFJFOiAAAAAAAgFH AAEAAAAyAAAAYz1C
RTthPVJUVDtwPUJBUkNPO2w9S05ETUVYMDEtMDkwNzI5MTUxMzMxWi05NjI4 OQAAAB4ASQABAAAA
RQAAAFtidWNrbWluc3Rlci1kZXZdIE5ldyB2ZXJzaW9uIG9mIEJ1Y2ttaW5z dGVyIEJvb2sgYXZh
aWxhYmxlIChyZXYwLjUpAAAAAEAATgAAdGVZ7A/KAR4AWgABAAAAJAAAAGJ1 Y2ttaW5zdGVyLWRl
di1ib3VuY2VzQGVjbGlwc2Uub3JnAAIBWwABAAAAZQAAAAAAAACBKx+kvqMQ GZ1uAN0BD1QCAAAA
AGJ1Y2ttaW5zdGVyLWRldi1ib3VuY2VzQGVjbGlwc2Uub3JnAFNNVFAAYnVj a21pbnN0ZXItZGV2
LWJvdW5jZXNAZWNsaXBzZS5vcmcAAAAAAgFcAAEAAAApAAAAU01UUDpCVUNL TUlOU1RFUi1ERVYt
Qk9VTkNFU0BFQ0xJUFNFLk9SRwAAAAAeAF0AAQAAABAAAABIZW5yaWsgTGlu ZGJlcmcAAgFeAAEA
AABMAAAAAAAAAIErH6S+oxAZnW4A3QEPVAIAAAAASGVucmlrIExpbmRiZXJn AFNNVFAAaGVucmlr
LmxpbmRiZXJnQGNsb3Vkc21pdGguY29tAAIBXwABAAAAJAAAAFNNVFA6SEVO UklLLkxJTkRCRVJH
QENMT1VEU01JVEguQ09NAB4AZgABAAAABQAAAFNNVFAAAAAAHgBnAAEAAAAk AAAAYnVja21pbnN0
ZXItZGV2LWJvdW5jZXNAZWNsaXBzZS5vcmcAHgBoAAEAAAAFAAAAU01UUAAA AAAeAGkAAQAAAB8A
AABoZW5yaWsubGluZGJlcmdAY2xvdWRzbWl0aC5jb20AAB4AcAABAAAARQAA AFtidWNrbWluc3Rl
ci1kZXZdIE5ldyB2ZXJzaW9uIG9mIEJ1Y2ttaW5zdGVyIEJvb2sgYXZhaWxh YmxlIChyZXYwLjUp
AAAAAAIBcQABAAAAGwAAAAHKD+zQPHpqOG6lJk7UvtwZ1UvveskAHB+CGwAe AHQAAQAAABwAAABi
dWNrbWluc3Rlci1kZXZAZWNsaXBzZS5vcmcAHgAaDAEAAAARAAAAQ2FpbGxp YXUsIERpZXRlcgAA
AAAeAB0OAQAAAEUAAABbYnVja21pbnN0ZXItZGV2XSBOZXcgdmVyc2lvbiBv ZiBCdWNrbWluc3Rl
ciBCb29rIGF2YWlsYWJsZSAocmV2MC41KQAAAAACAQkQAQAAAIYEAACCBAAA dgoAAExaRnXx2gSM
AwAKAHJjcGcxMjXiMgNDdGV4BUEBAwH3/wqAAqQD5AcTAoAP8wBQBFY/CFUH shElDlEDAQIAY2jh
CsBzZXQyBgAGwxEl9jMERhO3MBIsETMI7wn3tjsYHw4wNREiDGBjAFAzCwkB ZDM2FlALpiBXSmgJ
8CABkGxrC4BnTiABoAhgBUBzdgOgYk5yAHAT0AeRaSAYIGFeZB0wE+AFQAIg ZR4QaHUIYGwfQHUU
EB9RH9B2dwSQAJACIE8g4QUQAQAg+CgxKR7gA6AFoAbQC4C7H4AhISAD8B9g IJNyAMDKcCHQMiIA
b2YfUQQAPiACECOgIdAUEB/QYmWxF7B3KS4KogqAVCRyOySBIOF5HhAlcSVB Y2EvIGIjIB4QCeBt
BCBsaaZrJTEa0GttC4BzDrD9BcB2BAAjIAQgB0ADIB5o7wOgBbAEgR0wbySg C4AfQqslMikQIADA
dBPQLCMA7yRwE9AmYiBhbAeQKbEe0rh0eXAN4CnRJtB3AHDfH5UdgS1wHlUh 0G4rQB/AqwmAKyJk
K0BhK1MtK/K2LSxDJaZTK0AjICcEIPZtGtAjQGYtwCkiKzET4PMg4DEBc3AF kAaQDeAjlD0ksSAf
ICzhL7UkYygzfSIAKABwH0AtcDQiIKIu/GNxClAmwQdAH7EskSMhfx3iIKIf MClhBbEwMAEAc/Ul
pkMDkXkIYCJCB4Au048kVAtQHyAUED8gSR7R+R+Ra2Em0DC0OdAskDnj3HQ/ JcQlxDaybSbQM3Wd
HmQtNIs+qgyCIDwjoO46FBAKwBPQUB+AI0AioDkHgD0iKKArgC1wIj77QelC R3ADYClgKvIfEgSQ
rlQuIEOxHiEiIkJwH7ELAjBGknNDwG9zZ2l+LkPlMxEBkS1wQ8AzcGwvFBBH IDnQCHBjQ7F0cn8K
UERPRQgIcSSjH4BDwGhBAkBwOi8vLk2wL7ceIU3gJDB0LrAYIC8eZiNOtUOC L1x7AUB9P7MEYSAg
ZUEBgASQQh5zc0rfS5piY0WSNJAAIHnqUgEQIChweUPCKMc34NtHVkcgL1GP QkQvTFRWD/9XY0Wm
V+pXY0LYV+ZbnyHi/yCiDsBDkDxhJKADYSCTMOBcY3U7kiKzPqogYCE89Tfw OjmVTgRxQ3NDMSkh
dm5DwCJRLj+gR0IAcHmsLipHICBhVArAZxQg/lALYAAwJMFJhyDtQ8AecJB3 OlsnT1gnLGZKhF0v
TMQoUyk6T1j6LE9YIlX3PxQkAEGPQp/9Q6JjNIJRf0VfRm9Heyipf0j/Sg9W P0wvTT9ORnQBbv5r
T/9RD1IfUy9UP1VPem/vV2907yDlCFBuIOEzo3AT/x5keg91DXQAAHEkswNS YafkXihjACkkcJAD
UnyAzwtRc8A7kkPAJDFwkCsw/4bPKzCIH36Pf5mCHoufWP//bg9vH3AvcT9y T3Nfi691f+92j3ef
eK5jcGeWr3sffC//fT9+T39fgG+Bf4KOAZCcL/+E74X/hw+Kf4kvij+LT4xf X41vjn+Pj1o/W0h9
tFAAAB4ANRABAAAAPgAAADwwMjhBRThBN0MwNEVFMTQ4ODlCRTk5RTU0NTBC RTMyRDAzNkVCQTdD
QGtuZG1leDAxLmJhcmNvLmNvbT4AAAAeADkQAQAAACEAAAA8aDRvOHE5JHJp YSQxQGJ1aWxkLmVj
bGlwc2Uub3JnPgAAAAAeAEcQAQAAAA8AAABtZXNzYWdlL3JmYzgyMgAACwDy EAEAAAAfAPMQAQAA
AJ4AAABSAEUAJQAzAEEAIABbAGIAdQBjAGsAbQBpAG4AcwB0AGUAcgAtAGQA ZQB2AF0AIABOAGUA
dwAgAHYAZQByAHMAaQBvAG4AIABvAGYAIABCAHUAYwBrAG0AaQBuAHMAdABl AHIAIABCAG8AbwBr
ACAAYQB2AGEAaQBsAGEAYgBsAGUAIAAoAHIAZQB2ADAALgA1ACkALgBFAE0A TAAAAAAACwD2EAAA
AABAAAcwObVHTl0QygFAAAgwUagTIl8QygEDAN4/r28AAAMA8T8JBAAAHgD4 PwEAAAARAAAAQ2Fp
bGxpYXUsIERpZXRlcgAAAAACAfk/AQAAAEQAAAAAAAAA3KdAyMBCEBq0uQgA Ky/hggEAAAAAAAAA
L089QkFSQ08vT1U9QUcwMDEvQ049UkVDSVBJRU5UUy9DTj1ESUVDAB4A+j8B AAAAFQAAAFN5c3Rl
bSBBZG1pbmlzdHJhdG9yAAAAAAIB+z8BAAAAHgAAAAAAAADcp0DIwEIQGrS5 CAArL+GCAQAAAAAA
AAAuAAAAAwD9P+QEAAADABlAAAAAAAMAGkAAAAAAAwAdQAAAAAADAB5AAAAA AB4AMEABAAAABQAA
AERJRUMAAAAAHgAxQAEAAAAFAAAARElFQwAAAAAeADJAAQAAACQAAABidWNr bWluc3Rlci1kZXYt
Ym91bmNlc0BlY2xpcHNlLm9yZwAeADNAAQAAAB8AAABoZW5yaWsubGluZGJl cmdAY2xvdWRzbWl0
aC5jb20AAB4AOEABAAAABQAAAERJRUMAAAAAHgA5QAEAAAACAAAALgAAAAMA dkD/////CwApAAAA
AAALACMAAAAAAAMABhAjRp9fAwAHEF0GAAADABAQAAAAAAMAERABAAAAHgAI EAEAAABlAAAAV0hF
TlRBTEtJTkdBQk9VVFNWTkJSQU5DSEVTSVJFQURUSEFUT05FU0hPVUxEVVNF VEhFVkVSU0lPTk9W
RVJSSURFKDEpSU5DT01CSU5BVElPTldJVEhUSEVSTUFQKDIpT0ZUSAAAAAAC AX8AAQAAAD4AAAA8
MDI4QUU4QTdDMDRFRTE0ODg5QkU5OUU1NDUwQkUzMkQwMzZFQkE3Q0BrbmRt ZXgwMS5iYXJjby5j
b20+AAAAkWE=

------_=_NextPart_001_01CA105F.220EE395--
Re: [buckminster-dev] New version of Buckminster Book available (rev0.5) [message #373675 is a reply to message #370444] Wed, 29 July 2009 11:29 Go to previous messageGo to next message
Oisin Hurley is currently offline Oisin Hurley
Messages: 204
Registered: July 2009
Senior Member
I use RMAP to achieve this too:

<provider readerType="svn" componentTypes="eclipse.feature"
mutable="true" source="false">
<uri format=" http://dev.eclipse.org/svnroot/stp/{0}/{1}/{2}/build/buckmin ster/{3}">
<bc:propertyRef key="project.repo" />
<bc:propertyRef key="project.component" />
<bc:propertyRef key="project.tag" />
<bc:propertyRef key="buckminster.component" />
</uri>
</provider>

but in my case the branch/tag is specified outside the Buck build
and defaulted to 'trunk'. If I want to change the build, I just update
the 'project.tag' property to 'tags/3.5M5' or whatever is required.

I hope I am not subverting some kind of fancy feature here ;)

--oh
Re: [buckminster-dev] New version of Buckminster Book available (rev0.5) [message #374439 is a reply to message #373613] Wed, 29 July 2009 12:41 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2498
Registered: July 2009
Senior Member
Hi, where did you read that versionOverride should be used to get things
from different branches? I tried googling for your example, but without
luck. That example is not in the book BTW.

I think it is better to handle branches with entries in the RMAP. We
have several examples in the book that shows how to use this for
different repositories (nightly, integration, release etc), and this
naturally works well for SVN branches as well.

Controlling the routing in the RMAP with properties also makes it
possible to use advisor nodes where this property is set - this to
enable picking different components from different branches (instead of
using a version override).

- henrik


Cailliau, Dieter wrote:
> When talking about svn branches i read that one should use the versionOverride (1) in combination with the rmap (2) of this form (see below).
> This is very slow because it seems like buckminster visits all branches in order to find the best match, which is useless as i typically want one single branch (no need to do a find-best-match).
> So it's much faster to have a specific rmap for each branch this (3) (and leave the .cquery alone, without the advisor nodes).
> Can you comment on this please? Is it okay to do so, or not?
>
> (3) my faster branch-specific rmap
>
> <rm:searchPath name="bundle">
> <rm:provider readerType="svn" componentTypes="osgi.bundle" mutable="false" source="true">
> <rm:uri format=" http://.../svn/software/branches/branchname/{0}?moduleAfterB ranch">
> <bc:propertyRef key="buckminster.component" />
> </rm:uri>
> </rm:provider>
> </rm:searchPath>
>
>
>
> (1) the example from the documentation
>
> <cq:advisorNode namePattern="com.mycompany.*" useTargetPlatform="false" versionOverride=" raw:['branchname','branchname']/format(S):branchname,branchn ame "/>
>
> (2)
>
> <rm:searchPath name="cspec">
> <rm:provider readerType="svn" componentTypes="buckminster" mutable="false" source="true">
> <rm:uri format="http://.../svn/software/trunk/{0}?moduleAfterBranch">
> <bc:propertyRef key="buckminster.component" />
> </rm:uri>
> <rm:versionConverter type="branch">
> <rm:transform fromPattern="^(.*)$" fromReplacement="$1" toPattern="^(.*)$" toReplacement="$1" />
> </rm:versionConverter>
> </rm:provider>
> <rm:provider readerType="svn" componentTypes="buckminster" mutable="false" source="true">
> <rm:uri format="http://.../svn/software/trunk/{0}?moduleAfterTag">
> <bc:propertyRef key="buckminster.component" />
> </rm:uri>
> <rm:versionConverter type="tag">
> <rm:transform fromPattern="^(.*)$" fromReplacement="$1" toPattern="^(.*)$" toReplacement="$1" />
> </rm:versionConverter>
> </rm:provider>
> </rm:searchPath>
>
>
> DISCLAIMER:
> Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
Re: [buckminster-dev] New version of Buckminster Book available (rev0.5) [message #375231 is a reply to message #374439] Wed, 29 July 2009 14:16 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3214
Registered: July 2009
Senior Member
Hi Henrik and Dieter,
I think a clarification is in order here.

For the SVN reader type to recognize branches and tags correctly, it's required that you have 'trunk' in the path (as in
Dieters example). The parent of the trunk will be where Buckminster looks for the 'branches' and 'tags' folders. Which
branch/tag that is used is then normally controlled using the branch/tag path in the CQUERY.

The VersionConverter can be used too but, as Dieter has found, it's slower since Buckminster then must examine all
branches for the best match. Typically, the branches are a poor substitute for versions anyway since the version most
often is deducted from artifacts in the component source.

I would not recommend the use of direct branches in the RMAP when accessing SVN and in CVS it would be impossible since
the URI is the same for all branches (and HEAD). I think it's better to control the nightly/intergraion/release aspect
of SCM's using the CQUERY branch/tag path. When accessing P2 repositories or similar, it's a different story of course,
since the repository as a whole might be different for different types of builds.

HTH,
Thomas Hallgren


Henrik Lindberg wrote:
> Hi, where did you read that versionOverride should be used to get things
> from different branches? I tried googling for your example, but without
> luck. That example is not in the book BTW.
>
> I think it is better to handle branches with entries in the RMAP. We
> have several examples in the book that shows how to use this for
> different repositories (nightly, integration, release etc), and this
> naturally works well for SVN branches as well.
>
> Controlling the routing in the RMAP with properties also makes it
> possible to use advisor nodes where this property is set - this to
> enable picking different components from different branches (instead of
> using a version override).
>
> - henrik
>
>
> Cailliau, Dieter wrote:
>> When talking about svn branches i read that one should use the
>> versionOverride (1) in combination with the rmap (2) of this form (see
>> below).
>> This is very slow because it seems like buckminster visits all
>> branches in order to find the best match, which is useless as i
>> typically want one single branch (no need to do a find-best-match).
>> So it's much faster to have a specific rmap for each branch this (3)
>> (and leave the .cquery alone, without the advisor nodes).
>> Can you comment on this please? Is it okay to do so, or not?
>>
>> (3) my faster branch-specific rmap
>>
>> <rm:searchPath name="bundle">
>> <rm:provider readerType="svn" componentTypes="osgi.bundle"
>> mutable="false" source="true">
>> <rm:uri
>> format=" http://.../svn/software/branches/branchname/{0}?moduleAfterB ranch">
>>
>> <bc:propertyRef key="buckminster.component" />
>> </rm:uri>
>> </rm:provider>
>> </rm:searchPath>
>>
>>
>>
>> (1) the example from the documentation
>>
>> <cq:advisorNode namePattern="com.mycompany.*"
>> useTargetPlatform="false"
>> versionOverride=" raw:['branchname','branchname']/format(S):branchname,branchn ame "/>
>>
>>
>> (2)
>>
>> <rm:searchPath name="cspec">
>> <rm:provider readerType="svn" componentTypes="buckminster"
>> mutable="false" source="true">
>> <rm:uri
>> format="http://.../svn/software/trunk/{0}?moduleAfterBranch">
>> <bc:propertyRef key="buckminster.component" />
>> </rm:uri>
>> <rm:versionConverter type="branch">
>> <rm:transform fromPattern="^(.*)$"
>> fromReplacement="$1" toPattern="^(.*)$" toReplacement="$1" />
>> </rm:versionConverter>
>> </rm:provider>
>> <rm:provider readerType="svn" componentTypes="buckminster"
>> mutable="false" source="true">
>> <rm:uri
>> format="http://.../svn/software/trunk/{0}?moduleAfterTag">
>> <bc:propertyRef key="buckminster.component" />
>> </rm:uri>
>> <rm:versionConverter type="tag">
>> <rm:transform fromPattern="^(.*)$"
>> fromReplacement="$1" toPattern="^(.*)$" toReplacement="$1" />
>> </rm:versionConverter>
>> </rm:provider>
>> </rm:searchPath>
>>
>>
>> DISCLAIMER:
>> Unless indicated otherwise, the information contained in this message
>> is privileged and confidential, and is intended only for the use of
>> the addressee(s) named above and others who have been specifically
>> authorized to receive it. If you are not the intended recipient, you
>> are hereby notified that any dissemination, distribution or copying of
>> this message and/or attachments is strictly prohibited. The company
>> accepts no liability for any damage caused by any virus transmitted by
>> this email. Furthermore, the company does not warrant a proper and
>> complete transmission of this information, nor does it accept
>> liability for any delays. If you have received this message in error,
>> please contact the sender and delete the message. Thank you.
Re: [buckminster-dev] New version of Buckminster Book available (rev0.5) [message #375243 is a reply to message #375231] Wed, 29 July 2009 14:30 Go to previous messageGo to next message
Oisin Hurley is currently offline Oisin Hurley
Messages: 204
Registered: July 2009
Senior Member
Hi Thomas,

> I would not recommend the use of direct branches in the
> RMAP when accessing SVN

It seems practical enough, as well as being 'the most
obvious solution' (to my mind at least). Are you
recommending a different approach because the
way RMAP works might change, or something like
that? Maybe because there is an external dependency
on the property value?

> I think it's better to control the nightly/integration/release
> aspect of SCM's using the CQUERY branch/tag path.

Do you have an example that illustrates this approach
that you prefer, for informational purposes?

[I haven't read the book yet - keeping that for vacation -
so apologies if it is in there!]

cheers
--oh
Re: [buckminster-dev] New version of Buckminster Book available (rev0.5) [message #406186 is a reply to message #375243] Thu, 30 July 2009 02:31 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3214
Registered: July 2009
Senior Member
Hi Oisin,

Oisin Hurley wrote:
> Hi Thomas,
>
>> I would not recommend the use of direct branches in the
>> RMAP when accessing SVN
>
> It seems practical enough, as well as being 'the most
> obvious solution' (to my mind at least). Are you
> recommending a different approach because the
> way RMAP works might change, or something like
> that? Maybe because there is an external dependency
> on the property value?
>
SVN has the branch as part of the actual URI but not all SCM's has that. So when Buckminster was designed, we added a
generic concept of branches (and tags) that can be used for all SCM's. I don't see the RMAP changing but if we improve
the branch/tag management in some way, we will improve on this said concept since it affects all SCM's.

Here are some reasons why I think using direct branches in the RMAP is less optimal:
1. Using other SCM's, the approach will not work at all (CVS is one prominent example).
2. Conceptually, I think the selection trunk, branches, and tags, should be controlled by the CQUERY, not the RMAP.
3. You cannot make Buckminster look into one SVN branch and if not found, fall back to another. This is because
Buckminster, not knowing that it deals with branches, will select the most suitable component from all places that it
looks in.
4. Unless your SVN branch name is expanded from a property, you'll need to alter the RMAP whenever you add a new branch
or tag.


>> I think it's better to control the nightly/integration/release
>> aspect of SCM's using the CQUERY branch/tag path.
>
> Do you have an example that illustrates this approach
> that you prefer, for informational purposes?
>
Take a look at http://www.eclipse.org/buckminster/samples/queries/buckminst er-3.4.cquery. It has an advisor node element
that looks like this:

<cq:advisorNode namePattern="buckminster" sourceLevel="REQUIRE" useMaterialization="false" useTargetPlatform="false"
branchTagPath="Platform-3.4.x,main"/>

A corresponding node can be found in http://www.eclipse.org/buckminster/samples/queries/buckminst er-dev.cquery.

<cq:advisorNode namePattern="buckminster" sourceLevel="REQUIRE" useMaterialization="false" useTargetPlatform="false"/>

but there you don't see any branchTagPath. Both queries use the same RMAP.

The branchTagPath="Platform-3.4.x,main" instructs the resolver to first look in our "Platform-3.4.x" branch and if the
component is not found there, look in "main" (the trunk). Using this approach, if the component is found on the
"Platform-3.4.x" branch, the resolver will not look in the trunk since the branchTagPath has higher precedence then
versions.

The reason it's set up this way is that we do selective and lazy branching, i.e. we only branch a component when there's
a real need for it (most likely because the API changed between versions). When the source of a component is the same
for 3.4.x as it is in whatever we're developing on trunk, then we don't branch. The result of that approach is that we
save a lot of unnecessary merging from trunk to the branch when fixing bugs. Merging is only needed for the branched
components.

When we see that we need to branch a component, we just branch it right there an then. The next time someone runs the
buckmisnter-3.4.cquery, the branched component will be picked automatically instead of the trunk version.

One might argue that Buckminster would be able to do this by using explicit paths in the RMAP but in fact, it cannot do
that. The reason is that when you do that, Buckminster does not know that it is dealing branches and hence, it lets the
version have higher priority. In our case here, that would be really bad since the versions on trunk are always higher
then the versions on the "Platform-3.4.x" branch.

Regards,
Thomas Hallgren
Re: [buckminster-dev] New version of Buckminster Book available (rev0.5) [message #419083 is a reply to message #375243] Thu, 30 July 2009 07:22 Go to previous messageGo to next message
Oisin Hurley is currently offline Oisin Hurley
Messages: 204
Registered: July 2009
Senior Member
Hi Thomas
Great response - thanks for taking the time to write all that up, it
is most appreciated!

On Thu, Jul 30, 2009 at 7:31 AM, Thomas Hallgren<thomas@tada.se> wrote:

> 3. You cannot make Buckminster look into one SVN branch and if not found,
> fall back to another. This is because Buckminster, not knowing that it deals
> with branches, will select the most suitable component from all places that
> it looks in.

Ah, this behaviour is familiar from my Clearcase days - you only branch
the resources you actually change, and the resolution (visibility in view
in the ccase sense) is made by checking the branch first, then the precursor
branch and eventually back to trunk.

I guess this is a resolution behaviour that is not SCM-bound, and so it
needed to be built into Buckminster. That makes sense.

Thanks for the examples, I shall do some experimentation with them.

cheers
--oh
[buckminster-dev] buckminster installer [message #441405 is a reply to message #370444] Fri, 31 July 2009 06:46 Go to previous messageGo to next message
Eclipse User
Originally posted by: dieter.cailliau.barco.com

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA11CC.A2491123
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

There's something on p12 about a buckminster installer (see below). I =
can not find it anywhere.

I'm looking for a configurable webstartable installer: a thing i can =
host on a webserver, and when the user clicks it, it should install my =
application (download from my site.p2) on his machine. Is this what the =
"buckminster installer" promises to be, or not?

(from buckyBook)
The Buckminster installer
The Buckminster project also provides an installer. It is designed =
to be started via Java Web Start or
via a Java applet and it gets its initial parameters indirectly via =
a URL. Originally this installer used
Buckminster's provisioning capabilities and before p2 this was one =
of very few options available when
an external, web startable installer was wanted.
The Buckminster installer also includes a JSON client, and is =
capable of engaging in a dialog with an
smart repository and thereby present more information about what is =
being installed, manage a sign-
in dialog, branding, and much more.
The Buckminster installer is however not yet documented.


DISCLAIMER:
Unless indicated otherwise, the information contained in this message is =
privileged and confidential, and is intended only for the use of the =
addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.

------_=_NextPart_001_01CA11CC.A2491123
Content-Type: application/ms-tnef;
name="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+IjUKAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcA GAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEAFgAAAGJ1Y2tt aW5zdGVyIGluc3Rh
bGxlcgCVCAEFgAMADgAAANkHBwAfAAwALgAIAAUATQEBIIADAA4AAADZBwcA HwAMADEANAAFAHwB
AQmAAQAhAAAAMkFCNDRCRUZDRDlGNzQ0NTk3RkExQUREMDNBRDg0N0UAhQcB A5AGAAQLAAA5AAAA
AwAmAAAAAAADADYAAAAAAEAAOQAPDZAczBHKAR4APQABAAAAAQAAAAAAAAAC AUcAAQAAADIAAABj
PUJFO2E9UlRUO3A9QkFSQ087bD1LTkRNRVgwMS0wOTA3MzExMDQ5NTJaLTk5 MjM5AAAAHgBJAAEA
AABJAAAAUkU6IFtidWNrbWluc3Rlci1kZXZdIE5ldyB2ZXJzaW9uIG9mIEJ1 Y2ttaW5zdGVyIEJv
b2sgYXZhaWxhYmxlIChyZXYwLjUpAAAAAEAATgCV4w4iXxDKAR4AWgABAAAA JAAAAGJ1Y2ttaW5z
dGVyLWRldi1ib3VuY2VzQGVjbGlwc2Uub3JnAAIBWwABAAAAZQAAAAAAAACB Kx+kvqMQGZ1uAN0B
D1QCAAAAAGJ1Y2ttaW5zdGVyLWRldi1ib3VuY2VzQGVjbGlwc2Uub3JnAFNN VFAAYnVja21pbnN0
ZXItZGV2LWJvdW5jZXNAZWNsaXBzZS5vcmcAAAAAAgFcAAEAAAApAAAAU01U UDpCVUNLTUlOU1RF
Ui1ERVYtQk9VTkNFU0BFQ0xJUFNFLk9SRwAAAAAeAF0AAQAAABEAAABDYWls bGlhdSwgRGlldGVy
AAAAAAIBXgABAAAASAAAAAAAAACBKx+kvqMQGZ1uAN0BD1QCAAAAAENhaWxs aWF1LCBEaWV0ZXIA
U01UUABkaWV0ZXIuY2FpbGxpYXVAYmFyY28uY29tAAIBXwABAAAAHwAAAFNN VFA6RElFVEVSLkNB
SUxMSUFVQEJBUkNPLkNPTQAAHgBmAAEAAAAFAAAAU01UUAAAAAAeAGcAAQAA ACQAAABidWNrbWlu
c3Rlci1kZXYtYm91bmNlc0BlY2xpcHNlLm9yZwAeAGgAAQAAAAUAAABTTVRQ AAAAAB4AaQABAAAA
GgAAAGRpZXRlci5jYWlsbGlhdUBiYXJjby5jb20AAAAeAHAAAQAAABYAAABi dWNrbWluc3RlciBp
bnN0YWxsZXIAAAACAXEAAQAAACAAAAAByg/s0Dx6ajhupSZO1L7cGdVL73rJ ABwfghsAW7OSCR4A
dAABAAAAIgAAAEJ1Y2ttaW5zdGVyIGRldmVsb3BlciBkaXNjdXNzaW9ucwAA AB4AGgwBAAAAEQAA
AENhaWxsaWF1LCBEaWV0ZXIAAAAAHgAdDgEAAAAWAAAAYnVja21pbnN0ZXIg aW5zdGFsbGVyAAAA
AgEJEAEAAACTAwAAjwMAAJwFAABMWkZ1AtweHwMACgByY3BnMTI14jIDQ3Rl eAVBAQMB908KgAKk
A+MCAGNoCsBz8GV0MCAHEwKAD/MAUH8EVghVB7IRxQ5RAwEQxzL3BgAGwxHF MwRGEMkS2xHT2wjv
Cfc7GL8OMDURwgxgzmMAUAsJAWQzNhFQC6ZIIFRoBJBlJwQgc0sDcBEwaAuA ZyACICA6cA4gIAGg
CGAFQGEg0mIbcGttC4BzDrAFwKsf8gdAbBMhKBEgZR+QAmUYUHcpLiBJIFJj A5FubwVAZguAZKMg
UB9hbnl3HaIuCqJDCoQKgEknbSAYUG++ax5yAhAFwB+ABaBuInAOZwhwAaAg wCB3ZWJvIIEAICXj
IGc6H3EeVGn5IeNobyAQHqIfgCYyBJD6dgSQLCLhIqAjIQOgHlCtITB1KWEh 4GwN4GsEIJciwCnA
IsFzKJB1bCKh0SB0IG15HxBwC1AN4EhhdGkesShkIYBufRhQYSKgA1IswgCQ DrAu+HAyKR6iHmAE
IADBHmH/I2AhwAQgHlEEICMgLWAqY/YiH68gsiIe0ANhBAAHkbx0byFBKcAF sSIxPyOKpiguYzGS
eUIkkSkjhLkdkSBCMa8gwSOEIDiC2zaeMwFqBZAfYWweEDLy/HZpAQAEIAOR IGchsQVA/y+xOvEl
oDAwIqAzkx4AJnJHPNE60B+ASmF2H4BX/yZABgAmcjPxOCk94j4FLQL3ETAp 0yLBZxEwK1IrUQMA
7y1wB0Ae0ArAYR4xBJBB4mxkaRjAOiBsLOA/5FXUUkwhsE8FEGcLgCChfyzg MKMgaCqxCzE4RzbZ
XPgnOTIEIDqjAJACIB5y+yHwCrBiAxBCITsDIqAhUO8lASEwLzAwlWEEIAIg ITBcb2Y90ASQLOBm
B9Fv/wUwLYE7ET5AAxAl5CoxOCn/A5EOwQSRB0ApwCYxPVQmvP9K80sAAjAJ gCN1OI8gLDpTGwuA
KwB1OvM+EFNPTv8q8gnwK4FBAwQgSQMmAUuB+QnwZ2FEwSgRKPJDUAdAvm8e kAPwHlAi4VFZcwDA
+z7hGMBwKKAiwAWwLOEikfsqcRjAYizgMwAHkFUhLMD/SkILgCUBAMAtcx8k MPMvsfchUFbkIIRk
KcADgVbAITB7H4A8ki1RWVchV3QpwGLvJdBDQR6AKcRtG3BYEFtS/1FPUl8g wi+xKJAmMCmRIiNm
eUDRLdBjdQeAUQl9AWawAB4ANRABAAAAPgAAADwwMjhBRThBN0MwNEVFMTQ4 ODlCRTk5RTU0NTBC
RTMyRDAzNkVCQTgyQGtuZG1leDAxLmJhcmNvLmNvbT4AAAAeADkQAQAAAF8A AAA8aDRvOHE5JHJp
YSQxQGJ1aWxkLmVjbGlwc2Uub3JnPiA8MDI4QUU4QTdDMDRFRTE0ODg5QkU5 OUU1NDUwQkUzMkQw
MzZFQkE3Q0BrbmRtZXgwMS5iYXJjby5jb20+AAAeAEcQAQAAAA8AAABtZXNz YWdlL3JmYzgyMgAA
CwDyEAEAAAAfAPMQAQAAADQAAABiAHUAYwBrAG0AaQBuAHMAdABlAHIAIABp AG4AcwB0AGEAbABs
AGUAcgAuAEUATQBMAAAACwD2EAAAAABAAAcwDw2QHMwRygFAAAgwV19XoswR ygEDAN4/r28AAAMA
8T8JBAAAHgD4PwEAAAARAAAAQ2FpbGxpYXUsIERpZXRlcgAAAAACAfk/AQAA AEQAAAAAAAAA3KdA
yMBCEBq0uQgAKy/hggEAAAAAAAAAL089QkFSQ08vT1U9QUcwMDEvQ049UkVD SVBJRU5UUy9DTj1E
SUVDAB4A+j8BAAAAFQAAAFN5c3RlbSBBZG1pbmlzdHJhdG9yAAAAAAIB+z8B AAAAHgAAAAAAAADc
p0DIwEIQGrS5CAArL+GCAQAAAAAAAAAuAAAAAwD9P+QEAAADABlAAAAAAAMA GkAAAAAAAwAdQAAA
AAADAB5AAAAAAB4AMEABAAAABQAAAERJRUMAAAAAHgAxQAEAAAAFAAAARElF QwAAAAAeADJAAQAA
ACQAAABidWNrbWluc3Rlci1kZXYtYm91bmNlc0BlY2xpcHNlLm9yZwAeADNA AQAAABoAAABkaWV0
ZXIuY2FpbGxpYXVAYmFyY28uY29tAAAAHgA4QAEAAAAFAAAARElFQwAAAAAe ADlAAQAAAAIAAAAu
AAAAAwB2QP////8LACkAAAAAAAsAIwAAAAAAAwAGEBxFhDUDAAcQaQMAAAMA EBAAAAAAAwAREAEA
AAAeAAgQAQAAAGUAAABUSEVSRVNTT01FVEhJTkdPTlAxMkFCT1VUQUJVQ0tN SU5TVEVSSU5TVEFM
TEVSKFNFRUJFTE9XKUlDQU5OT1RGSU5ESVRBTllXSEVSRUlNTE9PS0lOR0ZP UkFDT05GSUdVUkFC
AAAAAAIBfwABAAAAPgAAADwwMjhBRThBN0MwNEVFMTQ4ODlCRTk5RTU0NTBC RTMyRDAzNkVCQTgy
QGtuZG1leDAxLmJhcmNvLmNvbT4AAAAJ3g==

------_=_NextPart_001_01CA11CC.A2491123--
Re: [buckminster-dev] buckminster installer [message #441651 is a reply to message #441405] Fri, 31 July 2009 07:08 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2498
Registered: July 2009
Senior Member
Hi, the short answer is: yes, that is what the buckminster installer is
intended to be. It is however undocumented, and has an API that uses
JSON to talk back to the server. It has been updated in 3.5 to use p2 to
install, but its not well tested. Also, the server side parts i.e.
getting java web start working, getting JSON to work, deliver all the
properties etc. is not included - you would need to do that part on your
own.

I should probably either remove the note from the book, or more clearly
describe its state. Right now I am not sure I would recommend direct use
other than looking at the code for inspiration.

- henrik


Cailliau, Dieter wrote:
> There's something on p12 about a buckminster installer (see below). I can not find it anywhere.
>
> I'm looking for a configurable webstartable installer: a thing i can host on a webserver, and when the user clicks it, it should install my application (download from my site.p2) on his machine. Is this what the "buckminster installer" promises to be, or not?
>
> (from buckyBook)
> The Buckminster installer
> The Buckminster project also provides an installer. It is designed to be started via Java Web Start or
> via a Java applet and it gets its initial parameters indirectly via a URL. Originally this installer used
> Buckminster's provisioning capabilities and before p2 this was one of very few options available when
> an external, web startable installer was wanted.
> The Buckminster installer also includes a JSON client, and is capable of engaging in a dialog with an
> smart repository and thereby present more information about what is being installed, manage a sign-
> in dialog, branding, and much more.
> The Buckminster installer is however not yet documented.
>
>
> DISCLAIMER:
> Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
Re: New version of Buckminster Book available (rev 0.5) [message #468490 is a reply to message #370444] Wed, 05 August 2009 12:19 Go to previous messageGo to next message
Tas Frangoullides is currently offline Tas Frangoullides
Messages: 195
Registered: July 2009
Senior Member
First line on page 69 is hard to follow. Might be a typo.

Tas

"Henrik Lindberg" <henrik.lindberg@cloudsmith.com> wrote in message
news:h4o8q9$ria$1@build.eclipse.org...
> New Draft of Buckminster Book is available at http://tinyurl.com/ncv4lq
>
> This is version 0.5 of the book, and it is now getting near completion. I
> (think) have one or two more examples to write, and then final editing and
> polish.
>
> Your feedback is much appreciated.
>
> Regards
> - henrik
Re: New version of Buckminster Book available (rev 0.5) [message #468504 is a reply to message #468490] Wed, 05 August 2009 13:17 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2498
Registered: July 2009
Senior Member
Hi, no, not a typo, but some commas would make it easier to read. I will
rephrase it.
- henrik

Tas Frangoullides wrote:
> First line on page 69 is hard to follow. Might be a typo.
>
> Tas
>
> "Henrik Lindberg" <henrik.lindberg@cloudsmith.com> wrote in message
> news:h4o8q9$ria$1@build.eclipse.org...
>> New Draft of Buckminster Book is available at http://tinyurl.com/ncv4lq
>>
>> This is version 0.5 of the book, and it is now getting near
>> completion. I (think) have one or two more examples to write, and then
>> final editing and polish.
>>
>> Your feedback is much appreciated.
>>
>> Regards
>> - henrik
>
Re: New version of Buckminster Book available (rev 0.5) [message #476279 is a reply to message #468504] Wed, 05 August 2009 19:48 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2498
Registered: July 2009
Senior Member
The text is now changed to read:

"As an example, if you want an attribute in component-C to include the
artifacts ‘g’, and ‘h’, you can declare the attribute’s base to be an
empty string (base=""), and use the paths ‘plugins/g’,
and ‘plugins/h’. You get the same result if you instead set the base
like this: base="plugins", and set the paths to just ‘g’ and ‘h’. Does
it matter which you use? The same files are referenced in both cases.
The answer is: yes, it matters when you are copying the result. Let’s
say you copy the result to a location ‘Z’. In the first case you would
get ‘Z/plugins/g’ and ‘Z/plugins/h’, and in the second case you would
get ‘Z/g’, and ‘Z/h’."

I hope that is clearer.
- henrik

Henrik Lindberg wrote:
> Hi, no, not a typo, but some commas would make it easier to read. I will
> rephrase it.
> - henrik
>
> Tas Frangoullides wrote:
>> First line on page 69 is hard to follow. Might be a typo.
>>
>> Tas
>>
>> "Henrik Lindberg" <henrik.lindberg@cloudsmith.com> wrote in message
>> news:h4o8q9$ria$1@build.eclipse.org...
>>> New Draft of Buckminster Book is available at http://tinyurl.com/ncv4lq
>>>
>>> This is version 0.5 of the book, and it is now getting near
>>> completion. I (think) have one or two more examples to write, and
>>> then final editing and polish.
>>>
>>> Your feedback is much appreciated.
>>>
>>> Regards
>>> - henrik
>>
Re: [buckminster-dev] Re: New version of Buckminster Book available (rev 0.5) [message #480423 is a reply to message #476279] Mon, 17 August 2009 02:16 Go to previous messageGo to next message
Guillaume Chatelet is currently offline Guillaume Chatelet
Messages: 146
Registered: July 2009
Senior Member
--000e0cd1fc0eec78490471505719
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Henrik,

Page 22 you're stating there are several types of actors for Bucky. You can
also add the 'executor' and 'fetcher' actors from the 'non java proposal'.
I really have to look at this book but unfortunately right now I'm flooded
with work, hope I'm gonna catch up soon.

Cheers,
Guillaume

--000e0cd1fc0eec78490471505719
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Henrik,<br><br>Page 22 you&#39;re stating there are several types of act=
ors for Bucky. You can also add the &#39;executor&#39; and &#39;fetcher&#39=
; actors from the &#39;non java proposal&#39;.<br>I really have to look at =
this book but unfortunately right now I&#39;m flooded with work, hope I&#39=
;m gonna catch up soon.<br>

<br>Cheers,<br>Guillaume<br>

--000e0cd1fc0eec78490471505719--
Re: [buckminster-dev] Re: New version of Buckminster Book available (rev 0.5) [message #480457 is a reply to message #480423] Mon, 17 August 2009 04:58 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2498
Registered: July 2009
Senior Member
Thanks,
I added them in the brief overview on p22.
- henrik

Guillaume Chatelet wrote:
> Hi Henrik,
>
> Page 22 you're stating there are several types of actors for Bucky. You
> can also add the 'executor' and 'fetcher' actors from the 'non java
> proposal'.
> I really have to look at this book but unfortunately right now I'm
> flooded with work, hope I'm gonna catch up soon.
>
> Cheers,
> Guillaume
Re: New version of Buckminster Book available (rev 0.5) [message #480471 is a reply to message #370444] Mon, 17 August 2009 05:47 Go to previous messageGo to next message
Tas Frangoullides is currently offline Tas Frangoullides
Messages: 195
Registered: July 2009
Senior Member
Hi Henrik,

The propertyElement example at the top of page 101 doesn't look like proper
XML. Does it need to be something like this?

<propertyElement
key="hatType"
mutable="true">
<constant value="bandana" />
</propertyElement>

Tas.


"Henrik Lindberg" <henrik.lindberg@cloudsmith.com> wrote in message
news:h4o8q9$ria$1@build.eclipse.org...
> New Draft of Buckminster Book is available at http://tinyurl.com/ncv4lq
>
> This is version 0.5 of the book, and it is now getting near completion. I
> (think) have one or two more examples to write, and then final editing and
> polish.
>
> Your feedback is much appreciated.
>
> Regards
> - henrik
Re: New version of Buckminster Book available (rev 0.5) [message #480477 is a reply to message #480471] Mon, 17 August 2009 06:04 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2498
Registered: July 2009
Senior Member
Yes, thanks. Fixed in 0.6.
- henrik

Tas Frangoullides wrote:
> The propertyElement example at the top of page 101 doesn't look like
> proper XML. Does it need to be something like this?
>
> <propertyElement
> key="hatType"
> mutable="true">
> <constant value="bandana" />
> </propertyElement>
>
> "Henrik Lindberg" <henrik.lindberg@cloudsmith.com> wrote
>> New Draft of Buckminster Book is available at http://tinyurl.com/ncv4lq
>>
Re: New version of Buckminster Book available (rev 0.5) [message #480843 is a reply to message #370444] Tue, 18 August 2009 12:20 Go to previous messageGo to next message
Tas Frangoullides is currently offline Tas Frangoullides
Messages: 195
Registered: July 2009
Senior Member
Hi Henrik,

Page 152, Section "Access to prerequisites and product location", First
sentence. There appears to be a small typo on the word 'though', which I
think should be 'thought'.

Tas

"Henrik Lindberg" <henrik.lindberg@cloudsmith.com> wrote in message
news:h4o8q9$ria$1@build.eclipse.org...
> New Draft of Buckminster Book is available at http://tinyurl.com/ncv4lq
>
> This is version 0.5 of the book, and it is now getting near completion. I
> (think) have one or two more examples to write, and then final editing and
> polish.
>
> Your feedback is much appreciated.
>
> Regards
> - henrik
Re: New version of Buckminster Book available (rev 0.5) [message #480861 is a reply to message #480843] Tue, 18 August 2009 13:16 Go to previous messageGo to next message
Henrik Lindberg is currently offline Henrik Lindberg
Messages: 2498
Registered: July 2009
Senior Member
Thanks,
fixed in 0.6.
- henrik
Tas Frangoullides wrote:
> Hi Henrik,
>
> Page 152, Section "Access to prerequisites and product location", First
> sentence. There appears to be a small typo on the word 'though', which I
> think should be 'thought'.
>
> Tas
>
Re: New version of Buckminster Book available (rev 0.5) [message #481675 is a reply to message #370444] Sun, 23 August 2009 03:44 Go to previous messageGo to next message
Eclipse User
Originally posted by: news.eclipse.org.08.lemmster.de

Henrik Lindberg wrote:
> New Draft of Buckminster Book is available at http://tinyurl.com/ncv4lq
>
> This is version 0.5 of the book, and it is now getting near completion.
> I (think) have one or two more examples to write, and then final editing
> and polish.
>
> Your feedback is much appreciated.
>
> Regards
> - henrik

Hi,

you might want to add "staging.area" to the list of properties in
section "site.p2" on page 139ff. Otherwise BM will use
"/home/data/download-staging.priv/tools/buckminster" as the staging area
for which most people won't have write permissions.

Markus
Re: New version of Buckminster Book available (rev 0.5) [message #482642 is a reply to message #481675] Thu, 27 August 2009 08:40 Go to previous message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3214
Registered: July 2009
Senior Member
I opened a bugzilla for this.

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

- thomas

On 08/23/2009 09:44 AM, Markus Kuppe wrote:
> Henrik Lindberg wrote:
>> New Draft of Buckminster Book is available at http://tinyurl.com/ncv4lq
>>
>> This is version 0.5 of the book, and it is now getting near completion.
>> I (think) have one or two more examples to write, and then final editing
>> and polish.
>>
>> Your feedback is much appreciated.
>>
>> Regards
>> - henrik
>
> Hi,
>
> you might want to add "staging.area" to the list of properties in
> section "site.p2" on page 139ff. Otherwise BM will use
> "/home/data/download-staging.priv/tools/buckminster" as the staging area
> for which most people won't have write permissions.
>
> Markus
Previous Topic:Buckminster and Bamboo
Next Topic:RE: [buckminster-dev] create.eclipse.jnlp.product issues
Goto Forum:
  


Current Time: Wed Jul 23 06:04:44 EDT 2014

Powered by FUDForum. Page generated in 0.04248 seconds