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

Page text matches

  • ...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
  • ...rom technical specifications of extension points to tutorials on extending Buckminster. [[Category:Buckminster]]
    3 members (0 subcategories, 0 files) - 13:44, 25 March 2009
  • ...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

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Back to the top