Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Search results

  • ...nt tools] (JDT), [http://eclipse.org/pde Plug-in Development Environment] (PDE), [[e4]], [http://eclipse.org/equinox Equinox], and [[Orion]]. The Eclipse * [[PDE]]
    2 KB (213 words) - 14:30, 20 November 2020
  • == API tests == ...n Numbering|version numbers]]. For more details on these tests, refer to [[PDE/API_Tools]].
    19 KB (2,890 words) - 02:29, 8 May 2022
  • This chapter should get you going. We also included some FAQs for plug-in developers who have already written plug-ins and want to get started with plug-in deve ...platform. This chapter focuses on user-level issues of interest to plug-in developers as users or as enablers for other users of the platform.
    40 KB (6,857 words) - 07:52, 27 February 2024
  • '''API Comparison Tool – Developer’s docs''' The tool helps developers track API changes. It allows:
    8 KB (1,230 words) - 16:10, 31 August 2007
  • While Eclipse has been very successful with Java developers on Windows systems, we endeavour to provide platform support for additional ...are for the Windows OS. Windows 7 is important as both a platform used by developers, as well as one to which the resultant applications and/or products will be
    22 KB (3,334 words) - 11:08, 1 March 2011
  • :#Learn about the tools/projects you use from their [http://www.eclipse.org/projects/ websites] or ...the pre-configured packages (eg., for Java, JEE/Web, C/C++, or RCP/Plug-in developers).
    83 KB (13,239 words) - 13:08, 7 February 2024
  • ...use, we highly recommend using the '''[[API Tooling User Guide|Eclipse API Tools]]. ...ompatibility of API is maintained with preceding major release, additional API is added and internals may change.
    62 KB (9,005 words) - 13:39, 20 June 2019
  • * PDE/Build ** API fixes
    7 KB (1,141 words) - 13:58, 27 March 2007
  • Those building both closed and open source tools on top of Mylyn may be interested in evolving the Mylyn APIs to ensure that ...articular to a specific tool or technology and leave them open for ongoing API or UI discussion needs.
    65 KB (10,332 words) - 12:53, 17 November 2017
  • {{PDE}} Welcome to the '''Plug-in Development Environment (PDE)''' Wiki Page.
    1 KB (174 words) - 16:30, 29 August 2013
  • ...uilds: see the [http://www.eclipse.org/projects/project-plan.php?projectid=tools.mylyn project plan] * Eclipse IDE for Java Developers: all of Mylyn except Team integration (e.g. automatic change sets) integrat
    112 KB (17,765 words) - 07:51, 20 April 2018
  • ...rent and predictable development cycle; Europa is about developers helping developers serve the whole Eclipse community. ...ipse.org/datatools DTP]<br/>(Connectivity, Enablement,<br/>Model Base, SQL Tools) || John Graham || || +1 || [[DTP_1.5_Rampdown_Policy | Policy]] || [http:/
    22 KB (3,201 words) - 21:25, 24 June 2014
  • ...rdized adoption of these practices. We have discovered we are replicating tools across projects and this wastes valuable committer time. We want to encoura ...ture versions between releases (TPTP, WTP, BIRT and platform teams written tools.)
    24 KB (3,681 words) - 13:53, 9 October 2009
  • * McQ: '''New People Coming Online''' to work on SWT, JDT, PDE. ** Foundation to employ developers to "do whatever is best for the Platform" : Who decides on features, and wh
    24 KB (3,803 words) - 11:31, 8 January 2014
  • ...n numbers, missing or incorrect <code>@since</code> tags, and usage of non-API code between plug-ins. The tooling will be integrated in the Eclipse SDK an * Identify usage of non-API code between plug-ins.
    2 KB (342 words) - 15:11, 5 June 2014
  • tools to manage remote systems under a single, consistent user interface. * Remote System Explorer End-User Runtime (General Purpose Tools; Mobile and Device Development; TM and RSE Main Features)<!-- same versions
    41 KB (6,808 words) - 07:53, 19 July 2016
  • ...the beginnings of a discussion about what sorts of data elements different tools ...rlaps between Kepler and other Eclipse projects, in order to have a common API and set of providers to adapt external project information into the system.
    5 KB (735 words) - 17:45, 1 February 2012
  • ...nsistency across grouped or related applications , and makes it easier for developers to integrate these projects with one another. Organizations can reap great ...the same essential requirements, such as supporting its users (architects, developers, project managers, etc.), tracking software issues and their respective res
    20 KB (2,817 words) - 17:46, 1 February 2012
  • ...y, I think, several methods and several tools, some nicely built in to the PDE or JDT ... some built in to build processes. The strategy and details of th # The eclipse Project model and nested projects: when developers lay out the directory structure on non-eclipse projects, they often use a t
    4 KB (615 words) - 14:38, 15 July 2013
  • ...ort descriptions of the features available in the framework for JUnit test developers. ...nnectivity or do you '''develop''' plugin(s) based on RSE and/or using RSE API?''
    19 KB (2,828 words) - 09:24, 2 January 2007

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

Back to the top