[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] build easier next steps

Thanks. I did get Buckminster installed in my Eclipse IDE and
successfully ran the demo example from the book.

I'm trying to install the headless version, but ran into some
difficulty as described below. Can you give me some further advice?

I interpreted Appendix A to say the following...

1.
Download the director. I read on www,ecliipse.org/buckminster
<quote>
In order to install the headless buckminster, you must use the P2
director. A headless command line version of the director can be found
here:  director_1.0.0.r10307.zip.
</quote>

I downloaded  director_1.0.0.r10307.zip and unzipped it into
/opt/headlessDirector. This produces a directory called director.

2.
I then entered the directory called director and issued the command as
described in Appendix A.

<quote>
director -r Ârepo-location -d Âinstall-folder -p Buckminster -i
org.eclipse.buckminster.cmdline.product
</quote>
 I got the following...

ted@MyHeron:/opt/headlessDirector/director$ ./director -r
http://download.eclipse.org/tools/buckminster/headless-3.5 -d
/opt/headlessBucky -p Buckminster -i
org.eclipse.buckminster.cmdline.product
Installing org.eclipse.buckminster.cmdline.product 1.1.350.r10447.
Operation completed in 34012 ms.
ted@MyHeron:/opt/headlessDirector/director$ ls
artifacts.xml  configuration  director  director.bat  eclipse.ini  p2  plugins

3.
Now I want to install additional features. Appendix A says I can use
the just installed Buckminster and gives the syntax as

<quote>
buckminster Ârepository-url Âfeature-id [ Âversion ]
Where Ârepository-url is the same as in the previous step, and
Âfeature-id is one of the features listed below. Optionally, a
specific version can be installed. Here are the features you can
install:

org.eclipse.buckminster.core.headless.feature
     The Core functionality â this feature is required if you want to
do anything with
      Buckminster  except installing additional features.
</quote>

and so I entered the directory /opt/headlessBucky which has an
executable buckminster and entered the following, replacing
repository-url with
http://download.eclipse.org/tools/buckminster/headless-3.5/ but then
got the following error...

<quote>
ted@MyHeron:/opt/headlessBucky$ ./buckminster
http://download.eclipse.org/tools/buckminster/headless-3.5/
org.eclipse.buckminster.core.headless.feature
Command 'http://download.eclipse.org/tools/buckminster/headless-3.5/' not found
</quote>

4.
I think I need to supply a command (but Appendix A does not show this
in the syntax). So I tried

ted@MyHeron:/opt/headlessBucky$  ./buckminster
org.eclipse.buckminster.installer.install
http://download.eclipse.org/tools/buckminster/headless-3.5/
org.eclipse.buckminster.core.headless.feature
ted@MyHeron:/opt/headlessBucky$

And as you can see, it was silent. So I don't know if anything happened.

 -ted



On Mon, Aug 10, 2009 at 2:29 AM, Thomas Hallgren<thomas@xxxxxxx> wrote:
> Hi Ted,
> The URL:
>
> Â http://download.cloudsmith.com/buckminster/external/
>
> is not an SVN repository. It is an update site that contains headless
> (complete) SVN features that we cannot distribute at eclipse.org due to IP
> issues. If you already have SVN working, you don't need anything from that
> site. In order to get the source for the the Hello XML example, simply
> import this CQUERY:
>
> Â http://www.eclipse.org/buckminster/samples/queries/demo.cquery
>
> The result of a "Resolve and Materialize" should bring all relevant source
> into our workspace.
>
> Regards,
> Thomas Hallgren
>
>
> Ted Kubaska wrote:
>
> Am I making a simple error here? .... (SVN works fine for me with
> local repositories) but when I
> newtricks:BuckyDemo ted$ svn checkout
> http://download.cloudsmith.com/buckminster/external/
>
> I get the error ...
>
> svn: PROPFIND request failed on '/buckminster/external'
> svn: PROPFIND of '/buckminster/external': 301 Moved Permanently
> (http://download.cloudsmith.com)
> newtricks:BuckyDemo ted$
>
> Basically I just wanted to get the stuff to do the Hello XML example
> in the Bucky book.
>
>  -ted
>
> On Sun, Aug 9, 2009 at 1:28 AM, Ted Kubaska<ted.kubaska@xxxxxxxxx> wrote:
>
>
> 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
>
>
>
>
>
> _______________________________________________
> ecf-dev mailing list
> ecf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ecf-dev
>
>



-- 
 -Ted