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

Page title matches

Page text matches

  • * [[DTP Development Environment]] * [[SQL Development Tools | SQL Development Tools]]
    7 KB (897 words) - 19:08, 13 September 2013
  • * And if possible, an easy, medium or hard rating of each project. ...with content provided by other projects. Please be sure to follow branding guidelines (e.g. "Eclipse Dash", not "Dash"). Putting things in alphabetical order see
    15 KB (2,264 words) - 20:11, 1 March 2023
  • ...es) for the associated Project and are expected to influence the Project's development. ...and responsibilities see [[COSMOS_Roles_and_Responsibilities|COSMOS Roles and Responsibilities]].
    2 KB (308 words) - 15:15, 20 April 2009
  • ...|How To Behave]]''' Practical advice on how to ask questions, report bugs, and be generally successful in your interactions with an Open Source Project. ...ugzilla] to track bugs and features. Please read the [[Bug Reporting FAQ]] and then sign up for a bugzilla account to join in the fun.
    21 KB (3,040 words) - 13:31, 22 August 2023
  • This page is to document processes and procedures for providing improved coordination of update sites provided by ...ts reviewed and discussed and improved by others, it will become a 'plan'. And then, eventually, once the plan seems to be
    20 KB (3,151 words) - 22:53, 26 August 2007
  • ===API Guidelines === ...clipse.org/articles/Article-API-Use/index.html How to use the Eclipse API] Guidelines for using Eclipse APIs to ensure that your code will keep working as Eclips
    3 KB (345 words) - 10:44, 7 February 2024
  • ...ndicate APIs that are still under development and subject to change. These guidelines are also useful for API clients who want to know about the state of a given ...er this point, so this document outlines guidelines for both phases of the development cycle.
    8 KB (1,286 words) - 08:05, 1 February 2024
  • * Ensure that project sets and meets schedules. * Ensure that rampdown, triage, and update site delivery occurs.
    5 KB (730 words) - 14:42, 16 August 2012
  • ...enon. In this chapter we discuss what Eclipse is and who is involved in it and give you a glimpse of how large a community has put its weight behind this ...y discussions in newsgroups and mailing lists, and a long list of articles and books that address the platform. The following pages will give you a roadma
    40 KB (6,857 words) - 07:52, 27 February 2024
  • ...involved with the community is to use the Eclipse IDE for your development and explore what the many [http://www.eclipse.org/projects/listofprojects.php E ...e0fd8dc newcomer forum]. The forum is monitored by seasoned Eclipse users and developers who are happy to answer your questions.
    7 KB (1,087 words) - 12:04, 23 April 2015
  • ...nd implementation for event handling, process orchestration, data mapping, and message exchange. ...t as the user’s request traverses other tools that may be invoked in the process of executing a ServiceFlow.
    18 KB (2,963 words) - 20:22, 6 September 2006
  • ...d quickly find quality and relevant complementary Eclipse-based technology and services. This document describes the mission, scope, and governance for the EPIC Component.
    6 KB (959 words) - 15:29, 17 July 2006
  • discussion and it has never been part of any of our processes. Incubator graduation is governed entirely by the Eclipse rules and guidelines.
    2 KB (342 words) - 23:05, 3 September 2009
  • * [http://www.eclipse.org/org/councils/themes.html v1 Themes and Priorities (2005)] * [http://www.eclipse.org/org/councils/roadmap_v2_0/themes_v2_0.php v2 Themes and Priorities (2006)]
    22 KB (3,334 words) - 11:08, 1 March 2011
  • '''Themes and Priorities for Q4 2006 and Q1 2007''' ...and priorities for EPIC. It is expected we will execute on these themes and priorities over the next 6 months.
    7 KB (1,039 words) - 11:17, 27 September 2006
  • Proposing to branch this week and use head for 4.7 while we rampdown on 4.6.2. * We are in lead approval for checkins already and will be in PMC approval mode
    4 KB (691 words) - 19:47, 11 January 2010
  • ...ks one would need to accomplish to become a "plugged-in" member of the GMF development community. ...mailing list! Development topics, architectural discussions, contribution and Committer voting, etc. all take place on the developer mailing list.
    27 KB (4,291 words) - 06:31, 6 August 2012
  • ...those to JWT, enrich them with technical details and then deploy them on a process engine. Therefore, we develop transformations from BPMN to JWT, from JWT to == Get and use Java Workflow Tooling! ==
    3 KB (410 words) - 09:02, 23 May 2013
  • This has been recorded in the [[COSMOS dev process|COSMOS Development Process]] ...e.g. SDD, are beginning to develop their use cases. While they are in the process of defining these, we've established a work area for them to hash out the d
    39 KB (6,082 words) - 12:34, 1 April 2009
  • ...to adding and updating wiki documentation. Committers review all changes and will update them as needed. Evolving the documentation with integrator con ...listing your Mylyn integration on the '''[[Mylyn/Extensions]]''' wiki page and in the '''[http://marketplace.eclipse.org/ Eclipse Marketplace]'''.
    62 KB (9,005 words) - 13:39, 20 June 2019
  • [http://www.eclipse.org/eclipse/development/index.php eclipse dev], [http://git.eclipse.org/c/mylyn/ source repository] ...s are mature components that are supported by the Mylyn project committers and may be distributed as part of the [http://www.eclipse.org/downloads/ Eclips
    65 KB (10,332 words) - 12:53, 17 November 2017
  • ...ments/Eclipse%20Development%20Process%202003_11_09%20FINAL.pdf Development Process]. General guidelines for using Bugzilla on Eclipse projects is found [http://www.eclipse.org/pro
    6 KB (1,011 words) - 16:35, 5 June 2007
  • ...ing project primarily represents a roll-up of constituent project features and API, although there are some organizational themes called out at the top-le ...xpressed an interest in the project. That said, the success of the project and its deliverables is soley dependent upon the contributions from its communi
    15 KB (2,230 words) - 22:12, 7 November 2008
  • We will hold daily conference calls at 11:00am and 5:00pm EST. Don Ebright (Jan 8 - Jan 9 morning and early afternoon)
    17 KB (2,753 words) - 09:39, 28 January 2008
  • ...Development Process]. The official approved version, along with guidelines and interpretations, is on the Eclipse website at [http://www.eclipse.org/proje ...s - the initial version and the community comments are here: [[Development Process 2006 Revision]]
    41 KB (6,248 words) - 21:13, 17 March 2007
  • ....org]. Note that the PMS colour listed for the 2-colour logo, 187-2, is a process (4-colour, CMYK) colour, not a matte colour. ...an Eclipse Day or Eclipse Summit event, we have some guidelines, templates and sponsorship details on the [[Eclipse_Day | Eclipse Day page]].
    6 KB (884 words) - 10:15, 28 February 2018
  • The event will start Wednesday January 24th at 1:00 and end Friday, January 26th at mid day. *The La Quinta is across the street (west) and has a visible swimming pool.
    15 KB (2,148 words) - 18:55, 25 January 2007
  • This page is information for active committers and contributors about Internationalization of the Higgins project. ...or the active proposal and implementation of the beta Internationalization guidelines for Higgins projects.
    7 KB (1,046 words) - 10:56, 25 July 2008
  • ...eclipsezone.com/eclipse/forums/t84076.rhtml 3]]. Program committee members and senior Eclipse leaders have posted a number of replies [[http://eclipse-pro ...[submitter], as with the other PC members, is a reasonable and fair person and will do what is right for the attendees.
    5 KB (705 words) - 15:23, 1 August 2007
  • ...2-13, 2006 to discuss build systems and release engineering around Europa (and Eclipse in general). ...have taken action items (recorded below) to improve the build and release process for Eclipse projects in general. This documentation is a recommendation by
    24 KB (3,681 words) - 13:53, 9 October 2009
  • ...pment Conventions and Guidelines] we should follow the following addtional guidelines. ...single entity, and you are not from that entity, you should add the line 'and others' to the copyright statement.
    2 KB (251 words) - 12:27, 27 May 2008
  • ...[Development Process 2006 Revision Final]]. That version was presented to, and approved by, the Board on January 17, 2007. The official version is located ...eted and accepted by the Board, the EMO will write a new set of guidelines and interpretations to replace the 2005 web pages [http://www.eclipse.org/proje
    77 KB (12,253 words) - 21:13, 17 March 2007
  • ...l be integrated in the Eclipse SDK and will be used in the automated build process. Specifically, the tooling is designed to do the following: * Provide new Javadoc tags and code assist to annotate types with special restrictions.
    2 KB (342 words) - 15:11, 5 June 2014
  • ...ters and especially DTP project leads. This list contains both reoccurring and non-reoccurring work items for the [http://wiki.eclipse.org/index.php/DTP_1 Everyone working on DTP should read and understand the following from the EMO. Note that these areas evolve, so per
    11 KB (1,828 words) - 23:22, 26 August 2007
  • =Guidelines for Incubation Phase= ...s.php#6_2_3_Incubation 6.2.3 Incubation Phase]" in the Eclipse Development Process.
    10 KB (1,438 words) - 22:26, 17 June 2020
  • ...ry for third party libraries that are approved for use in Eclipse projects and are to be used/distributed as bundles. If the incoming libraries are not al == Does Orbit replace or affect the Eclipse Foundation legal process? ==
    8 KB (1,257 words) - 12:40, 3 April 2023
  • ...Revision]] page was becoming a little difficult to read with conversations and old comments interspersed with the text, thus I moved some of the old comme ...kinds of criteria: Required, Recommend, and Suggested. I took their advice and changed to two more clearly separate names. ''--Bjorn Freeman-Benson''</div
    5 KB (808 words) - 18:07, 4 November 2006
  • ...rounds]] | [[TM 2.0 Known Issues and Workarounds]] | [[TM/3.0 Known Issues and Workarounds]] ...t. You can now use your [https://bugs.eclipse.org/bugs/ bugzilla] username and password to gain access.
    41 KB (6,808 words) - 07:53, 19 July 2016
  • == WTP Development Status Meeting 2006-11-16 == ;Announcements and Reminders
    11 KB (1,712 words) - 18:08, 16 November 2006
  • == WTP Development Status Meeting 2006-11-30 == ;Announcements and Reminders
    19 KB (2,841 words) - 17:22, 30 November 2006
  • == WTP Development Status Meeting 2006-12-07 == ;Announcements and Reminders
    20 KB (3,007 words) - 18:12, 7 December 2006
  • * Working on documenting interfaces and refining issues related to adopters with different data types * Gave brief overview of RM to Merri and Mark, members of the SDD team who are wanting to ramp up on SML
    24 KB (3,927 words) - 11:48, 7 November 2008
  • == WTP Development Status Meeting 2007-01-04 == [[#Announcements | Announcements and Reminders]]<br>
    22 KB (3,355 words) - 17:16, 4 January 2007
  • == WTP Development Status Meeting 2007-01-11 == [[#Announcements | Announcements and Reminders]]<br>
    24 KB (3,479 words) - 17:00, 11 January 2007
  • == WTP Development Status Meeting 2007-01-18 == === Announcements and Reminders ===
    25 KB (3,582 words) - 15:58, 18 January 2007
  • == WTP Development Status Meeting 2007-01-25 == ::1/26 - WTP PMC review and approval will begin for any changes.
    24 KB (3,573 words) - 11:52, 29 January 2007
  • == WTP Development Status Meeting 2007-02-01 == ...the edit next to your team's content. This should prevent any collisions and subsequent clearing of content. John following up with the webmaster to ge
    25 KB (3,633 words) - 18:31, 5 February 2007
  • ...ated with the project, and how to install, configure and use the necessary development environment. “up and running” faster and it allows them to contribute to the
    44 KB (6,811 words) - 13:47, 21 October 2015
  • ** 6 short talk submissions and 6 slots, so I accepted all. ...clipsecon.org/show_bug.cgi?id=3795 3795] || Eclipse as foundation for J2ME development tools || Christian withdrew this one.
    6 KB (903 words) - 13:12, 8 February 2007
  • == WTP Development Status Meeting 2007-02-08 == ...to roll out the 1.9.X version this quarter and with it, conflict detection and merging tools.
    25 KB (3,659 words) - 17:10, 8 February 2007

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

Back to the top