Re: [ecf-dev] build easier next steps

[Ted Kubaska <ted.kubaska@xxxxxxxxx>]

So this was my error .. I installed Bucky PDE Support and it looks OK -ted

On Sun, Aug 9, 2009 at 1:22 AM, Ted Kubaska<ted.kubaska@xxxxxxxxx> wrote:
> Aha, I did not install Buckminster PDE support ... only Core and CVS
> Support. SIgh. -ted
>
> On Sun, Aug 9, 2009 at 1:17 AM, Ted Kubaska<ted.kubaska@xxxxxxxxx> wrote:
>> I have to be honest and tell you that I followed the directions for
>> the demo on page 117 and do not see the action called site.p2. I tried
>> both using a buckminster.properties file and Run/Debug string
>> substitution. I can click on Buckminster -> Invoke Action ...browse to
>> my properties file, but when I click OK nothing happens.
>>
>> I have Mac OS X Leopard 10.5.7 and Eclipse 3.5.0. I also tried
>> hardcoding ${user.home} and making by hand the demosite and tmp
>> directories.
>>
>> Here is my buckminster.properties file
>> newtricks:BuckyProperties ted$ cat buckminster.properties
>> # Where all the output should go
>> buckminster.output.root=/Users/ted/BuckyDemo/demosite
>> # Where the temp files should go
>> buckminster.temp.root=/Users/ted/BuckyDemo/tmp/demosite.tmp
>> # How .qualifier in versions should be replaced
>> qualifier.replacement.*=generator:lastRevision
>>
>>
>> Here was the quote from the Bucky book instructions
>> <quote>
>> With the property file in place, we can now build the site. Right
>> click over the org.demo.demosite
>> project, and select Buckminster → Invoke Action..., and (if you
>> decided to use a properties file) in the
>> pop up that appears, browse for the buckminster.properties file we
>> just created (you will need
>> to navigate in the file system to find the workspace, project, and
>> then the file since the properties files
>> are typically placed in the file system, and not in the workspace).
>> When the properties file has been
>> found and selected (alternatively set the properties using Run/Debug
>> string substitution), select the
>> action called ‘site.p2’ in the list of presented actions, and click
>> ‘Ok’. You will now see some trace
>> output, and if everything worked ok, you now have an update site.
>> </quote>
>>
>> On Wed, Aug 5, 2009 at 3:47 PM, Scott Lewis<slewis@xxxxxxxxxxxxxxxxx> wrote:
>>> Also, see the new version of Buckminster book available (as of 7/28) as per
>>> this buckminster dev announcement:
>>>
>>> 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
>>> _______________________________________________
>>> buckminster-dev mailing list
>>> buckminster-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>>>
>>> Ted Kubaska wrote:
>>>>
>>>> I can do 8/10 morning. I'll read some of the Bucky book over the
>>>> weekend. I remember from the last discussion that Bucky has some
>>>> signing ability that unfortunately was not yet described in the book.
>>>> But I think there is a presentation somewhere that describes this.
>>>> Does anyone have a pointer?
>>>>
>>>>  -ted
>>>>
>>>> On Wed, Aug 5, 2009 at 12:00 AM, Markus Alexander
>>>> Kuppe<ecf-dev_eclipse.org@xxxxxxxxxxx> wrote:
>>>>
>>>>>
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>
>>>>> Ted Kubaska wrote:
>>>>>
>>>>>>
>>>>>> Next week is best for me. I'm out of town and on the road week of aug 4.
>>>>>> -ted
>>>>>>
>>>>>
>>>>> For me Monday 10th works best. I suggest the usual time (in the moring
>>>>> PDT/evening CEST).
>>>>>
>>>>> Cheers
>>>>> Markus
>>>>> -----BEGIN PGP SIGNATURE-----
>>>>> Version: GnuPG v1.4.9 (GNU/Linux)
>>>>>
>>>>> iEYEARECAAYFAkp5LigACgkQH/hL0IhDj1kOlwCg4rAvSp1gzuEoBq7k5gnLPN/d
>>>>> 7VQAoLhfj9C84Gyefx+kSmqFXngxTGYg
>>>>> =iGn4
>>>>> -----END PGP SIGNATURE-----
>>>>> _______________________________________________
>>>>> ecf-dev mailing list
>>>>> ecf-dev@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/ecf-dev
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> ecf-dev mailing list
>>> ecf-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/ecf-dev
>>>
>>
>>
>>
>> --
>>  -Ted
>>
>
>
>
> --
>  -Ted
>



-- 
 -Ted