https://wiki.eclipse.org/api.php?action=feedcontributions&user=Benjamin.cabe.anyware-tech.com&feedformat=atomEclipsepedia - User contributions [en]2024-03-19T06:46:01ZUser contributionsMediaWiki 1.26.4https://wiki.eclipse.org/index.php?title=PDE/Plan/3.6&diff=171780PDE/Plan/3.62009-09-22T21:13:16Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div>{{warning|Unofficial Planning Document|This is an unofficial document used by the PDE team to help with the planning process. Items on this list aren't guaranteed to be found in a release.}}<br />
== Schedule ==<br />
<br />
Dates are listed in the Eclipse Platform Releng Calendar (view as [http://www.google.com/calendar/ical/kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com/public/basic.ics iCal]) <br />
<br />
=== M1 - August 7th ===<br />
<br />
{{PlanItem|Use Wiki for meetings/planning||Complete}}<br />
{{PlanItem|Combine mailing lists|281272|Complete}}<br />
{{PlanItem|Handle xml parse errors in Ctx Help editor|284496|Complete}}<br />
{{PlanItem|Handle xml parse errors in ToC editor|280119|Complete}}<br />
<br />
=== M2 - September 18th ===<br />
<br />
{{PlanItem|Prepare 3.5.1 Fixes||Complete}}<br />
{{PlanItem|Create 3.6 Plan||InProgress}}<br />
{{PlanItem|Support spell checking in Cheat Sheet, TOC and Context Help Editor|286203|Complete}}<br />
{{PlanItem|User interface for generating API Use Reports|280467|Complete}}<br />
{{PlanItem|Override internal/API package name patterns for API use scan|289139|Complete}}<br />
<br />
=== M3 - October 30th ===<br />
<br />
{{PlanItem|Support headless launching for Eclipse and Equinox applications|278845|Complete}}<br />
{{PlanItem|Manage all target contents with a p2 profile|287619|Investigate}}<br />
* Work will continue into M4/M5<br />
{{PlanItem|Synchronize target contents with Java search|175134|InProgress}}<br />
{{PlanItem|Provision metadata for launching (p2 self-hosting)|250126|Investigate}}<br />
{{PlanItem|PDE build should honor project settings||Investigate}}<br />
* Add support for custom extension point attributes ({{bug|227055}})<br />
* File specific encodings ({{bug|155015}}, {{bug|260997}})<br />
* build.properties validation ({{bug|286808}}, {{bug|276931}}, {{bug|253950}})<br />
{{PlanItem|API Use Report enhancements||InProgress}}<br />
* A single line for each different piece of API being used {{bug|289903}}<br />
* Find migration issues based on use scan {{bug|280463}}<br />
* Compare API use reports {{bug|266903}}<br />
{{PlanItem|Graduate the PDE Bundle Visualizer|106676|InProgress}}<br />
<br />
=== M4 - December 11th === <br />
<br />
{{PlanItem|Better feature management in targets|284882|Investigate}}<br />
{{PlanItem|Improve feature management in the workspace|284887|Investigate}}<br />
{{PlanItem|Use features to manage launch contents (feature based launching)|284885|Investigate}}<br />
{{PlanItem|Embed source repository information in bundles|243582|Investigate}}<br />
{{PlanItem|PDE build should honor project settings||Investigate}}<br />
* Compiler settings ({{bug|169740}}, {{bug|154292}})<br />
{{PlanItem|Performance improvements for API tools||Investigate}}<br />
* Incremental build {{bug|233643}}<br />
* Memory foot print {{bug|231936}}<br />
<br />
=== M5 - January 29th ===<br />
<br />
{{PlanItem|Enhance error reporting from PDE build|290172|Investigate}}<br />
{{PlanItem|Prepare 3.5.2 Fixes||Investigate}}<br />
<br />
=== M6 - March 12th (API Freeze) ===<br />
<br />
=== M7 - April 30th (Feature Freeze) ===<br />
<br />
== Overall Goals ==<br />
<br />
==== Code Quality ====<br />
<br />
*Better testing <br />
*Better milestone/release ramp down<br />
<br />
==== Better Documentation ====<br />
<br />
*Use wiki as doc for better access and contribution from community <br />
*Start doc work earlier in cycle<br />
<br />
==== Performance ====<br />
<br />
*Continue to keep API tooling builder fast and small footprint <br />
*Keep an eye on performance as target platform code changes<br />
<br />
== Work Items ==<br />
<br />
=== General ===<br />
<br />
==== Bundles or Plug-ins ====<br />
<br />
*Rename PDE to Bundle Development Environment? <br />
*Use of the word plug-in in UI needs to stop<br />
<br />
==== Improve Communications ====<br />
<br />
*Continued web page improvements (M1/M2)<br />
*Use of wiki for meetings/planning (M1 Complete)<br />
*Combine mailing lists (M1 Complete) <br />
*Involve incubator projects such as Picasso to the webpage, and use Athena/Hudson to propose builds/update-sites of these projects (M2)<br />
*Integrate wiki based documentation<br />
<br />
<br />
<br />
=== PDE UI ===<br />
<br />
==== General ====<br />
<br />
*Write tests for core components <br />
*Improve code readability and javadoc of APIs (Ongoing)<br />
*Consider code coverage in tests<br />
*Fix samples generation/installation code for welcome page (Out of plan)<br />
<br />
==== XML Errors ====<br />
<br />
*{{bug|284496}} Handle xml parse errors in Ctx Help editor (M1 Complete)<br />
*{{bug|280119}} Handle xml parse errors in ToC editor (M1 Complete)<br />
<br />
==== Target Platform ====<br />
<br />
* Use targets in core PDE code<br />
**{{bug|283731}} Remove Dependency On Preferences (M2/M3)<br />
**{{bug|284875}} Associate OSGi state with the target (M2/M3)<br />
<br />
* Improve target models<br />
**{{bug|287619}} Manage all target contents with a p2 profile (M2/M3)<br />
**{{bug|169340}}: [API] [target] Expose a means to programmatically set and load a Target Platform <br />
**Manage target contents with features (similar to feature based launching)<br />
<br />
* Provide multiple target platforms<br />
**{{bug|159072}}: [target] associate target definitions on a per-project basis (multiple target platforms per workspace)<br />
<br />
==== Target-focused Quickfixes ====<br />
<br />
*Add quickfixes for missing imports or bundles<br />
* {{bug|175134}} Ability to add all target contents to java search<br />
<br />
==== Launching ====<br />
<br />
* Features as first class citizens again<br />
** Use features as a grouping mechanism<br />
** {{bug|284882}} Better feature management in targets (M2/M3)<br />
** {{bug|284885}} Use features to manage launch contents (feature based launching)<br />
** {{bug|284887}} Improve feature management in the workspace<br />
* P2 Self Hosting<br />
** {{bug|250126}} Create a p2 profile at launch time that can be manipulated in a target workspace.<br />
<br />
==== Product Definitions ====<br />
<br />
*Allow for both features AND bundles to be specified <br />
*Add support for properties and remove the ability to specify a config.ini<br />
<br />
==== Modernize Examples ====<br />
<br />
* {{bug|253105}} [templates] RCP Mail 2.0<br />
<br />
=== API Tools ===<br />
<br />
==== General ====<br />
<br />
*Improve builder performance <br />
**{{bug|233643}}: API builder performance bad for incremental build <br />
**{{bug|273295}}: ReferenceAnalyzer needs to handle different search scopes <br />
**{{bug|279286}}: Incremental compiler takes too long to react on Cancel <br />
**{{bug|280464}}: API tooling performance must be improved <br />
*Improve overall memory usage <br />
**{{bug|231936}}: Improve API description memory usage <br />
*Integrate target platforms more into scans / Ant tasks <br />
**{{bug|273621}}: API descriptions for source from the host are not properly loaded in target workspace <br />
*Improve code coverage <br />
*Examine support for using source attachments to resolve the use of in-lined Java members <br />
**{{bug|218566}}: Restricted field access not flagged as problem<br />
<br />
==== API Use Scans ====<br />
<br />
*Make it really easy to generate API use scans <br />
*Output can be HTML report or search results in the IDE (with attached source) <br />
*Compare API use scans to see summary of dependencies added/removed between successive scans <br />
*Analyze scans for potential breakage (internal dependencies) when moving to a new version of required components (for example WTP moving to a new version of the Eclipse SDK). <br />
*Consider scans taylored to show API use based on frequency of use - i.e. what APIs internals are used most heavily. <br />
*Performance improvements<br />
<br />
==== UI Consumability / Search ====<br />
<br />
*Provide current UI offering in core code. The current offering is available [http://www.eclipse.org/pde/pde-api-tools/internal_updates/ here]. <br />
*Update the code to be in a wizard, not necessarily in the search dialog <br />
*Provide output to search view / API tooling view along with reports<br />
<br />
==== Internal Use Breakage Analysis ====<br />
<br />
*Provide tooling to inspect internal use and breakage (potential or otherwise) <br />
*Provide as user-run tooling and evaluate build-time tooling<br />
<br />
==== Required Bundle Validation ====<br />
<br />
*Validate the bounds of required bundles based on the references from the bundle <br />
*Provide as user-run tooling and evaluate build-time performance<br />
<br />
==== Package Version Support ====<br />
<br />
*Validate package versions wrt bundle versions / usage from required bundles <br />
*Provided as user-run tooling and evaluate build-time performance<br />
<br />
=== Build ===<br />
<br />
==== Consumability ====<br />
<br />
* Invest in build technology - ideally any developer should be able to build the Eclipse SDK from any machine with relative ease. The result(and underlying process) should be the same as that produced by a release engineering build.<br />
* Improve error reporting from PDE/Build. Compilation errors can cause a cascade of errors making it difficult to see where a root problem lies. A dependency analysis should be performed on bundles that have compilation errors to derive error message ordering (bundles lowest on the stack first). <br />
* Particiapate in the b3 project<br />
<br />
==== Extensibility ====<br />
<br />
*Make PDE/Build extensible. Allow some information to be contributed by extension points. This can enable other bundles (pde.ui, or others) to contribute information that, for example, may be available in the workspace. <br />
**{{bug|106594}}: Make PDE fully workspace aware <br />
**{{bug|266311}}: PDE Build should use the new target definition mechanism<br />
<br />
==== Source bundles provide repo info ====<br />
<br />
* {{bug|243582}} Support embedding repository information in released bundles<br />
<br />
==== Single Entry Point Ant Tasks ====<br />
<br />
*Consider single-entry-point ant tasks for building features/plugins/sites/products. These would automatically set up default builders according to some defaults and then run them. This could be considered an analog of export, and becomes more effective given the extension points above.<br />
<br />
==== p2 Integration ====<br />
<br />
*Integration with p2. <br />
**p2 as input to build, extend use of p2 in fetching pre-reqs <br />
**how can building p2 enabled products be simplified<br />
<br />
==== Other ====<br />
<br />
*Feature patches? {{bug|84351}}<br />
<br />
*{{bug|154083}}: Incremental Plug-in Build <br />
*{{bug|222965}}: Use frameworkadmin to generate config.ini / eclipse.ini<br />
* Make PDE/Build match the development environment settings:<br />
** Changes in build path should be reflected in build.properties and visa versa<br />
** Pass extra project compiler settings to build for Eclipse Java compiler<br />
** {{bug|155015}} {{bug|260997}} {{bug|286808}}<br />
<br />
== Platform Support ==<br />
<br />
*Eclipse: 3.6 <br />
*Target Platforms back to 3.0 supported <br />
*Java: J2SE 1.4 or later required <br />
*Operating Systems: all supported by Eclipse<br />
<br />
[[Category:PDE]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=PDE/Incubator/b3/Proposal&diff=166170PDE/Incubator/b3/Proposal2009-07-30T07:56:33Z<p>Benjamin.cabe.anyware-tech.com: /* Interested Parties */</p>
<hr />
<div>=Introduction=<br />
<br />
B3 is a proposed open source project under the PDE Incubator project. This proposal is in the Project Proposal Phase (as defined in the Eclipse Development Process document) and is written to declare its intent and scope and to solicit additional input from the Eclipse community. You are invited to comment on and/or join the project. Please send all feedback to the eclipse.b3 newsgroup.<br />
<br />
=Objectives= <br />
<br />
The purpose of the project will be to develop a new generation of Eclipse technology addressing the concerns of software build and assembly. <br />
<br />
The work of the project will be a complement and potential successor to the PDE Build component.<br />
<br />
The project will have three key objectives:<br />
<br />
* Making build processes repeatable, reproducible and adaptable. Build specifics are often buried within a complicated build script or process definition, so when builds fail, they often do so for mysterious reasons. Similarly, build execution can be highly dependent on the details of a given developer's development setup, which makes builds difficult to run in different environments. The ambition of this project will be (1) to make it possible for a given build to execute in the exact same way when run by anyone, anywhere in the develop-test-deploy cycle and (2) to ensure that when a build fails, it fails for reasons that are clear and reproducible. Developing a declarative, model-driven approach to build definition and execution will be essential to realizing this ambition. Clear separations will be created between concerns of build definition and build execution. Build definitions will describe build input, tooling, platform constraints and processes in ways that are amenable to transformation and manipulation. Where possible, build models will be automatically generated from project structure, and build scripts/tasks will be generated from build models.<br />
<br />
* Bridging discontinuities between building and provisioning software. Software developers are linked in an iterative chain of building and provisioning, in which the output of a given build becomes an input in a subsequent build. Today, the tools and processes of building and provisioning are poorly integrated, resulting in broken hand-offs and wasted effort across the cycle. Automating the connection between each link in the chain will be a goal of this project. Build reproducibility will be a key means to realizing this goal. Each element of a given build process will be captured and reflected in the build definition, so that it can be executed as needed in subsequent steps in the cycle.<br />
<br />
* Aligning potentially overlapping Eclipse build technologies. Several key Eclipse technologies, most notably PDE Build and Buckminster, extend into the build & assembly domain. PDE Build provides the standard Eclipse framework for generating and orchestrating scripts used to build plug-ins. Buckminster has been developed primarily to automate component assembly and provisioning for Eclipse workspaces, but also can be used more generally in build automation. Delineating the relationship between these two technologies will be an important goal of this project, although further exploration will be needed to determine the best approach going forward, i.e., folding one technology into the other, creating a common successor technology for both, etc.<br />
<br />
=Technical Scope=<br />
<br />
Key technologies to be developed in this project will be (1) models describing various aspects of the build domain as well as the relationship between build and provisioning and (2) engines that interpret and act on these models.<br />
<br />
Leverage and support of established Eclipse technologies will be a priority.<br />
<br />
Buckminster and PDE Build are directly relevant to the work of this project, and we intend to combine their respective strengths and capabilities. <br />
<br />
Creating a common successor technology, or folding one technology into the other, will be within scope of this project.<br />
<br />
P2 will be a key technology to exploit, given our goal of addressing connections between build and provisioning concerns. P2 and PDE Build are highly interdependent. Clarifying the boundary between p2/provisioning and build concerns will be within scope of this project. Extension into the provisioning domain, as addressed by p2, will be out of scope. We also expect non-Eclipse build and continuous integration technologies to influence the project architecture and implementation. However, developing similar technology, to the extent not currently addressed by Buckminster or PDE Build will be out of scope. <br />
<br />
We plan to use EMF and related technologies to create the necessary build models and interpretation engines. <br />
<br />
Various community build/assembly tools have been implemented based on Buckminster, PDE Build and other relevant technologies. Continuing and expanding support for these and other community initiatives will be a priority for this project. <br />
<br />
=Project Team=<br />
<br />
==Initial Committers==<br />
<br />
* Ed Merks (Project Co-Lead)<br />
* Thomas Hallgren (Project Co-Lead)<br />
* Henrik Lindberg<br />
* Karel Brezina<br />
* Stefan Daume<br />
* Bjorn Freeman-Benson<br />
* Oisin Hurley<br />
* Eike Stepper<br />
* Chris Aniszczyk<br />
* Andrew Niefer<br />
* Ian Bull<br />
* Filip Hrbek<br />
* Michal Růžička<br />
<br />
Each initial committer is currently an active Eclipse committer on other projects.<br />
<br />
==Mentors==<br />
<br />
* Chris Aniszczyk<br />
* Ed Merks<br />
<br />
==Interested Parties==<br />
<br />
* [http://nick.divbyzero.com Nick Boldt]<br />
* Curtis Windatt<br />
* Darin Wright<br />
* [http://www.linkedin.com/in/danrubel Dan Rubel]<br />
* [http://www.linkedin.com/in/blacksmith Mark Russell]<br />
* Kim Moir<br />
* Paul Webster<br />
* Benjamin Cabé<br />
<br />
=Roadmap=<br />
<br />
A formal project roadmap and plan will be developed following approval and creation of this project.<br />
<br />
=Code Contributions=<br />
<br />
We do not currently plan any outside code contributions in connection with this project. <br />
<br />
All project code will either be developed in connection with this project or sourced from another Eclipse project.</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=PDE/Incubator/Modeling&diff=164302PDE/Incubator/Modeling2009-07-15T18:25:17Z<p>Benjamin.cabe.anyware-tech.com: creation of the page</p>
<hr />
<div>=== Work Area ===<br />
<br />
The goal of Modeling work area is to investigate how modeling technologies available at Eclipse could help to simplify OSGi tooling writing, and make this tooling easily extensible (there are lots of OSGi vendors out there...).<br />
<br />
=== Developers ===<br />
* Benjamin Cabé<br />
<br />
=== Plug-ins ===<br />
* TBC<br />
<br />
=== Resources ===<br />
<br />
* [http://dev.eclipse.org/viewcvs/index.cgi/pde-incubator/modeling/releng/org.eclipse.pde.ds.releng/ds-incubator-pserver.psf?view=co DS editor and EMF Forms geneeric editing framework PSF]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=PDE/Incubator&diff=164299PDE/Incubator2009-07-15T18:17:36Z<p>Benjamin.cabe.anyware-tech.com: /* Work Areas */</p>
<hr />
<div>Welcome to the '''Plug-in Development Environment (PDE) Incubator''' Wiki Page.<br />
<br />
The PDE Incubator provides a place to grow and test new ideas that fall into plug-in development space.<br />
<br />
== Work Areas ==<br />
<br />
[[PDE/Incubator/Visualization|Visualization]] - visualization.<br />
<br />
[[PDE/Incubator/XtremeSelfHosting|Extreme Self-Hosting]] - Extreme self-hosting.<br />
<br />
[[PDE/Incubator/DS|Declarative Services Tooling]] - Declarative Services tooling.<br />
<br />
[[PDE/Incubator/ProductCustomization|Product Customization]] - Tooling for Equinox Transforms and customization of products<br />
<br />
[[PDE/Incubator/Picasso|Picasso]] - UI Debugging by painting the workbench :)<br />
<br />
[[PDE/Incubator/UA|UA Refactoring]] - UA refactoring<br />
<br />
[[PDE/Incubator/Modeling|Modeling]] - Modeling the PDE to simplify tooling writing and easily allow extensions (e.g. by OSGi vendors)<br />
<br />
== Resources ==<br />
<br />
[http://www.eclipse.org/pde/pde-ui/ PDE UI Home Page] - The main PDE UI web site.<br />
<br />
[https://bugs.eclipse.org/bugs/ Eclipse Bugzilla] - Eclipse bug tracking database.</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=PDE/Retrospective&diff=159085PDE/Retrospective2009-06-17T20:22:05Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div>This page will be used to collect comments about PDE and our development process that were noticed during 3.5. What did we do well? What could be better? What should we do next release?<br />
<br />
== Coding Best Practices ==<br />
<br />
* If you write new core/model/non-UI code, '''write tests''' for it<br />
<br />
* '''Don't''' release a major change just before a milestone release or even right before an I build<br />
<br />
* If you create any kind of UI make sure it has a help topic. Also '''ensure''' that you create the help topic(s) at the time the UI is created. '''DO NOT''' leave it until the doc pass at the end of the release.<br />
<br />
== Bugzilla ==<br />
<br />
* If you add someone as a reviewer, add them as a cc<br />
<br />
* Only mark a bug with a specific target milestone if you seriously plan on fixing it during that milestone<br />
<br />
* If you are unsure about a change or the code you are committing is a major change, add a reviewer and get them to verify it<br />
<br />
== General Comments == <br />
<br />
* In 3.5 the target platform changes ended up dropping too late M6/M7 to get proper feedback. We recognized this as a risk beforehand and still went forward and we did get burned for this to some extent. There were too many RC fixes required to get it working.<br />
<br />
* Regularly run a profiler (or the like) over any new larger changes to catch performance regressions earlier<br />
<br />
* It would be good to always have another pair of eyes (or two) verify all fixes<br />
<br />
* We released 3.5 with two bugs marked BLOCKER and one CRITICAL. I haven't really checked if these really are severe defects, but we probably can have communicated better on the actual status of these issues.</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=PDE/Plan/3.6&diff=157118PDE/Plan/3.62009-06-08T13:16:04Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div><div style="border: thin solid black; background-color: #F4FFF4; margin: 3px"><div style="margin: 4px"><br />
Note: This is an unofficial document used by the PDE team to help with the planning process. Items on this list aren't guaranteed to be found in a release.<br />
</div></div><br />
<br />
= Schedule =<br />
<br />
Dates are listed in the Eclipse Platform Releng Calendar (view as [http://www.google.com/calendar/ical/kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com/public/basic.ics iCal].<br />
<br />
= Scope =<br />
<br />
TODO<br />
<br />
== Priorities ==<br />
<br />
* Revamp the PDE webpage to be more welcoming<br />
** Add missing Incubator projects such as Picasso to the webpage, and use Athena/Hudson to propose builds/update-sites of these projects<br />
* More tests to improve code coverage<br />
* More bundle, less plug-in<br />
* Get more committers<br />
* One mailing list (ie., just pde-dev, get rid of pde-build-dev and pde-ui-dev)<br />
<br />
== Platforms ==<br />
* Eclipse: 3.6<br />
* Target Platforms back to 3.0 supported<br />
* Java: J2SE 1.4 or later required<br />
* Operating Systems: all supported by Eclipse<br />
<br />
== Ramp Down ==<br />
<br />
TODO<br />
<br />
= Projects =<br />
<br />
== API Tools ==<br />
<br />
* {{bug|215073}}: [api tooling] Support for package versioning<br />
<br />
== Build ==<br />
<br />
* {{bug|154083}}: Incremental Plug-in Build<br />
* {{bug|106594}}: Make PDE fully workspace aware<br />
* {{bug|222965}}: Use frameworkadmin to generate config.ini / eclipse.ini<br />
<br />
== UI ==<br />
<br />
* {{bug|269573}}: [product] support more platforms in product files<br />
* {{bug|260328}}: [product] add a way to specify properties<br />
* {{bug|159072}}: [target] associate target definitions on a per-project basis (multiple target platforms per workspace)<br />
* {{bug|106676}}: [pde viz] Graduate<br />
* {{bug|142422}}: [refactoring] update class references in dependent plugins<br />
* {{bug|231099}}: [launching] Make launch config files more CVS-friendly<br />
* {{bug|164188}}: Need tooling for access rules on vm packages<br />
* {{bug|227055}}: [schema] allow for the definition of custom attribute types<br />
* p2 publishing tooling (replace update site tooling)<br />
<br />
[[Category:PDE]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=PDE/Plan/3.6&diff=155845PDE/Plan/3.62009-05-29T08:40:25Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div><div style="border: thin solid black; background-color: #F4FFF4; margin: 3px"><div style="margin: 4px"><br />
Note: This is an unofficial document used by the PDE team to help with the planning process. Items on this list aren't guaranteed to be found in a release.<br />
</div></div><br />
<br />
= Schedule =<br />
<br />
Dates are listed in the Eclipse Platform Releng Calendar (view as [http://www.google.com/calendar/ical/kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com/public/basic.ics iCal].<br />
<br />
= Scope =<br />
<br />
TODO<br />
<br />
== Priorities ==<br />
<br />
* Revamp the PDE webpage to be more welcoming<br />
* More tests to improve code coverage<br />
* More bundle, less plug-in<br />
* Get more committers<br />
* One mailing list (ie., just pde-dev, get rid of pde-build-dev and pde-ui-dev)<br />
<br />
== Platforms ==<br />
* Eclipse: 3.6<br />
* Target Platforms back to 3.0 supported<br />
* Java: J2SE 1.4 or later required<br />
* Operating Systems: all supported by Eclipse<br />
<br />
== Ramp Down ==<br />
<br />
TODO<br />
<br />
= Projects =<br />
<br />
== API Tools ==<br />
<br />
* {{bug|215073}}: [api tooling] Support for package versioning<br />
<br />
== Build ==<br />
<br />
* {{bug|154083}}: Incremental Plug-in Build<br />
* {{bug|106594}}: Make PDE fully workspace aware<br />
* {{bug|222965}}: Use frameworkadmin to generate config.ini / eclipse.ini<br />
<br />
== UI ==<br />
<br />
* {{bug|269573}}: [product] support more platforms in product files<br />
* {{bug|260328}}: [product] add a way to specify properties<br />
* {{bug|159072}}: [target] associate target definitions on a per-project basis (multiple target platforms per workspace)<br />
* {{bug|106676}}: [pde viz] Graduate<br />
* {{bug|142422}}: [refactoring] update class references in dependent plugins<br />
* {{bug|231099}}: [launching] Make launch config files more CVS-friendly<br />
* {{bug|164188}}: Need tooling for access rules on vm packages<br />
* {{bug|227055}}: [schema] allow for the definition of custom attribute types<br />
* p2 publishing tooling (replace update site tooling)<br />
<br />
[[Category:PDE]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=E4/Buzz&diff=154820E4/Buzz2009-05-23T08:58:38Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div>Here's some buzz around e4<br />
<br />
* [http://onflash.org/ted/2009/02/publish-swt-to-flash-player.php Eclipse E4 M1 SWT: JAVA to AS3]<br />
* [http://www.vogella.de/articles/EclipseE4/article.html Blog demo on e4]<br />
* [http://www.tekool.net/blog/2009/02/15/e4swt-java-for-flash-running-the-demos/ tekool entry]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Twitter&diff=151727Twitter2009-05-01T18:29:46Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div>[http://www.twitter.com Twitter] is a service for friends, family, and co–workers to communicate and stay connected through the exchange of quick, frequent answers to one simple question: What are you doing?<br />
<br />
The people listed below are part of the greater Eclipse community on Twitter.<br />
<br />
=== People ===<br />
<br />
* [http://twitter.com/caniszczyk Chris Aniszczyk]<br />
* [http://twitter.com/njbartlett Neil Bartlett]<br />
* [http://twitter.com/hbehrens Heiko Behrens]<br />
* [http://twitter.com/nickboldt Nick Boldt]<br />
* [http://twitter.com/bokowski Boris Bokowski]<br />
* [http://twitter.com/jordibohmelopez Jordi Böhme López]<br />
* [http://twitter.com/irbull Ian Bull]<br />
* [http://twitter.com/kartben Benjamin Cabé]<br />
* [http://twitter.com/christiancampo Christian Campo]<br />
* [http://twitter.com/kingargyle David Carver]<br />
* [http://twitter.com/ericcloninger Eric Cloninger]<br />
* [http://twitter.com/zvikico Zviki Cohen]<br />
* [http://twitter.com/nedgar Nick Edgar]<br />
* [http://twitter.com/svenefftinge Sven Efftinge]<br />
* [http://twitter.com/jeervin James E. Ervin]<br />
* [http://twitter.com/peterfriese Peter Friese]<br />
* [http://twitter.com/lorifraleigh Lori Fraleigh]<br />
* [http://twitter.com/douggaff Doug Gaff]<br />
* [http://twitter.com/lgayowski Lynn Gayowski]<br />
* [http://twitter.com/oisin Oisin Hurley]<br />
* [http://twitter.com/codesurgeon Mustafa K. Isik]<br />
* [http://twitter.com/mik_kersten Mik Kersten]<br />
* [http://twitter.com/kohlerm Markus Kohler]<br />
* [http://twitter.com/euxx Eugene Kuleshov]<br />
* [http://twitter.com/scottslewis Scott Lewis]<br />
* [http://twitter.com/martinlippert Martin Lippert]<br />
* [http://twitter.com/http://twitter.com/EdMerks Ed Merks]<br />
* [http://twitter.com/mmilinkov Mike Milinkovich]<br />
* [http://twitter.com/bmuskalla Benjamin Muskalla]<br />
* [http://twitter.com/moberh Martin Oberhuber]<br />
* [http://twitter.com/jrep Jack Repenning]<br />
* [http://twitter.com/VineetSinha Vineet Sinha]<br />
* [http://twitter.com/IanSkerrett Ian Skerrett]<br />
* [http://twitter.com/hstaudacher Holger Staudacher]<br />
* [http://twitter.com/dzonejames James Sugrue]<br />
* [http://twitter.com/darinrs Darin Swanson]<br />
* [http://twitter.com/kaitoedter Kai Tödter]<br />
* [http://twitter.com/eclipseguru Gunnar Wagenknecht]<br />
<br />
=== Organizations and projects ===<br />
<br />
* [http://twitter.com/EclipsePlanet Planet Eclipse]<br />
* [http://twitter.com/eclipsesource EclipseSource]<br />
* [http://twitter.com/m2eclipse Maven integration for Eclipse]<br />
* [http://twitter.com/nwire nWire Software]<br />
* [http://twitter.com/eclipsezone EclipseZone]<br />
* [http://twitter.com/GroovyEclipse Groovy Eclipse]<br />
<br />
=== Twitter Clients ===<br />
<br />
I highly recommend [http://www.tweetdeck.com TweetDeck] for your desktop, [http://twitterfon.net/ TwitterFon] for your iPhone, and [http://www.orangatame.com/products/twitterberry/ TwitterBerry] for Blackberry. Stay tuned for an Eclipse RCP/ECF-based Twitter client!<br />
<br />
[http://twitterfox.net/ TwitterFox] is a very nice Twitter client for FireFox. And [http://twittervision.com/maps/show_3d Twittervision] for a little Google Earth like fun in between.</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=User:Benjamin.cabe.anyware-tech.com&diff=150858User:Benjamin.cabe.anyware-tech.com2009-04-26T21:54:13Z<p>Benjamin.cabe.anyware-tech.com: New page: * PDE/Incubator committer * http://blog.benjamin-cabe.com</p>
<hr />
<div>* PDE/Incubator committer<br />
* http://blog.benjamin-cabe.com</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Xtext/Documentation&diff=146381Xtext/Documentation2009-03-26T06:08:50Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div>= What is Xtext? =<br />
<br />
The TMF Xtext project provides a domain-specific language (the grammar language) for description of textual programming languages and domain-specific languages. It is tightly integrated with the Eclipse Modeling Framework (EMF) and leverages the Eclipse Platform in order to provide language-specific tool support.<br />
In contrast to common parser (syntactic analyzer) generators of the grammar language is much simpler but is used to derive much more than just a parser and lexer (lexical analyzer).<br />
From a grammar the following is derived:<br />
<br />
* incremental, Antlr3-based parser and lexer<br />
* Ecore-based meta models (optional)<br />
* a serializer, used to serialize instances of such meta models back to a parseable textual representation<br />
* an implementation of the EMF Resource interface (based on the parser and the serializer)<br />
* a full-fledged integration of the language into Eclipse IDE<br />
** syntax coloring<br />
** navigation (F3, etc.) <br />
** code completion<br />
** outline views<br />
** code templates<br />
<br />
The generated artifacts are wired up through the [http://code.google.com/p/google-guice/ google guice] dependency injection framework, which makes it easy to exchange certain functionality in a non-invasive manner.<br />
For example if you don't like the default code assistant implementation, you need to come up with an alternative implementation of the corresponding service and configure it via dependency injection.<br />
<br />
= The Grammar Language =<br />
The [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.tmf/org.eclipse.xtext/plugins/org.eclipse.xtext/src/org/eclipse/xtext/Xtext.xtext?root=Modeling_Project&view=markup grammar language] is the corner stone of Xtext and is defined in itself - of course.<br />
<br />
It is a DSL carefully designed for description of textual languages, based on [http://en.wikipedia.org/wiki/LL_parser LL(*)-Parsing] that is like [http://www.artima.com/lejava/articles/antlr_3.html Antlr3's parsing strategy] and supported by [http://pdos.csail.mit.edu/~baford/packrat/ packrat parsers].<br />
The main idea is to let users describe the concrete syntax, and to automatically derive an in-memory model (semantic model) from that. <br />
<br />
== First an example ==<br />
To get an idea of how it works we'll start by implementing a [http://martinfowler.com/dslwip/Intro.html simple example] introduced by Martin Fowler.<br />
It's mainly about describing state machines used as the (un)lock mechanism of secret compartments. People who have secret compartments control their access in a very old-school way, e.g. by opening the door first and turning on the light afterwards. Then the secret compartment, for instance a panel, opens up.<br />
<br />
One of those state machines could look like this:<br />
<source lang="text"><br />
events<br />
doorClosed D1CL<br />
drawOpened D2OP<br />
lightOn L1ON<br />
doorOpened D1OP<br />
panelClosed PNCL<br />
end<br />
<br />
resetEvents<br />
doorOpened<br />
end<br />
<br />
commands<br />
unlockPanel PNUL<br />
lockPanel PNLK<br />
lockDoor D1LK<br />
unlockDoor D1UL<br />
end<br />
<br />
state idle<br />
actions {unlockDoor lockPanel}<br />
doorClosed => active<br />
end<br />
<br />
state active<br />
drawOpened => waitingForLight<br />
lightOn => waitingForDraw<br />
end<br />
<br />
state waitingForLight<br />
lightOn => unlockedPanel<br />
end<br />
<br />
state waitingForDraw<br />
drawOpened => unlockedPanel<br />
end<br />
<br />
state unlockedPanel<br />
actions {unlockPanel lockDoor}<br />
panelClosed => idle<br />
end<br />
</source><br />
So, we have a bunch of declared events, commands and states. Within states there are references to declared actions, which should be executed when entering such a state.<br />
Also there are transitions consisting of a reference to an event and a state. Please read [http://martinfowler.com/dslwip/Intro.html Martin's description] if it is not clear enough.<br />
<br />
In order to implement this language with Xtext you need to write the following grammar:<br />
<source lang="text"><br />
grammar SecretCompartments with org.eclipse.xtext.common.Terminals<br />
<br />
generate secretcompartment "http://www.eclipse.org/secretcompartment"<br />
<br />
Statemachine :<br />
'events'<br />
(events+=Event)+<br />
'end'<br />
('resetEvents'<br />
(resetEvents+=[Event])+<br />
'end')?<br />
'commands'<br />
(commands+=Command)+<br />
'end'<br />
(states+=State)+;<br />
<br />
Event :<br />
name=ID code=ID;<br />
<br />
Command :<br />
name=ID code=ID;<br />
<br />
State :<br />
'state' name=ID<br />
('actions' '{' (actions+=[Command])+ '}')?<br />
(transitions+=Transition)*<br />
'end';<br />
<br />
Transition :<br />
event=[Event] '=>' state=[State];<br />
</source><br />
<br />
In the following the different concepts of the grammar language are explained. We refer to this grammar when useful.<br />
<br />
== Language Declaration ==<br />
The first line<br />
<code lang="text"><br />
grammar SecretCompartments with org.eclipse.xtext.common.Terminals<br />
</code><br />
declares the name of the grammar. <br />
Xtext leverages Java's classpath mechanism. This means that the name can be any valid Java qualifier. <br />
The file name needs to correspond and have the file extension ''xtext''.<br />
This means that the name needs to be ''SecretCompartments.xtext'' and must be placed in the default package on the Java's class path.<br />
<br />
If you want to place it within a package (e.g. ''foo/SecretCompartment.xtext'') the first line must read:<br />
<code lang="text"><br />
grammar foo.SecretCompartment with ...<br />
</code><br />
The first line is also used to declare any used language (for mechanism details cf. [[#Language Inheritance|Language Inheritance]]).<br />
<br />
== EPackage declarations ==<br />
Xtext parsers instantiate Ecore models (aka meta model). An Ecore model basically consists of an EPackage containing EClasses, EDatatypes and EEnums.<br />
Xtext can infer Ecore models from a grammar (cf. [[#Meta-Model_inference|Meta-Model Inference]]) but it is also possible to instantiate existing Ecore models. You can even mix this, use multiple existing ecore models and infer some others from one grammar. <br />
<br />
=== EPackage generation ===<br />
The easiest way to get started is to let Xtext infer the meta model from your grammar. This is what is done in the secret compartment example.<br />
To do so just state:<br />
<code lang="text"><br />
generate secretcompartment "<nowiki>http://www.eclipse.org/secretcompartment</nowiki>"<br />
</code><br />
<br />
Which says: generate an EPackage with name secretcompartment and nsURI "<nowiki>http://www.eclipse.org/secretcompartment</nowiki>" (these are the properties needed to create an EPackage). See [[#Meta-Model_Inference|Meta-Model Inference]] for details.<br />
<br />
=== EPackage import ===<br />
If you already have created such an EPackage somehow, you could import it using either the name space URI or a resource URI (URIs are an EMF concept):<br />
<code lang="text"><br />
import "<nowiki>http://www.eclipse.org/secretcompartment</nowiki>"<br />
</code><br />
<br />
Note that if you use, a namespace URI, the corresponding EPackage needs to be installed into the workbench, so that the editor can find it.<br />
At runtime (i.e. when starting the generator) you need to make sure that the corresponding EPackage is registered in EPackage.Registry.INSTANCE.<br />
<br />
Xtext provides a new resource URI scheme, which is backed by the Java classpath. If you want to refer to an ecore file MyEcore.ecore, laying in a a package foo.bar, you could write <br />
<br />
<code lang="text"><br />
import "classpath:/foo/bar/MyEcore.ecore"<br />
</code><br />
<br />
Using the classpath scheme is considered the preferred way.<br />
<br />
=== Using multiple packages / meta model aliases ===<br />
If you want to use multiple EPackages you need to specify aliases like so:<br />
<code lang="text"><br />
generate secretcompartment "<nowiki>http://www.eclipse.org/secretcompartment</nowiki>"<br />
import "<nowiki>http://www.eclipse.org/anotherPackage</nowiki>" as another<br />
</code><br />
<br />
When referring to a type somewhere in the grammar you need to qualify them using that alias (example ''another::CoolType''). We'll see later where such type references occur.<br />
<br />
It is also supported to put multiple EPackage imports into one alias. This is no problem as long as there are no two EClassifiers with the same name. In such cases none of them are referable. It is even possible to have multiple ''import''s and one ''generate'' declared for the same alias. If you do so, for a reference to an EClassifier first the imported EPackages are scanned before it is assumed that a type needs to by generated into the to-be-generated package.<br />
<br />
Example:<br />
<code lang="text"><br />
generate toBeGenerated "<nowiki>http://www.eclipse.org/toBeGenerated</nowiki>"<br />
import "<nowiki>http://www.eclipse.org/packContainingClassA</nowiki>"<br />
import "<nowiki>http://www.eclipse.org/packContainingClassB</nowiki>"<br />
</code><br />
<br />
With the declaration from above <br />
# a reference to type ClassA would be linked to the EClass contained in "<nowiki>http://www.eclipse.org/packContainingClassA</nowiki>", <br />
# a reference to type ClassB would be linked to the EClass contained in "<nowiki>http://www.eclipse.org/packContainingClassB</nowiki>", <br />
# a reference to type NotYetDefined would be linked to a newly created EClass in "<nowiki>http://www.eclipse.org/toBeGenerated</nowiki>"<br />
<br />
Note, that using this feature is not recommended, because it might cause problems, which are hard to tackle down.<br />
For instance, a reference to ''classA'' would as well be linked to a newly created EClass, because the corresponding type in "<nowiki>http://www.eclipse.org/packContainingClassA</nowiki>" is spelled with a capital letter.<br />
<br />
== Rules ==<br />
The default parsing is based on a homegrown packrat parser. It can be substituted by an Anltr parser through the Xtext service mechanism. Antlr is a sophisticated parser generator framework based on [http://www.antlr.org/wiki/display/ANTLR3/3.+LL(*)+Parsing+(Excursion) an LL(*) parsing algorithm], that works quite well for Xtext. At the moment it is advised to download the plugin de.itemis.xtext.antlr (from update site [[http://www.itemis.com/xtext/updatesite/milestones]]) and use the Antlr Parser instead of the packrat parser (cf. [[Xtext_Workspace_Setup|Xtext Workspace Setup]]).<br />
<br />
Basically parsing can be separated in the following phases. <br />
# lexing<br />
# parsing<br />
# linking<br />
# validation<br />
<br />
=== Terminal Rules ===<br />
In the first phase, i.e. lexing, a sequence of characters (the text input) is transformed into a sequence of so called tokens. <br />
Each token consists of one or more characters and was matched by a particular terminal rule and represents a atomic symbol.<br />
In the secret compartments example there are no explicitly defined terminal rules, since it ly uses the ID rule which is inherited from the grammar org.eclipse.xtext.common.Terminals (cf. [[#Language_Inheritance | Language Inheritance]]).<br />
Terminal rules are also refered to as token rules or lexer rules. There is an informal naming convention that terminal-rule names are all uppercase.<br />
<br />
Therein the ID rule is defined as follows:<br />
<code lang="text"><br />
terminal ID : <br />
('^')?('a'..'z'|'A'..'Z'|'_') ('a'..'z'|'A'..'Z'|'_'|'0'..'9')*; <br />
</code><br />
<br />
It says that a Token ID starts with an optional '^' character, which is called caret, followed by a letter ('a'..'z'|'A'..'Z') or underscore ('_') followed by any number of letters, underscores and numbers ('0'..'9'). <br />
<br />
The caret is used to escape an identifier for cases where there are conflicts with keywords. It is removed during parsing. <br />
<br />
This is the formal definition of terminal rules:<br />
<br />
<code lang="text"><br />
TerminalRule :<br />
'terminal' name=ID ('returns' type=TypeRef)? ':' <br />
alternatives=TerminalAlternatives ';'<br />
;<br />
</code><br />
<br />
==== Return types ====<br />
A terminal rule returns a value, which is a string (type ecore::EString) by default.<br />
However, if you want to have a different type you can specify it. For instance, the rule 'INT' is defined as:<br />
<br />
<code lang="text"><br />
terminal INT returns ecore::EInt : <br />
('0'..'9')+;<br />
</code><br />
<br />
This means that the terminal rule INT returns instances of ecore::EInt. It is possible to define any kind of data type here, which just needs to be an instance of ecore::EDataType.<br />
In order to tell the parser how to convert the parsed string to a value of the declared data type, you need to provide your own implementation of 'IValueConverterService' (cf. [[Xtext/Documentation/ValueConverter|value converters]]).<br />
<br />
The implementation needs to be registered as a service (cf. [[#Service_Framework|Service Framework]]).<br />
This is also the point where you can remove things like quotes form string literals or the caret ('^') from identifiers.<br />
<br />
==== Extended Backus-Naur form expressions ====<br />
Token rules are described using [http://en.wikipedia.org/wiki/Extended_Backus%E2%80%93Naur_Form Extended Backus-Naur Form] (EBNF) expressions. The different expressions are described in the following.<br />
The one thing all of these expressions have in common is the quantifier operator.<br />
There are four different quantities<br />
# exactly one (the default no operator)<br />
# one or none (operator "?")<br />
# any (operator "*")<br />
# one or more (operator "+")<br />
<br />
==== Keywords / Characters ====<br />
Keywords are a kind of token rule literals. <br />
The ID rule in org.eclipse.xtext.common.Terminals for instance starts with a keyword :<br />
<code><br />
terminal ID : '^'? .... ;<br />
</code><br />
The question mark sets the cardinality to "none or one" (i.e. optional) like explained above.<br />
<br />
Note that a keyword can have any length and contain arbitrary characters.<br />
<br />
==== Character Ranges ====<br />
A character range can be declared using the '..' operator.<br />
Example:<br />
<code><br />
terminal INT returns ecore::EInt: ('0'..'9')+ ;<br />
</code><br />
<br />
In this case an INT is comprised of one or more (note the '+' operator) characters between (and including) '0' and '9'.<br />
<br />
==== Wildcard ====<br />
If you want to allow any character you can simple write a dot:<br />
Example:<br />
<br />
<code><br />
FOO : 'f' . 'o';<br />
</code><br />
<br />
The rule above would allow expressions like 'foo', 'f0o' or even 'f\no'.<br />
<br />
==== Until Token ====<br />
With the until token it is possible to state that everything should be consumed until a certain token occurs.<br />
The multi line comment is implemented using it:<br />
<br />
<code><br />
terminal ML_COMMENT : '/*' -> '*/' ;<br />
</code><br />
<br />
This is the rule for Java-style comments that begin with '/*' and end with '*/'.<br />
<br />
==== Negated Token ====<br />
All the tokens explained above can be inverted using a preceding explanation mark:<br />
<br />
<code><br />
terminal ML_COMMENT : '/*' (!'*/')+ ;<br />
</code><br />
<br />
==== Rule Calls ====<br />
Rules can refer to other rules. This is done by writing the name of the rule to be called.<br />
We refer to this as rule calls. Rule calls in terminal rules can only point to token rules.<br />
<br />
Example:<br />
<br />
<code><br />
terminal QUALIFIED_NAME : ID ('.' ID)*;<br />
</code><br />
<br />
==== Alternatives ====<br />
Using alternatives one can state multiple different alternatives.<br />
For instance, the whitespace rule uses alternatives like so:<br />
<br />
<code><br />
terminal WS : (' '|'\t'|'\r'|'\n')+ ;<br />
</code><br />
<br />
That is a WS can be made of one or more whitespace characters (including ' ','\t','\r','\n')<br />
<br />
==== Groups ====<br />
Finally, if you put tokens one after another, the whole sequence is referred to as a group.<br />
Example:<br />
<code><br />
terminal FOO : '0x' ('0'..'7') ('0'..'9'|'A'..'F') ;<br />
</code><br />
That is the 4-digit hexadecimal code of ascii characters.<br />
<br />
=== Datatype rules ===<br />
Datatype rules are parsing-phase rules, which like token rules create instances of EDatatype.<br />
The nice thing about Datatype rules is that they are actually parser rules and are therefore <br />
# context sensitive and <br />
# allow for use of hidden tokens<br />
<br />
If you, for instance, want to define a rule to consume Java-like qualified names (e.g. "foo.bar.Baz")<br />
you could write:<br />
<br />
<code><br />
QualifiedName :<br />
ID ('.' ID)*;<br />
</code><br />
<br />
Which looks similar to the terminal rule we've defined above in order to explain rule calls.<br />
However, the difference is that because it is a parser rule and therefore only valid in certain contexts, it won't conflict with ID.<br />
If you had defined it as a terminal rule, it would overlay the ID rule.<br />
<br />
In addition having this defined as a datatype rule, it is allowed to use hidden tokens (e.g. "/* comment */") between the IDs and dots (e.g. "foo/* comment */. bar . Baz")<br />
<br />
Return types can be specified like in token rules:<br />
<code><br />
QualifiedName returns ecore::EString : ID ('.' ID)*;<br />
</code><br />
<br />
Note that if a rule does not call another parser rule and does not contain any actions nor assignments (see parser rules), it is considered a datatype rule and the datatype EString is implied if not explicitly declared differently.<br />
<br />
For conversion again value converters are responsible (cf. [[Xtext/Documentation/ValueConverter|value converters]]).<br />
<br />
=== Enum Rules ===<br />
Enum rules return enumeration literals from strings. They can be seen as a shortcut for datatype rules with specific value converters.<br />
The main advantage of enum rules is their simplicity, typesafety and therefore nice validation. Furthermore it is possible to infere enums and their respective literals during the metamodel transformation.<br />
<br />
If you want to define a ChangeKind [[http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.emf.doc/references/javadoc/org/eclipse/emf/ecore/change/impl/package-summary.html org.eclipse.emf.ecore.change/model/Change.ecore]] with 'ADD', 'MOVE' and 'REMOVE' you could write:<br />
<br />
<code><br />
enum ChangeKind :<br />
ADD | MOVE | REMOVE;<br />
</code><br />
<br />
It is even possible to use alternative literals for your enums or reference an enum value twice:<br />
<br />
<code><br />
enum ChangeKind :<br />
ADD = 'add' | ADD = '+' | <br />
MOVE = 'move' | MOVE = '->' | <br />
REMOVE = 'remove' | REMOVE = '-';<br />
</code><br />
<br />
=== Parser Rules ===<br />
The parser reads in a sequence of terminals and walks through the parser rules. That's why a parser rule - contrary to a terminal rule - does not produce a single terminal token but a tree of non-terminal and terminal tokens that lead to a so called parse tree (in Xtext it is a.k.a node model). Furthermore, parser rules are handled as kind of a building plan to create EObjects that form the semantic model (the AST). The different constructs like actions and assignments are used to derive types and initialize the semantic objects accordingly. <br />
==== Extended Backus-Naur Form expressions ====<br />
In parser rules (as well as in datatype rules) not all the expressions available for terminal rules can be used. Character ranges, wildcards, the until token and the negation are currently only available for terminal rules. <br />
Available in parser rules as well as in terminal rules are<br />
# [[#Groups|groups]], <br />
# [[#Alternatives|alternatives]], <br />
# [[#Keywords|keywords]] and <br />
# [[#Rule Calls|rule calls]].<br />
<br />
In addition to these elements, there are some expressions used to direct how the AST is constructed, which are listed and explained in the following.<br />
<br />
==== Assignments ====<br />
Assignments are used to assign parsed information to a feature of the current EClass. The current EClass is specified by the return type resp. if not explicitely stated it is implied that the type's name equals the rule's name.<br />
<br />
Example:<br />
<code><br />
State :<br />
'state' name=ID<br />
('actions' '{' (actions+=[Command])+ '}')?<br />
(transitions+=Transition)*<br />
'end';<br />
</code> <br />
<br />
The syntactic declaration for states in the state machine example starts with a keyword 'state' followed by an assignment :<br />
<code><br />
name=ID<br />
</code><br />
Where the left hand side refers to a feature of the current EClass (assumed to be EClass 'State'). <br />
The right hand side can be a rule call, a keyword, a cross reference (explained later) or even an alternative comprised by the former.<br />
The type of the feature needs to be compatible to the type of the expression on the right. As ID returns an EString the feature name needs to be of type EString as well.<br />
<br />
===== Assignment Operators =====<br />
There are three different assignment operators, each with different semantics<br />
# the simple equal sign "=" is the straight forward assignment, and used for features which take only one element<br />
# the "+=" sign (the add operator) awaits a multiple feature and adds the value on the right hand to that feature, which is, of course, a list feature<br />
# the "?=" sign (boolean operator) awaits a feature if type EBoolean and sets it to true if the right hand side was consumed (no matter with what values)<br />
<br />
==== Cross References ====<br />
A unique feature of Xtext is the ability to declare cross links in the grammar. In traditional compiler construction the cross links are not established during parsing but in a later linking phase. This is the same in Xtext, but we allow to specify cross link information in the grammar, which is used during the linking phase.<br />
The syntax for cross links is:<br />
<code><br />
CrossReference :<br />
'[' type=TypeRef ('|' ^terminal=CrossReferenceableTerminal )? ']'<br />
;<br />
</code><br />
<br />
For example, the transition is made up of two cross references, pointing to an event and a state:<br />
<code><br />
Transition :<br />
event=[Event] '=>' state=[State];<br />
</code> <br />
It is important to understand that the text between the square brackets does not refer to another rule, but to the type!<br />
This is sometimes confusing, because one usually uses the same name for the rules and the types.<br />
That is if we had named the type for events differently like in the following the cross references needs to be adapted as well:<br />
<code><br />
Transition :<br />
event=[MyEvent] '=>' state=[State];<br />
<br />
Event returns MyEvent : ....;<br />
</code> <br />
<br />
Looking at the syntax definition of cross references, there is an optional part starting with a vertical bar followed by 'CrossReferenceableTerminal'. This is the part describing the concrete text, from which the crosslink later should be established.<br />
By default (that's why it's optional) it is "|ID".<br />
<br />
Have a look at the [[#Linking| linking section]] in order to understand how linking is done.<br />
<br />
==== Actions ====<br />
By default the object to be returned by parser rule is created lazily on the first assignment. Then the type of the EObject to be created is determined from the specified return type (or the rule name if not explicit return type is specified).<br />
With Actions however, creation of EObject can be made explicit. We have two kinds of Actions:<br />
<br />
If at some point you want to enforce creation of a specific type you can use simple actions.<br />
Example : <br />
<code><br />
MyRule returns TypeA :<br />
"A" name=ID |<br />
{TypeB} "B" name=ID; <br />
</code><br />
<br />
In this example TypeB must be a subtype of TypeA. If an expression " A foo " is parsed an instance of TypeA is created as soon as the assignment is evaluated. An expression "B foo" would result in creation of TypeB.<br />
<br />
==== Unassigned rule calls ====<br />
We previously explained, that the EObject to be returned is created lazily when the first assignment occurs or when a simple action is evaluated. There is another way one can set the EObject to be returned, which we call an "unassigned rule call".<br />
<br />
Unassigned rule calls (the name suggests it) are rule calls to other parser rules, which are not used within an assignment. If there is no feature the returned value shall be assigned to, the value is assigned to the "to-be-returned" reference.<br />
<br />
With unassigned rule calls one can, for instance, create rules which just dispatch between several other rules:<br />
<br />
<code><br />
AbstractToken :<br />
TokenA |<br />
TokenB |<br />
TokenC;<br />
</code><br />
<br />
As AbstractToken could possibly return an instance of TokenA, TokenB or TokenC its type must by a super type to these types.<br />
It is now for instance as well possible to further change the state of the AST element by assigning additional things.<br />
Example:<br />
<br />
<code><br />
AbstractToken :<br />
(TokenA |<br />
TokenB |<br />
TokenC ) (cardinality=('?'|'+'|'*'))?;<br />
</code><br />
<br />
Thus, to state the cardinality is optional (last question mark) and can be represented by a question mark, a plus, or an asterisk.<br />
<br />
==== Actions revisited ====<br />
LL parsing has some significant advantages over LR algorithms. The most important ones for Xtext are, that the generated code is much simpler to understand and debug and that it is easier to recover from errors and especially Antlr has a very nice generic error recovery mechanism. This allows to have AST constructed even if there are syntactic errors in the text. You wouldn't get any of the nice IDE features as soon as there is one little error, if we hadn't error recovery.<br />
<br />
However, LL also has some drawbacks. The most important is, that it does not allow left recursive grammars.<br />
For instance, the following is not allowed in LL based grammars, because "Expression '+' Expression" is left recursive:<br />
<br />
<code><br />
Expression :<br />
Expression '+' Expression |<br />
'(' Expression ')'<br />
INT;<br />
</code><br />
<br />
Instead one has to rewrite such things by "left-factoring" it:<br />
<code><br />
Expression :<br />
TerminalExpression ('+' TerminalExpression)?;<br />
<br />
TerminalExpression :<br />
'(' Expression ')' |<br />
INT <br />
</code><br />
<br />
In practice this is always the same pattern and therefore not problematic. <br />
However, by simply applying Xtext's AST construction we know so far like so ...<br />
<br />
<code><br />
Expression :<br />
{Operation} left=TerminalExpression (op='+' right=TerminalExpression)?;<br />
<br />
TerminalExpression returns Expression:<br />
'(' Expression ')' |<br />
{IntLiteral} value=INT;<br />
</code><br />
<br />
... one would get unwanted elements in the resulting AST.<br />
For instance the expression " ( 42 ) " would result in a tree like this:<br />
<br />
<code><br />
Operation {<br />
left=Operation {<br />
left=IntLiteral {<br />
value=42<br />
}<br />
}<br />
}<br />
</code><br />
Typically one would only want to have one instance of IntLiteral.<br />
<br />
One can solve this problem using a combination of unassigned rule calls and actions:<br />
<code><br />
Expression :<br />
TerminalExpression ({Operation.left=current} op='+' right=TerminalExpression)?;<br />
<br />
TerminalExpression returns Expression:<br />
'(' Expression ')' |<br />
{IntLiteral} value=INT;<br />
</code><br />
<br />
==== Hidden terminal symbols ====<br />
Because parser rules describe not a single token, but a sequence of patterns in the input, it is necessary to define the interesting parts of the input. Xtext introduces the concept of hidden tokens to handle the "noise" like whitespaces, comments etc. in the input sequence gracefully. It is possible to define a set of terminal symbols, that are hidden from the parser rules and automatically skipped when they are recognized. Nevertheless, they are transparently woven into the node model, but not relevant for the semantic model. <br />
<br />
Hidden terminals may (or may not) appear between any other terminals in any cardinality. They can be described per rule or for the whole grammar. The grammar org.eclipse.xtext.common.Terminals comes with a reasonable default and hides all comments and whitespace from the parser rules.<br />
<br />
If a rule defines hidden symbols, you can think of a kind of scope that is automatically introduced. Any rule that is called from the declaring rule uses the same hidden terminals as the calling rule, unless it defines other hidden tokens itself.<br />
<br />
<code lang="text"><br />
Person hidden(WS, ML_COMMENT, SL_COMMENT): <br />
name=fullname age=INT ';';<br />
<br />
Fullname: <br />
(firstname=ID)? lastname=ID;<br />
</code><br />
<br />
The sample rule "Person" defines multiple-line comments (ML_COMMENT), single-line comments (SL_COMMENT), and whitespaces (WS) to be allowed between the fullname and the age. Because "Fullname" does not introduce another set of hidden terminals, it allows the same symbols to appear between 'firstname' and 'lastname' as the calling rule "person." Thus, the following input is perfectly valid for the given grammar snippet:<br />
<br />
<code lang="text"><br />
John /* comment */ Smith // line comment<br />
/* comment */<br />
42 ;<br />
</code><br />
<br />
To see a list of all default terminals like WS look up [[#Language_Inheritance | Language Inheritance]].<br />
<br />
== Meta-Model inference ==<br />
<br />
The meta model of a textual language describes the structure of its abstract syntax trees (AST). <br />
<br />
Xtext uses Ecore EPackages to define meta models. Meta models are declared to be either inferred (generated) from the grammar or imported. <br />
By using the 'generate' directive, one tells Xtext to derive an EPackage from the grammar. <br />
All elements/types can occur multiple times, but are generated only once. <br />
<br />
==== Type and Package Generation ====<br />
Xtext creates<br />
;an EPackage<br />
* for each generated package declaration. After the directive ''generate'' a list of parameters follows. The ''name'' of the EPackage will be set to the first parameter, its ''nsURI'' to the second parameter. An optional alias as the third parameter allows to distinguish generated EPackages later. Only one generated package declaration without an alias is allowed per grammar. The aliases have to be unique among every generated EPackage.<br />
;an EClass<br />
* for each return type of a parser rule. If a parser rule does not define a return type, an implicit one with the same name is assumed. You can specify more than one rule that return the same type but only one EClass will be generated.<br />
* for each type defined in an action or a cross-reference.<br />
;an EEnum<br />
* for each return type of an enum rule.<br />
;an EDatatype<br />
* for each return type of a terminal rule or a datatype rule.<br />
<br />
All EClasses, EEnums and EDatatypes are added to the EPackage referred to by the alias provided in the type reference they were created from.<br />
<br />
==== Feature and Type Hierarchy Generation ====<br />
While walking through the grammar, the algorithm keeps track of a set of the currently possible return types to add features to. <br />
* Entering a parser rule the set contains only the return type of the rule. <br />
* Entering a group in an alternative the set is reset to the same state it was in when entering the first group of this alternative. <br />
* Leaving an alternative the set contains the union of all types at the end of each of its groups.<br />
* After an optional element, the set is reset to the same state it was before entering it. <br />
* After a mandatory (non-optional) rule call or mandatory action the set contains only the return type of the called rule or action. <br />
* An optional rule call does not modify the set.<br />
* A rule call is optional, if its cardinality is '?' or '*'.<br />
<br />
While iterating the parser rules Xtext creates<br />
;an EAttribute in each current return type<br />
* of type EBoolean for each feature assignment using the '?=' operator. No further EReferences or EAttributes will be generated from this assignment.<br />
* for each assignment with the '=' or '+=' operator calling a terminal rule. Its type will be the return type of the called rule.<br />
;an EReference in each current return type<br />
* for each assignment with the '=' or '+=' operator in a parser rule calling a parser rule. The EReference type will be the return type of the called parser rule.<br />
* for each action. The reference's type will be set to the return type of the current calling rule. <br />
<br />
Each EAttribute or EReference takes its name from the assignment/action that caused it. Multiplicities will be 0...1 for assignments with the '=' operator and 0...* for assignments with the '+=' operator. <br />
<br />
Furthermore, each type that is added to the currently possible return types automatically inherits from the current return type of the parser rule. You can specify additional common supertypes by means of "artificial" parser rules, that are never called, e.g.<br />
<br />
CommonSuperType:<br />
SubTypeA | SubTypeB | SubTypeC;<br />
<br />
==== Enum Literal Generation ====<br />
For each alternative defined in an enum rule, the transformer creates an enum literal, when another with the same name cannot be found. The 'literal' property of the generated enum literal is set to the right hand side of the declaration. If it is ommitted, you'll get an enum literal with equal 'name' and 'literal' attributes.<br />
<br />
<code><br />
enum MyGeneratedEnum:<br />
NAME = 'literal' | EQUAL_NAME_AND_LITERAL;<br />
</code><br />
<br />
==== Feature Normalization ====<br />
As a last step, the generator examines all generated EClasses and lifts up similar features to supertypes if there is more than one subtype and the feature is defined in every subtypes. This does even work for multiple supertypes.<br />
<br />
==== Error Conditions ====<br />
The following conditions cause an error<br />
* An EAttribute or EReference has two different types or different cardinality.<br />
* There are an EAttribute and an EReference with the same name in the same EClass.<br />
* There is a cycle in the type hierarchy.<br />
* An new EAttribute, EReference or supertype is added to an imported type.<br />
* An EClass is added to an imported EPackage.<br />
* An undeclared alias is used. <br />
* An imported metamodel cannot be loaded.<br />
<br />
=== Importing existing Meta Models ===<br />
With the import directive in Xtext you can refer to existing Ecore metamodels and reuse the types that are declared in an EPackage. Xtext uses this technique by itself to leverage Ecore datatypes.<br />
<br />
<code lang="text"><br />
import "http://www.eclipse.org/emf/2002/Ecore" as ecore;<br />
</code><br />
<br />
Specify an explicit return type to reuse such imported types. Note that this even works for lexer rules.<br />
<br />
<code lang="text"><br />
terminal INT returns ecore::EInt : ('0'..'9')+;<br />
</code><br />
<br />
== Language Inheritance ==<br />
Xtext supports language inheritance. Grammars that are created via the Xtext wizard extend *org.eclipse.xtext.common.Terminals* by default. <br />
<br />
<source lang="text"><br />
grammar org.xtext.example.MyDsl with org.eclipse.xtext.common.Terminals<br />
<br />
generate myDsl "http://www.xtext.org/example/MyDsl"<br />
<br />
....<br />
</source><br />
<br />
Inheriting from another grammar makes the rules defined in that grammar referable. It is also possible to overwrite rules from the super grammar. <br />
Example :<br />
<source lang="text"><br />
grammar my.SuperGrammar<br />
...<br />
RuleA : "a" stuff=RuleB;<br />
RuleB : "{" name=ID "}";<br />
</source><br />
<br />
<source lang="text"><br />
grammar my.SubGrammar with my.SuperGrammar<br />
<br />
Model : (ruleAs+=RuleA)*;<br />
<br />
// overwrites my.SuperGrammar.RuleB<br />
RuleB : '[' name=ID ']';<br />
</source><br />
<br />
==== Default tokens ====<br />
Xtext is shipped with a default set of predefined, reasonable and often required terminal rules. This grammar is defined as follows:<br />
<source lang="text"><br />
grammar org.eclipse.xtext.common.Terminals hidden(WS, ML_COMMENT, SL_COMMENT)<br />
<br />
import "http://www.eclipse.org/emf/2002/Ecore" as ecore<br />
<br />
terminal ID : '^'?('a'..'z'|'A'..'Z'|'_') ('a'..'z'|'A'..'Z'|'_'|'0'..'9')* ;<br />
terminal INT returns ecore::EInt: ('0'..'9')+ ;<br />
terminal STRING : <br />
'"' ( '\\' ('b'|'t'|'n'|'f'|'r'|'"'|"'"|'\\') | !('\\'|'"') )* '"' |<br />
"'" ( '\\' ('b'|'t'|'n'|'f'|'r'|'"'|"'"|'\\') | !('\\'|"'") )* "'"<br />
; <br />
terminal ML_COMMENT : '/*' -> '*/' ;<br />
terminal SL_COMMENT : '//' !('\n'|'\r')* ('\r'? '\n')? ;<br />
<br />
terminal WS : (' '|'\t'|'\r'|'\n')+ ;<br />
<br />
terminal ANY_OTHER: . ;<br />
</source><br />
<br />
= Architectural Overview =<br />
TMF Xtext itself and every language infrastructure developed with TMF Xtext is configured and wired-up using dependency injection (DI).<br />
We use Google Guice as the underlying framework, and haven't built much on top of it as it pretty much does what we need.<br />
So instead of describing how google guice works, we refer to the website, where additional information can be found [http://code.google.com/p/google-guice/]. <br />
<br />
Using DI allows everyone to set up and change all components. This does not mean that everything which gets configured using DI (we use it a lot) is automatically public API. But we don't forbid use of non-public API, as we think you should decide, if you want to rely on stable API only or use things which might be changed (further enhanced ;-)) in future. See [[Xtext/Documentation/API]].<br />
<br />
== Runtime setup (ISetup) ==<br />
For each language there is an implementation of ISetup generated. <br />
It implements a method called 'doSetup()', which can be called do the global setup.<br />
<br />
This class is intended to be used for runtime and unit testing, only.<br />
The setup method returns an Injector, which can further be used to obtain a parser, etc.<br />
The setup method also registers the ResourceFactory and generated EPackage with the respective global registries provided by EMF.<br />
<br />
So basically you can just run the setup and start using EMF API to load and store models of your language.<br />
<br />
== Setup within Eclipse / Equinox ==<br />
Within Eclipse we have a generated Activator, which creates a Guice injector using the [[Modules|modules]].<br />
In addition an IExecutableExtensionFactory is generated for each language, which is used to create ExecutableExtensions.<br />
This means that everything which is created via extension points is managed by guice as well, i.e. you can declare dependencies and get them injected up on creation. <br />
<br />
The only thing you have to do in order to use this factory is to prefix the class with the factory (guice.Aware) name followed by a colon.<br />
<br />
<extension<br />
point="org.eclipse.ui.editors"><br />
<editor<br />
class="guice.Aware:org.eclipse.xtext.ui.core.editor.XtextEditor"<br />
contributorClass="org.eclipse.ui.editors.text.TextEditorActionContributor"<br />
default="true"<br />
extensions="ecoredsl"<br />
id="org.eclipse.xtext.example.EcoreDsl"<br />
name="EcoreDsl Editor"><br />
</editor><br />
</extension><br />
<br />
== Modules ==<br />
The Guice Injector configuration is done through the use of Modules (also a Guice concept).<br />
The generator provides two modules when first called, one for runtime ([MyLanguage]RuntimeModule) and one for UI ([MyLanguage]UIModule).<br />
These modules are initially empty and intended to be manually edited when needed. These are also the modules used directly by the setup methods. <br />
By default these modules extend a fully generated module.<br />
<br />
=== Generated Modules ===<br />
The fully generated modules (never touch them!) are called Abstract[MyLanguage]RuntimeModule and Abstract[MyLanguage]UiModule resp. <br />
They contain all components which have been generated specifically for the language at hand.<br />
Examples are: the generated parsers, serializer or for UI a proposal provider for content assist is generated.<br />
What goes into the modules depends on how your generator is configured.<br />
<br />
=== Default Modules ===<br />
Finally the fully generated modules extend the DefaultRuntimeModule (resp. DefaultUiModule), which contains all the default configuration. The default configuration consists of all components for which we have generic default implementations (interpreting as opposed to generated). <br />
Examples are all the components used in linking, the outline view, hyperlinking and navigation. <br />
<br />
=== Changing Configuration ===<br />
We use the primary modules ([MyLanguage]RuntimeModule and [MyLanguage]UiModule) in order to change the configuration. <br />
The class is initially empty and has been generated only to allow for arbitrary customization.<br />
<br />
In order to provide a simple and convenient way, in TMF Xtext every module extends AbstractXtextModule. <br />
This class allows to write bindings like so:<br />
<br />
public Class<? extends MyInterface> bind[anyname]() {<br />
return MyInterfaceImpl.class;<br />
}<br />
<br />
<br />
Such a method will be interpreted as a binding from MyInterface to MyInterfaceImpl. Note that you simply have to override a method from a super class (e.g. from the generated or default module) in order to change the respective binding.<br />
Although this is a convenient and simple way, you have of course also the full power of Guice, i.e. you can override the Guice method ''void bind(Binding)'' and do what every you want.<br />
<br />
= Runtime Architecture =<br />
== Value Converters ==<br />
== Linking ==<br />
The linking feature allows for specification of cross references within an Xtext grammar.<br />
The following things are needed for the linking:<br />
# declaration of a cross link in the grammar (at least in the meta model)<br />
# specification of linking semantics<br />
<br />
=== Declaration of cross links ===<br />
In the grammar a cross reference is specified using square brackets.<br />
<br />
CrossReference :<br />
'[' ReferencedEClass ('|' terminal=AbstractTerminal)? ']'<br />
<br />
Example:<br />
<br />
ReferringType :<br />
'ref' referencedObject=[Entity|(ID|STRING)];<br />
<br />
The meta model derivation would create an EClass 'ReferringType' with an EReference 'referencedObject' of type 'Entity' (containment=false). The referenced object would be identified either by an ID or a STRING and the surrounding information (see scoping).<br />
<br />
Example: While parsing a given input string, say<br />
<br />
ref Entity01<br />
<br />
Xtext produces an instance of 'ReferringType'. After this parsing step it enters the linking phase and tries to find an instance of ''Entity'' using the parsed text 'Entity01'. The input <br />
<br />
ref "EntityWithÄÖÜ"<br />
<br />
would work analogously. This is not an ID (umlauts are not allowed), but a STRING (as it is apparent from the quotation marks).<br />
<br />
=== Specification of linking semantics ===<br />
The default ILinker implementation is provided with an instance of ILinkingService.<br />
Although the default linking behavior is appropriate in many cases there might be scenarios where this is not sufficient. For each grammar a linking service can be implemented/configured, which implements the following interface:<br />
<source lang="java"><br />
public interface ILinkingService extends ILanguageService {<br />
<br />
/**<br />
* Returns all EObjects referenced by the given link text in the given context.<br />
*/<br />
List<EObject> getLinkedObjects(EObject context, EReference reference, LeafNode text);<br />
<br />
/**<br />
* Returns the textual representation of a given object as it would be serialized in the given context.<br />
* <br />
* @param object<br />
* @param reference<br />
* @param context<br />
* @return the text representation.<br />
*/<br />
String getLinkText(EObject object, EReference reference, EObject context);<br />
}<br />
<br />
</source><br />
The method getLinkedObjects is directly related to this topic whereas getLinkText adresses complementary functionality: it is used for Serialization.<br />
<br />
A simple implementation of the linking service (DefaultLinkingService.java) is shipped with Xtext and is used for any grammar per default. It uses the default implementation of IScopeProvider. <br />
<br />
An IScopeProvider is responsible for providing an IScope for a given EObject and it's EReference, for which all candidates shall be returned. <br />
<br />
<source lang="java"><br />
public interface IScopeProvider extends ILanguageService {<br />
<br />
/**<br />
* Returns a scope for the given context.<br />
*<br />
* @param context - the element from which an element shall be referenced <br />
* @param reference - the reference to be filled. <br />
* @return {@link IScope} representing the inner most {@link IScope} for the passed context and reference<br />
*/<br />
public IScope getScope(EObject context, EReference reference);<br />
}<br />
<br />
</source><br />
<br />
An IScope represents an element of a linked list of scopes. That means that a scope can be nested within an outer scope.<br />
For instance Java has multiple kinds of scopes (object scope, type scope, etc,).<br />
<br />
For Java one would create the scope hierarchy as commented in the following example:<br />
<br />
<source lang="java"><br />
<br />
// file contents scope<br />
import static my.Constants.STATIC;<br />
<br />
public class ScopeExample { // class body scope<br />
private Object field = STATIC;<br />
<br />
private void method(String param) { // method body scope<br />
String localVar = "bar";<br />
innerBlock: { // block scope<br />
String innerScopeVar = "foo";<br />
Object field = innerScopeVar;<br />
// the scope hierarchy at this point would look like so:<br />
//blockScope{field,innerScopeVar}-><br />
//methodScope{localVar,param}-><br />
//classScope{field}-> ('field' is overlayed)<br />
//fileScope{STATIC}-><br />
//classpathScope{'all qualified names of accessible static fields'} -><br />
//NULLSCOPE{}<br />
//<br />
}<br />
field.add(localVar);<br />
}<br />
}<br />
<br />
</source><br />
<br />
In fact the class path scope should also reflect the order of class path entries.<br />
For instance:<br />
classpathScope{stuff from bin/} -> classpathScope{stuff from foo.jar/} -> ... -> classpathScope{stuff from JRE System Library} -> NULLSCOPE{}<br />
<br />
=== Default linking semantics ===<br />
The default implementation for all languages, looks within the current file for an EObject of the respective type ('Entity') which has a name attribute set to 'Entity01'. <br />
<br />
''Example:''<br />
Given the grammar :<br />
...<br />
Model : (stuff+=(Ref|Entity))*;<br />
<br />
Ref : 'ref' referencedObject=[Entity|ID] ';';<br />
<br />
Entity : 'entity' name=ID ';';<br />
<br />
In the following model :<br />
ref Entity01;<br />
entity Entity01;<br />
<br />
the ref would be linked to the declared entity ('entity Entity01;').<br />
<br />
==== Default Imports ====<br />
There is a default implementation for inter-resource referencing, which as well uses convention:<br />
<br />
''Example:''<br />
Given the grammar :<br />
...<br />
Model : (imports+=Import)* (stuff+=(Ref|Entity))*;<br />
<br />
Import : 'import' importURI=STRING ';';<br />
<br />
Ref : 'ref' referencedObject=[Entity|ID] ';';<br />
<br />
Entity : 'entity' name=ID ';';<br />
<br />
With this grammar in place it would be possible to write three files in the new DSL where the first references the other two, like this:<br />
<br />
--file model.dsl<br />
import "model1.dsl";<br />
import "model2.dsl";<br />
<br />
ref Foo;<br />
entity Bar;<br />
<br />
--file model1.dsl <br />
entity Stuff;<br />
<br />
--file model2.dsl<br />
entity Foo;<br />
<br />
The resulting default scope list is as follows:<br />
<br />
Scope (model.dsl) {<br />
parent : Scope (model1.dsl) {<br />
parent : Scope (model2.dsl) {}<br />
}<br />
}<br />
<br />
So, the outer scope is asked for an Entity named 'Foo', as it does not contain such a declaration itself its parent is asked and so on.<br />
The default implementation of IScopeProvider creates this kind of scope chain.<br />
<br />
=== Fragment Provider - Playing nice with EMF URIs ===<br />
Although inter-Xtext linking is not done by URIs, you may want to be able to reference your EObject from non-Xtext models.<br />
In those cases URIs are used, which are made up of a part identifying the resource. Each EObject contained in a Resource can be identified by a so called 'fragment'.<br />
A fragment is a part of an EMF URI and needs to be unique per resource.<br />
The generic XMI resource shipped with EMF provides a generic path-like computation of fragments. With an XMI or other binary-like serialization it is also common and possible to use UUIDs.<br />
<br />
However with a textual concrete syntax we want to be able to compute fragments out of the given information. We don't want to force people to use UUIDs (i.e. synthetic identifiers) or relative generic pathes (very fragile), in order to refer to EObjects.<br />
Therefore one can contribute a so called IFragmentProvider per language.<br />
<source lang="java"><br />
public interface IFragmentProvider extends ILanguageService {<br />
<br />
/**<br />
* Computes the local ID of the given object. <br />
* @param obj<br />
* The EObject to compute the fragment for<br />
* @return the fragment, which can be an arbitrary string but must be unique<br />
* within a resource. Return null to use default implementation<br />
*/<br />
String getFragment(EObject obj);<br />
<br />
/**<br />
* Locates an EObject in a resource by its fragment. <br />
* @param resource<br />
* @param fragment<br />
* @return the EObject <br />
*/<br />
EObject getEObject(Resource resource, String fragment);<br />
}<br />
</source><br />
<br />
However, the currently available default fragment provider does nothing.<br />
<br />
= UI Architecture =<br />
<br />
For the following part we will refer to a concrete example grammar in order to explain certain aspect of the UI more clearly. The used example grammar is as follows:<br />
<br />
<source lang="text"><br />
Model :<br />
"model" intAttribute = INT ( stringDescription = STRING ) ? "{" <br />
( rules += AbstractRule | types += CustomTypeParserRule ) * <br />
"}" <br />
;<br />
<br />
AbstractRule:<br />
RuleA | RuleB<br />
;<br />
<br />
RuleA :<br />
"RuleA" "(" name = ID ")" ;<br />
<br />
RuleB :<br />
"RuleB" "(" ruleA = [RuleA] ")" ;<br />
<br />
CustomTypeParserRule returns ReferenceModel::CustomType :<br />
'type' name=ID;<br />
</source><br />
<br />
== Content Assist ==<br />
<br />
The Xtext generator, amongst other things, generates the following two content assist (CA) related artefacts:<br />
<br />
* a concrete proposal provider class named ''[Language]GenProposalProvider'' generated into the src-gen folder within the 'ui' project<br />
* a service framework configuration for the related CA interfaces (IProposalProvider,IContentAssistant and IContentAssistProcessor)<br />
<br />
First we will investigate the generated ''[Language]GenProposalProvider'' which contains the following methods (for the example grammar above):<br />
<br />
=== ProposalProvider ===<br />
<br />
<source lang="java"><br />
public List<? extends ICompletionProposal> completeModelIntAttribute(Assignment assignment, EObject model, String prefix, IDocument doc,int offset) {<br />
return Collections.singletonList(createCompletionProposal("1", offset)); <br />
}<br />
<br />
public List<? extends ICompletionProposal> completeModelStringDescription(Assignment assignment, EObject model, String prefix, IDocument doc,int offset) {<br />
return Collections.singletonList(createCompletionProposal("\"ModelStringDescription\"", offset)); <br />
}<br />
<br />
public List<? extends ICompletionProposal> completeModelRules(Assignment assignment, EObject model, String prefix, IDocument doc,int offset) {<br />
return Collections.emptyList();<br />
}<br />
<br />
public List<? extends ICompletionProposal> completeModelTypes(Assignment assignment, EObject model, String prefix, IDocument doc,int offset) {<br />
return Collections.emptyList();<br />
}<br />
<br />
public List<? extends ICompletionProposal> completeRuleAName(Assignment assignment, EObject model, String prefix, IDocument doc,int offset) {<br />
return Collections.singletonList(createCompletionProposal("RuleAName", offset));<br />
}<br />
<br />
public List<? extends ICompletionProposal> completeRuleBRuleA(Assignment assignment, EObject model, String prefix, IDocument doc,int offset) {<br />
return lookupCrossReference(((CrossReference)assignment.getTerminal()), model, offset);<br />
}<br />
<br />
public List<? extends ICompletionProposal> completeCustomTypeParserRuleName(Assignment assignment, EObject model, String prefix, IDocument doc,int offset) {<br />
return Collections.singletonList(createCompletionProposal("CustomTypeParserRuleName", offset));<br />
}<br />
<br />
public List<? extends ICompletionProposal> completeReferenceModelCustomType(RuleCall ruleCall, EObject model, String prefix,IDocument doc, int offset) {<br />
return Collections.emptyList();<br />
}<br />
<br />
@Override<br />
protected String getDefaultImageFilePath() {<br />
return "icons/editor.gif";<br />
}<br />
<br />
@Override<br />
protected String getPluginId() {<br />
return UI_PLUGIN_ID;<br />
}<br />
</source><br />
<br />
As you can see from the snippet above the generated ProposalProvider class contains a 'completion' proposal method for each assignment and rule with a custom return type. In addition to the methods declared in interface ''IProposalProvider'', the framework tries to call these methods for assignments and rules using reflection. The signature of the generated 'completion' proposal methods are named after the following pattern.<br />
<br />
''for assignments''<br />
<source lang="java"><br />
public List<ICompletionProposal> complete[Typename][featureName](Assignment ele, EObject model, String prefix, int offset);<br />
</source><br />
<br />
''for rules '''with a custom return type'''''<br />
<br />
<source lang="java"><br />
public List<? extends ICompletionProposal> complete[ModelAlias][ReturnType](RuleCall ruleCall, EObject model, String prefix,IDocument doc, int offset);<br />
</source><br />
<br />
'''Note that if you have generated Java classes for your domain model (meta model) you can alternatively declare the second parameter (model) using a specific type.'''<br />
<br />
''for assignments with a custom return type''<br />
<br />
<source lang="java"><br />
public List<ICompletionProposal> completeCustomTypeParserRuleName(Assignment ele, ReferenceModel.CustomType model, String prefix, int offset);<br />
</source><br />
<br />
=== Service Configuration ===<br />
<br />
The configuration of the CA related part goes into the generated [Namespace]Gen[Grammar]UiConfig class and includes the following three interfaces.<br />
<br />
* org.eclipse.xtext.ui.common.editor.codecompletion.IProposalProvider<br />
* org.eclipse.jface.text.contentassist.IContentAssistant ([[http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/api/org/eclipse/jface/text/contentassist/IContentAssistant.html]])<br />
* org.eclipse.jface.text.contentassist.IContentAssistProcessor ([[http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/api/org/eclipse/jface/text/contentassist/IContentAssistProcessor.html]])<br />
<br />
TODO: describe/link where to configure a manual implementation of IProposalProvider??<br />
<br />
=== Runtime Examples ===<br />
<br />
<source lang="text"><br />
model 0 >>CA<<<br />
</source><br />
<br />
will execute the following call sequence to ''IProposalProvider'' implementations<br />
<br />
#completeRuleCall 'STRING' <br />
#completeModelStringDescription feature 'stringDescription' <br />
#completeKeyword '{'<br />
<br />
<source lang="text"><br />
model 0 "ModelStringDescriptionSTRING" {<br />
>>CA<<<br />
}<br />
</source><br />
<br />
# completeRuleCall 'AbstractRule'<br />
# completeRuleCall 'RuleA' <br />
# completeKeyword 'RuleA' <br />
# completeRuleCall 'RuleB'<br />
# completeKeyword 'RuleB' <br />
# completeModelRules feature 'rules' <br />
# completeRuleCall 'CustomTypeParserRule' <br />
# completeReferenceModelCustomType 'CustomTypeParserRule' <br />
# completeKeyword 'type' <br />
# completeModelTypes feature 'types' <br />
# completeKeyword '}'<br />
<br />
<source lang="text"><br />
model 0 "ModelStringDescriptionSTRING" {<br />
type >>CA<<<br />
}<br />
</source><br />
<br />
#completeRuleCall 'ID' <br />
#completeCustomTypeParserRuleName feature 'name'<br />
<br />
<source lang="text"><br />
model 0 "ModelStringDescriptionSTRING" {<br />
RuleA (RuleAName)<br />
RuleB (>>CA<<<br />
}<br />
</source><br />
<br />
#completeRuleBRuleA feature 'ruleA' - Which in turn invokes ''lookupCrossReference'' which delegates to the configured '''ILinkingCandidatesService#getLinkingCandidates''' to determine all available 'link' candidates.</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Equinox/p2/Obsolete_Docs/Proposals/Install_Handler_Proposal&diff=140331Equinox/p2/Obsolete Docs/Proposals/Install Handler Proposal2009-02-14T11:12:05Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div>{{CommentBox|W.I.P}}<br />
=Introduction=<br />
This page describes a proposal for adding support for a mechanism similar to the Update Manager's "Install Handler". <br />
<br />
* See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=257792 bug 257792] for general discussion.<br />
* See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=263304 bug 263304] for discussion about meta data format.<br />
<br />
==Background==<br />
When using Update Manager it is possible to write a plugin, that is packaged as a jar and included in a feature. <br />
The feature manifest is modified to refer to the jar, and the class that implements the install handler to use.<br />
Update Manager executes this handler as part of the installation after having set up an environment consisting of org.eclipse.core.runtime, org.eclipse.update.core, and optionally (unless running in the headless mode) org.eclipse.ui. <br />
==Requirements on a p2 equivalent service==<br />
* Does not have to be backwards compatible with UM's Install Handlers<br />
* Does not replace the need to write a custom installer when different startup, splash-screens etc. are required.<br />
* Should provide a mechanism to allow an IU to specify requirements on the installer configuration<br />
<br />
And - as discovered when elaborating on the solution:<br />
* Should handle version differences between local existing meta data, the version of an installer, and the version of what is being provisioned. At least to the degree that a user would not be able to destroy an exiting installation, or install a combination that later will be unable to update itself.<br />
<br />
=Proposal=<br />
The provisioning of install handlers can be seen as a provisioning/update of the currently running installer. First, the resolution is computed. Once all the IU's to process are known, the requirements on the installer are collected. A new resolution is then performed against the installer/agent profile. When resolved, any new installation/update required in installer/agent is performed. Once processed, the install of the original plan proceeds. Any custom install instructions are performed on custom touchpoints.<br />
<br />
Although this sound simple - there are many issues to overcome.<br />
<br />
==Issues==<br />
* Installing an IU into the agent profile can have an effect on the already calculated plan when agent profile and profile to install to is the same<br />
* An install handler needs to be installed in all agents that perform operations on a profile repository where a bundle requiring an install handler is installed. (Install handler may have uninstall instructions, and the install location may be garbage collected). The install handler must be available locally as it would be bad to require a fetch from some remote meta data repository (which may not even exist when the user wants to uninstall some bundle).<br />
* When an update of a bundle requires a newer version of the install handler both the old and the new version must be available to the agent.<br />
* Attempt will probably be made to use different version of an installer against different versions of the p2 data area. (Typically a newer installer will be used to install an older app, and attempts will be made to upgrade using both older and newer installations).<br />
* Currently, p2 can only have one running setup, but an experiment shows that it is possible to stop and start p2 services to enable a series of provisioning actions to take place - this is fine, but services where not designed to handle this, and multithreaded use can produce surprises.<br />
* Acting on install handlers depending on the type of installation - an example is an IH that sets a registry key - this is not wanted if the installation is performed for the purpose of packaging.<br />
<br />
==Solutions==<br />
After several iterations and attempts to work around limitations and issues - here is the final proposal.<br />
<br />
Considerations:<br />
* Should be implementable within the 3.5 timeframe<br />
* Should handle first install as well as updates <br />
* Should handle Eclipse SDK, as well as "other apps"<br />
* Should handle provisioning of "anything" - what is installed is not a java application<br />
<br />
Main Idea:<br />
Use a primary/bootstrap and a secondary installer. The "primary/bootstrap" installer is what gets downloaded by users (like the current p2-installer). The primary installer's main task is to install the secondary installer and hand the installation work over to the second installer.<br />
<br />
The second installer can be as complex as the publisher wants - the only requirements is that it has a "secondary installer API" that enables the primary installer to hand over the task. More specifically, the secondary installer can be as complex as the entire Eclipse SDK - the secondary installer in this case can be the embedded director.app.<br />
<br />
The primary installer is restricted in that it does not handle install handlers - this task is performed by the secondary installer.<br />
<br />
===Primary to Secondary API===<br />
The primary installer can be used to either perform a new install, or to modify an existing installation. In the "new install" case, the primary installer must be given information about how to set up the profile and where to install the secondary installer. In the "update existing" case, the primary installer needs to find this information in what is already installed.<br />
<br />
====The Profile====<br />
Properties in the profile should define how to start the secondary installer.<br />
<br />
* o.e.e.p2.secondary.launcher - defines a secondary launcher name. If property is missing it defaults to the product's launcher<br />
* o.e.e.p2.secondary.app - defines the application name (can default to "director.app" if missing).<br />
* o.e.e.p2.secondary.installLocation - a directory path (if different than the product's install location)<br />
<br />
Parameters to the secondary installer should be passed via a single command line argument - a URI to a properties file (which in most cases can be the same properties file as being used to drive the primary installer).<br />
<br />
====The Installer.properties====<br />
The installer.properties should be expanded to include the following:<br />
* o.e.e.p2.secondary.rootId - the UI rootId for the secondary installer<br />
* o.e.e.p2.secondary.launcher - if different than the primary launcher<br />
* o.e.e.p2.secondary.secondary.app - the application name for the secondary installer<br />
* o.e.e.p2.secondary.relativeLocation - a path relative to the install location where the secondary installer should be installed (optional)<br />
* o.e.e.p2.p2DataAreaVersion - a requirement on the primary installer - (see below)<br />
* o.e.e.p2.secondary.mode - how feedback is provided to the user (see below)<br />
<br />
'''p2DataAreaVersion'''<br/><br />
This property is required as it is otherwise impossible to know if the primary installer instance is capable of producing a "compatible p2 container" for what it is installing.<br />
A primary installer may have backwards compatibility and needs to know which version it should use when writing a new data area and profile. This property also prevents a user mistake where the wrong primary installer is selected. If the primary installer is not capable of satisfying the request it can simply give up and tell the user to get the correct version.<br />
<br />
In addition to this, a p2 data area should contain meta data that states its version. <br />
<br />
Example of issues. A 3.n version is used to create shared installations, and later a 3.n+1 version tries to install shared. The product to install requires that it supports 3.n+1.<br />
Currently, (best case) some p2 service would detect that the meta data it tries to read is of the wrong version, and worst case is that the newer version writes something that existing installed versions does not understand.<br />
<br />
The issue arises since there is a requirement on the "container" when something that manages itself is installed. When standalone installations are made, the secondary installer could perform an upgrade of the data area, but in a shared scenario this becomes very difficult.<br />
<br />
Ideally, the IU's being installed should declare their requirements on the container they are installed into. This information is however obtained too late since the profile is needed at the very beginning of the installation.<br />
<br />
'''mode'''<br/><br />
When the primary hands over to the secondary installer, this property tells the secondary how progress and feedback to the user should be handled. It could define something like "headless" or "ui", where "headless" means that ui should not be loaded, no ui progress monitor, and no ui for explaining errors. The "ui" mode means that the secondary installer is responsible for providing the ui (if it has any).<br />
<br />
A third alternative mode is that the secondary installer reports progress to the primary using a socket. Such a progress monitor implementation is available in buckminster.<br />
<br />
====FAQ Primary/Secondary====<br />
'''Why the separation on primary and secondary?'''<br/><br />
Primarily [sic] it provides a separation of concerns - the primary installer has one task - to install the secondary installer in a p2 container of a specified version. It uses a defined set of protocols, and does not support install handlers. <br />
<br />
'''Why not let the primary also handle install handlers?'''<br/><br />
The main reason is that the p2, once started, is tied to one p2 data area. Although experiments have shown that it is possible to stop all p2 services and restart them on a different area, and thus making it possible to run a sequence of provisioning jobs, the services where not designed to be used this way, and code that makes use of the services may break. This is important, since if the primary installer should update itself to include everything that is needed to carry out a complex installation it would need to a) first calculate the plan for the thing to install, b) detect if this plan needs special install handling - to do a) and b) it needs to run against the target p2 data area. It would then c) need to switch back to its own data area to d) install the missing bundles detected in b). Once it has updated itself, it must again switch to the target data area and e) execute the plan to install into the target. <br />
<br />
Having done all of the above, continued operations (by a user) requires that the install handlers are also available in the target (since it is self managed). All the work to get the install handlers into the primary installer is thus wasted effort. <br />
<br />
===Install Handlers===<br />
The install handler issue is now much easier to handle. The secondary installer (i.e. director) does the following:<br />
* a) create the plan for target install<br />
* b) creates an install handler plan based on the requirements on installer from the plan in a)<br />
* c) if the plan in b) is empty, everything required is already in place (skip to step e), if not, the plan from b) is executed<br />
* d) a new plan for the target install must be computed as the installation of the installer requirements in c) may have an effect on the plan from a)<br />
* e) the target plan (from a, (or d)) is executed.<br />
<br />
The director always does this. It does not matter if it was given instructions from a user in a "self managed ui", or from a primary installer.<br />
<br />
[[Category:Equinox p2|Install Handler Proposal]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Using_Policy_Files&diff=140305Using Policy Files2009-02-13T16:59:24Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div>=Eclipse 3.4 p2 Note=<br />
<br />
Using Policy files for "[[Using_Policy_Files#mirrorControl|mirror control]]" is obsoleted by [[Equinox p2]], available in Eclipse 3.4.<br />
<br />
To avoid reaching mirrors specified for a particular update site / repository, there are two ways:<br />
<br />
* If you are in control of the repo, you can remove the mirroring information to make the site unaware of any remote mirrors.<br />
<br />
<site pack200="true"<br />
digestURL="http://download.eclipse.org/modeling/emf/updates/milestones/"<br />
mirrorsURL="http://www.eclipse.org/downloads/download.php?file=/modeling/emf/updates/milestones/site.xml&amp;format=xml"><br />
<br />
becomes<br />
<br />
<site pack200="true"><br />
<br />
* If you are not in control of the repo, you can tell the [[Equinox_p2_director_application|p2 director]] to ignore mirrors:<br />
<br />
-vmargs -Declipse.p2.mirrors=false<br />
<br />
See also: {{bug|241430}}, {{bug|236762}}.<br />
<br />
=Usage=<br />
<br />
Policy files allow a user to configure where to search for updates to a feature when checking for updates. <br />
<br />
Why would you want this? <br />
<br />
* <span id="mirrorControl">'''For mirror control'''. With a policy file you can force your users to update from a mirror within your organization's firewall, instead of letting them choose a public mirror. This might give better performance or at least let you monitor the bits being transferred. Of course you'd have to [http://www.eclipse.org/downloads/mir_request.php be an Eclipse mirror] first.</span><br />
<br />
* <span id="testing">'''For testing'''. If your features point to one update site (eg., for Releases) and you want to test doing an update from an old Release to a current Integration build, but that Integration build is not listed on the Releases site. For example, EMF uses [http://download.eclipse.org/modeling/emf/updates/site.xml http://download.eclipse.org/modeling/emf/updates/] for Releases and [http://download.eclipse.org/modeling/emf/updates/site-interim.xml http://download.eclipse.org/modeling/emf/updates/site-interim.xml] for all other builds (I, M, S). </span><br />
<br />
* <span id="patching">'''For patching'''. With a policy file you can update a publicly available EPL'd feature with your own custom version. Bear in mind doing so still must be done in adherence to EPL rules. See [http://www.eclipse.org/legal/ http://www.eclipse.org/legal/].</span><br />
<br />
==Creating the Policy File==<br />
A sample policy file is shown below:<br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<update-policy><br />
<url-map pattern="feature.id" url="<nowiki>http://hostname/update/nightly/nightlySite.xml</nowiki>"/><br />
</update-policy><br />
<br />
In this example, we save this to an XML file named "policy.xml". This is then placed next to the corresponding update site.xml. This effectively says "when I see feature with id x, instead go to update site y rather than the default". The pattern attribute is a string that represents prefix of a feature ID (up to and including a complete ID). A value of "<tt>*</tt>" matches '''all''' features. For example, a pattern of "<tt>org.eclipse</tt>" will match <tt>org.eclipse.jdt</tt> and <tt>org.eclipse.swt</tt> but '''not''' <tt>com.mycompany.myproduct</tt><br />
<br />
Note that the wildcard does not work embedded within a larger pattern; it can only be used by itself. For example, a pattern like "<tt>org.*</tt>" does '''not''' match all plugins that start with <tt>org</tt><br />
<br />
===Example===<br />
<br />
If you wanted to update all features from a non-standard update site, you could use a policy file to redirect from the default Update site to a secondary one. For example:<br />
<br />
<?xml version="1.0" encoding="UTF-8"?><br />
<update-policy><br />
<url-map pattern="*" url="http://download.eclipse.org/modeling/emf/updates/site-interim.xml"/><br />
</update-policy><br />
<br />
==Using the Policy File==<br />
<br />
In Eclipse, navigate to <code>Window > Preferences > Install/Update</code>, and paste in the URL to the policy file and hit OK, eg:<br />
http://download.eclipse.org/modeling/mdt/updates/policy.xml<br />
:: or, for a local file:<br />
<nowiki>file:///home/nickb/workspace2/modeling/mdt/updates/policy.xml</nowiki><br />
<br />
The next time you search for updates, Eclipse will use the URL specified in the policy file, instead of what's in the feature.xml files.<br />
<br />
----<br />
<br />
<br />
An additional thought is to provide a preference page to allow the end user to choose which "release stream" they wish to subscribe to. In this case, there is a radio button that might specify "stable", "rc" and "nightly". Selecting one of these radio buttons would automatically set the policy file behind the scenes.<br />
<br />
[[Category:Releng]] [[Category:Coordinated]] [[Category:Ganymede]] [[Category:Europa]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Google_Summer_of_Code_2009_Ideas&diff=137306Google Summer of Code 2009 Ideas2009-01-19T17:53:21Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div>== Rules ==<br />
* Be creative<br />
* Be specific: what do you want to be implemented<br />
* If you are willing to mentors those ideas, add your name and email to the idea.<br />
* It is ok to have a project idea without parent project<br />
* If you're an interested student, add your name and email next to the idea. It is ok to have several students interested by one idea.<br />
<br />
== Ideas ==<br />
<br />
{| border="1" cellpadding="2" width="100%"<br />
!width="20%"|Title<br />
!width="5%" align="center"|Project<br />
!width="40%"|Abstract - links to details/bugs/etc<br />
!width="10%"|Reporter<br />
!width="10%"|Possible mentor(s)<br />
!width="15%"|Comments<br />
!width="10%"|Potential student(s)<br />
|-<br />
| Your project title here e.g. Cure world hunger<br />
| Your project link here e.g. [http://www.eclipse.org/soc SoC]<br />
| Your project description here. Be as precise and specific as possible. Link to bugs...<br />
| Your name here<br />
| Your Prospective mentors here (If you're an eclipse committer + the reporter, you should leave your name here too!<br />
| Your additional comments<br />
| <br><br />
|-<br />
| PDE Menage A Trois<br />
| [http://www.eclipse.org/pde PDE]<br />
| The goal of this project is to update PDE to use EMF and Databinding under the covers. In PDE, we have a lot of models and editors backed by custom code that has shown its age and is difficult to maintain. This is an opportunity to modernize PDE and make it more extensible.<br />
| <interested student here><br />
| Chris Aniszczyk, Benjamin Cabé<br />
| None<br />
| <br><br />
|-<br />
| Write Eclipse plug-ins in PHP<br />
| [[e4/Languages]]<br />
| Leverage one of existing PHP/Java bridges for adding a PHP support into [[e4]]<br />
| <interested student here><br />
| Michael Spector<br />
| None<br />
| <br><br />
|-<br />
| Ant buildfile refactorings<br />
| [http://www.eclipse.org/eclipse/ant/ Platform Ant]<br />
| Ant buildfiles can become large and complex and would benefit from refactoring. Currently there is no support beyond renaming within a buildfile to allow the developer to efficiently refactor Ant buildfiles. The goals would be to implement an infrastructure to support refactorings in Ant buildfiles, participate in other components refactorings and provide a starter set of Ant buildfile refactorings. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=89938 bug 89938] for some initial buildfile refactoring ideas.<br />
| Darin Swanson<br />
| [mailto:Darin_Swanson@us.ibm.com Darin Swanson]<br />
| None<br />
| [mailto:allenchue@gmail.com Yin Qiu] from Nanjing Univ., China<br />
|-<br />
| XSLT Refactorings<br />
| [http://www.eclipse.org/webtools/incubator/ Webtools XSL Tools]<br />
| XSL Tools provides editing and debugging support. Currently there is no refactoring support for XSLT 1.0 or XSLT 2.0 stylesheets. Refactorings could include Extract Template, Extract Call Template, etc. Refactorings should participate with the platform refactoring framework.<br />
| David Carver<br />
| [mailto:d_a_carver@yahoo.com David Carver]<br />
| None<br />
| <br><br />
|-<br />
| External XSLT Transformations<br />
| [http://www.eclipse.org/webtools/incubator/ Webtools XSL Tools]<br />
| Implement a configuration option and launching ability for non java XSLT processors. Particularly add support so that xsltproc could be used as a processor. {{bug|245743}}<br />
| David Carver<br />
| [mailto:d_a_carver@yahoo.com David Carver]<br />
| None<br />
| <br><br />
|-<br />
| XQuery/XPath Parser<br />
| [http://www.eclipse.org/webtools/incubator/ Webtools XQuery]<br />
| Currently the XQuery Development Tools is using an Antlr xpath parser from the XQPretty project. However this does not currently integrate well with the editor, and a javacc implementation that expands the current XML javacc parser would be ideal. This would leverage and hook into the existing parsing framework for the Structured Source Editor and provide identification of Regions and Partitions for the editor. A bonus would be to have validation of the XQuery syntax as well. See {{bug|226245}} for more information in regards to the XPath 2.0 support. <br />
| David Carver<br />
| [mailto:d_a_carver@yahoo.com David Carver]<br />
| None<br />
| [mailto:jin.phd@gmail.com Jin Mingjian], Chinese Academy of Sciences, China<br />
|-<br />
| VEX (Visual Editor for XML) Multipage Editor support<br />
| [http://www.eclipse.org/webtools/incubator/ Webtools VEX]<br />
| VEX supports the visual editing in a word processor like feel of a variety of XML formats. With the use of CSS stylesheets for the XML, it can render a WYSIWYG presentation. VEX currently does not have a working Multipage Editor..meaning that switching from the Design view to a source view, the XML is not shown in the source view and not synchronized. The model is EMF based, and the XML editor from WTP is DOM based, this project would leverage the EMF2SSEDOM framework for providing the synchronization between the two. The project is also open to other alternatives, and will allow the candidate wide latitude in experimentation of ways to implement the synchronization.<br />
| David Carver<br />
| [mailto:d_a_carver@yahoo.com David Carver]<br />
| None<br />
| <br><br />
|-<br />
| RelaxNG Validator<br />
| [http://www.eclipse.org/webtools/incubator/ Webtools Incubator]<br />
| RelaxNG is an alternative schema language to the more widely known XML Schemas and DTDs. This project would implement RelaxNG valadition using the WTP validation framework. This should allow for both the as you type validation, as well as batch validation.<br />
| David Carver<br />
| [mailto:d_a_carver@yahoo.com David Carver]<br />
| None<br />
| <br><br />
|-<br />
| RelaxNG Editor<br />
| [http://www.eclipse.org/webtools/incubator/ Webtools Incubator]<br />
| Implement a full featured editor for the RelaxNG compact syntax, with optional editing of the RelaxNG XML syntax as well. Should offer syntax highlighting, content assistance, validation against the relaxng specification, file wizards, preference pages, etc. Ideally built off and leverages the Structured Source Editor from WTP.<br />
| David Carver<br />
| [mailto:d_a_carver@yahoo.com David Carver]<br />
| None<br />
| <br><br />
|-<br />
| VEX - Docbook 5 support<br />
| [http://www.eclipse.org/webtools/incubator/ Webtools VEX]<br />
| Implement a set of CSS stylesheets and appropriate outline views and enhancements for DocBook 5 features. This may require enhancements to the VEX model to support XML Namespaces, and displaying of images. DocBook 4.5 and Simplified Docbook 1.0 are currently supported, and can be used as a basis to provide Docbook 5 support.<br />
| David Carver<br />
| [mailto:d_a_carver@yahoo.com David Carver]<br />
| None<br />
| <br><br />
|-<br />
| XSLT 2.0 content assistance<br />
| [http://www.eclipse.org/webtools/incubator/ Webtools XSL Tools]<br />
| XSL Tools provides good support for the XSLT 1.0 specification in the way of content assistance. It however does not provide support for some more advance features in XSLT 2.0 like custom functions, and content assistance for these features. Custom functions can be written in xslt 2.0, and then used within the stylesheet within XPath expressions. This allows for the generation of reuseable libraries like FXSL, to be created entirely in XSLT 2.0.<br />
| David Carver<br />
| [mailto:d_a_carver@yahoo.com David Carver]<br />
| None<br />
| <br><br />
|-<br />
| API Tooling for the Extension Registry<br />
| [http://www.eclipse.org/pde PDE]<br />
| The goal of this project is to add support to API Tools to work with the extension registry. For example, there are things in extensions that can be considered API. For example, the id of a view can be referenced by anyone. This should be considered API and changing it has the potential of breaking downstream clients. <br />
| <interested student here><br />
| Chris Aniszczyk, Darin Wright<br />
| None<br />
| <br><br />
|-<br />
| ECF connections for JDBC and DTP<br />
| [http://www.eclipse.org/datatools]<br />
| We'd like to find a way to bridge the gap between DTP and ECF to find a way to use a shared connection framework in E4. The idea would be to have an ECF connection for JDBC (would require jdbc url, jar list, uid/pwd, and any other properties) that could then be used to get the raw JDBC connection to be used in DTP...<br />
| <interested student here><br />
| Brian Fitzpatrick, Scott Lewis<br />
| Brian Fitzpatrick (brianf@sybase.com)<br />
| <br><br />
|-<br />
|}<br />
<br />
Old ideas can be found at [[Google Summer of Code 2007 Ideas|Google Summer of Code 2007 ideas]] and [[Google Summer of Code 2008 Ideas|Google Summer of Code 2008 ideas]].</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Eclipse_DemoCamps_November_2008/Toulouse&diff=128577Eclipse DemoCamps November 2008/Toulouse2008-11-14T08:17:54Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div>[[Image:eclipse-camp.gif]] [[Eclipse_DemoCamps_November_2008 | What is an Eclipse DemoCamp?]] <br />
=== Location ===<br />
Le Pakito - 10 rue des filatiers - 31000 Toulouse<br />
<br />
=== Date and Time ===<br />
November, 26 - From 7.30pm to 10.30pm<br />
<br />
=== Organizer ===<br />
Jocya Leroy, Anyware Technologies<br />
<br />
=== Presenters ===<br />
If you would like to present at the DemoCamp, please feel free to add your name and topic to the list. Depending on the number of people interested we may have to limit the number of presenters and time of each demo.<br />
# David Sciamma - M2M Developer Suite<br />
# Benjamin Cabé - p2, la nouvelle plateforme de provisioning d'Eclipse<br />
<br />
=== Who Is Attending ===<br />
If you plan on attending please add your name to the list below. We'd like to see as many people show up as possible.<br />
# Jocya Leroy, Anyware Technologies<br />
# David Sciamma, Anyware Technologies<br />
# Benjamin Cabé, Anyware Technologies<br />
# Mahshad Koohgoli, [http://www.protecode.com/ Protecode Inc]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=WTP/XQuery/Proposal&diff=116546WTP/XQuery/Proposal2008-09-03T16:12:28Z<p>Benjamin.cabe.anyware-tech.com: /* Interested Parties */</p>
<hr />
<div>The XQuery Development Toolkit (XQDT) is a proposed project under the Web Tools Project.<br />
<br />
According to the [http://www.eclipse.org/projects/dev_process/ Eclipse Development Process], this proposal is intended to declare the intent and scope of the XQuery Development Toolkit project as well as to gather input from the Eclipse community. You are invited to comment on and/or join the project.<br />
<br />
= Background =<br />
<br />
XQuery was designed by XML Query working group of the W3C in order to present a convenient way to query largely (but not limited to) XML data collections and became a W3C recommendation on January 23, 2007. Currently many commercial XML Databases support XQuery as a platform to query its data. Also with the upcoming new XQuery version which is 1.1, it is believed XQuery will be the main data query technique for XML documents as well as databases. As such, it is quite useful to have an editor for XQuery with rich functionality such as syntax validation and content assistance under WTP umbrella.<br />
<br />
= Introduction =<br />
<br />
XQuery Development Toolkit(XQDT) is mainly an editor built on Structured Source Editor(SSE) for easy XQuery handling. It will initially have basic text editor functions such as syntax colouring and content assistance to create and modify XQuery documents easily. Later it could be added more rich features such as content formatting, advance preferences, error tips and support to other commercial XML databases through extension points.<br />
<br />
= Project Description =<br />
<br />
XQuery Development Toolkit project will be based on the project done by Buddhika Laknath for Summer of Code 2008 named "New Eclipse Plugin for XQuery" mentored by David Carver who is a committer for XSL Tools. The initial idea of the project is to fill gaps in Eclipse in regards to new XML formats and persuade more web and XML users to choose Eclipse as their native platform.<br />
<br />
= Goal =<br />
<br />
Basic goal of the project is to provide a rich text editor for XQuery developments with Eclipse. Other than that, it's our hope that this will be an incentive to draw more attention from XML users into accepting Eclipse as their main development platform.<br />
<br />
= Scope =<br />
<br />
Currently Scope is limited to providing basic text editing features for XQuery language based on Structured Source Editing components. But at the end of first phase, providing that users requesting more features into the editor, it will be moving forward to bring more rich text editing experience to users. <br />
<br />
As always, scope can change based on community and adopter feedback as well as changes in XQuery standards.<br />
<br />
= Features =<br />
<br />
The following features are planned or currently implemented:<br />
<br />
* Content Assistance (planned)<br />
** XPath 2.0 <br />
** Xquery Templates<br />
** XQuery User Defined Functions<br />
** Namespaces<br />
* Syntax Coloring (partially implemented) - the editor is currently aware of XQuery/Xpath 2.0 specific syntax and will color keywords accordingly. It still needs to be made configurable.<br />
** XML syntax coloring is inherited from the XML editor<br />
* Validation<br />
** Validation of XQuery code.<br />
** Validation for XQuery Engine specific functionality. [http://xqilla.sourceforge.net/HomePage XQilla], [http://exist.sourceforge.net/ exist-db], and [http://www.sqlsummit.com/XQueryProv.htm others].<br />
** Project Level validation<br />
** Error Level control for specific errors.<br />
* Template support<br />
* New File Wizard<br />
<br />
<br />
Possible future features<br />
<br />
* XQuery Database Explorer - possible integration into DTP for exploring a XML database<br />
* Debugging - allows step through debugging support of XQuery scripts and possible transition between XSLT, Java, and other languages and XQuery code.<br />
<br />
= Perspectives and Views =<br />
<br />
The initial views will leverage many of the views provided by the XSL Tools project. These are:<br />
<br />
Perspectives:<br />
<br />
* XML Perspective - general editing perspective for XML related functionality.<br />
* Database Perspective - for XML Database browsing.<br />
<br />
It will leverage the following existing views.<br />
<br />
Views:<br />
* Project Explorer<br />
* Outline View<br />
* XPath View<br />
* Properties View<br />
* Problems View<br />
* Templates View<br />
<br />
Possible new views:<br />
* [http://xqdoc.org/ XQDoc] - XQDoc does for XQuery what JavaDoc does for java. It provides a platform neutral way of documenting XQuery.<br />
<br />
= Extension Points =<br />
<br />
Possible extension points include:<br />
<br />
* XQuery Engines - Allows for the selection and installation of various XQuery Engines used during Launch Configurations.<br />
* XQuery Engine specific Validation. Leveraging the existing WTP Validation framework, allow for projects to have specific XQuery Engines used for validation.<br />
* Debugging Support - If an engine supports Debugging allow it to contribute functionality.<br />
<br />
= Project Organization =<br />
<br />
We propose this project should be undertaken as an incubator project with the Web Tools project.<br />
<br />
= Mentors =<br />
<br />
* Chris Aniszczyk (Code 9)<br />
* David Williams?<br />
<br />
Need WTP Mentors.<br />
<br />
== Committers ==<br />
<br />
* Budhikka Laknath - Contribution/Committer - Budhikka wrote the initial code during the Google Summer of Code Project.<br />
* David Carver (XSL Tooling Committer)<br />
<br />
== Initial Code Contribution ==<br />
<br />
The initial code contribution comes from the Summer of Code 2008 project which is hosted at sourceforge, [http://eclipse-incub.cvs.sourceforge.net/eclipse-incub/org.eclipse.wst.xquery XQuery Plugin]<br />
<br />
=== Licensing and Intellectual property ===<br />
<br />
All code is being relicensed under the terms of the Eclipse Public License. All committers have agreed to these relicensing terms.<br />
<br />
== Interested Parties ==<br />
<br />
* [http://www.starstandard.org/ Standards for Technology in Automotive Retail]<br />
* Benjamin Cabé (Anyware Technologies): XML Database Explorer<br />
<br />
== User community ==<br />
XQuery already has a large user community that covers both the data side of xml as well as the document centric side of the XML. It is becoming the defacto standard for querying XML repositories and data bases, and is a good complement to other XML technologies like XSL. As more traditional database add support for XML databases having a good base set of XQuery tools to use and extend will become increasing important.<br />
<br />
<br />
== Tentative Development plan ==<br />
<br />
The tentative plan is the be incubating by the end of 2008. Initial steps will be:<br />
<br />
* Submit code through IP review.<br />
* Start content assistance.<br />
* Finish syntax coloring<br />
* Start work on Validation support.<br />
<br />
The project plans to try and follow the current WTP schedule for milestones and release candidates. The project may deviate from this schedule of problems or issues arise.<br />
<br />
= Relation to other Eclipse projects and other open source projects =<br />
<br />
* [http://www.w3.org/TR/xquery/ W3C XQuery 1.0]<br />
* [http://www.w3.org/TR/2008/CR-xquery-update-10-20080801/ W3C XQuery Update 1.0]<br />
* [http://jcp.org/en/jsr/detail?id=225 XQJ] - a java API standard for talking to XML Databases using XQuery.<br />
* [http://www.oracle.com/database/berkeley-db/xml/index.html Berkeley XML DB]<br />
* [http://exist.sourceforge.net exist-db]<br />
* [http://code.google.com/p/xqpretty/ XQPretty] - provides XPath 2.0 and XQuery parsing ability.<br />
* [http://antlr.org/ ANTLR V3] - used by XQPretty.<br />
* [http://www.eclipse.org/datatools/ Data Tools Platform]<br />
* [http://www.eclipse.org/webtools/ Web Tools Platform]<br />
* [http://xqdoc.org/ XQDoc]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Equinox_p2_Metadata_Repository_Authoring&diff=115938Equinox p2 Metadata Repository Authoring2008-08-29T18:00:15Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div>= Introduction =<br />
== Purpose ==<br />
The aim of this document is to list and explain some functionalities needed for a Metadata Repository Editor.<br />
<br />
== Context ==<br />
In Eclipse 3.4 context, a new framework, named p2, replaces the Update Manager. Anyware wants to provide to team leaders a user-friendly tool, to help them to manage an "œunder control" Eclipse configuration for all the team members.<br />
<br />
Such a tool will be a Metadata Repository Editor, allowing user to easily configure a file named content.xml, provided by an update site to install/update softwares in Eclipse.<br />
<br />
<nowiki>A [p2-dev] </nowiki>mailing-list member, Henrik Lindberg, has developed an editor to allow users to easily configure an Installable Unit, which is a part of a Metadata Repository. We will explain how we willl include this tool in ours.<br />
<br />
== Acronyms and abbreviations ==<br />
<br />
{| class="prettytable"<br />
! <center>Acronym</center><br />
! <center>Definition</center><br />
|-<br />
| <center>'''IU'''</center><br />
| Installable Unit : a part of a Metadata Repository. It contains required and provided capabilities, artifacts, touchpoints...<br />
|-<br />
| <center>'''EMF'''</center><br />
| Eclipse Modelling Framework<br />
|-<br />
| <center>'''MVC'''</center><br />
| Model-View-Controller<br />
|}<br />
= Editor general description =<br />
== General behavior ==<br />
This editor is a standard Eclipse editor. It allows to edit a Metadata repository object, and to save it as a ''content.xml'' file.<br />
<br />
Once the user has set some parameters required for his project, he can provide an Update Site for members of a team, allowing them to use the same Eclipse context.<br />
<br />
== Users ==<br />
Users are project managers, team leaders, system administrators...<br />
<br />
== Use case scenario. ==<br />
=== Scenario 1: ===<br />
The team leader wants to set a unique configuration for all his team members. He knows that the project will require some libraries or plug-ins sets: resources that p2 calls Installable Units. <br />
<br />
Through an Eclipse wizard, he builds a new Update Site Model : it creates a new ''.mr'' file. This file is the input file our Metadata Repository Editor expects.<br />
<br />
Then in editor view, a multi page editor is opened, inviting the user to fill or customize what he wants to. <br />
<br />
The first tab is an Overview of the Metadata Repository : name, description, version... A button allows to build a concrete update site form the currently edited ''.mr'' file.<br />
<br />
The second tab allows to add/edit/remove IUs for this repository. This tab is a kind of Master/Details, to quickly see and edit some relevant properties on the selected IU. For a complete IU edition, the user click on "Edit" button to open another editor, provided by Henrik Lindberg. This is inspired by the Update Site editor, where double-clicking on a feature opens the editor for this feature.<br />
<br />
<br />
== General constraints of architecture ==<br />
To make simple a data binding mechanism between the model (a repository) and the previous interface, we decided to use EMF<br />
<br />
But, as p2 models are not designed by EMF, we make the choice to not modify p2 APIs with EMF. So a p2 IMetadataRepository is first converted into an EMF model. This EMF model is edited with our Metadata Repository Editor, and saved as a ''.mr'' file. That's why we include in the editor the opportunity to "build" the Metadata Repository: the EMF Metadata repo EObject, is converted into a p2 object, and we use p2 API to serialize this p2 object to an xml file.<br />
<br />
<br />
[[Image:Img1.PNG]]<br />
<br />
<br />
= Detailed description =<br />
== Data description ==<br />
Here is an Ecore diagram, showing the data model behind the editor.<br />
<br />
[[Image:Img2.jpg]]<br />
<br />
The Metadata Repository Editor will allow to edit some of the MetadataRepository attributes, and the installableUnits relation.<br />
<br />
<br />
Installable Unit edition will be delegated to another editor. Some properties and attributes will be still editable in the Metadata Repository Editor.<br />
<br />
== User Interfaces ==<br />
Our Metadata Repository editor is a multi-tab page, displayed in the Eclipse editor view. <br />
<br />
* 1<sup>st</sup> tab must allow to edit general properties for the repository<br />
* 2<sup>nd</sup> tab must display Installable Units for the repository<br />
* It must open a more detailed editor when editing an IU. This operation can be performed with a button and/or a double-click on an IU.<br />
* It must support an undo/redo mechanism<br />
* The tab title in the editor view must display a dirty marker (*) when modifications have been done.<br />
* The editor must flag incorrect values, such as incorrect value number,<br />
* The editor must disallow any Save operation while editors has incorrect values<br />
<br />
=== Wizard for new Metadata Repository ===<br />
A wizard is necessary to allow the user to create a repository from scratch.<br />
<br />
* The wizard shall be available in''' File/New/p2/Metadata Repository'''. <br />
* It shall ask for<br />
<br />
* ''.mr'' file name : mandatory field<br />
* Repository name : mandatory field, a user friendly name for the metadata repository<br />
* Repository version : default to 1.0.0<br />
<br />
* Validating the wizard must initialize a new simple project (no peculiar nature), containing a ''.mr'' file, and directly open the Metadata Repository Editor for the new created file.<br />
<br />
=== Export/Import a model ===<br />
* After editing a Metadata Repository, the user should be able to export it as a p2 Metadata Repository, building a ''content.xml'' file. <br />
* In the other way, the user should be able to load an existing p2 Metadata Repository, giving a valid ''content.xml'' file.<br />
<br />
These options could be available by 2 ways : <br />
<br />
* A right click on the ''.mr'' file could display 2 specific options :<br />
** "Build Metadata Repository" : the user should add some installable units to the current repository; otherwise a repository has no sense. So if the user clicks on this option, if no installable unit is associated, the user is invited to add any installable unit. If any installable unit is filled for this repository, clicking on this option open a popup asking the user where he wants to deploy its site. Once the location is entered, a file content.xml is generated at this place. This file contains all information filled through our editor.<br />
** "Load Metadata Repository" : build a ''.mr'' file from a ''content.xml'' file (location given by the user), to edit its contents through the editor.<br />
* 2 icons in overview tab could allow the user to perform an import or export.<br />
<br />
=== Overview page ===<br />
Here is a sketch of how the first tab could be like.<br />
<br />
<center>[[Image:Img3.jpg]]</center><br />
<br />
<br />
Overview tab display those fields. <br />
<br />
* Name is default filled with the repository name from the wizard<br />
* Description is a summary for the metadata repository<br />
* Version is the current version for the metadata repository<br />
* Type is not displayed, but set to org.eclipse.equinox.internal.p2.metadata.repository.LocalMetadataRepository (TBD)<br />
<br />
=== Installable units page ===<br />
Here is a sketch of how the second tab could be like.<br />
<br />
<center>[[Image:Img4.jpg]]</center><br />
<br />
* On the left, a list viewer must display all IUs associated to the current repository. For a new repository, this list is empty. The list can be displayed as a Tree, using the IU ''group'' property to build such an organization.<br />
<br />
* Add button : <br />
** Always enabled. <br />
** Allows to add an installable unit, using a dialog to select them from a distant site, or IU present in the workspace (.iu file ?).<br />
* Remove button : <br />
** Enable only when any IU is selected. <br />
** Remove the association between the edited repository and the selected IU.<br />
* Edit button : <br />
** Enable on only when any IU is selected and when this IU is available as a ''.iu'' file in the user's workspace<br />
** Uses another editor (maybe Henrik Lindberg's one : org.eclipse.equinox.p2.authoring). <br />
** When closing this other editor, our editor shall be consequently updated.<br />
<br />
Details section displays some details about the selected IU. They can be updated. Properties are also available here (this is not the case in the external IU editor). The user can add new ones or override them.<br />
<br />
[[Category:Equinox p2|Metadata Repository Authoring]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Equinox_p2_Metadata_Repository_Authoring&diff=115935Equinox p2 Metadata Repository Authoring2008-08-29T17:55:31Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div>= Introduction =<br />
== Purpose ==<br />
The aim of this document is to list and explain some functionalities needed for a Metadata Repository Editor.<br />
<br />
== Context ==<br />
In Eclipse 3.4 context, a new framework, named p2, replaces the Update Manager. Anyware wants to provide to team leaders a user-friendly tool, to help them to manage an "œunder control" Eclipse configuration for all the team members.<br />
<br />
<br />
Such tool will be a Metadata Repository Editor, allowing user to easily configure a file named content.xml, provided by an update site to install/update softwares in Eclipse.<br />
<br />
<br />
<nowiki>A [p2-dev] </nowiki>mailing-list member, Henrik Lindberg, has developed an editor to allow users to easily configure an Installable Unit, which is a part of a Metadata Repository. We will explain how we willl include this tool in ours.<br />
<br />
== Acronyms and abbreviations ==<br />
<br />
{| class="prettytable"<br />
! <center>Acronym</center><br />
! <center>Definition</center><br />
|-<br />
| <center>'''IU'''</center><br />
| Installable Unit : a part of a Metadata Repository. It contains required and provided capabilities, artifacts, touchpoints...<br />
|-<br />
| <center>'''EMF'''</center><br />
| Eclipse Modelling Framework<br />
|-<br />
| <center>'''MVC'''</center><br />
| Model-View-Controller<br />
|}<br />
= Editor general description =<br />
== General behavior ==<br />
This editor is a standard Eclipse editor. It allows to edit a Metadata repository object, and to save it as a ''content.xml'' file.<br />
<br />
Once the user has set some parameters required for his project, he can provide an Update Site for members of a team, allowing them to use the same Eclipse context.<br />
<br />
<br />
== Users ==<br />
Users are project managers, team leaders, system administrators...<br />
<br />
<br />
== Use case scenario. ==<br />
=== Scenario 1: ===<br />
The team leader wants to set a unique configuration for all his team members. He knows that the project will require some libraries or plug-ins sets: resources that p2 calls Installable Units. <br />
<br />
Through an Eclipse wizard, he builds a new Update Site Model : it creates a new ''.mr'' file. This file is the input file our Metadata Repository Editor expects.<br />
<br />
Then in editor view, a multi page editor is opened, inviting the user to fill or customize what he wants to. <br />
<br />
The first tab is an Overview of the Metadata Repository : name, description, version... A button allows to build a concrete update site form the currently edited ''.mr'' file.<br />
<br />
The second tab allows to add/edit/remove IUs for this repository. This tab is a kind of Master/Details, to quickly see and edit some relevant properties on the selected IU. For a complete IU edition, the user click on "Edit" button to open another editor, provided by Henrik Lindberg. This is inspired by the Update Site editor, where double-clicking on a feature opens the editor for this feature.<br />
<br />
<br />
== General constraints of architecture ==<br />
To make simple a data binding mechanism between the model (a repository) and the previous interface, we decided to use EMF<br />
<br />
But, as p2 models are not designed by EMF, we make the choice to not modify p2 APIs with EMF. So a p2 IMetadataRepository is first converted into an EMF model. This EMF model is edited with our Metadata Repository Editor, and saved as a ''.mr'' file. That's why we include in the editor the opportunity to "build" the Metadata Repository: the EMF Metadata repo EObject, is converted into a p2 object, and we use p2 API to serialize this p2 object to an xml file.<br />
<br />
<br />
[[Image:Img1.PNG]]<br />
<br />
<br />
= Detailed description =<br />
== Data description ==<br />
Here is an Ecore diagram, showing the data model behind the editor.<br />
<br />
[[Image:Img2.jpg]]<br />
<br />
The Metadata Repository Editor will allow to edit some of the MetadataRepository attributes, and the installableUnits relation.<br />
<br />
<br />
Installable Unit edition will be delegated to another editor. Some properties and attributes will be still editable in the Metadata Repository Editor.<br />
<br />
== User Interfaces ==<br />
Our Metadata Repository editor is a multi-tab page, displayed in the Eclipse editor view. <br />
<br />
* 1<sup>st</sup> tab must allow to edit general properties for the repository<br />
* 2<sup>nd</sup> tab must display Installable Units for the repository<br />
* It must open a more detailed editor when editing an IU. This operation can be performed with a button and/or a double-click on an IU.<br />
* It must support an undo/redo mechanism<br />
* The tab title in the editor view must display a dirty marker (*) when modifications have been done.<br />
* The editor must flag incorrect values, such as incorrect value number,<br />
* The editor must disallow any Save operation while editors has incorrect values<br />
<br />
=== Wizard for new Metadata Repository ===<br />
A wizard is necessary to allow the user to create a repository from scratch.<br />
<br />
* The wizard shall be available in''' File/New/p2/Metadata Repository'''. <br />
* It shall ask for<br />
<br />
* ''.mr'' file name : mandatory field<br />
* Repository name : mandatory field, a user friendly name for the metadata repository<br />
* Repository version : default to 1.0.0<br />
<br />
* Validating the wizard must initialize a new simple project (no peculiar nature), containing a ''.mr'' file, and directly open the Metadata Repository Editor for the new created file.<br />
<br />
=== Export/Import a model ===<br />
* After editing a Metadata Repository, the user should be able to export it as a p2 Metadata Repository, building a ''content.xml'' file. <br />
* In the other way, the user should be able to load an existing p2 Metadata Repository, giving a valid ''content.xml'' file.<br />
<br />
These options could be available by 2 ways : <br />
<br />
* A right click on the ''.mr'' file could display 2 specific options :<br />
** "Build Metadata Repository" : the user should add some installable units to the current repository; otherwise a repository has no sense. So if the user clicks on this option, if no installable unit is associated, the user is invited to add any installable unit. If any installable unit is filled for this repository, clicking on this option open a popup asking the user where he wants to deploy its site. Once the location is entered, a file content.xml is generated at this place. This file contains all information filled through our editor.<br />
** "Load Metadata Repository" : build a ''.mr'' file from a ''content.xml'' file (location given by the user), to edit its contents through the editor.<br />
* 2 icons in overview tab could allow the user to perform an import or export.<br />
<br />
=== Overview page ===<br />
Here is a sketch of how the first tab could be like.<br />
<br />
<center>[[Image:Img3.jpg]]</center><br />
<br />
<br />
Overview tab display those fields. <br />
<br />
* Name is default filled with the repository name from the wizard<br />
* Description is a summary for the metadata repository<br />
* Version is the current version for the metadata repository<br />
* Type is not displayed, but set to org.eclipse.equinox.internal.p2.metadata.repository.LocalMetadataRepository (TBD)<br />
<br />
=== Installable units page ===<br />
Here is a sketch of how the second tab could be like.<br />
<br />
<center>[[Image:Img4.jpg]]</center><br />
<br />
<br />
* On the left, a list viewer must display all IUs associated to the current repository. For a new repository, this list is empty. The list can be displayed as a Tree, using the IU ''group'' property to build such an organization.<br />
<br />
* Add button : <br />
** Always enabled. <br />
** Allows to add an installable unit, using a dialog to select them from a distant site, or IU present in the workspace (.iu file ?).<br />
* Remove button : <br />
** Enable only when any IU is selected. <br />
** Remove the association between the edited repository and the selected IU.<br />
* Edit button : <br />
** Enable on only when any IU is selected and when this IU is available as a ''.iu'' file in the user's workspace<br />
** Uses another editor (maybe Henrik Lindberg's one : org.eclipse.equinox.p2.authoring). <br />
** When closing this other editor, our editor shall be consequently updated.<br />
<br />
Details section displays some details about the selected IU. They can be updated. Properties are also available here (this is not the case in the external IU editor). The user can add new ones or override them.<br />
<br />
[[Category:Equinox p2|Metadata Repository Authoring]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Equinox_p2_Metadata_Repository_Authoring&diff=115934Equinox p2 Metadata Repository Authoring2008-08-29T17:50:23Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div><center>'''Metadata Repository Editor'''</center><br />
<center>'''for p2'''</center><br />
<br />
= Introduction =<br />
== Purpose ==<br />
The aim of this document is to list and explain some functionalities we need for our Metadata Repository Editor.<br />
<br />
== Context ==<br />
In Eclipse 3.4 context, a new framework, named p2, replaces the Update Manager. Anyware wants to provide to team leaders a user-friendly tool, to help them to manage an "œunder control" Eclipse configuration for all the team members.<br />
<br />
<br />
Such tool will be a Metadata Repository Editor, allowing user to easily configure a file named content.xml, provided by an update site to install/update softwares in Eclipse.<br />
<br />
<br />
<nowiki>A [p2-dev] </nowiki>mailing-list member, Henrik Lindberg, has developed an editor to allow users to easily configure an Installable Unit, which is a part of a Metadata Repository. We will explain how we willl include this tool in ours.<br />
<br />
== Acronyms and abbreviations ==<br />
<br />
{| class="prettytable"<br />
! <center>Acronym</center><br />
! <center>Definition</center><br />
<br />
<br />
<br />
<br />
|-<br />
| <center>'''IU'''</center><br />
| Installable Unit : a part of a Metadata Repository. It contains required and provided capabilities, artifacts, touchpoints...¦<br />
<br />
<br />
<br />
<br />
|-<br />
| <center>'''EMF'''</center><br />
| Eclipse Modelling Framework<br />
<br />
<br />
<br />
<br />
|-<br />
| <center>'''MVC'''</center><br />
| Model-View-Controller<br />
<br />
<br />
<br />
<br />
|}<br />
= Editor general description =<br />
== General behavior ==<br />
This editor is a standard Eclipse editor. It allows to edit a Metadata repository object, and to save it as a ''content.xml'' file.<br />
<br />
Once the user has set some parameters required for his project, he can provide an Update Site for members of a team, allowing them to use the same Eclipse context.<br />
<br />
<br />
== Users ==<br />
Users are project managers, team leaders, system administrators...¦ <br />
<br />
<br />
== Use case scenario. ==<br />
=== Scenario 1: ===<br />
The team leader wants to set a unique configuration for all his team members. He knows that the project will require some libraries or plug-ins sets: resources that p2 calls Installable Units. <br />
<br />
Through an Eclipse wizard, he builds a new Update Site Model : it creates a new ''.mr'' file. This file is the input file our Metadata Repository Editor expects.<br />
<br />
Then in editor view, a multi page editor is opened, inviting the user to fill or customize what he wants to. <br />
<br />
The first tab is an Overview of the Metadata Repository : name, description, version...¦ A button allows to build a concrete update site form the currently edited ''.mr'' file.<br />
<br />
The second tab allows to add/edit/remove IUs for this repository. This tab is a kind of Master/Details, to quickly see and edit some relevant properties on the selected IU. For a complete IU edition, the user click on "Edit" button to open another editor, provided by Henrik Lindberg. This is inspired by the Update Site editor, where double-clicking on a feature opens the editor for this feature.<br />
<br />
<br />
== General constraints of architecture ==<br />
To make simple a data binding mechanism between the model (a repository) and the previous interface, we decided to use EMF¦<br />
<br />
But, as p2 models are not designed by EMF, we make the choice to not modify p2 APIs with EMF. So a p2 IMetadataRepository is first converted into an EMF model. This EMF model is edited with our Metadata Repository Editor, and saved as a ''.mr'' file. That's why we include in the editor the opportunity to "build" the Metadata Repository: the EMF Metadata repo EObject, is converted into a p2 object, and we use p2 API to serialize this p2 object to an xml file.<br />
<br />
<br />
[[Image:Img1.PNG]]<br />
<br />
<br />
= Detailed description =<br />
== Data description ==<br />
Here is an Ecore diagram, showing the data model behind the editor.<br />
<br />
[[Image:Img2.jpg]]<br />
<br />
The Metadata Repository Editor will allow to edit some of the MetadataRepository attributes, and the installableUnits relation.<br />
<br />
<br />
Installable Unit edition will be delegated to another editor. Some properties and attributes will be still editable in the Metadata Repository Editor.<br />
<br />
== User Interfaces ==<br />
Our Metadata Repository editor is a multi-tab page, displayed in the Eclipse editor view. <br />
<br />
* 1<sup>st</sup> tab must allow to edit general properties for the repository<br />
* 2<sup>nd</sup> tab must display Installable Units for the repository<br />
* It must open a more detailed editor when editing an IU. This operation can be performed with a button and/or a double-click on an IU.<br />
* It must support an undo/redo mechanism<br />
* The tab title in the editor view must display a dirty marker (*) when modifications have been done.<br />
* The editor must flag incorrect values, such as incorrect value number,<br />
* The editor must disallow any Save operation while editors has incorrect values<br />
<br />
=== Wizard for new Metadata Repository ===<br />
A wizard is necessary to allow the user to create a repository from scratch.<br />
<br />
* The wizard shall be available in''' File/New/p2/Metadata Repository'''. <br />
* It shall ask for<br />
<br />
* ''.mr'' file name : mandatory field<br />
* Repository name : mandatory field, a user friendly name for the metadata repository<br />
* Repository version : default to 1.0.0<br />
<br />
* Validating the wizard must initialize a new simple project (no peculiar nature), containing a ''.mr'' file, and directly open the Metadata Repository Editor for the new created file.<br />
<br />
=== Export/Import a model ===<br />
* After editing a Metadata Repository, the user should be able to export it as a p2 Metadata Repository, building a ''content.xml'' file. <br />
* In the other way, the user should be able to load an existing p2 Metadata Repository, giving a valid ''content.xml'' file.<br />
<br />
These options could be available by 2 ways : <br />
<br />
* A right click on the ''.mr'' file could display 2 specific options :<br />
** "Build Metadata Repository" : the user should add some installable units to the current repository; otherwise a repository has no sense. So if the user clicks on this option, if no installable unit is associated, the user is invited to add any installable unit. If any installable unit is filled for this repository, clicking on this option open a popup asking the user where he wants to deploy its site. Once the location is entered, a file content.xml is generated at this place. This file contains all information filled through our editor.<br />
** "Load Metadata Repository" : build a ''.mr'' file from a ''content.xml'' file (location given by the user), to edit its contents through the editor.<br />
* 2 icons in overview tab could allow the user to perform an import or export.<br />
<br />
=== Overview page ===<br />
Here is a sketch of how the first tab could be like.<br />
<br />
<center>[[Image:Img3.jpg]]</center><br />
<br />
<br />
Overview tab display those fields. <br />
<br />
* Name is default filled with the repository name from the wizard<br />
* Description is a summary for the metadata repository<br />
* Version is the current version for the metadata repository<br />
* Type is not displayed, but set to org.eclipse.equinox.internal.p2.metadata.repository.LocalMetadataRepository (TBD)<br />
<br />
=== Installable units page ===<br />
Here is a sketch of how the second tab could be like.<br />
<br />
<center>[[Image:Img4.jpg]]</center><br />
<br />
<br />
* On the left, a list viewer must display all IUs associated to the current repository. For a new repository, this list is empty. The list can be displayed as a Tree, using the IU ''group'' property to build such an organization.<br />
<br />
* Add button : <br />
** Always enabled. <br />
** Allows to add an installable unit, using a dialog to select them from a distant site, or IU present in the workspace (.iu file ?).<br />
* Remove button : <br />
** Enable only when any IU is selected. <br />
** Remove the association between the edited repository and the selected IU.<br />
* Edit button : <br />
** Enable on only when any IU is selected and when this IU is available as a ''.iu'' file in the user's workspace<br />
** Uses another editor (maybe Henrik Lindberg's one : org.eclipse.equinox.p2.authoring). <br />
** When closing this other editor, our editor shall be consequently updated.<br />
<br />
Details section displays some details about the selected IU. They can be updated. Properties are also available here (this is not the case in the external IU editor). The user can add new ones or override them.</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Equinox_p2_Metadata_Repository_Authoring&diff=115932Equinox p2 Metadata Repository Authoring2008-08-29T17:48:14Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div><center>'''Metadata Repository Editor'''</center><br />
<center>'''for p2'''</center><br />
<br />
= Introduction =<br />
== Purpose ==<br />
The aim of this document is to list and explain some functionalities we need for our Metadata Repository Editor.<br />
<br />
== Context ==<br />
In Eclipse 3.4 context, a new framework, named p2, replaces the Update Manager. Anyware wants to provide to team leaders a user-friendly tool, to help them to manage an "œunder control" Eclipse configuration for all the team members.<br />
<br />
<br />
Such tool will be a Metadata Repository Editor, allowing user to easily configure a file named content.xml, provided by an update site to install/update softwares in Eclipse.<br />
<br />
<br />
<nowiki>A [p2-dev] </nowiki>mailing-list member, Henrik Lindberg, has developed an editor to allow users to easily configure an Installable Unit, which is a part of a Metadata Repository. We will explain how we willl include this tool in ours.<br />
<br />
== Acronyms and abbreviations ==<br />
<br />
{| class="prettytable"<br />
! <center>Acronym</center><br />
! <center>Definition</center><br />
<br />
<br />
<br />
<br />
|-<br />
| <center>'''IU'''</center><br />
| Installable Unit : a part of a Metadata Repository. It contains required and provided capabilities, artifacts, touchpoints...¦<br />
<br />
<br />
<br />
<br />
|-<br />
| <center>'''EMF'''</center><br />
| Eclipse Modelling Framework<br />
<br />
<br />
<br />
<br />
|-<br />
| <center>'''MVC'''</center><br />
| Model-View-Controller<br />
<br />
<br />
<br />
<br />
|}<br />
= Editor general description =<br />
== General behavior ==<br />
This editor is a standard Eclipse editor. It allows to edit a Metadata repository object, and to save it as a ''content.xml'' file.<br />
<br />
Once the user has set some parameters required for his project, he can provide an Update Site for members of a team, allowing them to use the same Eclipse context.<br />
<br />
<br />
== Users ==<br />
Users are project managers, team leaders, system administrators...¦ <br />
<br />
<br />
== Use case scenario. ==<br />
=== Scenario 1: ===<br />
The team leader wants to set a unique configuration for all his team members. He knows that the project will require some libraries or plug-ins sets: resources that p2 calls Installable Units. <br />
<br />
Through an Eclipse wizard, he builds a new Update Site Model : it creates a new ''.mr'' file. This file is the input file our Metadata Repository Editor expects.<br />
<br />
Then in editor view, a multi page editor is opened, inviting the user to fill or customize what he wants to. <br />
<br />
The first tab is an Overview of the Metadata Repository : name, description, version...¦ A button allows to build a concrete update site form the currently edited ''.mr'' file.<br />
<br />
The second tab allows to add/edit/remove IUs for this repository. This tab is a kind of Master/Details, to quickly see and edit some relevant properties on the selected IU. For a complete IU edition, the user click on "Edit" button to open another editor, provided by Henrik Lindberg. This is inspired by the Update Site editor, where double-clicking on a feature opens the editor for this feature.<br />
<br />
<br />
== General constraints of architecture ==<br />
To make simple a data binding mechanism between the model (a repository) and the previous interface, we decided to use EMF¦<br />
<br />
But, as p2 models are not designed by EMF, we make the choice to not modify p2 APIs with EMF. So a p2 IMetadataRepository is first converted into an EMF model. This EMF model is edited with our Metadata Repository Editor, and saved as a ''.mr'' file. That's why we include in the editor the opportunity to "build" the Metadata Repository: the EMF Metadata repo EObject, is converted into a p2 object, and we use p2 API to serialize this p2 object to an xml file.<br />
<br />
<br />
[[Image:Img1.PNG]]<br />
<br />
<br />
= Detailed description =<br />
== Data description ==<br />
Here is an Ecore diagram, showing the data model behind the editor.<br />
<br />
[[Image:Img2.jpg]]<br />
<br />
The Metadata Repository Editor will allow to edit some of the MetadataRepository attributes, and the installableUnits relation.<br />
<br />
<br />
Installable Unit edition will be delegated to another editor. Some properties and attributes will be still editable in the Metadata Repository Editor.<br />
<br />
== User Interfaces ==<br />
Our Metadata Repository editor is a multi-tab page, displayed in the Eclipse editor view. <br />
<br />
* 1<sup>st</sup> tab must allow to edit general properties for the repository<br />
* 2<sup>nd</sup> tab must display Installable Units for the repository<br />
* It must open a more detailed editor when editing an IU. This operation can be performed with a button and/or a double-click on an IU.<br />
* It must support an undo/redo mechanism<br />
* The tab title in the editor view must display a dirty marker (*) when modifications have been done.<br />
* The editor must flag incorrect values, such as incorrect value number,<br />
* The editor must disallow any Save operation while editors has incorrect values<br />
<br />
=== Wizard for new Metadata Repository ===<br />
A wizard is necessary to allow the user to create a “from scratch†repository.<br />
<br />
* The wizard shall be available in''' File/New/p2/Metadata Repository'''. <br />
* It shall ask for<br />
<br />
* ''.mr'' file name : mandatory field<br />
* Repository name : mandatory field, a user friendly name for the metadata repository<br />
* Repository version : default to 1.0.0<br />
<br />
* Validating the wizard must initialize a new simple project (no peculiar nature), containing a ''.mr'' file, and directly open the Metadata Repository Editor for the new created file.<br />
<br />
=== Export/Import a model ===<br />
* After editing a Metadata Repository, the user should be able to export it as a “p2 Metadata Repositoryâ€, building a ''content.xml'' file. <br />
* In the other way, the user should be able to load an existing “p2 Metadata Repositoryâ€, giving a valid ''content.xml'' file.<br />
<br />
These options could be available by 2 ways : <br />
<br />
* A right click on the ''.mr'' file could display 2 specific options :<br />
** “Build Metadata Repository…†: the user should add some installable units to the current repository; otherwise a repository has no sense. So if the user clicks on this option, if no installable unit is associated, the user is invited to add any installable unit. If any installable unit is filled for this repository, clicking on this option open a popup asking the user where he wants to deploy its site. Once the location is entered, a file content.xml is generated at this place. This file contains all information filled through our editor.<br />
** “Load Metadata Repository†: build a ''.mr'' file from a ''content.xml'' file (location given by the user), to edit its contents through the editor.<br />
* 2 icons in overview tab could allow the user to perform an import or export.<br />
<br />
=== Overview page ===<br />
Here is a sketch of how the first tab could be like.<br />
<br />
<center>[[Image:Img3.jpg]]</center><br />
<br />
<br />
Overview tab display those fields. <br />
<br />
* Name is default filled with the repository name from the wizard<br />
* Description is a summary for the metadata repository<br />
* Version is the current version for the metadata repository<br />
* Type is not displayed, but set to org.eclipse.equinox.internal.p2.metadata.repository.LocalMetadataRepository (TBD)<br />
<br />
=== Installable units page ===<br />
Here is a sketch of how the second tab could be like.<br />
<br />
<center>[[Image:Img4.jpg]]</center><br />
<br />
<br />
* On the left, a list viewer must display all IUs associated to the current repository. For a new repository, this list is empty. The list can be displayed as a Tree, using the IU “group†property to build such an organization.<br />
<br />
* Add button : <br />
** Always enabled. <br />
** Allows to add an installable unit, using a dialog to select them from a distant site, or IU present in the workspace (.iu file ?).<br />
* Remove button : <br />
** Enable only when any IU is selected. <br />
** Remove the association between the edited repository and the selected IU.<br />
* Edit button : <br />
** Enable on only when any IU is selected and when this IU is available as a ''.iu'' file in user’s the workspace<br />
** Uses another editor (maybe Henrik Lindberg’s one : org.eclipse.equinox.p2.authoring). <br />
** When closing this other editor, our editor shall be consequently updated.<br />
<br />
Details section displays some details about the selected IU. They can be updated. Properties are also available here (this is not the case in the external IU editor). The user can add new ones or override them.</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=File:Img4.jpg&diff=115930File:Img4.jpg2008-08-29T17:45:31Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div></div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=File:Img3.jpg&diff=115929File:Img3.jpg2008-08-29T17:45:08Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div></div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=File:Img2.jpg&diff=115928File:Img2.jpg2008-08-29T17:44:51Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div></div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=File:Img1.PNG&diff=115926File:Img1.PNG2008-08-29T17:44:07Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div></div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Equinox_p2_Metadata_Repository_Authoring&diff=115924Equinox p2 Metadata Repository Authoring2008-08-29T17:40:44Z<p>Benjamin.cabe.anyware-tech.com: New page: <center>'''Metadata Repository Editor'''</center> <center>'''for p2'''</center> = Introduction = == Purpose == The aim of this document is to list and explain some functionalities we need...</p>
<hr />
<div><center>'''Metadata Repository Editor'''</center><br />
<center>'''for p2'''</center><br />
<br />
= Introduction =<br />
== Purpose ==<br />
The aim of this document is to list and explain some functionalities we need for our Metadata Repository Editor.<br />
<br />
== Context ==<br />
In Eclipse 3.4 context, a new framework, named p2, replaces the Update Manager. Anyware wants to provide to team leaders a user-friendly tool, to help them to manage an "œunder control" Eclipse configuration for all the team members.<br />
<br />
<br />
Such tool will be a Metadata Repository Editor, allowing user to easily configure a file named content.xml, provided by an update site to install/update softwares in Eclipse.<br />
<br />
<br />
<nowiki>A [p2-dev] </nowiki>mailing-list member, Henrik Lindberg, has developed an editor to allow users to easily configure an Installable Unit, which is a part of a Metadata Repository. We will explain how we willl include this tool in ours.<br />
<br />
== Acronyms and abbreviations ==<br />
<br />
{| class="prettytable"<br />
! <center>Acronym</center><br />
! <center>Definition</center><br />
<br />
<br />
<br />
<br />
|-<br />
| <center>'''IU'''</center><br />
| Installable Unit : a part of a Metadata Repository. It contains required and provided capabilities, artifacts, touchpoints...¦<br />
<br />
<br />
<br />
<br />
|-<br />
| <center>'''EMF'''</center><br />
| Eclipse Modelling Framework<br />
<br />
<br />
<br />
<br />
|-<br />
| <center>'''MVC'''</center><br />
| Model-View-Controller<br />
<br />
<br />
<br />
<br />
|}<br />
= Editor general description =<br />
== General behavior ==<br />
This editor is a standard Eclipse editor. It allows to edit a Metadata repository object, and to save it as a ''content.xml'' file.<br />
<br />
Once the user has set some parameters required for his project, he can provide an Update Site for members of a team, allowing them to use the same Eclipse context.<br />
<br />
<br />
== Users ==<br />
Users are project managers, team leaders, system administrators...¦ <br />
<br />
<br />
== Use case scenario. ==<br />
=== Scenario 1: ===<br />
The team leader wants to set a unique configuration for all his team members. He knows that the project will require some libraries or plug-ins sets: resources that p2 calls Installable Units. <br />
<br />
Through an Eclipse wizard, he builds a new Update Site Model : it creates a new ''.mr'' file. This file is the input file our Metadata Repository Editor expects.<br />
<br />
Then in editor view, a multi page editor is opened, inviting the user to fill or customize what he wants to. <br />
<br />
The first tab is an Overview of the Metadata Repository : name, description, version...¦ A button allows to build a concrete update site form the currently edited ''.mr'' file.<br />
<br />
The second tab allows to add/edit/remove IUs for this repository. This tab is a kind of Master/Details, to quickly see and edit some relevant properties on the selected IU. For a complete IU edition, the user click on "Edit" button to open another editor, provided by Henrik Lindberg. This is inspired by the Update Site editor, where double-clicking on a feature opens the editor for this feature.<br />
<br />
<br />
== General constraints of architecture ==<br />
To make simple a data binding mechanism between the model (a repository) and the previous interface, we decided to use EMF¦<br />
<br />
But, as p2 models are not designed by EMF, we make the choice to not modify p2 APIs with EMF. So a p2 IMetadataRepository is first converted into an EMF model. This EMF model is edited with our Metadata Repository Editor, and saved as a ''.mr'' file. That's why we include in the editor the opportunity to "build" the Metadata Repository: the EMF Metadata repo EObject, is converted into a p2 object, and we use p2 API to serialize this p2 object to an xml file.<br />
<br />
<br />
[[Image:]]<br />
<br />
<br />
= Detailed description =<br />
== Data description ==<br />
Here is an Ecore diagram, showing the data model behind the editor.<br />
<br />
[[Image:]]<br />
<br />
The Metadata Repository Editor will allow to edit some of the MetadataRepository attributes, and the installableUnits relation.<br />
<br />
<br />
Installable Unit edition will be delegated to another editor. Some properties and attributes will be still editable in the Metadata Repository Editor.<br />
<br />
== User Interfaces ==<br />
Our Metadata Repository editor is a multi-tab page, displayed in the Eclipse editor view. <br />
<br />
* 1<sup>st</sup> tab must allow to edit general properties for the repository<br />
* 2<sup>nd</sup> tab must display Installable Units for the repository<br />
* It must open a more detailed editor when editing an IU. This operation can be performed with a button and/or a double-click on an IU.<br />
* It must support an undo/redo mechanism<br />
* The tab title in the editor view must display a dirty marker (*) when modifications have been done.<br />
* The editor must flag incorrect values, such as incorrect value number,<br />
* The editor must disallow any Save operation while editors has incorrect values<br />
<br />
=== Wizard for new Metadata Repository ===<br />
A wizard is necessary to allow the user to create a “from scratch†repository.<br />
<br />
* The wizard shall be available in''' File/New/p2/Metadata Repository'''. <br />
* It shall ask for<br />
<br />
* ''.mr'' file name : mandatory field<br />
* Repository name : mandatory field, a user friendly name for the metadata repository<br />
* Repository version : default to 1.0.0<br />
<br />
* Validating the wizard must initialize a new simple project (no peculiar nature), containing a ''.mr'' file, and directly open the Metadata Repository Editor for the new created file.<br />
<br />
=== Export/Import a model ===<br />
* After editing a Metadata Repository, the user should be able to export it as a “p2 Metadata Repositoryâ€, building a ''content.xml'' file. <br />
* In the other way, the user should be able to load an existing “p2 Metadata Repositoryâ€, giving a valid ''content.xml'' file.<br />
<br />
These options could be available by 2 ways : <br />
<br />
* A right click on the ''.mr'' file could display 2 specific options :<br />
** “Build Metadata Repository…†: the user should add some installable units to the current repository; otherwise a repository has no sense. So if the user clicks on this option, if no installable unit is associated, the user is invited to add any installable unit. If any installable unit is filled for this repository, clicking on this option open a popup asking the user where he wants to deploy its site. Once the location is entered, a file content.xml is generated at this place. This file contains all information filled through our editor.<br />
** “Load Metadata Repository†: build a ''.mr'' file from a ''content.xml'' file (location given by the user), to edit its contents through the editor.<br />
* 2 icons in overview tab could allow the user to perform an import or export.<br />
<br />
=== Overview page ===<br />
Here is a sketch of how the first tab could be like.<br />
<br />
<center>[[Image:]]</center><br />
<br />
<br />
Overview tab display those fields. <br />
<br />
* Name is default filled with the repository name from the wizard<br />
* Description is a summary for the metadata repository<br />
* Version is the current version for the metadata repository<br />
* Type is not displayed, but set to org.eclipse.equinox.internal.p2.metadata.repository.LocalMetadataRepository (TBD)<br />
<br />
=== Installable units page ===<br />
Here is a sketch of how the second tab could be like.<br />
<br />
<center>[[Image:]]</center><br />
<br />
<br />
* On the left, a list viewer must display all IUs associated to the current repository. For a new repository, this list is empty. The list can be displayed as a Tree, using the IU “group†property to build such an organization.<br />
<br />
* Add button : <br />
** Always enabled. <br />
** Allows to add an installable unit, using a dialog to select them from a distant site, or IU present in the workspace (.iu file ?).<br />
* Remove button : <br />
** Enable only when any IU is selected. <br />
** Remove the association between the edited repository and the selected IU.<br />
* Edit button : <br />
** Enable on only when any IU is selected and when this IU is available as a ''.iu'' file in user’s the workspace<br />
** Uses another editor (maybe Henrik Lindberg’s one : org.eclipse.equinox.p2.authoring). <br />
** When closing this other editor, our editor shall be consequently updated.<br />
<br />
Details section displays some details about the selected IU. They can be updated. Properties are also available here (this is not the case in the external IU editor). The user can add new ones or override them.</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=PDE/Ideas&diff=114062PDE/Ideas2008-08-18T19:10:03Z<p>Benjamin.cabe.anyware-tech.com: /* Authoring */</p>
<hr />
<div>== Introduction ==<br />
<br />
This page contains blue sky thinking about the kind of things we would like to see in PDE's future. This is a place to collect ideas - it does not represent a commitment to implement the ideas.<br />
<br />
== Target Management ==<br />
<br />
* Enhance target platform provisioning. Leverage p2 to create and configure profiles that can be used as target platforms, and leverage p2 to reflect on the contents of a profile. One could compose a target platform by installing features into a profile from p2 repositories.<br />
* Simplify and improve the user interface for defining and managing multiple targets in the workspace. Eventually, it would be nice to be able to support more than one target platform in the workspace (i.e. allow different projects to compile against different target platforms). Currently targets can be defined by target files or by the "target platform" user preference. Perhaps a preference page that allowed multiple targets to be defined (like the API Baselines or Installed JREs page) would be more intuitive. Creating/editing a target would open a wizard to modify that specific target, and a check box could be used to specify the "active" workspace target.<br />
** This is one area where I hope that PDE and WTP can collaborate. I would argue that at base level the requirements for PDE target management and WTP "server runtime targeting" features are very similar. It would be nice if both can use the same high-level API and UI. This becomes particularly interesting when you consider OSGi-based servers where the end users would likely need to use both WTP and PDE. There is some code in WTP right now that implements such high-level API and UI. It is already fairly generic, but it can be re-factored and modified to suit our combined requirements and placed somewhere commonly accessible. [konstantin.komissarchik@oracle.com]<br />
* Target launching should leverage Framework Admin, rather than hand-crafting a command line. This way, launching a target platform would be the same as running the executable in the file system.<br />
* Improve plug-in import. Determine when plug-in import is useful and whether it can be done better. Needs better integration with the target platform. Should source bundles be imported?<br />
<br />
== Source Management ==<br />
<br />
* Simplify the installation of source for debugging and developing against the target platform. For example, a user is debugging something and enters a class for which they have no source. There should be a simple way to install source for the associated bundle.<br />
* Clean up source bundles in the UI. Source bundles are not installed into the runtime and their role in the target platform is not clearly defined, so they appear in many lists of bundles. In some cases filtering may be satisfactory.<br />
* Provide an easy way to generate source bundles when exporting plug-ins/features.<br />
<br />
== Building ==<br />
<br />
* Improve the common self-hosting scenario of exporting a plug-in (bundle) and running with it. It would be nice to be able to build, export, and install a bundle (or set of bundles) into the running SDK with the click of a button (or at least from within one wizard). It should also be easy to generate and install the latest associated source bundles.<br />
* Workspace based building. Currently, the build process is Ant based and does not leverage workspace builders or project specific settings. As the number of builders/settings grows a workspace based build would allow for simpler integration and better report generation with the build process. A challenge here is around bootstrapping a pure source build scenario.<br />
* Parallel compilation in headless build<br />
<br />
== Authoring ==<br />
<br />
* Enhance authoring tools for p2. Traditionally Eclipse has been feature based. Moving forward we need to decide if features still make sense, or if we should encourage the use of installable units. One could imagine tools to author, export/build, and publish installable units. Some incubating stuff is available in the [[Equinox p2 Metadata Authoring]] page.<br />
<br />
== File Manipulation ==<br />
<br />
* There have been several requests for APIs to manipulate bundle definition files - MANIFEST.MF, plugin.xml, and build.properties.<br />
* Provide ASTs for PDE documents: would make document creation / editing trivial. Would be nice to have something like this backing the PDE editors...<br />
<br />
== API Tooling ==<br />
<br />
* Enhance API analysis to avoid false positives. Leak detection can be improved to not report problems when an internal superclass does not expose any visible members. Some API use problems should not be reported for bundles that are friends - for example, a bundle that is a friend should be able to implement restricted interfaces from its friend.<br />
* Allow a public visibile type to be restricted for 'internal/private' use only. This allows classes that need to be visible for implementation purposes to be effectively private.<br />
* Support API analysis for pure Java projects (not just plug-ins).<br />
* Seek performance improvements - perhaps by integrating with the Java builder as a compilation participant, and implementing an MRU cache of API descriptions.<br />
* Support edit time analysis similar to the Java editor. This would flag API problems as the user types without having to save/build.<br />
* Analyze extension points and extensions for compatibility.<br />
* Analyze prerequisite bundles for version range compatibility. The analysis would determine if all references to a prerequiste bundle are satisfied by a particular version of that bundle - or which versions of a prerequisite bundle are API compatible. NOTE: this would not guarantee runtime behavior to be correct.<br />
* Support searching an API baseline (existing product) for references/use of an API or internal code.<br />
* Support for package versioning.<br />
* Analyze JRE/system library references for illegal use based on bundle required execution environment. For example, if a bundle claims to run on J2SE-1.4, there should be no references to methods introduced in J2SE-1.5.<br />
* Create scanning abstraction layer: separate scanning source kind from tooling. I.e. the tooling should not care whether the 'source' to be scanned is binary (class files, etc) or pure source.<br />
* Test coverage for all aspects of the builder (currently there is only coverage for unsupported tag usage)<br />
* Better handling of preferences and how they drive the different parts of the tooling. For example, setting the preferences to say 'only find binary compatibility problems for classes', should not scan for any other type of problem.<br />
* Consider making the delta scanning pluggable, where each section for compatibility scanning is a participant (goes along with the point above about preferences driving the work that is done).<br />
* More reusable ant tasks for reporting (provide more tangible benefits to the tooling).</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Equinox_p2_Metadata_Generator&diff=108659Equinox p2 Metadata Generator2008-07-05T09:29:40Z<p>Benjamin.cabe.anyware-tech.com: /* Arguments describing the input */</p>
<hr />
<div>The p2 metadata generator is a utility tool that generates metadata and artifact repositories from a given input. The generator is available both as an Eclipse application, and as an Ant task.<br />
<br />
= Generator Application =<br />
<br />
The generator application is contained in bundle org.eclipse.equinox.p2.metadata.generator. This bundle is part of the Eclipse SDK, and is also available in the p2 [[Equinox p2 Getting Started Admin UI|Admin UI]]. The generator can be invoked using the generic Eclipse launcher as follows:<br />
<br />
eclipse -application org.eclipse.equinox.p2.metadata.generator.EclipseGenerator <generatorArgs><br />
<br />
The generator application has three primary modes of operation:<br />
# Generating metadata for a folder containing bundles and features (-source argument)<br />
# Generating metadata for a traditional Eclipse update site (-updateSite argument)<br />
# Generating metadata for an existing Eclipse application that does not contain p2 metadata (-config argument)<br />
<br />
<br />
= Generating metadata from an update manager site =<br />
The following example shows how to generate metadata from an pre-existing update site located in "d:\ganymedeM5".<br />
<tt><br />
-application org.eclipse.equinox.p2.metadata.generator.EclipseGenerator<br />
-updateSite d:/ganymedeM5/<br />
-site file:d:/ganymedeM5/site.xml<br />
-metadataRepository file:d:/ganymedeM5/<br />
-metadataRepositoryName "Ganymede Update Site"<br />
-artifactRepository file:d:/ganymedeM5/<br />
-artifactRepositoryName "Ganymede Artifacts"<br />
-compress<br />
-reusePack200Files<br />
-noDefaultIUs<br />
-vmargs -Xmx256m<br />
</tt><br />
<br />
Want to simplify that down to a shell script with a couple of inputs -- site name ("Ganymede") and site path ("d:/ganymedeM5/")? Try [http://dev.eclipse.org/viewcvs/index.cgi/releng-common/tools/scripts/buildUpdateSiteMetadata.sh?root=Modeling_Project&content-type=text%2Fplain&view=co this script]. To run this you need either Eclipse, [http://download.eclipse.org/eclipse/equinox/drops/S-3.4M7-200805020100/index.php#Launchers the p2-agent], or [[Platform-releng-basebuilder#May_5.2C_2008|releng.basebuilder from tag M7_34 or later]].<br />
<br />
Be sure to give the JVM enough heap space (-Xmx argument), since insufficient heap space can lead it to delete your valuable plugins! See {{Bug|233240}}.<br />
<br />
== Arguments describing the input ==<br />
<br />
; -source <path> :the path to a folder containing plugins and folders to generate p2 metadata for<br />
; -updateSite <path> :the path of a traditional update site to generate p2 metadata for<br />
; -config <path> :the path of an Eclipse application that is not p2-enabled<br />
; -exe <path> :the location of the application launcher executable<br />
; -launcherConfig <path> :the path of the launcher configuration file (eclipse.ini)<br />
; -features <path> :the location of features to generate metadata for<br />
; -bundles <path> : the location of bundles to generate metadata for<br />
; -base <path> :a base location containing a plugins/ and features/ directory<br />
; -p2.os :the operating system of the application metadata is being generated for<br />
; -site <path> :the URL of a site.xml file used to generator categories<br />
<br />
== Arguments describing the output ==<br />
<br />
; -metadataRepository :the URL to a writable metadata repository that will contain the produced installable units<br />
; -metadataRepositoryName :a user friendly name for the metadata repository<br />
; -artifactRepository :the URL to a writable artifact repository that will contain the produced artifacts<br />
; -artifactRepositoryName :a user friendly name for the artifact repository<br />
; -publishArtifacts :flag indicating whether the artifacts should be published to the repository. When this flag is not set, the actual bytes underlying the artifact will not be copied, but the repository index will be created. When this option is not specified, it is recommended to set the artifactRepository to be in the same location as the source (-source)<br />
; -publishArtifactRepository<br />
; -append :flag indicating that repositories will be appended to<br />
; -root :The name of the installable unit referring to all the IUs that have been added to the repository during the run<br />
; -rootVersion :The version of the root installable unit<br />
; -flavor :the flavor associated with the configuration units generated. (This will be removed for 1.0)<br />
; -inplace :causes the metadata and artifact repositories to be written into the source location<br />
; -noDefaultIUs :flag to indicate the default configuration units should not be created<br />
; -compress :cause the repositories to store their index in compressed form<br />
; -reusePack200Files :Specifying -reusePack200 does not require you to have pack200 files on the server, nor does it cause pack200 files to be created. When this option is specified, the generator looks for pack.gz files and if available it creates an entry for them in the artifacts.jar.<br />
<br />
= Generator Ant Task =<br />
<br />
The generator Ant task is called "p2.generator". This task is also available in the org.eclipse.equinox.p2.metadata.generator bundle.<br />
<br />
[[Category:Equinox_p2|Metadata generator]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Equinox_p2_3.5_contributions&diff=108649Equinox p2 3.5 contributions2008-07-04T20:51:52Z<p>Benjamin.cabe.anyware-tech.com: /* Cloudsmith */</p>
<hr />
<div>== IBM ==<br />
; '''Metadata improvement'''<br />
:Provide additional metadata construct to separate the line-up information from the raw dependency information.<br />
<br />
; '''API'''<br />
:Define an API for p2 and provide some reusable UI building blocks<br />
<br />
<br />
== Cloudsmith ==<br />
; '''[[Equinox_p2_Metadata_Authoring|Meta data authoring]]'''<br />
;'''Remote repositories'''<br />
: reference to wiki page TBD - includes search/browse/publish<br />
;'''Installer'''<br />
: Buckminster has an installer, seems a waste to have duplicate efforts. <br />
;'''Inclusion of more links in IU'''<br />
: We think it is a good idea to include more "bookmarks" (in the form of an OPML) into an IU - this to enable links to not only License and Copyright, but any set of useful links and RSS feeds to information that a publisher sees fit. We have an implementation of this in Buckminster that can be modified and contributed.<br />
;'''installation/materialization of source/projects'''<br />
: Buckminster has this, again, seems a waste to have duplicate efforts.<br />
;'''version type support'''<br />
: Currently p2 supports only OSGi type versions, we think versions needs to be typed (OSGi, Triplet,...). We would like to contribute the implementation (if someone else does not add this), as we want to be able to use p2 for technologies other than OSGi.<br />
<br />
== Siemens AG ==<br />
; '''Better RCP support'''<br />
: It's is great that 3.4 can create p2 repositories in the product export wizard. Whas's missing is PDE support for the director application. Suggestion: Include a "Create installation from created repository" that prepares all the infrastructure for self-updating of an exported RCP application <br />
;'''Provide more customizable end user UI'''<br />
: The current software update dialogs used in Eclipse have great potential to be reusable in domain specific RCP applications. It would be great if things like "Add update site" could to be optional.<br />
<br />
== Contributor name ==<br />
; '''Area of interest'''<br />
:Details about it<br />
<br />
[[Category:Equinox p2|3.5 contributions]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Equinox/p2/Director_application&diff=107196Equinox/p2/Director application2008-06-26T16:12:11Z<p>Benjamin.cabe.anyware-tech.com: </p>
<hr />
<div>The director application is a headless way of performing some of the p2 operations such as installing or uninstalling installable units. Given the appropriate metadata, this application is capable on provisioning a complete installation from scratch or simply extending your application. <br />
<br />
Depending on the needs, this application can be executed inside or outside of the application being provisioned<br />
<br />
<br />
== Terminology ==<br />
; Director application :the application performing p2 operations such as install or uninstall. This application is provided by the org.eclipse.equinox.p2.director.app bundle.<br />
; Provisioning operation :an operation installing, uninstalling features.<br />
; Target product :the installation targeted by the provisioning operation.<br />
<br />
== Running inside the target application ==<br />
In this mode, the provisioning operation happens from within the targeted product that you are provisioning. It is equivalent to starting up the targeted product and using the p2 UI to perform the equivalent operation. <br />
<br />
This means that the target application has to be in a runnable state and that it has to contain the director application bundle. Also since the target product will have run, cache files will have been created in the configuration folder (e.g. configuration/org.eclipse.osgi).<br />
<br />
The following example shows the command line used to install CDT into the SDK. <br />
<tt><br />
<targetProductFolder>/eclipse.exe <br />
-application org.eclipse.equinox.p2.director.app.application <br />
-metadataRepository file:d:/tmp/cdt/site.xml <br />
-artifactRepository file:d:/tmp/cdt/site.xml<br />
-installIU org.eclipse.cdt.feature.group<br />
</tt><br />
<br />
Note that this mode is equivalent to the former update manager command line application (http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/update_standalone.html).<br />
<br />
== Provisioning without running the target application ==<br />
In this case the provisioning operation is happening "outside" of the targeted product. The "targeted product" is *not* started. This allows to both modify an existing installation and create a complete installation from scratch given proper metadata. <br />
<br />
It also has the advantage that since the targeted product does not need to be started, the provisioning operation can be performed on any platform for any other platform (e.g. on my windows machine, I can create add plug-ins to a linux-based target application).<br />
<br />
=== Installing / uninstalling IUs into a target product ===<br />
To install or uninstall something into an existing target product a few extra arguments than in the "inside" mode need to be set. It mostly consist in letting the provisioning operation the ID of the profile it needs to operate on, and where it is located on disk.<br />
<br />
For example, if from a directory called "d:\builder", you want to install CDT into an existing SDK located into "d:\eclipse", you would use the following command line. It is important to note the presence of the VM args and set it properly.<br />
<br />
<tt><br />
d:\builder\eclipse.exe<br />
-application org.eclipse.equinox.p2.director.app.application<br />
-metadataRepository file:d:/tmp/cdt/site.xml<br />
-artifactRepository file:d:/tmp/cdt/site.xml<br />
-installIU org.eclipse.cdt.feature.group<br />
-destination d:/eclipse/<br />
-profile SDKProfile<br />
<br />
-vmArgs<br />
-Declipse.p2.data.area=d:/eclipse/p2<br />
</tt><br />
<br />
Note that there is no need to describe the os/ws/arch of the platform being targeted because all this information is already being available in the profile.<br />
<br />
=== Installing a complete product ===<br />
The creation of a complete product using the director application only needs a few extra arguments to the previous example. Most of these consist in values used to initialize the profile in which the application will be provisioned. <br />
<br />
The following example demonstrate how to create a linux/gtk installation of the Eclipse SDK into a folder called "d:\eclipse" using a director application located in "d:\builder".<br />
<br />
<tt><br />
d:\builder\eclipse.exe<br />
-application org.eclipse.equinox.p2.director.app.application<br />
-metadataRepository http://update.eclipse.org/testUpdates<br />
-artifactRepository http://update.eclipse.org/testUpdates<br />
-installIU org.eclipse.sdk.ide<br />
-destination d:/eclipse/<br />
-profile SDKProfile<br />
-profileProperties org.eclipse.update.install.features=true<br />
-bundlepool d:/eclipse/<br />
-p2.os linux<br />
-p2.ws gtk<br />
-p2.arch x86<br />
-roaming<br />
<br />
-vmargs<br />
-Declipse.p2.data.area=d:/eclipse/p2<br />
</tt><br />
<br />
The -p2.* arguments describe the os/ws/arch that the provisioned product is targeting.<br />
<br />
Here again notice the presence of the -vmargs pointing at the eclipse data area for the installation being created.<br />
<br />
== Arguments Description ==<br />
; -application org.eclipse.equinox.p2.director.app.application :the application ID.<br />
; -metadataRepository : a comma separated list of metadata repositories where the installable units to be installed can be found.<br />
; -artifactRepository :a comma separated list of artifact repositories where the artifacts can be found.<br />
; -installIU :the identifier of the installable unit to install. If you are looking to install a feature, the identifier of the feature has to be suffixed with ".feature.group".<br />
; -version :the version of the IU to be installed.<br />
; -destination :the folder in which the targeted product is located.<br />
; -profile :the profile id containing the description of the targeted product. This ID is usually found eclipse.p2.profile property contained in the config.ini of the targeted product. For the Eclipse SDK the ID is "SDKProfile"<br />
; -profileProperties :a comma separated list of <key>=<value> pair. The property org.eclipse.update.install.features=true will cause the update manager features to be installed.<br />
; eclipse.p2.data.area :this property points at location of the profile registry containing the description of the profile set in "-profile". It is recommended to set it to be <destination>/p2. This property *must* be set as a VM argument.<br />
; -bundlepool :the location of where the plug-ins and features will be stored. This value is only taken into account when a new profile is created. For an application where all the bundles are located into the plugins/ folder of the destination, set it to <destination>.<br />
; -p2.os :the OS to use when the profile is created. This will be used to filter which OS specific installable units need to be installed.<br />
; -p2.ws :the windowing system to use when the profile is created. This will be used to filter which WS specific installable units need to be installed.<br />
; -p2.arch :the architecture to use when the profile is created. This will be used to filter which architecture specific installable units need to be installed.<br />
; -roaming :indicates that the product resulting from the installation can be moved. This property only makes sense when the destination, bundle pool are in the same location and eclipse.p2.data.area is set to destination/p2. This value is only taken into account when the profile is created. <br />
<br />
[[Category:Equinox_p2|Director application]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=Eclipse_DemoCamps_2008_-_Ganymede_Edition/Toulouse&diff=93942Eclipse DemoCamps 2008 - Ganymede Edition/Toulouse2008-04-22T19:21:48Z<p>Benjamin.cabe.anyware-tech.com: /* Who Is Attending */</p>
<hr />
<div>[[Image:eclipse-camp.gif]] [[Eclipse_DemoCamps_2008_-_Ganymede_Edition | What is an Eclipse DemoCamp?]] <br />
=== Location ===<br />
To be determined<br />
<br />
=== Date and Time ===<br />
June 19, 2008<br />
<br />
=== Organizer ===<br />
Jocya Leroy, Anyware Technologies<br />
<br />
=== Presenters ===<br />
If you would like to present at the DemoCamp, please feel free to add your name and topic to the list. Depending on the number of people interested we may have to limit the number of presenters and time of each demo.<br />
# Presenter Name, Demo Topic<br />
<br />
=== Who Is Attending ===<br />
If you plan on attending please add your name to the list below. We'd like to see as many people show up as possible.<br />
# Jocya Leroy, Anyware Technologies<br />
# David Sciamma, Anyware Technologies<br />
# [http://blog.benjamin-cabe.com Benjamin Cabé], Anyware Technologies</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=API/EclipseCon2008Workshop&diff=87706API/EclipseCon2008Workshop2008-03-17T17:36:02Z<p>Benjamin.cabe.anyware-tech.com: /* Participants */</p>
<hr />
<div>This page collects topics for the API Design Workshop at EclipseCon 2008.<br />
<br />
Status: the [https://eclipsecon.greenmeetingsystems.com/submissions/view/65 workshop submission] has been accepted for EclipseCon 2008! It will be held on Monday, March 17, from 8:00 a.m. to 12:30 a.m. in Room 203/204 of the convention center.<br />
<br />
=== Abstract ===<br />
In this workshop, targeted at Eclipse committers, we will work together on best practices for API design. This workshop will be run in an [http://en.wikipedia.org/wiki/Open_Space_Technology Open Space format] to ensure maximum benefit for the participants. In advance of the workshop, participants will use a wiki page to sign up for the workshop and to coordinate topics they want to discuss or learn about. During the workshop, we will have several breakout discussion sessions about the topics that matter the most to the participants. Discussion notes or results will be posted on the wiki. The workshop organizer will bring a 4-hour slide deck about Java API design just in case. However, I hope that together as a group, we can do better than just listening to one individual.<br />
<br />
=== Participants ===<br />
* Boris Bokowski, IBM Rational, Canada<br />
* Jim des Rivières, IBM Rational, Canada<br />
* Christopher Daniel, Poznan University of Technology, Poland<br />
* Brian Carroll, Serena Software (bcarroll@serena.com)<br />
* Paul Fullbright, Oracle (paul.fullbright@oracle.com)<br />
* Pawel Piech, Wind River (pawel.piech@windriver.com)<br />
* Benjamin Cabé, Anyware Technologies (benjamin.cabe@anyware-tech.com)<br />
* ... add your name...<br />
<br />
=== Topics ===<br />
<br />
* Binary compatibility vs. source compatibility vs. contract compatibility<br />
* API design process best practices<br />
* Exposing the API of an OSGi bundle:<br />
** Import-Package vs. Require-Bundle<br />
** How to use Export-Package with x-internal, x-friends, etc<br />
** Bundle version numbers and package version numbers<br />
** Expressing dependency on execution environments<br />
* API testing<br />
* Guidance on how to approach restructuring a Java library that was not desgined with bundles/plugins in mind to properly expose the APIs for eventual use as a bundle<br />
** Granularity in API design - Guidance on how to organize APIs. At first glance, I would expect to apply traditional OO design criteria and techniques to organize an API, but are there additional considerations for bundles?<br />
* Guidance on designing an API with both flexibility and maintenance (backwards compatibility) in mind<br />
* ... add your own topic ...<br />
<br />
=== Notes from 8:00-10:00 Session (courtesy of Anders Skarby) ===<br />
<br />
* On "How to structure existing code, into an API" and a "API design process".<br />
* Don't want to guide the user in best practices, rather support users to do things and be flexible, than guide for best practices. Allow for good practices, and stupid implementations.<br />
* A good API cannot be constructed from existing code, without making modifications to the existing code base.<br />
* API is an interface between components and also teams, defines interfaces / boundaries for the API working within those limitations everything goes (is allowed).<br />
* APIs will be best if designed as an API from scratch, have a specification in mind. It's easier to design for something when having a cover story available (all questions should be answered.<br />
* Every API designed should at least have one client (user). The more distance between the API and the client, the better.<br />
* Interaction between client and API teams should be incremental. Implement inital draft, document, ship to client - be prepared of any inconvinience reports, get that feedback and go onto another iteration.<br />
* It's okay to change an API until it's published. Once published the API should be freezed (locked down for changes). Since unknown party of clients there's no way of changing the implementaiton and mediate the information about that. If inhouse API this might be an acceptable situation since informaiton CAN be mediated.<br />
* It pays to design upfront, and understand what you will be serving. You want to expand the API over time but not retract any parts of the API.<br />
* If clients starts relying upon implementaiton details instead of API you have a problem since you don't have a way to change the API specification.<br />
* The client can not (may not) assume anothing that's not in the API contract.<br />
* The API dictates a contract of decoupling code.<br />
* Unit tests don't dictate behaviour since the implementation of the test (if written by the specific part of the API) since it's only testing for the behaviour the developer is consious about.<br />
* Unit tests should probably be looked over, or written by, another party so that it is written against the API specificaiton.<br />
* Documenting your API (Javadoc specification) is important, it can rely on a platform convention (not talking about null values, assumes that they are accepted) or being specific (being verbose about whether an argument or return type accepts null).<br />
* Annotations could also be used for using tooling (like findbugs, eg.) to verify that a null-check is implemented in the code using the API.<br />
* Internal packages are used to mediate that the behaviour in these packages are not for users, it's possible to access or do in java code - but PDE suports that it is not desirable. Dictating non-public code in private classes limits the usability of that code in a too strict sense. <br />
* x-internal (statements in MANIFEST.MF) can be used for marking internal classes so that they can be used of other plugins, although they get a warning, marking API without enforcing it in a strict / dictating way.<br />
* The signature of a method sometimes exposes an internal packages class to the API - this is not best practice and should generally be avoided.<br />
* Overloading is sometimes an issue (or becomes an issue) when serving convenience, but over tiem null arguments can lead to new methods bein invoked and unintended behaviour occuring at the client side.<br />
* It's very difficult to protect against overloading and various other functionalities in Java - still it's desirable to guide the user / client as far as possible and guard against the API speicification.<br />
* Eclipse uses binary compatibility between releases, so that any plugin mediating that it relies on version XX or later can run on the API of that version or later. Source compatibility between releases is not always sufficient. Step carefully to ensure binary compatibilty between releases (guidelines on Eclipse WIKI on evolving APIs).<br />
* In terms of process for maintaining version compatability (within the Eclipse platform) an API freeze is enforced from Milestone 6 so that you can enforce stability in the end of a release cycle. Furthermore public classes / exposed API is checked for binary compatibility (internal classes are assumed safe). It's an investment against stability and to provide upwards compatbility. If any API breaks occur, they to into the migration guide.<br />
* When going between major versions of API release, a compatability layer should be present to provide a bridge between older versions and the new version (and keep clients utilitizng older versions of APIs functioning on the new API).<br />
* You can't always clean up APIs by deprecating parts of an API, since a flood of warning / errors would occur at the client side. Keep the users existing code in mind, and for that rather keep the old APIs present and provide new APIs. An example of this is the command extension point vs. action contributions.<br />
* There API and non-API, but sometimes you want to release a partial implementation (or not available in a final implementation) - this is the provisional available code, this is however non-API and the only promise made is that compatability WILL be broken. It's also available to service API work that spans multiple release cycles, to get users (external clients) feedback. Provisinal "APIs" should be placed in internal packages to indicate that changes will occur.<br />
* Versioning indicates API changes in the following way: Changes to major version segment indicates changes that breaks API compability, Changes to minor version segment mediates non-breaking API changes. Changes to micro version segment mediates bug fixes, code changes that don't affect the API from a client point of view etc.</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=BugDay/February_2008&diff=86373BugDay/February 20082008-03-07T08:57:29Z<p>Benjamin.cabe.anyware-tech.com: /* Participants */</p>
<hr />
<div>== Eclipse Bug Day ([http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=29&year=2008 Time and Date]) ==<br />
'''[[Bug Day]]''' will be held on February 29th.<br />
<br />
=== Projects ===<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Project !! Contacts(s) !! [irc://irc.freenode.net/#eclipse IRC nick] !! Triage !! Bugs !! [[PSF]] !! Mylyn Query<br />
|-<br />
| [http://www.eclipse.org/ecf ECF] || Chris Aniszczyk<br/> Remy Suen<br/> Scott Lewis|| zx<br/> rcjsuen<br/> slewis2 || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/ecf/org.eclipse.ecf.docs/ecf-anonymous.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/pde PDE] || Chris Aniszczyk<br/> Brian Bauman || zx<br/> baumanbr || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/pde/pde-ui/project-set-files/pde-ui-pserver.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/dsdp/tm DSDP-TM] || [mailto:martin.oberhuber@windriver.com Martin Oberhuber]<br/> Dave McKnight<br/> Kevin Doyle || mober<br/> dmcknigh<br/> kjdoyle|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=2.0.1&keywords_type=nowords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [http://www.eclipse.org/dsdp/tm/development/cvs_setup.php Link] ||<br />
|-<br />
| [http://www.eclipse.org/rap RAP] || Benjamin Muskalla || benny`work || N/A || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=RAP&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/rap/resources/rap.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/wtp Web Tools Platform]<br />
|| [mailto:gerry.kessler@oracle.com Gerry Kessler (JSF)] || gkessler || N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=WebTools&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link]<br />
|N/A ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/debug/index.php JDT/Platform Debug]<br />
| [mailto:Michael_Rennie@ca.ibm.com Michael Rennie] <br/> [mailto:cwindatt@ca.ibm.com Curtis Windatt] || -<br/> - || [https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed&namedcmd=Inbox Link]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=JDT&product=Platform&component=Debug&component=Debug&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&resolution=LATER&resolution=REMIND&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [http://www.eclipse.org/eclipse/debug/documents/project_sets/debug.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/mylyn Mylyn] ([[Mylyn Contributor Reference|Contributor Ref.]])<br />
|| [mailto:eu@md.pp.ru Eugene Kuleshov] || ekuleshov || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [http://www.eclipse.org/mylyn/doc/dev/mylyn.psf Link] ||<br />
[http://wiki.eclipse.org/images/1/1b/Eclipse%2BMylyn%2BBugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/vep Visual Editor] ([[VE/Contributing|Contributor Ref.]])<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] || pombreda || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=VE&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/attachment.cgi?id=78346 Link] ||<br />
|-<br />
| [http://www.eclipse.org/atf Ajax and JavaScript Web tools]<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] <br/> Robert Goodman <br/> Javier Pedemonte<br />
|| pombreda <br/> Robert_Goodman <br/> jhpedemonte<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=ATF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [http://wiki.eclipse.org/images/8/89/Atf-psf.zip Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-ui Platform UI] ([[Platform_UI/How_to_Contribute|How to Contribute]])<br />
|| [mailto:Boris_Bokowski@ca.ibm.com Boris Bokowski]<br />
|| blupin<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=Eclipse&component=IDE&component=UI&email1=&email2=&emailtype1=substring&emailtype2=substring&field-1-0-0=classification&field-1-1-0=product&field-1-2-0=component&field-1-3-0=bug_status&field-1-4-0=keywords&field0-0-0=noop&keywords=bugday&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=Platform&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type-1-3-0=anyexact&type-1-4-0=allwords&type0-0-0=noop&value-1-0-0=Eclipse&value-1-1-0=Platform&value-1-2-0=IDE%2CUI&value-1-3-0=NEW%2CASSIGNED%2CREOPENED&value-1-4-0=bugday&value0-0-0=&votes=&order=bugs.bug_id&query_based_on= Link]<br />
|| [http://www.eclipse.org/eclipse/platform-ui/psf/ Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-releng Platform Releng] <br />
|| [mailto:Kim_Moir@ca.ibm.com Kim Moir]<br />
|| k2moir<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Releng&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| ||<br />
|-<br />
| [http://wiki.eclipse.org/Workspace_Team Platform Workspace]<br />
|| [mailto:Szymon.Brandys@pl.ibm.com Szymon Brandys] <br/> [mailto:Tomasz.Zarna@pl.ibm.com Tomasz Zarna]<br />
|| SzymonB <br/> z4z4<br />
|| [[Workspace_Bugs|Link]]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Compare&component=CVS&component=Resources&component=Team&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [[Workspace_Development#Project_Set_Files_for_Platform_Workspace|Link]]<br />
|| [http://wiki.eclipse.org/images/3/3d/Eclipse_Workspace_BugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/gef/ GEF]<br />
|| [mailto:anthonyh@ca.ibm.com Anthony Hunter]<br />
|| <br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=GEF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| <br />
|}<br />
<br />
<br />
<br />
[http://eclipse.org/mylyn/ Mylyn Query] you can save and import into the Task List view to have up to date list of BugDay bugs<br />
<br />
=== Participants ===<br />
<br />
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-25&chfieldto=2008-03-03&chfield=bug_status&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs Fixed]<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Name !! Bug(s) || Project<br />
|-<br />
| [mailto:d_a_carver@yahoo.com David Carver] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209356 209356] || Webtools<br />
|-<br />
| [mailto:bartosz.michalik@gmail.com Bartosz Michalik] ||<strike>{{bug|18500}}</strike>|| PDE<br />
|-<br />
| [mailto:benjamin.cabe@anyware-tech.com Benjamin Cabé] ||<strike>{{bug|219513}}</strike> <strike>{{bug|220258}}</strike>|| PDE<br />
|-<br />
| [mailto:r.gerganov@prosyst.bg Radoslav Gerganov] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=181563 181563] || DSDP-TM<br />
|}<br />
[[Category:Bug Day]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=BugDay/February_2008&diff=85276BugDay/February 20082008-03-01T10:12:40Z<p>Benjamin.cabe.anyware-tech.com: /* Participants */</p>
<hr />
<div>== Eclipse Bug Day ([http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=29&year=2008 Time and Date]) ==<br />
'''[[Bug Day]]''' will be held on February 29th.<br />
<br />
=== Projects ===<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Project !! Contacts(s) !! [irc://irc.freenode.net/#eclipse IRC nick] !! Triage !! Bugs !! [[PSF]] !! Mylyn Query<br />
|-<br />
| [http://www.eclipse.org/ecf ECF] || Chris Aniszczyk<br/> Remy Suen<br/> Scott Lewis|| zx<br/> rcjsuen<br/> slewis2 || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/ecf/org.eclipse.ecf.docs/ecf-anonymous.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/pde PDE] || Chris Aniszczyk<br/> Brian Bauman || zx<br/> baumanbr || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/pde/pde-ui/project-set-files/pde-ui-pserver.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/dsdp/tm DSDP-TM] || [mailto:martin.oberhuber@windriver.com Martin Oberhuber]<br/> Dave McKnight<br/> Kevin Doyle || mober<br/> dmcknigh<br/> kjdoyle|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=2.0.1&keywords_type=nowords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [http://www.eclipse.org/dsdp/tm/development/cvs_setup.php Link] ||<br />
|-<br />
| [http://www.eclipse.org/rap RAP] || Benjamin Muskalla || benny`work || N/A || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=RAP&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/rap/resources/rap.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/wtp Web Tools Platform]<br />
|| [mailto:gerry.kessler@oracle.com Gerry Kessler (JSF)] || gkessler || N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=WebTools&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link]<br />
|N/A ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/debug/index.php JDT/Platform Debug]<br />
| [mailto:Michael_Rennie@ca.ibm.com Michael Rennie] <br/> [mailto:cwindatt@ca.ibm.com Curtis Windatt] || -<br/> - || [https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed&namedcmd=Inbox Link]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=JDT&product=Platform&component=Debug&component=Debug&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&resolution=LATER&resolution=REMIND&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [http://www.eclipse.org/eclipse/debug/documents/project_sets/debug.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/mylyn Mylyn] ([[Mylyn Contributor Reference|Contributor Ref.]])<br />
|| [mailto:eu@md.pp.ru Eugene Kuleshov] || ekuleshov || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [http://www.eclipse.org/mylyn/doc/dev/mylyn.psf Link] ||<br />
[http://wiki.eclipse.org/images/1/1b/Eclipse%2BMylyn%2BBugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/vep Visual Editor] ([[VE/Contributing|Contributor Ref.]])<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] || pombreda || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=VE&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/attachment.cgi?id=78346 Link] ||<br />
|-<br />
| [http://www.eclipse.org/atf Ajax and JavaScript Web tools]<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] <br/> Robert Goodman <br/> Javier Pedemonte<br />
|| pombreda <br/> Robert_Goodman <br/> jhpedemonte<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=ATF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [http://wiki.eclipse.org/images/8/89/Atf-psf.zip Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-ui Platform UI] ([[Platform_UI/How_to_Contribute|How to Contribute]])<br />
|| [mailto:Boris_Bokowski@ca.ibm.com Boris Bokowski]<br />
|| blupin<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=Eclipse&component=IDE&component=UI&email1=&email2=&emailtype1=substring&emailtype2=substring&field-1-0-0=classification&field-1-1-0=product&field-1-2-0=component&field-1-3-0=bug_status&field-1-4-0=keywords&field0-0-0=noop&keywords=bugday&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=Platform&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type-1-3-0=anyexact&type-1-4-0=allwords&type0-0-0=noop&value-1-0-0=Eclipse&value-1-1-0=Platform&value-1-2-0=IDE%2CUI&value-1-3-0=NEW%2CASSIGNED%2CREOPENED&value-1-4-0=bugday&value0-0-0=&votes=&order=bugs.bug_id&query_based_on= Link]<br />
|| [http://www.eclipse.org/eclipse/platform-ui/psf/ Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-releng Platform Releng] <br />
|| [mailto:Kim_Moir@ca.ibm.com Kim Moir]<br />
|| k2moir<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Releng&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| ||<br />
|-<br />
| [http://wiki.eclipse.org/Workspace_Team Platform Workspace]<br />
|| [mailto:Szymon.Brandys@pl.ibm.com Szymon Brandys] <br/> [mailto:Tomasz.Zarna@pl.ibm.com Tomasz Zarna]<br />
|| SzymonB <br/> z4z4<br />
|| [[Workspace_Bugs|Link]]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Compare&component=CVS&component=Resources&component=Team&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [[Workspace_Development#Project_Set_Files_for_Platform_Workspace|Link]]<br />
|| [http://wiki.eclipse.org/images/3/3d/Eclipse_Workspace_BugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/gef/ GEF]<br />
|| [mailto:anthonyh@ca.ibm.com Anthony Hunter]<br />
|| <br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=GEF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| <br />
|}<br />
<br />
<br />
<br />
[http://eclipse.org/mylyn/ Mylyn Query] you can save and import into the Task List view to have up to date list of BugDay bugs<br />
<br />
=== Participants ===<br />
<br />
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2008-01-25&chfieldto=2008-03-03&chfield=bug_status&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs Fixed]<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Name !! Bug(s) || Project<br />
|-<br />
| [mailto:d_a_carver@yahoo.com David Carver] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209356 209356] || Webtools<br />
|-<br />
| [mailto:bartosz.michalik@gmail.com Bartosz Michalik] ||<strike>{{bug|18500}}</strike>|| PDE<br />
|-<br />
| [mailto:benjamin.cabe@anyware-tech.com Benjamin Cabé] ||{{bug|219513}} <strike>{{bug|220258}}</strike>|| PDE<br />
|-<br />
| [mailto:r.gerganov@prosyst.bg Radoslav Gerganov] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=181563 181563] || DSDP-TM<br />
|}<br />
[[Category:Bug Day]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=BugDay/February_2008&diff=85275BugDay/February 20082008-03-01T10:11:14Z<p>Benjamin.cabe.anyware-tech.com: /* Participants */</p>
<hr />
<div>== Eclipse Bug Day ([http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=29&year=2008 Time and Date]) ==<br />
'''[[Bug Day]]''' will be held on February 29th.<br />
<br />
=== Projects ===<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Project !! Contacts(s) !! [irc://irc.freenode.net/#eclipse IRC nick] !! Triage !! Bugs !! [[PSF]] !! Mylyn Query<br />
|-<br />
| [http://www.eclipse.org/ecf ECF] || Chris Aniszczyk<br/> Remy Suen<br/> Scott Lewis|| zx<br/> rcjsuen<br/> slewis2 || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/ecf/org.eclipse.ecf.docs/ecf-anonymous.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/pde PDE] || Chris Aniszczyk<br/> Brian Bauman || zx<br/> baumanbr || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/pde/pde-ui/project-set-files/pde-ui-pserver.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/dsdp/tm DSDP-TM] || [mailto:martin.oberhuber@windriver.com Martin Oberhuber]<br/> Dave McKnight<br/> Kevin Doyle || mober<br/> dmcknigh<br/> kjdoyle|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=2.0.1&keywords_type=nowords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [http://www.eclipse.org/dsdp/tm/development/cvs_setup.php Link] ||<br />
|-<br />
| [http://www.eclipse.org/rap RAP] || Benjamin Muskalla || benny`work || N/A || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=RAP&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/rap/resources/rap.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/wtp Web Tools Platform]<br />
|| [mailto:gerry.kessler@oracle.com Gerry Kessler (JSF)] || gkessler || N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=WebTools&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link]<br />
|N/A ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/debug/index.php JDT/Platform Debug]<br />
| [mailto:Michael_Rennie@ca.ibm.com Michael Rennie] <br/> [mailto:cwindatt@ca.ibm.com Curtis Windatt] || -<br/> - || [https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed&namedcmd=Inbox Link]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=JDT&product=Platform&component=Debug&component=Debug&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&resolution=LATER&resolution=REMIND&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [http://www.eclipse.org/eclipse/debug/documents/project_sets/debug.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/mylyn Mylyn] ([[Mylyn Contributor Reference|Contributor Ref.]])<br />
|| [mailto:eu@md.pp.ru Eugene Kuleshov] || ekuleshov || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [http://www.eclipse.org/mylyn/doc/dev/mylyn.psf Link] ||<br />
[http://wiki.eclipse.org/images/1/1b/Eclipse%2BMylyn%2BBugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/vep Visual Editor] ([[VE/Contributing|Contributor Ref.]])<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] || pombreda || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=VE&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/attachment.cgi?id=78346 Link] ||<br />
|-<br />
| [http://www.eclipse.org/atf Ajax and JavaScript Web tools]<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] <br/> Robert Goodman <br/> Javier Pedemonte<br />
|| pombreda <br/> Robert_Goodman <br/> jhpedemonte<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=ATF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [http://wiki.eclipse.org/images/8/89/Atf-psf.zip Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-ui Platform UI] ([[Platform_UI/How_to_Contribute|How to Contribute]])<br />
|| [mailto:Boris_Bokowski@ca.ibm.com Boris Bokowski]<br />
|| blupin<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=Eclipse&component=IDE&component=UI&email1=&email2=&emailtype1=substring&emailtype2=substring&field-1-0-0=classification&field-1-1-0=product&field-1-2-0=component&field-1-3-0=bug_status&field-1-4-0=keywords&field0-0-0=noop&keywords=bugday&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=Platform&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type-1-3-0=anyexact&type-1-4-0=allwords&type0-0-0=noop&value-1-0-0=Eclipse&value-1-1-0=Platform&value-1-2-0=IDE%2CUI&value-1-3-0=NEW%2CASSIGNED%2CREOPENED&value-1-4-0=bugday&value0-0-0=&votes=&order=bugs.bug_id&query_based_on= Link]<br />
|| [http://www.eclipse.org/eclipse/platform-ui/psf/ Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-releng Platform Releng] <br />
|| [mailto:Kim_Moir@ca.ibm.com Kim Moir]<br />
|| k2moir<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Releng&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| ||<br />
|-<br />
| [http://wiki.eclipse.org/Workspace_Team Platform Workspace]<br />
|| [mailto:Szymon.Brandys@pl.ibm.com Szymon Brandys] <br/> [mailto:Tomasz.Zarna@pl.ibm.com Tomasz Zarna]<br />
|| SzymonB <br/> z4z4<br />
|| [[Workspace_Bugs|Link]]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Compare&component=CVS&component=Resources&component=Team&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [[Workspace_Development#Project_Set_Files_for_Platform_Workspace|Link]]<br />
|| [http://wiki.eclipse.org/images/3/3d/Eclipse_Workspace_BugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/gef/ GEF]<br />
|| [mailto:anthonyh@ca.ibm.com Anthony Hunter]<br />
|| <br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=GEF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| <br />
|}<br />
<br />
<br />
<br />
[http://eclipse.org/mylyn/ Mylyn Query] you can save and import into the Task List view to have up to date list of BugDay bugs<br />
<br />
=== Participants ===<br />
<br />
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2007-10-06&chfieldto=2007-11-02&chfield=bug_status&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs Fixed]<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Name !! Bug(s) || Project<br />
|-<br />
| [mailto:d_a_carver@yahoo.com David Carver] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209356 209356] || Webtools<br />
|-<br />
| [mailto:bartosz.michalik@gmail.com Bartosz Michalik] ||<strike>{{bug|18500}}</strike>|| PDE<br />
|-<br />
| [mailto:benjamin.cabe@anyware-tech.com Benjamin Cabé] ||{{bug|219513}} <strike>{{bug|220258}}</strike>|| PDE<br />
|-<br />
| [mailto:r.gerganov@prosyst.bg Radoslav Gerganov] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=181563 181563] || DSDP-TM<br />
|}<br />
[[Category:Bug Day]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=BugDay/February_2008&diff=83898BugDay/February 20082008-02-22T18:36:50Z<p>Benjamin.cabe.anyware-tech.com: /* Participants */</p>
<hr />
<div>== Eclipse Bug Day ([http://www.timeanddate.com/worldclock/fixedtime.html?month=2&day=29&year=2008 Time and Date]) ==<br />
'''[[Bug Day]]''' will be held on February 29th.<br />
<br />
=== Projects ===<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Project !! Contacts(s) !! [irc://irc.freenode.net/#eclipse IRC nick] !! Triage !! Bugs !! [[PSF]] !! Mylyn Query<br />
|-<br />
| [http://www.eclipse.org/ecf ECF] || Chris Aniszczyk<br/> Remy Suen<br/> Scott Lewis|| zx<br/> rcjsuen<br/> slewis2 || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/ecf/org.eclipse.ecf.docs/ecf-anonymous.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/pde PDE] || Chris Aniszczyk<br/> Brian Bauman || zx<br/> baumanbr || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/pde/pde-ui/project-set-files/pde-ui-pserver.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/dsdp/tm DSDP-TM] || [mailto:martin.oberhuber@windriver.com Martin Oberhuber]<br/> Dave McKnight<br/> Kevin Doyle || mober<br/> dmcknigh<br/> kjdoyle|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=2.0.1&keywords_type=nowords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [http://www.eclipse.org/dsdp/tm/development/cvs_setup.php Link] ||<br />
|-<br />
| [http://www.eclipse.org/rap RAP] || Benjamin Muskalla || benny`work || N/A || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=RAP&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/rap/resources/rap.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/wtp Web Tools Platform]<br />
|| [mailto:gerry.kessler@oracle.com Gerry Kessler (JSF)] || gkessler || N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=WebTools&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link]<br />
|N/A ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/debug/index.php JDT/Platform Debug]<br />
| [mailto:Michael_Rennie@ca.ibm.com Michael Rennie] <br/> [mailto:cwindatt@ca.ibm.com Curtis Windatt] || -<br/> - || [https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed&namedcmd=Inbox Link]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=JDT&product=Platform&component=Debug&component=Debug&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&resolution=LATER&resolution=REMIND&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [http://www.eclipse.org/eclipse/debug/documents/project_sets/debug.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/mylyn Mylyn] ([[Mylyn Contributor Reference|Contributor Ref.]])<br />
|| [mailto:eu@md.pp.ru Eugene Kuleshov] || ekuleshov || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [http://www.eclipse.org/mylyn/doc/dev/mylyn.psf Link] ||<br />
[http://wiki.eclipse.org/images/1/1b/Eclipse%2BMylyn%2BBugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/vep Visual Editor] ([[VE/Contributing|Contributor Ref.]])<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] || pombreda || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=VE&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/attachment.cgi?id=78346 Link] ||<br />
|-<br />
| [http://www.eclipse.org/atf Ajax and JavaScript Web tools]<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] <br/> Robert Goodman <br/> Javier Pedemonte<br />
|| pombreda <br/> Robert_Goodman <br/> jhpedemonte<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=ATF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [http://wiki.eclipse.org/images/8/89/Atf-psf.zip Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-ui Platform UI] ([[Platform_UI/How_to_Contribute|How to Contribute]])<br />
|| [mailto:Boris_Bokowski@ca.ibm.com Boris Bokowski]<br />
|| blupin<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=Eclipse&component=IDE&component=UI&email1=&email2=&emailtype1=substring&emailtype2=substring&field-1-0-0=classification&field-1-1-0=product&field-1-2-0=component&field-1-3-0=bug_status&field-1-4-0=keywords&field0-0-0=noop&keywords=bugday&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=Platform&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type-1-3-0=anyexact&type-1-4-0=allwords&type0-0-0=noop&value-1-0-0=Eclipse&value-1-1-0=Platform&value-1-2-0=IDE%2CUI&value-1-3-0=NEW%2CASSIGNED%2CREOPENED&value-1-4-0=bugday&value0-0-0=&votes=&order=bugs.bug_id&query_based_on= Link]<br />
|| [http://www.eclipse.org/eclipse/platform-ui/psf/ Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-releng Platform Releng] <br />
|| [mailto:Kim_Moir@ca.ibm.com Kim Moir]<br />
|| k2moir<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Releng&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| ||<br />
|-<br />
| [http://wiki.eclipse.org/Workspace_Team Platform Workspace]<br />
|| [mailto:Szymon.Brandys@pl.ibm.com Szymon Brandys] <br/> [mailto:Tomasz.Zarna@pl.ibm.com Tomasz Zarna]<br />
|| SzymonB <br/> z4z4<br />
|| [[Workspace_Bugs|Link]]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Compare&component=CVS&component=Resources&component=Team&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [[Workspace_Development#Project_Set_Files_for_Platform_Workspace|Link]]<br />
|| [http://wiki.eclipse.org/images/3/3d/Eclipse_Workspace_BugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/gef/ GEF]<br />
|| [mailto:anthonyh@ca.ibm.com Anthony Hunter]<br />
|| <br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=GEF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| <br />
|}<br />
<br />
<br />
<br />
[http://eclipse.org/mylyn/ Mylyn Query] you can save and import into the Task List view to have up to date list of BugDay bugs<br />
<br />
=== Participants ===<br />
<br />
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2007-10-06&chfieldto=2007-11-02&chfield=bug_status&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs Fixed]<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Name !! Bug(s) || Project<br />
|-<br />
| [mailto:d_a_carver@yahoo.com David Carver] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209356 209356] || Webtools<br />
|-<br />
| [mailto:bartosz.michalik@gmail.com Bartosz Michalik] ||<strike>{{bug|18500}}</strike>|| PDE<br />
|-<br />
| [mailto:benjamin.cabe@anyware-tech.com Benjamin Cabé] ||{{bug|219513}}|| PDE<br />
|}<br />
[[Category:Bug Day]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=BugDay/January_2008&diff=77243BugDay/January 20082008-01-25T20:06:37Z<p>Benjamin.cabe.anyware-tech.com: /* Eclipse Bug Day ([http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=26&year=2008 Time and Date]) */</p>
<hr />
<div>== Eclipse Bug Day ([http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=26&year=2008 Time and Date]) ==<br />
'''[[Bug Day]]''' will be held on January 25th.<br />
<br />
=== Projects ===<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Project !! Contacts(s) !! [irc://irc.freenode.net/#eclipse IRC nick] !! Triage !! Bugs !! [[PSF]] !! Mylyn Query<br />
|-<br />
| [http://www.eclipse.org/ecf ECF] || Chris Aniszczyk<br/> Remy Suen<br/> Scott Lewis|| zx<br/> rcjsuen<br/> slewis2 || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/ecf/org.eclipse.ecf.docs/ecf-anonymous.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/pde PDE] || Chris Aniszczyk<br/> Brian Bauman || zx<br/> baumanbr || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/pde/pde-ui/project-set-files/pde-ui-pserver.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/dsdp/tm DSDP-TM] || [mailto:martin.oberhuber@windriver.com Martin Oberhuber]<br/> Dave McKnight<br/> Kevin Doyle || mober<br/> dmcknigh<br/> kjdoyle|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=2.0.1&keywords_type=nowords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [http://www.eclipse.org/dsdp/tm/development/cvs_setup.php Link] ||<br />
|-<br />
| [http://www.eclipse.org/rap RAP] || Benjamin Muskalla || benny`work || N/A || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=RAP&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/rap/resources/rap.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/wtp Web Tools Platform]<br />
|| [mailto:gerry.kessler@oracle.com Gerry Kessler (JSF)] || gkessler || N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=WebTools&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link]<br />
|N/A ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/debug/index.php JDT/Platform Debug]<br />
| [mailto:Michael_Rennie@ca.ibm.com Michael Rennie] <br/> [mailto:cwindatt@ca.ibm.com Curtis Windatt] || -<br/> - || [https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed&namedcmd=Inbox Link]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=JDT&product=Platform&component=Debug&component=Debug&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&resolution=LATER&resolution=REMIND&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [http://www.eclipse.org/eclipse/debug/documents/project_sets/debug.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/mylyn Mylyn] ([[Mylyn Contributor Reference|Contributor Ref.]])<br />
|| [mailto:eu@md.pp.ru Eugene Kuleshov] || ekuleshov || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [http://www.eclipse.org/mylyn/doc/dev/mylyn.psf Link] ||<br />
[http://wiki.eclipse.org/images/1/1b/Eclipse%2BMylyn%2BBugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/vep Visual Editor] ([[VE/Contributing|Contributor Ref.]])<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] || pombreda || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=VE&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/attachment.cgi?id=78346 Link] ||<br />
|-<br />
| [http://www.eclipse.org/atf Ajax and JavaScript Web tools]<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] <br/> Robert Goodman <br/> Javier Pedemonte<br />
|| pombreda <br/> Robert_Goodman <br/> jhpedemonte<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=ATF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [http://wiki.eclipse.org/images/8/89/Atf-psf.zip Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-ui Platform UI] ([[Platform_UI/How_to_Contribute|How to Contribute]])<br />
|| [mailto:Boris_Bokowski@ca.ibm.com Boris Bokowski]<br />
|| blupin<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=Eclipse&component=IDE&component=UI&email1=&email2=&emailtype1=substring&emailtype2=substring&field-1-0-0=classification&field-1-1-0=product&field-1-2-0=component&field-1-3-0=bug_status&field-1-4-0=keywords&field0-0-0=noop&keywords=bugday&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=Platform&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type-1-3-0=anyexact&type-1-4-0=allwords&type0-0-0=noop&value-1-0-0=Eclipse&value-1-1-0=Platform&value-1-2-0=IDE%2CUI&value-1-3-0=NEW%2CASSIGNED%2CREOPENED&value-1-4-0=bugday&value0-0-0=&votes=&order=bugs.bug_id&query_based_on= Link]<br />
|| [http://www.eclipse.org/eclipse/platform-ui/psf/ Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-releng Platform Releng] <br />
|| [mailto:Kim_Moir@ca.ibm.com Kim Moir]<br />
|| k2moir<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Releng&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| ||<br />
|-<br />
| [http://wiki.eclipse.org/Workspace_Team Platform Workspace]<br />
|| [mailto:Szymon.Brandys@pl.ibm.com Szymon Brandys] <br/> [mailto:Tomasz.Zarna@pl.ibm.com Tomasz Zarna]<br />
|| SzymonB <br/> z4z4<br />
|| [[Workspace_Bugs|Link]]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Compare&component=CVS&component=Resources&component=Team&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [[Workspace_Development#Project_Set_Files_for_Platform_Workspace|Link]]<br />
|| [http://wiki.eclipse.org/images/3/3d/Eclipse_Workspace_BugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/gef/ GEF]<br />
|| [mailto:anthonyh@ca.ibm.com Anthony Hunter]<br />
|| <br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=GEF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| <br />
|}<br />
<br />
<br />
<br />
[http://eclipse.org/mylyn/ Mylyn Query] you can save and import into the Task List view to have up to date list of BugDay bugs<br />
<br />
=== Participants ===<br />
<br />
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2007-10-06&chfieldto=2007-11-02&chfield=bug_status&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs Fixed]<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Name !! Bug(s) || Project<br />
|-<br />
| [mailto:d_a_carver@yahoo.com David Carver] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209356 209356] || Webtools<br />
|-<br />
| [mailto:bartosz.michalik@gmail.com Bartosz Michalik] ||<strike>{{bug|214156}}</strike>, <strike>{{bug|209432}}</strike> || PDE<br />
|}<br />
[[Category:Bug Day]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=BugDay/November_2007&diff=65435BugDay/November 20072007-12-02T18:39:31Z<p>Benjamin.cabe.anyware-tech.com: /* Participants */</p>
<hr />
<div>== Eclipse Bug Day ([http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=30&year=2007 Time and Date]) ==<br />
'''[[Bug Day]]''' will be held on November 30th.<br />
<br />
=== Projects ===<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Project !! Contacts(s) !! [irc://irc.freenode.net/#eclipse IRC nick] !! Triage !! Bugs !! [[PSF]] !! Mylyn Query<br />
|-<br />
| [http://www.eclipse.org/ecf ECF] || Chris Aniszczyk<br/> Remy Suen<br/> Scott Lewis|| zx<br/> rcjsuen<br/> slewis2 || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/ecf/org.eclipse.ecf.docs/ecf-anonymous.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/pde PDE] || Chris Aniszczyk<br/> Brian Bauman || zx<br/> baumanbr || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/pde/pde-ui/project-set-files/pde-ui-pserver.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/dsdp/tm DSDP-TM] || [mailto:martin.oberhuber@windriver.com Martin Oberhuber]<br/> Dave McKnight<br/> Kevin Doyle || mober<br/> dmcknigh<br/> kjdoyle|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=2.0.1&keywords_type=nowords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [http://www.eclipse.org/dsdp/tm/development/cvs_setup.php Link] ||<br />
|-<br />
| [http://www.eclipse.org/rap RAP] || Benjamin Muskalla || benny`work || N/A || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=RAP&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/rap/resources/rap.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/wtp Web Tools Platform]<br />
|| [http://wiki.eclipse.org/User:Nitind Nitin Dahyabhai]<br/> [mailto:gerry.kessler@oracle.com Gerry Kessler (JSF)] || nitind<br/> gkessler || N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=WebTools&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link]<br />
|N/A ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/debug/index.php JDT/Platform Debug]<br />
| [mailto:Michael_Rennie@ca.ibm.com Michael Rennie] <br/> [mailto:cwindatt@ca.ibm.com Curtis Windatt] || -<br/> - || [https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed&namedcmd=Inbox Link]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=JDT&product=Platform&component=Debug&component=Debug&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&resolution=LATER&resolution=REMIND&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [http://www.eclipse.org/eclipse/debug/documents/project_sets/debug.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/mylyn Mylyn] ([[Mylyn Contributor Reference|Contributor Ref.]])<br />
|| [mailto:eu@md.pp.ru Eugene Kuleshov] || ekuleshov || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [http://www.eclipse.org/mylyn/doc/dev/mylyn.psf Link] ||<br />
[http://wiki.eclipse.org/images/1/1b/Eclipse%2BMylyn%2BBugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/vep Visual Editor] ([[VE/Contributing|Contributor Ref.]])<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] || pombreda || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=VE&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/attachment.cgi?id=78346 Link] ||<br />
|-<br />
| [http://www.eclipse.org/atf Ajax and JavaScript Web tools]<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] <br/> Robert Goodman <br/> Javier Pedemonte<br />
|| pombreda <br/> Robert_Goodman <br/> jhpedemonte<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=ATF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [http://wiki.eclipse.org/images/8/89/Atf-psf.zip Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-ui Platform UI] ([[Platform_UI/How_to_Contribute|How to Contribute]])<br />
|| [mailto:Boris_Bokowski@ca.ibm.com Boris Bokowski]<br />
|| blupin<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=Eclipse&component=IDE&component=UI&email1=&email2=&emailtype1=substring&emailtype2=substring&field-1-0-0=classification&field-1-1-0=product&field-1-2-0=component&field-1-3-0=bug_status&field-1-4-0=keywords&field0-0-0=noop&keywords=bugday&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=Platform&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type-1-3-0=anyexact&type-1-4-0=allwords&type0-0-0=noop&value-1-0-0=Eclipse&value-1-1-0=Platform&value-1-2-0=IDE%2CUI&value-1-3-0=NEW%2CASSIGNED%2CREOPENED&value-1-4-0=bugday&value0-0-0=&votes=&order=bugs.bug_id&query_based_on= Link]<br />
|| [http://www.eclipse.org/eclipse/platform-ui/psf/ Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-releng Platform Releng] <br />
|| [mailto:Kim_Moir@ca.ibm.com Kim Moir]<br />
|| k2moir<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Releng&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| ||<br />
|-<br />
| [http://wiki.eclipse.org/Workspace_Team Platform Workspace]<br />
|| [mailto:Szymon.Brandys@pl.ibm.com Szymon Brandys] <br/> [mailto:Tomasz.Zarna@pl.ibm.com Tomasz Zarna]<br />
|| SzymonB <br/> z4z4<br />
|| [[Workspace_Bugs|Link]]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Compare&component=CVS&component=Resources&component=Team&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [[Workspace_Development#Project_Set_Files_for_Platform_Workspace|Link]]<br />
|| [http://wiki.eclipse.org/images/3/3d/Eclipse_Workspace_BugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/gef/ GEF]<br />
|| [mailto:anthonyh@ca.ibm.com Anthony Hunter]<br />
|| <br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=GEF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| <br />
|}<br />
<br />
<br />
<br />
[http://eclipse.org/mylyn/ Mylyn Query] you can save and import into the Task List view to have up to date list of BugDay bugs<br />
<br />
=== Participants ===<br />
<br />
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2007-10-06&chfieldto=2007-11-02&chfield=bug_status&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs Fixed]<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Name !! Bug(s) || Project<br />
|-<br />
| [mailto:d_a_carver@yahoo.com David Carver] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209356 209356], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130007 130007], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=204488 204488] || Webtools<br />
|-<br />
| [mailto:davidk@kelman.com David Kyle] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155704 155704] || Platform Workspace<br />
|-<br />
| [mailto:zx@us.ibm.com Chris Aniszczyk] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209572 209572] || Mylyn<br />
|-<br />
| [mailto:joern@dinkla.net Joern Dinkla] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=210264 210264], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209941 209941] || PDE <br />
|-<br />
| [mailto:benjamin.cabe@anyware-tech.com Benjamin Cabé] || <strike>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=211580 211580]</strike>, <strike>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=209487 209487]</strike> <br />[https://bugs.eclipse.org/bugs/show_bug.cgi?id=56313 56313] || PDE<br /> Platform UI<br />
|}<br />
<br />
[[Category:Bug Day]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=BugDay/November_2007&diff=65323BugDay/November 20072007-11-30T18:41:59Z<p>Benjamin.cabe.anyware-tech.com: /* Participants */</p>
<hr />
<div>== Eclipse Bug Day ([http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=30&year=2007 Time and Date]) ==<br />
'''[[Bug Day]]''' will be held on November 30th.<br />
<br />
=== Projects ===<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Project !! Contacts(s) !! [irc://irc.freenode.net/#eclipse IRC nick] !! Triage !! Bugs !! [[PSF]] !! Mylyn Query<br />
|-<br />
| [http://www.eclipse.org/ecf ECF] || Chris Aniszczyk<br/> Remy Suen<br/> Scott Lewis|| zx<br/> rcjsuen<br/> slewis2 || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/ecf/org.eclipse.ecf.docs/ecf-anonymous.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/pde PDE] || Chris Aniszczyk<br/> Brian Bauman || zx<br/> baumanbr || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/pde/pde-ui/project-set-files/pde-ui-pserver.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/dsdp/tm DSDP-TM] || [mailto:martin.oberhuber@windriver.com Martin Oberhuber]<br/> Dave McKnight<br/> Kevin Doyle || mober<br/> dmcknigh<br/> kjdoyle|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=2.0.1&keywords_type=nowords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [http://www.eclipse.org/dsdp/tm/development/cvs_setup.php Link] ||<br />
|-<br />
| [http://www.eclipse.org/rap RAP] || Benjamin Muskalla || benny`work || N/A || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=RAP&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/rap/resources/rap.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/wtp Web Tools Platform]<br />
|| [http://wiki.eclipse.org/User:Nitind Nitin Dahyabhai]<br/> [mailto:gerry.kessler@oracle.com Gerry Kessler (JSF)] || nitind<br/> gkessler || N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=WebTools&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link]<br />
|N/A ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/debug/index.php JDT/Platform Debug]<br />
| [mailto:Michael_Rennie@ca.ibm.com Michael Rennie] <br/> [mailto:cwindatt@ca.ibm.com Curtis Windatt] || -<br/> - || [https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed&namedcmd=Inbox Link]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=JDT&product=Platform&component=Debug&component=Debug&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&resolution=LATER&resolution=REMIND&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [http://www.eclipse.org/eclipse/debug/documents/project_sets/debug.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/mylyn Mylyn] ([[Mylyn Contributor Reference|Contributor Ref.]])<br />
|| [mailto:eu@md.pp.ru Eugene Kuleshov] || ekuleshov || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [http://www.eclipse.org/mylyn/doc/dev/mylyn.psf Link] ||<br />
[http://wiki.eclipse.org/images/1/1b/Eclipse%2BMylyn%2BBugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/vep Visual Editor] ([[VE/Contributing|Contributor Ref.]])<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] || pombreda || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=VE&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/attachment.cgi?id=78346 Link] ||<br />
|-<br />
| [http://www.eclipse.org/atf Ajax and JavaScript Web tools]<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] <br/> Robert Goodman <br/> Javier Pedemonte<br />
|| pombreda <br/> Robert_Goodman <br/> jhpedemonte<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=ATF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [http://wiki.eclipse.org/images/8/89/Atf-psf.zip Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-ui Platform UI] ([[Platform_UI/How_to_Contribute|How to Contribute]])<br />
|| [mailto:Boris_Bokowski@ca.ibm.com Boris Bokowski]<br />
|| blupin<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=Eclipse&component=IDE&component=UI&email1=&email2=&emailtype1=substring&emailtype2=substring&field-1-0-0=classification&field-1-1-0=product&field-1-2-0=component&field-1-3-0=bug_status&field-1-4-0=keywords&field0-0-0=noop&keywords=bugday&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=Platform&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type-1-3-0=anyexact&type-1-4-0=allwords&type0-0-0=noop&value-1-0-0=Eclipse&value-1-1-0=Platform&value-1-2-0=IDE%2CUI&value-1-3-0=NEW%2CASSIGNED%2CREOPENED&value-1-4-0=bugday&value0-0-0=&votes=&order=bugs.bug_id&query_based_on= Link]<br />
|| [http://www.eclipse.org/eclipse/platform-ui/psf/ Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-releng Platform Releng] <br />
|| [mailto:Kim_Moir@ca.ibm.com Kim Moir]<br />
|| k2moir<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Releng&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| ||<br />
|-<br />
| [http://wiki.eclipse.org/Workspace_Team Platform Workspace]<br />
|| [mailto:Szymon.Brandys@pl.ibm.com Szymon Brandys] <br/> [mailto:Tomasz.Zarna@pl.ibm.com Tomasz Zarna]<br />
|| SzymonB <br/> z4z4<br />
|| [[Workspace_Bugs|Link]]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Compare&component=CVS&component=Resources&component=Team&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [[Workspace_Development#Project_Set_Files_for_Platform_Workspace|Link]]<br />
|| [http://wiki.eclipse.org/images/3/3d/Eclipse_Workspace_BugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/gef/ GEF]<br />
|| [mailto:anthonyh@ca.ibm.com Anthony Hunter]<br />
|| <br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=GEF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| <br />
|}<br />
<br />
<br />
<br />
[http://eclipse.org/mylyn/ Mylyn Query] you can save and import into the Task List view to have up to date list of BugDay bugs<br />
<br />
=== Participants ===<br />
<br />
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2007-10-06&chfieldto=2007-11-02&chfield=bug_status&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs Fixed]<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Name !! Bug(s) || Project<br />
|-<br />
| [mailto:d_a_carver@yahoo.com David Carver] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209356 209356], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130007 130007] || Webtools<br />
|-<br />
| [mailto:davidk@kelman.com David Kyle] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155704 155704] || Platform Workspace<br />
|-<br />
| [mailto:zx@us.ibm.com Chris Aniszczyk] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209572 209572] || Mylyn<br />
|-<br />
| [mailto:joern@dinkla.net Joern Dinkla] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=210264 210264], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209941 209941] || PDE <br />
|-<br />
| [mailto:benjamin.cabe@anyware-tech.com Benjamin Cabé] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=211580 211580], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209487 209487] <br />[https://bugs.eclipse.org/bugs/show_bug.cgi?id=56313 56313] || PDE<br /> Platform UI<br />
|}<br />
<br />
[[Category:Bug Day]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=BugDay/November_2007&diff=65247BugDay/November 20072007-11-30T16:13:09Z<p>Benjamin.cabe.anyware-tech.com: /* Participants */</p>
<hr />
<div>== Eclipse Bug Day ([http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=30&year=2007 Time and Date]) ==<br />
'''[[Bug Day]]''' will be held on November 30th.<br />
<br />
=== Projects ===<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Project !! Contacts(s) !! [irc://irc.freenode.net/#eclipse IRC nick] !! Triage !! Bugs !! [[PSF]] !! Mylyn Query<br />
|-<br />
| [http://www.eclipse.org/ecf ECF] || Chris Aniszczyk<br/> Remy Suen<br/> Scott Lewis|| zx<br/> rcjsuen<br/> slewis2 || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/ecf/org.eclipse.ecf.docs/ecf-anonymous.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/pde PDE] || Chris Aniszczyk<br/> Brian Bauman || zx<br/> baumanbr || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/pde/pde-ui/project-set-files/pde-ui-pserver.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/dsdp/tm DSDP-TM] || [mailto:martin.oberhuber@windriver.com Martin Oberhuber]<br/> Dave McKnight<br/> Kevin Doyle || mober<br/> dmcknigh<br/> kjdoyle|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=2.0.1&keywords_type=nowords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [http://www.eclipse.org/dsdp/tm/development/cvs_setup.php Link] ||<br />
|-<br />
| [http://www.eclipse.org/rap RAP] || Benjamin Muskalla || benny`work || N/A || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=RAP&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/rap/resources/rap.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/wtp Web Tools Platform]<br />
|| [http://wiki.eclipse.org/User:Nitind Nitin Dahyabhai]<br/> [mailto:gerry.kessler@oracle.com Gerry Kessler (JSF)] || nitind<br/> gkessler || N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=WebTools&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link]<br />
|N/A ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/debug/index.php JDT/Platform Debug]<br />
| [mailto:Michael_Rennie@ca.ibm.com Michael Rennie] <br/> [mailto:cwindatt@ca.ibm.com Curtis Windatt] || -<br/> - || [https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed&namedcmd=Inbox Link]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=JDT&product=Platform&component=Debug&component=Debug&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&resolution=LATER&resolution=REMIND&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [http://www.eclipse.org/eclipse/debug/documents/project_sets/debug.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/mylyn Mylyn] ([[Mylyn Contributor Reference|Contributor Ref.]])<br />
|| [mailto:eu@md.pp.ru Eugene Kuleshov] || ekuleshov || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [http://www.eclipse.org/mylyn/doc/dev/mylyn.psf Link] ||<br />
[http://wiki.eclipse.org/images/1/1b/Eclipse%2BMylyn%2BBugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/vep Visual Editor] ([[VE/Contributing|Contributor Ref.]])<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] || pombreda || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=VE&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/attachment.cgi?id=78346 Link] ||<br />
|-<br />
| [http://www.eclipse.org/atf Ajax and JavaScript Web tools]<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] <br/> Robert Goodman <br/> Javier Pedemonte<br />
|| pombreda <br/> Robert_Goodman <br/> jhpedemonte<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=ATF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [http://wiki.eclipse.org/images/8/89/Atf-psf.zip Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-ui Platform UI] ([[Platform_UI/How_to_Contribute|How to Contribute]])<br />
|| [mailto:Boris_Bokowski@ca.ibm.com Boris Bokowski]<br />
|| blupin<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=Eclipse&component=IDE&component=UI&email1=&email2=&emailtype1=substring&emailtype2=substring&field-1-0-0=classification&field-1-1-0=product&field-1-2-0=component&field-1-3-0=bug_status&field-1-4-0=keywords&field0-0-0=noop&keywords=bugday&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=Platform&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type-1-3-0=anyexact&type-1-4-0=allwords&type0-0-0=noop&value-1-0-0=Eclipse&value-1-1-0=Platform&value-1-2-0=IDE%2CUI&value-1-3-0=NEW%2CASSIGNED%2CREOPENED&value-1-4-0=bugday&value0-0-0=&votes=&order=bugs.bug_id&query_based_on= Link]<br />
|| [http://www.eclipse.org/eclipse/platform-ui/psf/ Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-releng Platform Releng] <br />
|| [mailto:Kim_Moir@ca.ibm.com Kim Moir]<br />
|| k2moir<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Releng&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| ||<br />
|-<br />
| [http://wiki.eclipse.org/Workspace_Team Platform Workspace]<br />
|| [mailto:Szymon.Brandys@pl.ibm.com Szymon Brandys] <br/> [mailto:Tomasz.Zarna@pl.ibm.com Tomasz Zarna]<br />
|| SzymonB <br/> z4z4<br />
|| [[Workspace_Bugs|Link]]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Compare&component=CVS&component=Resources&component=Team&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [[Workspace_Development#Project_Set_Files_for_Platform_Workspace|Link]]<br />
|| [http://wiki.eclipse.org/images/3/3d/Eclipse_Workspace_BugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/gef/ GEF]<br />
|| [mailto:anthonyh@ca.ibm.com Anthony Hunter]<br />
|| <br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=GEF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| <br />
|}<br />
<br />
<br />
<br />
[http://eclipse.org/mylyn/ Mylyn Query] you can save and import into the Task List view to have up to date list of BugDay bugs<br />
<br />
=== Participants ===<br />
<br />
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2007-10-06&chfieldto=2007-11-02&chfield=bug_status&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs Fixed]<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Name !! Bug(s) || Project<br />
|-<br />
| [mailto:d_a_carver@yahoo.com David Carver] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209356 209356], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130007 130007] || Webtools<br />
|-<br />
| [mailto:davidk@kelman.com David Kyle] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155704 155704] || Platform Workspace<br />
|-<br />
| [mailto:zx@us.ibm.com Chris Aniszczyk] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209572 209572] || Mylyn<br />
|-<br />
| [mailto:joern@dinkla.net Joern Dinkla] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=210264 210264], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209941 209941] || PDE <br />
|-<br />
| [mailto:benjamin.cabe@anyware-tech.com Benjamin Cabé] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=211580 211580] <br />[https://bugs.eclipse.org/bugs/show_bug.cgi?id=56313 56313] || PDE<br /> Platform UI<br />
|}<br />
<br />
[[Category:Bug Day]]</div>Benjamin.cabe.anyware-tech.comhttps://wiki.eclipse.org/index.php?title=BugDay/November_2007&diff=65185BugDay/November 20072007-11-30T14:23:02Z<p>Benjamin.cabe.anyware-tech.com: /* Participants */</p>
<hr />
<div>== Eclipse Bug Day ([http://www.timeanddate.com/worldclock/fixedtime.html?month=1&day=30&year=2007 Time and Date]) ==<br />
'''[[Bug Day]]''' will be held on November 30th.<br />
<br />
=== Projects ===<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Project !! Contacts(s) !! [irc://irc.freenode.net/#eclipse IRC nick] !! Triage !! Bugs !! [[PSF]] !! Mylyn Query<br />
|-<br />
| [http://www.eclipse.org/ecf ECF] || Chris Aniszczyk<br/> Remy Suen<br/> Scott Lewis|| zx<br/> rcjsuen<br/> slewis2 || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=ECF&component=ecf.core&component=ecf.doc&component=ecf.examples&component=ecf.protocols&component=ecf.providers&component=ecf.test&component=ecf.ui&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/ecf/org.eclipse.ecf.docs/ecf-anonymous.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/pde PDE] || Chris Aniszczyk<br/> Brian Bauman || zx<br/> baumanbr || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=PDE&component=UI&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/pde/pde-ui/project-set-files/pde-ui-pserver.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/dsdp/tm DSDP-TM] || [mailto:martin.oberhuber@windriver.com Martin Oberhuber]<br/> Dave McKnight<br/> Kevin Doyle || mober<br/> dmcknigh<br/> kjdoyle|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&target_milestone=---&target_milestone=2.0.1&keywords_type=nowords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=DSDP&product=Target+Management&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link] || [http://www.eclipse.org/dsdp/tm/development/cvs_setup.php Link] ||<br />
|-<br />
| [http://www.eclipse.org/rap RAP] || Benjamin Muskalla || benny`work || N/A || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=RAP&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] || [http://www.eclipse.org/rap/resources/rap.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/wtp Web Tools Platform]<br />
|| [http://wiki.eclipse.org/User:Nitind Nitin Dahyabhai]<br/> [mailto:gerry.kessler@oracle.com Gerry Kessler (JSF)] || nitind<br/> gkessler || N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&classification=WebTools&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Link]<br />
|N/A ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/debug/index.php JDT/Platform Debug]<br />
| [mailto:Michael_Rennie@ca.ibm.com Michael Rennie] <br/> [mailto:cwindatt@ca.ibm.com Curtis Windatt] || -<br/> - || [https://bugs.eclipse.org/bugs/buglist.cgi?cmdtype=runnamed&namedcmd=Inbox Link]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=JDT&product=Platform&component=Debug&component=Debug&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&resolution=LATER&resolution=REMIND&resolution=---&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [http://www.eclipse.org/eclipse/debug/documents/project_sets/debug.psf Link] ||<br />
|-<br />
| [http://www.eclipse.org/mylyn Mylyn] ([[Mylyn Contributor Reference|Contributor Ref.]])<br />
|| [mailto:eu@md.pp.ru Eugene Kuleshov] || ekuleshov || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=anywords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link] <br />
|| [http://www.eclipse.org/mylyn/doc/dev/mylyn.psf Link] ||<br />
[http://wiki.eclipse.org/images/1/1b/Eclipse%2BMylyn%2BBugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/vep Visual Editor] ([[VE/Contributing|Contributor Ref.]])<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] || pombreda || [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=VE&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/attachment.cgi?id=78346 Link] ||<br />
|-<br />
| [http://www.eclipse.org/atf Ajax and JavaScript Web tools]<br />
|| [mailto:philippe.ombredanne@eclipse.org Philippe Ombredanne] <br/> Robert Goodman <br/> Javier Pedemonte<br />
|| pombreda <br/> Robert_Goodman <br/> jhpedemonte<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=ATF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| [http://wiki.eclipse.org/images/8/89/Atf-psf.zip Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-ui Platform UI] ([[Platform_UI/How_to_Contribute|How to Contribute]])<br />
|| [mailto:Boris_Bokowski@ca.ibm.com Boris Bokowski]<br />
|| blupin<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?bug_file_loc=&bug_file_loc_type=allwordssubstr&bug_id=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bugidtype=include&chfieldfrom=&chfieldto=Now&chfieldvalue=&classification=Eclipse&component=IDE&component=UI&email1=&email2=&emailtype1=substring&emailtype2=substring&field-1-0-0=classification&field-1-1-0=product&field-1-2-0=component&field-1-3-0=bug_status&field-1-4-0=keywords&field0-0-0=noop&keywords=bugday&keywords_type=allwords&long_desc=&long_desc_type=allwordssubstr&product=Platform&query_format=advanced&remaction=&short_desc=&short_desc_type=allwordssubstr&status_whiteboard=&status_whiteboard_type=allwordssubstr&type-1-0-0=anyexact&type-1-1-0=anyexact&type-1-2-0=anyexact&type-1-3-0=anyexact&type-1-4-0=allwords&type0-0-0=noop&value-1-0-0=Eclipse&value-1-1-0=Platform&value-1-2-0=IDE%2CUI&value-1-3-0=NEW%2CASSIGNED%2CREOPENED&value-1-4-0=bugday&value0-0-0=&votes=&order=bugs.bug_id&query_based_on= Link]<br />
|| [http://www.eclipse.org/eclipse/platform-ui/psf/ Link] ||<br />
|-<br />
| [http://www.eclipse.org/eclipse/platform-releng Platform Releng] <br />
|| [mailto:Kim_Moir@ca.ibm.com Kim Moir]<br />
|| k2moir<br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Releng&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| ||<br />
|-<br />
| [http://wiki.eclipse.org/Workspace_Team Platform Workspace]<br />
|| [mailto:Szymon.Brandys@pl.ibm.com Szymon Brandys] <br/> [mailto:Tomasz.Zarna@pl.ibm.com Tomasz Zarna]<br />
|| SzymonB <br/> z4z4<br />
|| [[Workspace_Bugs|Link]]<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Eclipse&product=Platform&component=Compare&component=CVS&component=Resources&component=Team&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| [[Workspace_Development#Project_Set_Files_for_Platform_Workspace|Link]]<br />
|| [http://wiki.eclipse.org/images/3/3d/Eclipse_Workspace_BugDay.xml.zip Link]<br />
|-<br />
| [http://www.eclipse.org/gef/ GEF]<br />
|| [mailto:anthonyh@ca.ibm.com Anthony Hunter]<br />
|| <br />
|| N/A<br />
|| [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=GEF&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Link]<br />
|| N/A<br />
|| <br />
|}<br />
<br />
<br />
<br />
[http://eclipse.org/mylyn/ Mylyn Query] you can save and import into the Task List view to have up to date list of BugDay bugs<br />
<br />
=== Participants ===<br />
<br />
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=2007-10-06&chfieldto=2007-11-02&chfield=bug_status&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Bugs Fixed]<br />
<br />
{| border="1" align="center" cellpadding="3" cellspacing="1"<br />
! Name !! Bug(s) || Project<br />
|-<br />
| [mailto:d_a_carver@yahoo.com David Carver] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209356 209356], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130007 130007] || Webtools<br />
|-<br />
| [mailto:davidk@kelman.com David Kyle] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155704 155704] || Platform Workspace<br />
|-<br />
| [mailto:zx@us.ibm.com Chris Aniszczyk] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209572 209572] || Mylyn<br />
|-<br />
| [mailto:joern@dinkla.net Joern Dinkla] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=210264 210264], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=209941 209941] || PDE <br />
|-<br />
| [mailto:benjamin.cabe@anyware-tech.com Benjamin Cabé] || [https://bugs.eclipse.org/bugs/show_bug.cgi?id=211580 211580] || PDE <br />
|}<br />
<br />
[[Category:Bug Day]]</div>Benjamin.cabe.anyware-tech.com