Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Search results

Page title matches

  • ...ions for each Buckminster extension, examples and guidelines for extending Buckminster. ==Extending the Buckminster framework==
    402 bytes (45 words) - 09:50, 18 January 2008
  • {{Backlink|Buckminster Project}} ...tensions. It is really beyond the scope of the documentation provided with Buckminster to cover the general plug-in mechanism of Eclipse. Please see the Eclipse d
    2 KB (343 words) - 10:24, 19 July 2007
  • #redirect [[Extension Point (Buckminster)]]
    43 bytes (4 words) - 03:05, 13 November 2006
  • {{Backlink|Buckminster Project}} ...pecification Extension allows you to decorate a [[Component Specification (Buckminster)|Component Specification]] in a powerful way. It is possible to add, overri
    470 bytes (63 words) - 10:02, 18 January 2008

Page text matches

  • ...ki. This is the Wiki home page for the [http://www.eclipse.org/buckminster Buckminster Component Assembly project], an [http://www.eclipse.org/tools/eclipsetools- Buckminster is a component resolution & materialization framework. Its purpose is to ge
    3 KB (489 words) - 08:53, 2 August 2010
  • ==Buckminster Dependency Specification== <p>Buckminster creates component dependency graphs using a Dependency Specification,
    3 KB (426 words) - 06:06, 12 December 2005
  • ==Buckminster Resource Map== <p>Each Buckminster installation will utilize one or more <i>resource maps</i> (an XML
    7 KB (1,122 words) - 06:27, 12 December 2005
  • {{Backlink|Buckminster Project}} ...erializing and publishing component specifications. It provides samples of Buckminster code as XML fragments, and illustrates common usage scenarios.
    67 KB (9,899 words) - 20:05, 14 February 2009
  • ...r Architecture]]''' - provides an overview of the architectural details of Buckminster. ...know more about "How Buckminster does things" rather than "what it does". Extension point implementers should find this useful.
    823 bytes (122 words) - 07:27, 31 August 2007
  • ...ions for each Buckminster extension, examples and guidelines for extending Buckminster. ==Extending the Buckminster framework==
    402 bytes (45 words) - 09:50, 18 January 2008
  • ** Martin -- Added Mutex; I-builds fixed; Discussions with Buckminster; Simple renamings **** 248 matches for "SystemFactory" (case insensitive, not whole word) - extension points, docs, local variables
    9 KB (1,295 words) - 11:09, 16 August 2006
  • {{Backlink|Buckminster Project}} Through 2007, the Project will aim for a significant elaboration or extension of functionality at roughly three-month intervals. Our roadmap for the ne
    2 KB (233 words) - 23:45, 14 February 2009
  • {{Backlink|Buckminster Project}} ...tensions. It is really beyond the scope of the documentation provided with Buckminster to cover the general plug-in mechanism of Eclipse. Please see the Eclipse d
    2 KB (343 words) - 10:24, 19 July 2007
  • {{Backlink|Buckminster Project}} This page has been archived. Go to [[Buckminster UI Guide]] instead.
    9 KB (1,494 words) - 10:01, 24 January 2008
  • <noinclude>{{Backlink|Buckminster Project}} ...d it can read individual files, and materialize component contents for a [[Buckminster Version Selector|Version Selector]].
    4 KB (541 words) - 03:08, 26 June 2008
  • <noinclude>{{Backlink|Buckminster Project}} ...erence appoints a public attribute in a CSPEC of another component via a [[Buckminster CSPEC Dependency|dependency]]. The execution of an ''action'' will often pr
    4 KB (595 words) - 15:02, 17 July 2007
  • {{Backlink|Buckminster Project}} ...nderstands the content of a component and is responsible for producing a [[Buckminster Component Specification]] (CSPEC) containing dependency information for the
    8 KB (1,159 words) - 11:43, 31 May 2012
  • <noinclude>{{Backlink|Buckminster Project}} A [[Buckminster Version Converter|Version Converter]] is responsible for (bidirectional) tr
    2 KB (368 words) - 10:37, 19 July 2007
  • <noinclude>{{Backlink|Buckminster Project}} ...will be asked to parse and compare the text between the delimiters in a [[Buckminster Version Designator|Version Designator]].
    3 KB (399 words) - 10:38, 19 July 2007
  • Buckminster XML Schemas can be found at _www.eclipse.org/buckminster/schemas/_, but you are not allowed to browse the catalog. ====[[Component Specification (Buckminster)|CSPEC]] and its extension====
    920 bytes (109 words) - 10:23, 19 July 2007
  • ...ituations where it's not possible to use a graphical user interface. Thus, Buckminster recognizes the need to provide a way to do these things from the command li ...any other aspects of Buckminster (and Eclipse in general, of course) it is extension based, thus making it easy to plug in new commands to work seamlessly toget
    2 KB (229 words) - 19:12, 23 March 2009
  • To allow a user to do anything useful with a 'raw' [[Buckminster Headless]]. Buckminster has a minimum, core command set. ...fast way to get a reminder on what command to use. Or, to verify that the extension command just written was actually linked in properly.
    2 KB (250 words) - 15:00, 17 July 2007
  • buckminster helloworld ...which is always prefixed to the name) and 0-M aliases are declared in the extension point along with an implementation class. The implementation class must der
    3 KB (411 words) - 10:17, 18 January 2008
  • ==Declare the command using the command extension point== ...on the <tt>org.eclipse.buckminster.cmdline</tt> plugin in order to see the extension point. Use the plugin manifest editor to add this dependency.
    6 KB (937 words) - 11:32, 28 August 2009
  • Below is a reasonably current version of an early design document for [[Buckminster Headless]], describing reasons why the boot process, in particular, is some =Goal: Buckminster must be possible to run from the command line, a.k.a. headless=
    9 KB (1,494 words) - 10:15, 18 January 2008
  • {{Backlink|Buckminster Project}} This examples shows several Buckminster features in action. What these components actualy do when they are executed
    12 KB (1,862 words) - 19:31, 7 December 2011
  • ==Buckminster Progress== **Need for new functionality in Buckminster
    3 KB (475 words) - 13:28, 17 October 2006
  • #redirect [[Extension Point (Buckminster)]]
    43 bytes (4 words) - 03:05, 13 November 2006
  • {{Backlink|Buckminster Project}} * The Buckminster Project Wizard helps the user using Buckminster with a project. It provides sanity checking/health status reporting, and he
    5 KB (875 words) - 05:46, 30 November 2006
  • {{Backlink|Buckminster Project}} ...pecification Extension allows you to decorate a [[Component Specification (Buckminster)|Component Specification]] in a powerful way. It is possible to add, overri
    470 bytes (63 words) - 10:02, 18 January 2008
  • ...nce, making it difficult for someone starting to use Buckminster. Where is Buckminster? How do I use it? == Buckminster View ==
    2 KB (264 words) - 05:42, 30 November 2006
  • * '''MUST''' define appropriate extension points to enable third-party tool configuration to be added to the model. ...Maven's POM (http://maven.apache.org/ref/current/maven-model/maven.html), Buckminster's Component Specification model (CSPEC), DOAP (http://usefulinc.com/doap) a
    20 KB (2,817 words) - 17:46, 1 February 2012
  • ...formatted using the (new) native Kepler project model syntax as '''kmodel-extension''' files, since they are meant to catch project metadata that cannot be sto ...l be integration of existing technologies from both Eclipse projects (e.g. Buckminster, PDE, ALF, Corona, EMFT, ECF, Phoenix, etc), and other open source communit
    6 KB (808 words) - 17:46, 1 February 2012
  • {{Backlink|Buckminster Project}} ...on with Eclipse PDE-build|Tight integration with Eclipse PDE-build]]</b> - Buckminster is now able to build the org.eclipse.rcp feature from source using releng s
    8 KB (1,216 words) - 09:29, 18 January 2008
  • =Setting up Subclipse for committer access to the Buckminster repo= ...SVN repository view: "svn+ssh://dev.eclipse.org/svnroot/tools/org.eclipse.buckminster"
    13 KB (2,300 words) - 08:22, 10 September 2008
  • ...cally out of Maya's specific implementation scope. An example of one such extension point could be license enforcement and tracking. ...re has architectural and development responsibility for large parts of the Buckminster framework. Thomas ia also an initial committer to the Spaces and Kepler pr
    10 KB (1,349 words) - 08:59, 10 April 2007
  • Buckminster passes two types of arguments to the Ant actor: ...d script registered using the ''org.eclipse.buckminster.ant.buildScripts'' extension point.
    5 KB (704 words) - 13:37, 25 March 2009
  • {{Backlink|Buckminster Project}} =Welcome to Buckminster=
    43 KB (7,063 words) - 10:24, 18 January 2008
  • {{Backlink|Buckminster Project}} The purpose of this document is to provide a concise overview of the Buckminster framework. It will outline the main concepts, usage patterns and applicatio
    13 KB (1,925 words) - 09:30, 22 June 2007
  • {{Backlink|Buckminster Project}} =Welcome to Buckminster=
    46 KB (7,380 words) - 21:48, 23 April 2011
  • {{Backlink|Buckminster Project}} <td>The wizards for new cspec and cspec extension uses incorrect filenames</td>
    433 bytes (63 words) - 09:29, 18 January 2008
  • {{Backlink|Buckminster Project}} The purpose of this document is to provide a concise overview of the Buckminster framework. It will outline the main concepts, usage patterns and applicatio
    13 KB (1,925 words) - 20:39, 14 February 2009
  • Each provider of spaces creates a plugin for a "Spaces Service Provider" extension point. When a user wants to add a <i>Space Resource</i> to a project, the f ...an have a small set of hardwired ways of publishing, but this should be an extension point in the future. The Wizard UI then gets slightly more complex as the d
    18 KB (2,928 words) - 19:24, 20 January 2008
  • =====Buckminster===== |'''URL:''' || [http://www.eclipse.org/buckminster Buckminster web site]
    14 KB (2,063 words) - 21:12, 16 January 2008
  • ...s and API's that we are truly happy with. So a thorough review of both our extension points and public API's are required. In addition to this we need to begin This is here to ensure that we get back to full feature parity with our new Buckminster based build system. The ability to have full site generation together with
    3 KB (516 words) - 05:19, 10 January 2008
  • ...s he suspected there was some network problems. Adrian also asked that the buckminster build be rolled into an automated build framework such as cruisecontrol so ...hat features we should be developing, when we intend to finalize API's and extension points etc. Adrian agreed to get this started immediately. This will be cir
    2 KB (370 words) - 07:43, 3 January 2008
  • {{Backlink|Buckminster Project}} Below are some brief guidelines with regard to adding categories to new Buckminster Wiki pages. Some basic rules:
    4 KB (517 words) - 23:37, 14 February 2009
  • ** The addspace wizard extension point is used to add a wizard for a "providerScheme" - the "providerScheme" ...n extension point to their headless space provider plugin - if there is an extension it is used to obtain needed password, if it is not extended, the provider w
    19 KB (3,221 words) - 16:53, 21 January 2008
  • ...lowing to build annotations on any URI in the workspace with the necessary extension point to further integrate it for dedicated purpose. The current POC allows ...workspace materialization, and when used in conjunction with Tigerstripe's Buckminster headless support.
    12 KB (1,929 words) - 10:39, 19 November 2008
  • =Setting up Subclipse for committer access to the Buckminster repo= # Copy the contents of the private key (the file named mykey with no extension) to your clipboard and paste it into temporary file on your local computer.
    12 KB (2,120 words) - 10:29, 17 April 2008
  • ...c...). In this version, the configuration will still be handled through an extension point, although we plan to provide a proper UI for it. We also plan to provide a Buckminster integration to allow users to pull down a set of Model components through t
    6 KB (956 words) - 15:23, 8 September 2008
  • ...self hosted mode. Checkout the project "org.equinox.p2.authoring" from the Buckminster SVN found at: svn://dev.eclipse.org/svnroot/tools/org.eclipse.buckminster/trunk. (An Eclipse 3.4 with ecf and ecf file transfer is needed). This arti
    11 KB (1,791 words) - 10:21, 25 September 2008
  • {{Backlink|Buckminster Project}} {{Backlink|Helping_Out_(Buckminster)}}
    11 KB (1,543 words) - 11:52, 13 December 2008
  • * Buckminster configuration ## the parser has to support the extension. Particularly, there must be the possibility to add some tags from SVG name
    7 KB (992 words) - 05:49, 27 May 2010
  • Buckminster integration allows IAM users to materialize Maven dependencies in their Ecl ==What is Buckminster==
    19 KB (2,479 words) - 09:24, 19 May 2011
  • ** The ability to leverage '''Buckminster''' and '''Maven''' to facilitate simplified workspace resolution and contin * '''Equipment-model''': a Tigerstripe model that is an extension of the "common-model" to model a ''Router'' and its ''Ports''. This project
    6 KB (820 words) - 06:23, 20 November 2008
  • New extension points allow third parties to develop and register search engines for their = [[IAM Buckminster Integration]] =
    4 KB (543 words) - 11:24, 27 August 2010
  • * enhancements (mickael) : custom property view extension, choose jar, widgets ; put them in jwt-we-plugins : one dir of plugins and ** dialog in editor page using an extension point TODO in bugzilla
    3 KB (484 words) - 09:32, 8 December 2008
  • {{Backlink|Buckminster Project}} Buckminster is also packaged in a so called 'Headless' command line oriented version su
    5 KB (781 words) - 05:24, 17 July 2009
  • ...ert.de/blog/eclipsercp/rcp_builds/ Building Eclipse RCP applications using Buckminster and Hudson]. <br> *The [http://wiki.hudson-ci.org/display/HUDSON/Buckminster+PlugIn Buckminster PlugIn] for Hudson
    13 KB (2,047 words) - 07:12, 20 August 2020
  • ...framework for generating and orchestrating scripts used to build plug-ins. Buckminster has been developed primarily to automate component assembly and provisionin Buckminster and PDE Build are directly relevant to the work of this project, and we int
    8 KB (1,171 words) - 09:43, 1 September 2010
  • * Providing proxy units that provide the original as a capability - the extension is done on the proxy ...n on the syntax. The b3 build file has the context as its root, and as the extension of a component has no business providing advice outside of the build unit i
    7 KB (1,319 words) - 15:27, 19 April 2010
  • * embedding advice in units (compared to buckminster CSPEX) ...les in this language should be ".b3" files (no variations like ".b3x" for extension - analogous with ".java" files containing classes or interfaces).
    1 KB (218 words) - 11:14, 8 October 2009
  • *Visualization Extension for WST *Visualization Extension for PDT
    45 KB (6,657 words) - 13:53, 17 June 2010
  • '''Clearing extension of Association Classes (Bugzilla [https://bugs.eclipse.org/bugs/show_bug.cg .../show_bug.cgi?id=253292 253292] - Add Tigerstripe Generator support to the Buckminster integration plug-in<br/>
    7 KB (1,027 words) - 16:57, 22 December 2010
  • - Buckminster is another tool that has come into use for builds recently (Ganymede/Galile - B3 is an iteration upon Buckminster. Refining what was learned and strengthening its deficiencies. It is, howev
    6 KB (893 words) - 12:11, 4 April 2011
  • The portfolio targets first Hudson and Buckminster. ...metamodel extended by build extension metamodels (see Figures 2 and 3). An extension metamodel enables to address a specific build concern.
    3 KB (475 words) - 19:12, 18 April 2011
  • ...''' ('''KDM''', an ''OMG/ADM'' standard), corresponding discoverers, a KDM extension for weaving models of code with models of physical resources, a transformat MoDisco uses a '''Buckminster'''-based system to build and promote versions.<br/>
    10 KB (1,388 words) - 08:51, 29 May 2012
  • ...acet provides a generic and extensible MDE framework to support meta-model extension and model customization. EMF Facet uses a '''Buckminster'''-based system to build and promote versions.<br/>
    8 KB (1,224 words) - 12:59, 20 June 2012
  • ...xecution). Extending the core model and behaviors is the first type of EGF extension. For instance, to conduct a generation, EGF enables to support Java tasks; ...tor) and to generate all the scripts for a build platform, i.e. Hudson and Buckminster today. For instance, the EGF Helios and Indigo build chains are realized wi
    7 KB (993 words) - 05:09, 27 July 2011
  • Participant conference extension: '''701 then enter pin: 51968''' ** Eike: Build uses buckminster, there is no target definition - would hate to maintain two redundant artif
    6 KB (875 words) - 06:12, 21 December 2012
  • The portfolio targets first Hudson and Buckminster. ...metamodel extended by build extension metamodels (see Figures 2 and 3). An extension metamodel enables to address a specific build concern.
    3 KB (490 words) - 11:46, 1 September 2011
  • ..., Java task, Ant task) and tools (e.g., Acceleo, ATL, JET), or any further extension, are engine extensions.<br> ...tor) and to generate all the scripts for a build platform, i.e. Hudson and Buckminster/Jenkins today. The EGF build chains are realized with this portfolio.<br>
    9 KB (1,286 words) - 08:38, 5 June 2012
  • ...''' ('''KDM''', an ''OMG/ADM'' standard), corresponding discoverers, a KDM extension for weaving models of code with models of physical resources, a transformat MoDisco uses a '''Buckminster'''-based system to build and promote versions.<br/>
    11 KB (1,602 words) - 04:16, 6 June 2012
  • ...acet provides a generic and extensible MDE framework to support meta-model extension and model customization. EMF Facet uses a '''Buckminster'''-based system to build and promote versions. We plan to move to Tycho for
    16 KB (2,345 words) - 11:14, 20 March 2013
  • * Build based on Buckminster * Some ‘discouraged access’ warnings in cases of metamodel extension (plug-in compatibility restricted to minor version)
    5 KB (701 words) - 10:29, 5 June 2012
  • ...on of the project is managed in an Eclipse git repository and built, using Buckminster, on the Hudson installation at Eclipse. | Extension::isRequired
    33 KB (4,307 words) - 10:25, 21 February 2014
  • * Participant conference extension: 717, then enter pin 57932# ...Henrik Lindberg, Thomas Hallgren http://www.eclipse.org/buckminster/
    5 KB (535 words) - 13:04, 12 February 2014
  • * The UML2 build system has been migrated from Buckminster to Tycho (see bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=526568 526 ...has been added to the <code>org.eclipse.uml2.uml.generated_package</code> extension point (see bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=529564 529564
    6 KB (930 words) - 11:11, 14 May 2018
  • * Migration of the build from Buckminster to Tycho ...//bugs.eclipse.org/499509 499509] OCL is now built using Tycho rather than Buckminster
    8 KB (1,080 words) - 04:18, 2 July 2018

Back to the top