https://wiki.eclipse.org/api.php?action=feedcontributions&user=Techtonik.php.net&feedformat=atomEclipsepedia - User contributions [en]2024-03-28T20:03:42ZUser contributionsMediaWiki 1.26.4https://wiki.eclipse.org/index.php?title=Skype_Provider&diff=239155Skype Provider2011-02-17T14:31:33Z<p>Techtonik.php.net: add ECF category</p>
<hr />
<div>==Skype Provider==<br />
<br />
The Skype Provider now implements the ECF [[ECF_Providers#Call_.28org.eclipse.ecf.call.29|Call API]], the [[ECF_API_Docs#Presence_API|Presence API]], and the [[ECF_API_Docs#Datashare_API|Datashare API]]. <br />
<br />
You can install the plugin via the [http://github.com/ECF ECF OSU OSL Web Page]. It's currently working for win32 at the moment...we are working on getting the macosx and linux fragments going properly and need access to mac and linux boxes for testing. Please [mailto:ecf-dev@eclipse.org email us] if you would like to help.<br />
<br />
==Source Code==<br />
<br />
Here is a project set file to get read access to the Skype provider bundle projects. This currently only include the Windows native code fragment, but we are working on Mac OSX, and Linux fragments. Save the following to a local file (e.g. ecf_skype.psf), and them within Eclipse choose File->Import...->Team Project Set->Browse... and choose the file saved. When prompted for username/password give username->anonymous, password-><leave empty><br />
<br />
Note. You will need the ECF core plugins to build/compile the plugins included below. Get the core plugins <br />
[http://www.eclipse.org/ecf/dev_resources.php here]<br />
<br />
<source lang="xml"><br />
<?xml version="1.0" encoding="UTF-8"?><br />
<psf version="2.0"><br />
<provider id="org.eclipse.team.cvs.core.cvsnature"><br />
<project reference="1.0,:pserver:cvs.sourceforge.jp:/cvsroot/skype,eclipse/plugins/com.skype,com.skype"/><br />
<project reference="1.0,:pserver:cvs.sourceforge.jp:/cvsroot/skype,eclipse/plugins/com.skype.linux.x86,com.skype.linux.x86"/><br />
<project reference="1.0,:pserver:cvs.sourceforge.jp:/cvsroot/skype,eclipse/plugins/com.skype.win32.win32.x86,com.skype.win32.win32.x86"/><br />
<project reference="1.0,:pserver:ecf1.osuosl.org:/ecf,plugins/org.eclipse.ecf.provider.skype,org.eclipse.ecf.provider.skype"/><br />
<project reference="1.0,:pserver:ecf1.osuosl.org:/ecf,plugins/org.eclipse.ecf.provider.skype.ui,org.eclipse.ecf.provider.skype.ui"/><br />
</provider><br />
</psf><br />
</source><br />
<br />
==Screen Shots==<br />
<br />
===Connecting to Skype (assumes Skype already running)===<br />
[[Image:Skype1.png]]<br />
<br />
===Permission Dialog===<br />
[[Image:Skype2.png]]<br />
<br />
===Connect Wizard===<br />
[[Image:Skype3.png]]<br />
<br />
===Buddy List Info===<br />
[[Image:Skype4.png]]<br />
<br />
===Calling Users with Context Menu===<br />
[[Image:Skype5.png]]<br />
<br />
===Starting IM/Chat===<br />
[[Image:Skype6.png]]<br />
<br />
===Sending/Receiving IM===<br />
[[Image:Skype7.png]]<br />
<br />
[[Category:Eclipse Communication Framework]]<br />
[[Category:ECF]]</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=ECF/DocShare_Plugin&diff=239154ECF/DocShare Plugin2011-02-17T14:28:49Z<p>Techtonik.php.net: /* Requirements */ fix link to Skype provider</p>
<hr />
<div>ECF version 2.0.0 and up includes a plugin called DocShare ('''org.eclipse.ecf.docshare''') that implements real-time shared editing.<br />
<br />
=Requirements=<br />
<br />
*[http://www.eclipse.org/ecf/downloads.php ECF 2.0.0]. ECF 2.0.0 will run on either Eclipse 3.3 and/or Eclipse 3.4. For Eclipse 3.5, use ECF 3.1.<br />
*Connect via a supported provider that supports the [[ECF_API_Docs#Datashare_API | ECF Datashare API]]. Supported providers are: XMPP (Google Talk, Jabber), Skype (found [[SkypeProvider | here]]). Instructions for connecting are [http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.ecf.doc/html/gettingstarted/quickStart.html here].<br />
*You must also have a contact currently also connected to your supported provider.<br />
<br />
=How to Use=<br />
<br />
*Open a TextEditor on a text resource from your workspace (e.g. a .java file, or .txt file).<br />
*Open the Context Menu (right click) on the text editor, and you should see a context menu like this<br />
<br />
[[Image:docshareslewis2.png]]<br />
<br />
*Select the target user to share your editor session with. Note that if you select a target user that is not running ECF client, it will have no effect and the target user will not see a notification. In the near future (ECF 2.0.1), only the users that support/are running docshare will appear in this list, but for now all contacts will appear.<br />
<br />
Once the receiver accepts the docshare, both participants may edit the document via their local editor and the changes will be immediately distributed to the other participant via ECF.<br />
<br />
===How to Stop===<br />
<br />
*Open the context menu for the editor being shared.<br />
*Select "Stop Sharing Editor with ..."<br />
<br />
=Screen Shots=<br />
<br />
'slewis' client (the initiator), before starting editor sharing<br />
<br />
[[Image:docshareslewis1.png]]<br />
<br />
'fliwatuet' client (the receiver), before starting editor sharing<br />
<br />
[[Image:docsharefliwatuet1.png]]<br />
<br />
Slewis initiates the real-time shared editing by opening the context menu in the editor, and choosing '''Share Editor With -> slewis@ecf.eclipse.org ->ECF -> fliwatuet@ecf.eclipse.org'''<br />
<br />
[[Image:docshareslewis2.png]]<br />
<br />
Fliwatuet receives a notice and can accept or reject the shared editing session<br />
<br />
[[Image:docsharefliwatuet2.png]]<br />
<br />
If fliwatuet accepts, the editor is opened with slewis' current editor content on fliwatuet's workbench<br />
<br />
[[Image:docsharefliwatuet3.png]]<br />
<br />
At this point, both participants can edit the text and updates will be immediately distributed and shown on the other's corresponding editor.<br />
<br />
So, for example, here fliwatuet enters a new method (baz)<br />
<br />
[[Image:docsharefliwatuet4.png]]<br />
<br />
These same updates appear immediately on slewis' workbench. Slewis can also make changes and these are reflected on fliwatuet's workbench.<br />
<br />
[[Image:docshareslewis3.png]]<br />
<br />
=Technical Info and Source Code=<br />
<br />
DocShare detects conflicts and resolves them using an algorithm and implementation called 'Cola'. That work is described in [[RT_Shared_Editing|Real-Time Shared Editing]].<br />
<br />
The source code for docshare can be browsed by clicking [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.ecf/plugins/org.eclipse.ecf.docshare/?root=Technology_Project here].<br />
<br />
To work with the source code for DocShare and/or all of ECF, see [http://www.eclipse.org/ecf/dev_resources.php here].<br />
<br />
{{ECF}}<br />
<br />
[[Category:Eclipse Communication Framework]]<br />
[[Category:ECF]]<br />
[[Category:Draft Documentation]]</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=DLTK&diff=219974DLTK2010-09-14T21:11:51Z<p>Techtonik.php.net: move 1.0 planning section under 'get involved'</p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
Welcome to our Wiki. This is the Wiki home page for the '''Dynamic Languages Toolkit project''', an Eclipse Technology sub project.<br />
<br />
Dynamic Languages Toolkit (DLTK) is a tool for vendors, researchers, and end-users who rely on dynamic languages. DLTK is comprised of a set of extensible frameworks designed to reduce the complexity of building full featured development environments for dynamic languages such as PHP and Perl. Besides a set of frameworks DLTK provides exemplary Tcl, Ruby, and Python development environments ready to use out of the box.<br />
<br />
While the main DLTK [http://www.eclipse.org/dltk website] contains the bulk of information regarding the project, the type of information more appropriately hosted on a wiki is (or will be) found here, such as: FAQs, tutorials, requirements, discussions, etc.<br />
<br />
{| border="0" cellspacing="15" valign="top" style="width:100%;"<br />
<br />
|-valign="top"<br />
|style="width:50%;"|<br />
<h1>User Resources</h1><br />
*'''[[DLTK Installation]]''' - DLTK versions and installation instuctions<br />
*'''[[DLTK Validators User Guide]]''' - Using DLTK validators - external tools to perform code analysis tasks<br />
*'''[[DLTK Based Projects|Products and Projects built on DLTK]]''' - list of products and projects built on top of DLTK.<br />
*'''[[DLTK Ruby RemoteDebugger]]''' - How to start remote ruby debugger<br />
|<br />
<h1>Developer Resources</h1><br />
*'''[[DLTK CVS Checkout information]]''' - Checking out DLTK sources information<br />
*'''[[DLTK Mini-HOWTO|Mini-HOWTO]]''' - Minimalistic HOWTO answering common questions from IDE implementers <br />
*'''[[DLTK Core Architecture|Core Architecture]]'''<br />
*'''[[A guide to building a DLTK-based language IDE|Guide to build IDE]]''' - Detailed guilde to build DLTK-based Python IDE<br />
*'''[[Remote API Migration guide]]''' - Migration guilde to build DLTK-based IDEs compatible with RSE Remote projects<br />
*'''[[DLTK Mini Tutorials|Mini Tutorials]]''' - Here you will find a series of mini tutorials for adding functionality to a DLTK project<br />
*'''[[DLTK Project Builders]]''' - APIs related to building the project in DLTK<br />
|-valign="top" <br />
|style="width:50%;"|<br />
<h1>Get Involved</h1><br />
*'''[[DLTK 0.9 Project Plan]]''' - released in Summer 2007, and a part of [[Europa]]<br />
*'''[[DLTK 0.95 Project Plan]]''' - released in Summer 2008, and a part of [[Ganymede]]<br />
*'''[[DLTK 1.0 Planning]]''' - released in Summer 2009 as a part of [[Galileo]]<br />
*'''[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=DLTK&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED Active DLTK Bugs]''' - review and create Bugzilla entries<br />
|<br />
<h1>Project Components</h1><br />
*'''[[DLTK_TCL|DLTK's TCL IDE Component]]''' - DLTK's TCL IDE Component<br />
|}<br />
<br />
<br />
[[Category:DLTK]]<br />
[[Category:Eclipse Technology Project]]</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=DLTK_Installation&diff=219969DLTK Installation2010-09-14T21:05:05Z<p>Techtonik.php.net: /* Requirements */ update for 2.0</p>
<hr />
<div>{{incubation}}<br />
<br />
== Requirements ==<br />
<br />
[[DLTK|Dynamic Languages Toolkit]] 2.0 requires [http://www.eclipse.org/platform Eclipse Platform] 3.5 or later. Optional DLTK components like [http://www.eclipse.org/mylyn Mylyn] integration or remote development with [http://www.eclipse.org/dsdp/tm DSDP TM] component may enforce additional requirements. Please check requirements section on download pages.<br />
<br />
==Installing DLTK==<br />
<br />
DLTK 1.0 was a part of [http://www.eclipse.org/galileo/ Eclipse Galileo] annual release. Latest DLTK 2.0 is a part of [http://www.eclipse.org/helios/ Eclipse Helios].<br />
<br />
DLTK can be downloaded from the [http://download.eclipse.org/technology/dltk/downloads/ DLTK Downloads page], or with Eclipse Update Manager using Dynamic Languages Toolkit Update Site: [http://download.eclipse.org/technology/dltk/updates http://download.eclipse.org/technology/dltk/updates] ('''Releases only'''). <br />
<br />
[[Category:DLTK]]</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=DLTK_Installation&diff=219968DLTK Installation2010-09-14T21:03:48Z<p>Techtonik.php.net: /* Installing DLTK */ update to helios</p>
<hr />
<div>{{incubation}}<br />
<br />
== Requirements ==<br />
<br />
[[DLTK|Dynamic Languages Toolkit]] 1.0 require [http://www.eclipse.org/platform Eclipse Platform] 3.4 or later. Optional DLTK components like [http://www.eclipse.org/mylyn Mylyn] integration component or remote development with [http://www.eclipse.org/dsdp/tm DSDP TM] component may enforce additional requirements. Please check requirements section on download pages.<br />
<br />
==Installing DLTK==<br />
<br />
DLTK 1.0 was a part of [http://www.eclipse.org/galileo/ Eclipse Galileo] annual release. Latest DLTK 2.0 is a part of [http://www.eclipse.org/helios/ Eclipse Helios].<br />
<br />
DLTK can be downloaded from the [http://download.eclipse.org/technology/dltk/downloads/ DLTK Downloads page], or with Eclipse Update Manager using Dynamic Languages Toolkit Update Site: [http://download.eclipse.org/technology/dltk/updates http://download.eclipse.org/technology/dltk/updates] ('''Releases only'''). <br />
<br />
[[Category:DLTK]]</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=DLTK&diff=199775DLTK2010-05-07T21:27:25Z<p>Techtonik.php.net: 0.95 released long ago</p>
<hr />
<div>__NOTOC__<br />
__NOEDITSECTION__<br />
<br />
Welcome to our Wiki. This is the Wiki home page for the '''Dynamic Languages Toolkit project''', an Eclipse Technology sub project.<br />
<br />
Dynamic Languages Toolkit (DLTK) is a tool for vendors, researchers, and end-users who rely on dynamic languages. DLTK is comprised of a set of extensible frameworks designed to reduce the complexity of building full featured development environments for dynamic languages such as PHP and Perl. Besides a set of frameworks DLTK provides exemplary Tcl, Ruby, and Python development environments ready to use out of the box.<br />
<br />
While the main DLTK [http://www.eclipse.org/dltk website] contains the bulk of information regarding the project, the type of information more appropriately hosted on a wiki is (or will be) found here, such as: FAQs, tutorials, requirements, discussions, etc.<br />
<br />
{| border="0" cellspacing="15" valign="top" style="width:100%;"<br />
<br />
|-valign="top"<br />
|style="width:50%;"|<br />
<h1>User Resources</h1><br />
*'''[[DLTK Installation]]''' - DLTK versions and installation instuctions<br />
*'''[[DLTK Validators User Guide]]''' - Using DLTK validators - external tools to perform code analysis tasks<br />
*'''[[DLTK Based Projects|Products and Projects built on DLTK]]''' - list of products and projects built on top of DLTK.<br />
*'''[[DLTK Ruby RemoteDebugger]]''' - How to start remote ruby debugger<br />
|<br />
<h1>Developer Resources</h1><br />
*'''[[DLTK CVS Checkout information]]''' - Checking out DLTK sources information<br />
*'''[[DLTK 1.0 Planning|1.0 Planning]]''' - Planning DLTK 1.0 <br />
*'''[[DLTK Mini-HOWTO|Mini-HOWTO]]''' - Minimalistic HOWTO answering common questions from IDE implementers <br />
*'''[[DLTK Core Architecture|Core Architecture]]'''<br />
*'''[[A guide to building a DLTK-based language IDE|Guide to build IDE]]''' - Detailed guilde to build DLTK-based Python IDE<br />
*'''[[Remote API Migration guide]]''' - Migration guilde to build DLTK-based IDEs compatible with RSE Remote projects<br />
*'''[[DLTK Mini Tutorials|Mini Tutorials]]''' - Here you will find a series of mini tutorials for adding functionality to a DLTK project<br />
*'''[[DLTK Project Builders]]''' - APIs related to building the project in DLTK<br />
|-valign="top" <br />
|style="width:50%;"|<br />
<h1>Get Involved</h1><br />
*'''[[DLTK 0.9 Project Plan]]''' - released in Summer 2007, and a part of [[Europa]]<br />
*'''[[DLTK 0.95 Project Plan]]''' - released in Summer 2008, and a part of [[Ganymede]]<br />
*'''[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&product=DLTK&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED Active DLTK Bugs]''' - review and create Bugzilla entries<br />
|<br />
<h1>Project Components</h1><br />
*'''[[DLTK_TCL|DLTK's TCL IDE Component]]''' - DLTK's TCL IDE Component<br />
|}<br />
<br />
<br />
[[Category:DLTK]]<br />
[[Category:Eclipse Technology Project]]</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=DLTK_Installation&diff=199774DLTK Installation2010-05-07T21:23:42Z<p>Techtonik.php.net: /* Installing DLTK */ update to 1.0 / 2.0</p>
<hr />
<div>{{incubation}}<br />
<br />
== Requirements ==<br />
<br />
[[DLTK|Dynamic Languages Toolkit]] 1.0 require [http://www.eclipse.org/platform Eclipse Platform] 3.4 or later. Optional DLTK components like [http://www.eclipse.org/mylyn Mylyn] integration component or remote development with [http://www.eclipse.org/dsdp/tm DSDP TM] component may enforce additional requirements. Please check requirements section on download pages.<br />
<br />
==Installing DLTK==<br />
<br />
DLTK 1.0 is a part of [http://www.eclipse.org/galileo/ Eclipse Galileo] annual release. DLTK 2.0 is going to be a part of [http://www.eclipse.org/helios/ Helios Release Train], so DLTK may be installed with simultaneous release installation process.<br />
<br />
You may download DLTK from the [http://download.eclipse.org/technology/dltk/downloads/ DLTK Downloads page], or use Eclipse Update Manager with Dynamic Languages Toolkit Update Site: [http://download.eclipse.org/technology/dltk/updates http://download.eclipse.org/technology/dltk/updates] ('''Releases only'''). <br />
<br />
[[Category:DLTK]]</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=DLTK_Installation&diff=199773DLTK Installation2010-05-07T21:16:32Z<p>Techtonik.php.net: /* Requirements */ update for 1.0</p>
<hr />
<div>{{incubation}}<br />
<br />
== Requirements ==<br />
<br />
[[DLTK|Dynamic Languages Toolkit]] 1.0 require [http://www.eclipse.org/platform Eclipse Platform] 3.4 or later. Optional DLTK components like [http://www.eclipse.org/mylyn Mylyn] integration component or remote development with [http://www.eclipse.org/dsdp/tm DSDP TM] component may enforce additional requirements. Please check requirements section on download pages.<br />
<br />
==Installing DLTK==<br />
<br />
DLTK 0.9 is a part of [http://www.eclipse.org/europa/ Eclipse Europa] annual release. DLTK 0.95 is going to be a part of [http://www.eclipse.org/ganymede/ Ganymede Release Train], so DLTK may be installed with simultaneous release installation process.<br />
<br />
You may download DLTK from the [http://download.eclipse.org/technology/dltk/downloads/ DLTK Downloads page], or use Eclipse Update Manager with Dynamic Languages Toolkit Update Site: [http://download.eclipse.org/technology/dltk/updates http://download.eclipse.org/technology/dltk/updates] ('''Releases only'''). <br />
<br />
[[Category:DLTK]]</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=Eclipse_Monkey/1.0_Project_Plan&diff=118807Eclipse Monkey/1.0 Project Plan2008-09-17T12:37:40Z<p>Techtonik.php.net: fix project termination link</p>
<hr />
<div><div style="border: thin solid orange; width: 60%">The Eclipse Monkey component of the Dash Project has been archived [http://www.eclipse.org/project-slides/2008.08.13%20Monkey%20Termination%20Review.pdf]. <br>Thus this page is no longer active.</div><br />
<br />
(obsolete; removing)</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=Eclipse_Monkey/Javascript_Editor&diff=118806Eclipse Monkey/Javascript Editor2008-09-17T12:35:53Z<p>Techtonik.php.net: fix project termination link</p>
<hr />
<div><div style="border: thin solid orange; width: 60%">The Eclipse Monkey component of the Dash Project has been archived [http://www.eclipse.org/project-slides/2008.08.13%20Monkey%20Termination%20Review.pdf]. <br>Thus this page is no longer active.</div><br />
<br />
This page covers the org.eclipse.eclipsemonkey.lang.javascript.doms.editors.Editor class, which is what you get from this line:<br />
:var sourceEditor = editors.activeEditor;<br />
<br />
This documentation was written for version ???<br />
<br />
===Properties:===<br />
====Read-only:====<br />
*id: ?<br />
*lineDelimiter: the correct End of Line characters for the current file?<br />
*source: the current contents of the editor, as a Java String.<br />
*sourceLength: the length of the current contents of the editor.<br />
*selectionRange: the range of text that is currently selected in the editor. It contains two integers, startingOffset and endingOffset. These may be used to find the selected text within the source property. If nothing is selected endingOffset == startingOffset.<br />
*title: ?<br />
*textEditor: ?<br />
<br />
====Read/write:====<br />
*currentOffset: ?<br />
<br />
===Functions:===<br />
*applyEdit(int offset, int deleteLength, String insertText): Used to insert and/or delete text. <code>offset</code> is a position within the source property. <code>deleteLength</code> is the length of the existing text to remove; use 0 to not delete anything. <code>insertText</code> is text to insert at offset; use "" to not insert anything.<br />
*beginCompoundChange(): ?<br />
*close(boolean save): close the current editor, saving its contents if save == true?<br />
*endCompoundChange(): ?<br />
*getLineAtOffset(int offset): returns the number of the line that contains <code>offset</code>.<br />
*getOffsetAtLine(final int line): returns the offset of the first character in line <code>line</code>.<br />
*save(): saves the current contents of the editor?<br />
*selectAndReveal(final int offset, final int length): selects the text starting at <code>offset</code> and ending at <code>(offset + length)</code>. Will scroll the text as needed to make the selection visible on screen. <code>length</code> may be 0 to force a line to be visible without selecting anything.<br />
*toString(): returns "[object Editor]"<br />
<br />
[[Category:Dash Project]] [[Category:Eclipse Monkey Project]]</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=Eclipse_Monkey&diff=118805Eclipse Monkey2008-09-17T12:33:59Z<p>Techtonik.php.net: fix project termination link</p>
<hr />
<div><div style="border: thin solid orange; width: 60%">The Eclipse Monkey component of the Dash Project has been archived [http://www.eclipse.org/project-slides/2008.08.13%20Monkey%20Termination%20Review.pdf]. <br>Thus this page is no longer active.</div></div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=Eclipse_Monkey/Overview&diff=118803Eclipse Monkey/Overview2008-09-17T12:31:13Z<p>Techtonik.php.net: fix project termination link</p>
<hr />
<div><div style="border: thin solid orange; width: 60%">The Eclipse Monkey component of the Dash Project has been archived [http://www.eclipse.org/project-slides/2008.08.13%20Monkey%20Termination%20Review.pdf]. <br>Thus this page is no longer active.</div><br />
<br />
==Eclipse Monkey Overview==<br />
<br />
Eclipse Monkey allows you to write scripts that run inside Eclipse and through DOMs are able to access and control(script) parts of the Eclipse Platform.<br />
<br />
===Eclipse Monkey Help===<br />
<br />
[http://www.eclipse.org/dash/monkey-help.php Monkey Help]<br />
<br />
===Getting the Source===<br />
<br />
The [http://www.eclipse.org/dash/monkey-help.php?key=source-code recommended method] is to use Buckminster.<br />
<br />
If that doesn't work you can get the code with anonymous CVS:<br />
<br />
# Define a new cvs location: pserver:anonymous@dev.eclipse.org:/cvsroot/technology<br />
# Checkout all projects from org.eclipse.dash folder into your workspace. Make sure you checkout projects beneath org.eclipse.dash, not the org.eclipse.dash folder itself.<br />
<br />
===Documentation===<br />
<br />
[http://www.eclipse.org/dash/monkey-help.php Monkey Help] covers the basics of running and writing scripts.<br />
<br />
Basic interaction with the Eclipse editor can be done using the built in DOM. The main component is the [[Eclipse Monkey/Javascript Editor | Editor]].<br />
<br />
===Eclipse Monkey Script Exchange===<br />
<br />
[http://monkey.brain-bakery.com/entry/list Eclipse Monkey Exchange] Site to share Eclipse Monkey scripts. (unavailable from time to time because of temporary ISP problems)<br />
<br />
[http://eclipse.dzone.com/news/introduction-scripting-eclipse Eclipse Monkey Scripting] Introduction to Eclipse Monkey script writing.<br />
<br />
===Eclipse Monkey Plugins===<br />
<br />
[http://code.google.com/p/jrfonseca/wiki/PythonMonkey PythonMonkey] PythonMonkey plugin to support Python Language.<br />
<br />
[http://groovy.codehaus.org/Groovy+Monkey GroovyMonkey] GroovyMonkey plugin to support Groovy Language.<br />
<br />
[http://muellerware.org/projects/em-sl/ ScriptLoader] An Eclipse Monkey DOM plugin to load other scripts, called Script Loader.<br />
<br />
[[Category:Dash_Project]] [[Category:Eclipse Monkey Project]]</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=Mylyn/SOC/2006/Trac_Connector&diff=49369Mylyn/SOC/2006/Trac Connector2007-09-06T09:35:50Z<p>Techtonik.php.net: /* Source */</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
The goal of this [http://code.google.com/soc/ Google Summer of Code] project is to provide a [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140512 Trac connector plug-in for Mylyn]. [http://trac.edgewall.com/ Trac] is a web-based issue tracking system with an integrated wiki.<br />
<br />
The Mylyn API already supports multiple issue tracking systems, therefore the existing abstraction is used to implement a Trac connector. Trac issues are accessed remotely through a query script that outputs tab-delimited text as well as through a [http://trac-hacks.org/wiki/XmlRpcPlugin XML-RPC interface]. The XML-RPC interface has not yet been integrated into the main distribution of Trac but is available as a separate plug-in.<br />
<br />
The project has been accomplished in two iterations. The goal of the first iteration was to make the connector work with existing Trac deployments through Trac's web interface. This retrieved ticket information is used for read-only display in Mylar. Tickets can be edited through a web-browser.<br />
<br />
The second iteration focused on enhancing the support for Trac's XML-RPC interface. The XML-RPC interface allows full featured access to all ticket information and allows manipulation of tickets. The editing of tickets is done through Eclipse forms based editor.<br />
<br />
The Trac connector is now maintained in the Mylyn CVS and is shipped with the regular releases.<br />
<br />
== ChangeLog ==<br />
<br />
=== '''M1 (completed):''' ''Web linking only repository integration ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=146334 #148378])'' ===<br />
<br />
* Create and edit Trac repositories ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147817 #147817], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=148378 #148378])<br />
** Templates for common repository locations ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150677 #150677])<br />
* Data model for repository access ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147816 #147816])<br />
** Access through Trac's query script ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=148090 #148090])<br />
** Access through the Trac XML-RPC plug-in ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=148089 #148089])<br />
* Create new tasks through web-browser ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150699 #150699])<br />
* Add exiting tasks to task list ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149385 #149385])<br />
* Query repository in task list view through Bugzilla like query dialog ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149386 #149386])<br />
<br />
This milestone is available as part of the Mylar 0.6.1 release.<br />
<br />
=== '''M2 (completed):''' ''Full integration based on the Trac XML-RPC plug-in'' ===<br />
<br />
* Digest authentication ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=151077 #151077])<br />
* Handle trailing slashes in repository urls ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150890 #150890])''<br />
* Update repository attributes from task repository context menu ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=152325 #152325])<br />
* Unescape HTML entities when updating repository attributes ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=153496 #153496], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154098 #154098])<br />
* Query repositories from Eclipse search ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=153539 #153539], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154772 #154772])<br />
* Remember repository attributes ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150670 #150670])<br />
* Update repository attributes when query dialog is opened ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154347 #154347])<br />
* Attachment support and context uploading and retrieving ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=151900 #151900], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154441 #154441], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154372 #154372])<br />
* Change query urls accordingly when repository url is changed ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154798 #154798])<br />
* Authoring of reports within native Eclipse editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=151899 #151899], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=146334 #146334], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154377 #154377], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154962 #154962])<br />
* Fixed notifications for Trac task ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154379 #154379]<br />
* Check revision of XML-RPC Plugin ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154931 #154931])<br />
* Properly check for Trac repository during validation ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154464 #154464])<br />
<br />
This milestone is available as part of the Mylar 0.6.2 release.<br />
<br />
=== '''Future planning''' ===<br />
<br />
Please refer to the [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=Mylar&component=Trac&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= Eclipse Bugzilla] for bug reports and feature requests.<br />
<br />
== Download ==<br />
<br />
Please refer to the [http://www.eclipse.org/mylyn/downloads/ Mylyn download page].<br />
<br />
== Source ==<br />
<br />
Please refer to the [[Mylar Contributor Reference]] for information about how to obtain and build Mylyn and its connectors.<br />
<br />
The source is available in the Mylyn CVS:<br />
<br />
[http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/?root=Tools_Project http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/?root=Tools_Project]<br />
<br />
Plug-ins:<br />
<br />
* [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/org.eclipse.mylyn.trac.core/?root=Tools_Project org.eclipse.mylyn.trac.core]<br />
* [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/org.eclipse.mylyn.trac-feature/?root=Tools_Project org.eclipse.mylyn.trac-feature]<br />
* [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/org.eclipse.mylyn.trac.tests/?root=Tools_Project org.eclipse.mylyn.trac.tests]<br />
* [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/org.eclipse.mylyn.trac.ui/?root=Tools_Project org.eclipse.mylyn.trac.ui]<br />
<br />
Project Team Set:<br />
<br />
* [http://www.eclipse.org/mylyn/doc/dev/projects-trac.psf http://www.eclipse.org/mylyn/doc/dev/projects-trac.psf]<br />
<br />
== Architecture ==<br />
<br />
* Core and Model: Provides Java abstraction for repository access<br />
** Abstraction for query script and XML-RPC access<br />
** (Eclipse independent) model classes that represent Trac data<br />
* UI: Tasklist classes<br />
* Tests: Tests for Core and UI<br />
<br />
For the XML-RPC calls [http://ws.apache.org/xmlrpc/ Apache XML-RPC] is used.</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=Mylyn/SOC/2006/Trac_Connector&diff=49368Mylyn/SOC/2006/Trac Connector2007-09-06T09:31:01Z<p>Techtonik.php.net: /* Source */ -fix VieVC links</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
The goal of this [http://code.google.com/soc/ Google Summer of Code] project is to provide a [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140512 Trac connector plug-in for Mylyn]. [http://trac.edgewall.com/ Trac] is a web-based issue tracking system with an integrated wiki.<br />
<br />
The Mylyn API already supports multiple issue tracking systems, therefore the existing abstraction is used to implement a Trac connector. Trac issues are accessed remotely through a query script that outputs tab-delimited text as well as through a [http://trac-hacks.org/wiki/XmlRpcPlugin XML-RPC interface]. The XML-RPC interface has not yet been integrated into the main distribution of Trac but is available as a separate plug-in.<br />
<br />
The project has been accomplished in two iterations. The goal of the first iteration was to make the connector work with existing Trac deployments through Trac's web interface. This retrieved ticket information is used for read-only display in Mylar. Tickets can be edited through a web-browser.<br />
<br />
The second iteration focused on enhancing the support for Trac's XML-RPC interface. The XML-RPC interface allows full featured access to all ticket information and allows manipulation of tickets. The editing of tickets is done through Eclipse forms based editor.<br />
<br />
The Trac connector is now maintained in the Mylyn CVS and is shipped with the regular releases.<br />
<br />
== ChangeLog ==<br />
<br />
=== '''M1 (completed):''' ''Web linking only repository integration ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=146334 #148378])'' ===<br />
<br />
* Create and edit Trac repositories ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147817 #147817], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=148378 #148378])<br />
** Templates for common repository locations ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150677 #150677])<br />
* Data model for repository access ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147816 #147816])<br />
** Access through Trac's query script ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=148090 #148090])<br />
** Access through the Trac XML-RPC plug-in ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=148089 #148089])<br />
* Create new tasks through web-browser ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150699 #150699])<br />
* Add exiting tasks to task list ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149385 #149385])<br />
* Query repository in task list view through Bugzilla like query dialog ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149386 #149386])<br />
<br />
This milestone is available as part of the Mylar 0.6.1 release.<br />
<br />
=== '''M2 (completed):''' ''Full integration based on the Trac XML-RPC plug-in'' ===<br />
<br />
* Digest authentication ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=151077 #151077])<br />
* Handle trailing slashes in repository urls ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150890 #150890])''<br />
* Update repository attributes from task repository context menu ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=152325 #152325])<br />
* Unescape HTML entities when updating repository attributes ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=153496 #153496], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154098 #154098])<br />
* Query repositories from Eclipse search ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=153539 #153539], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154772 #154772])<br />
* Remember repository attributes ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150670 #150670])<br />
* Update repository attributes when query dialog is opened ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154347 #154347])<br />
* Attachment support and context uploading and retrieving ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=151900 #151900], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154441 #154441], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154372 #154372])<br />
* Change query urls accordingly when repository url is changed ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154798 #154798])<br />
* Authoring of reports within native Eclipse editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=151899 #151899], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=146334 #146334], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154377 #154377], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154962 #154962])<br />
* Fixed notifications for Trac task ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154379 #154379]<br />
* Check revision of XML-RPC Plugin ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154931 #154931])<br />
* Properly check for Trac repository during validation ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154464 #154464])<br />
<br />
This milestone is available as part of the Mylar 0.6.2 release.<br />
<br />
=== '''Future planning''' ===<br />
<br />
Please refer to the [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=Mylar&component=Trac&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= Eclipse Bugzilla] for bug reports and feature requests.<br />
<br />
== Download ==<br />
<br />
Please refer to the [http://www.eclipse.org/mylyn/downloads/ Mylyn download page].<br />
<br />
== Source ==<br />
<br />
Please refer to the [[Mylar Contributor Reference]] for information about how to obtain and build Mylyn and its connectors.<br />
<br />
The source is available in the Mylyn CVS:<br />
<br />
[http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/?root=Tools_Project http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/?root=Tools_Project]<br />
<br />
Plug-ins:<br />
<br />
* [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/org.eclipse.mylyn.trac.ui/?root=Tools_Project org.eclipse.mylyn.trac.core]<br />
* [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/org.eclipse.mylyn.trac-feature/?root=Tools_Project org.eclipse.mylyn.trac-feature]<br />
* [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/org.eclipse.mylyn.trac.tests/?root=Tools_Project org.eclipse.mylyn.trac.tests]<br />
* [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/org.eclipse.mylyn.trac.ui/?root=Tools_Project org.eclipse.mylyn.trac.ui]<br />
<br />
Project Team Set:<br />
<br />
* [http://www.eclipse.org/mylar/doc/dev/projects-trac.psf http://www.eclipse.org/mylar/doc/dev/projects-trac.psf]<br />
<br />
== Architecture ==<br />
<br />
* Core and Model: Provides Java abstraction for repository access<br />
** Abstraction for query script and XML-RPC access<br />
** (Eclipse independent) model classes that represent Trac data<br />
* UI: Tasklist classes<br />
* Tests: Tests for Core and UI<br />
<br />
For the XML-RPC calls [http://ws.apache.org/xmlrpc/ Apache XML-RPC] is used.</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=Mylyn/Contributor_Reference&diff=49367Mylyn/Contributor Reference2007-09-06T09:24:53Z<p>Techtonik.php.net: + ViewVC to see also</p>
<hr />
<div>[[Category:Mylyn]] <br />
See also: [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&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= helpwanted bugs], <br />
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&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= discussion bugs], <br />
[http://www.eclipse.org/eclipse/development/index.php eclipse dev], [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/?root=Tools_Project ViewVC], [http://dev.eclipse.org/viewcvs/index.cgi/www/mylyn/?root=Eclipse_Website ViewVC for Mylyn Web]<br />
<br />
== Conventions ==<br />
<br />
All contributions to Mylar need to be made using Mylar since it links source changes to tasks and contexts, making open development and collaboration easier. Using Mylar ensures that:<br />
* All Bugzilla reports have a corresponding task context, making them easy to reopen or pick up by you and by others.<br />
* All commits correspond to a single Bugzilla report, making it easy to navigate from changes to bugs.<br />
<br />
=== Links ===<br />
* [[Development Conventions and Guidelines | Eclipse Code Conventions]]<br />
* [[User Interface Guidelines | Eclipse User Interface Guidelines]]<br />
* [[Eclipse Doc Style Guide | Documentation Style Guidelines]]<br />
* [http://en.wikipedia.org/wiki/Eat_one's_own_dog_food Eating your own dog food (Wikipedia)]<br />
<br />
=== Bugzilla ===<br />
<br />
* Any user-reported bug should be resolved by one of: code improvements, documentation/FAQ improvements, or being marked a duplicate of another bug. All but the last require attaching a context.<br />
* Be judicious in marking bugs for LATER, because this typically communicates that the bug will never be resolved. Do this only if the bug does not fit in with the current scope of the project but is related to the mission. Otherwise mark P4/P5 and "helpwanted" to encourage a contribution that is not part of our current prioritization and plan.<br />
* When naming bugs, try to describe the use case or problem instead of the implementation unless there is no ambiguity in how the fix should be implemented. If the implementation approach helps with queries append it.<br />
** Bad: task list working set<br />
** Good: support nesting top level task list elements, e.g. via working sets<br />
<br />
=== Feature Maturity ===<br />
<br />
Mylyn features vary in UI maturity and availibility of support. The following is a guideline for what it takes to move from experimentation through to maturity. (Note that this is partially based on the [http://www.eclipse.org/projects/dev_process/development_process.php#6_2_3_Incubation Eclipse project lifecycle] and could converge further with that lifecycle if Mylyn were split into a separate incubation project or subprojects.)<br />
<br />
'''Mature''': packaged Eclipse downloads and available via main update site<br />
<br />
* UI quality: Eclipse SKD features have set a very high quality and UI consistency bar that needs to be met in order to make it possible to improve users' productivity with Eclipse.<br />
<br />
* UI simplicity: the Mylyn project's goal is to simplify and streamline the user experience. A simple and self-evident UI also helps ensure a manageable support burdeon on the component.<br />
<br />
* Availability of support: the feature must have an owner or organization with a long-term commitment to the quality of the feature and the ability to provide responsive support for feedback on that feature. <br />
<br />
* Responsiveness to feedback: the feature owner and other contributors must process and prioritize user feedback and respond to the highest priority needs in a timely manner (e.g. blockers and critical bugs need to be fixed within one release of being submitted, key enhancements help the feature evolve to meet users' needs).<br />
<br />
'''Incubation''': available via the ''Extras'' update site<br />
<br />
* High quality components that meet most but not all of the above criteria. To graduate, sufficient community feedback must be available on the quality and usability of the component (e.g. 100+ resolved bugs) and committers must vote to determine whether component meets the UI quality and simplicity guidelines.<br />
<br />
'''Sandbox''': available via the ''Extras'' update site<br />
<br />
* Unsupported components used for experimentation and not intended for daily use.<br />
<br />
* Community interest and contributions determine which experimental features move from the Sandbox into Incubation.<br />
<br />
== Workspace ==<br />
<br />
The recommended way to work with Mylar sources is by checking them out of CVS. Doing this makes it easy to try the latest changes and work with patches and ensures that you can easily browse the source code and documenation using Eclipse's facilities and avoids compilation problems such as [https://bugs.eclipse.org/bugs/show_bug.cgi?id=157375 PDE bug 157375].<br />
<br />
=== Setup ===<br />
<br />
Install Eclipse and get it configured for developing Java 5 applications.<br />
* Unless targeting a particular Eclipse release, download the latest [http://download.eclipse.org/eclipse/downloads/ Eclipse milestone release]. <br />
* Associate J2SE-1.5 with your installed JRE via the ''Window -> Preferences -> Java -> Installed JREs -> Execution Environments''. <br />
<br />
=== Checkout ===<br />
<br />
The Mylar CVS repository contains the following branches. Each can be checked via saving the linked <code>.psf</code> file locally, and then using ''File -> Import -> Team Project Set''. Use username "anonymous" and an empty password. If you are only interested in parts of Mylar, the additional projects can be deleted after the import. After the checkout you should have no errors or warnings from the Mylar projects.<br />
<br />
Note: these project sets specify anonymous <code>pserver</code> access. If that does not work for you see the [[CVS Howto]].<br />
<br />
'''Active branches:'''<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn.psf <code>HEAD</code>]: Mylyn 2.0 stream for Eclipse 3.3 (latest 3.3 milestone)<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_2_m_2_0.psf <code>e_3_2</code>]: Mylyn 2.0 stream for Eclipse 3.2 (branched projects updated with each release)<br />
'''Maintenance branches:'''<br />
Not updated unless a severe defect is found, or a request is made with sufficient reason or patch.<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_3_m_1_0.psf <code>e_3_3_m_1_0</code>]: Mylyn 1.0 stream for Eclipse 3.3 (currently supports 3.3M4 only)<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_2_m_1_0.psf <code>e_3_2_m_1_0</code>]: Mylyn 1.0 stream for Eclipse 3.2<br />
'''End-of-life branches:'''<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-compatibility.psf <code>compatibility</code>]: required for building Mylyn 2.0, prevent <code>org.eclipse.mylar</code> plug-ins from loading<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_1.psf <code>e_3_1</code>]: Mylyn 0.6 for Eclipse 3.1 <br />
'''Other:'''<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-web.psf Web site]: for updating eclipse.org/mylyn<br />
* <code>:pserver:dev.eclipse.org:/cvsroot/tools</code> can be used for manual checkout<br />
<br />
=== JUnit tests ===<br />
Each component has it's own All<Component>Tests suite. If not familiar with running PDE JUnit tests, refer to the [http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_main.htm Eclipse Documentation].<br />
* Add a ''credentials.properties'' file to org.eclipse.mylyn.context.tests and put the following into it:<br />
user: <user><br />
pass: <pass><br />
* For <user> use "tests<at sign>mylyn.eclipse.org". For <pass> use "<project's name lowercase>test". If you have any trouble making this work email mylar-dev@eclipse.org.<br />
* Add the following to the test configuration under Arguments -> VM Arguments: -enableassertions -Xmx384M <br />
Test suites (in <code>org.eclipse.mylar.tests</code>):<br />
* '''<code>AllTests</code>''': all of the automatic tests, should always pass, run as a ''JUnit Plug-in Test''<br />
* '''<code>AllStandaloneTests</code>''': do not require workbench, can run as ''JUnit Test'', subset of <code>AllTests</code><br />
* '''<code>AllFragileWebTests</code>''': web connector tests, some templates may periodically fail<br />
<br />
=== Manual tests ===<br />
<br />
The manual tests can be found on the '''[[Mylyn Testing]]''' page.<br />
* Component owners are responsible for maintaining their respective manual tests and ensuring they are covered two days prior to release.<br />
<br />
Trac Connector <br />
* A Trac test repository that offers anonymous access through XML-RPC is available at http://mylyn.eclipse.org/tractest. Feel free to create or modify any tickets.<br />
<br />
=== Self-hosting ===<br />
Self-hosting, also known as working bootstrapped (i.e. self-hosted) makes [http://en.wikipedia.org/wiki/Eat_one's_own_dog_food eating your own dog food] easier and avoids having to update to dev builds. <br />
<br />
The following is an example of how to set up a bootstrap workspace, using Eclipse 3.3 on Windows and a <tt>C:/Dev</tt> workspace directory as an example.<br />
<br />
* Create a new directory for your build workspace, e.g.: <tt>C:/Dev/build-e3.3</tt><br />
* Launch Eclipse with this workspace, e.g.: <tt>C:\Apps\eclipse-3.3\eclipse.exe -data C:\Dev\build-3.3</tt><br />
* Check out Mylar from CVS into this workspace, see [[#Setup]]<br />
* Create a new Launch Configuration:<br />
** Select''Run -> Run...'' -> create a new Eclipse Application.<br />
** Call the application ''Mylar Bootstrap''.<br />
** On the ''Main'' tab, set the ''Location''<br />
*** You can use the existing workspace that you used Mylar with previously<br />
*** You can create a new workspace (e.g. <tt>C:/Dev/bootstrap</tt>)<br />
* Launching with this launch configuration will give you a second workbench with Mylar. This workbench will be created based on the target platform (the workbench you're launching from) and the plugins in <tt>C:/Dev/build-3.3</tt>.<br />
* Do your development in the runtime workspace (<tt>C:/Dev/workspace</tt>).<br />
* Whenever your changes make it into HEAD that you would like to use, close your runtime workspace (<tt>C:/Dev/workspace</tt>), update from CVS in the build workspace (<tt>C:/Dev/build-3.3</tt>), and then re-launch your runtime workspace. <br />
<br />
Notes:<br />
* The launching workspace will typically consume very little memory. <br />
* Working in bootstrap mode means you have the source code checked out at least twice, once to bootstrap Mylar, and once to actually develop.<br />
* You must have two distinct workspaces, you can't bootstrap into the same workspace as you launch from. <br />
* It is possible to run in debug mode so that the changes apply to the workspace immediately after synch, but this can cause problems with the running workspace if classes change or go missing. This is because the hot-swap virtual machine can only change method bodies, not class definitions.<br />
<br />
== Contributors ==<br />
<br />
=== Getting Started ===<br />
* Use Bugzilla for all of your communication. This helps committers track the contribution.<br />
* Before setting out to contribute to a bug report, post on the bug report describing your intention. This helps committers guide the contribution and avoids problems with patches going stale due to related work being done concurrently.<br />
* For contribution ideas see the list of [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&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= helpwanted bugs] to find one that interests you, file a new bug of your own, or email mylyn-dev for ideas.<br />
<br />
=== Tips ===<br />
<br />
Following these steps will help get your patches applied more quickly. <br />
# Before implementing the functionality post a brief proposal of the implementation and UI changes/additions and get a committer's feedback.<br />
# Post a patch to the core functionality with reasonable unit test coverage.<br />
# After that's applied iterate on the UI proposal if needed and the post the patch to the UI.<br />
# Note that the smaller you make patches and the more focused they are on individual and well-tested units of functionality the more quickly they will get applied.<br />
<br />
=== Patches ===<br />
<br />
'''Creating'''<br />
* Each patch should correspond to a single bug report, and a single patch should be made for each set of changes to be reviewed. <br />
* A task context should be attached to each patch to make applying and evolving it easier.<br />
* With few exceptions patches should be accompanied by a JUnit test, and in general unit tests are one of the most valuable and long-lived contributions. If you are having trouble writing a test (e.g. trickiness verifying what happens in the UI) comment on the corresponding bug report so that we can point you at similar test cases or consider extending the test harness if needed. <br />
* Minimize the amount of changes to existing code to make review easier. <br />
* Synchronize often to ensure you have the latest code. Once you start modifying resources, put the Synchronize view in Outgoing mode and press the Change Set button so that Mylar tracks the context for the patch. <br />
* Before creating a new JUnit test class class check the components test suite for similar test cases (e.g. AllTasklistTests). <br />
* Set the formatter by importing <tt>org.eclipse.mylyn/mylyn-settings-formatter.xml</tt> from the org.eclipse.mylyn project into <i>Window -> Preferences -> Java -> Code Style -> Formatter</i>. Format code using Eclipse's formatter (Ctrl+Shift+F) and ensure that no have been added. <br />
* Add an <tt>@author</tt> tag to each class that you create or make significant modification to, placed below any existing author tags and indicating the bug, e.g.: <tt>@author Rob Elves (bug 160315)</tt><br />
* Ensure that there is no console output. For logging errors use MylarStatusHandler. <br />
<br />
'''Submitting'''<br />
* Ensure there are no build errors, warnings, and that org.eclipse.mylar.tests.AllTests passes. <br />
* Do not include binary files such as GIF icons in the patch, they need to be attached separately.<br />
* Synchronize using Incoming mode and ensure that there are no conflicts, and merge them locally if there are. <br />
* Right click the task context change set (or the project containing the patch--patches should be made for a project, not a file), press ''Team -> Create Patch'' and select ''Save to clipboard''.<br />
* In the ''Attachments'' section of the ''Task Editor'' select ''Attach File...'' and use ''Clipboard'' as the source. Check off the ''Patch'' and ''Attach Context'' checkboxes in this wizard page.<br />
* Add a description of issues addressed and comment on what testing was done to validate it (e.g. unit test coverage, manual tests performed). Also indicate any changes made to the existing UI in the comment (e.g. reordering of menu actions). Also indicate if patch is intended to resolve bug report or further work is required.<br />
<br />
== Committers ==<br />
<br />
The [http://www.eclipse.org/projects/dev_process/Eclipse_Standard_TopLevel_Charter_v1.0.php Eclipse Charter] explains how developers can gain commit rights.<br />
<br />
=== Participation ===<br />
Committers should:<br />
* Sign up for all of the project mailing lists.<br />
* Read the newsgroup regularly, and respond to posts in their area of expertise.<br />
* Respond to mylar-dev email in their area of expertise.<br />
* Watch and update all wiki pages related to components that they contribute to.<br />
<br />
=== Communication ===<br />
Mylar committers are required to follow these communication guidelines. Our philosophy is that '''the user is always right''', even if it takes time to figure out how or why they are right. Our project thrives on the feedback of users, whether they are seasoned experts or newbies. Feedback defines how the tool should work, how it should be simplified, and how it should evolve. <br />
<br />
* All feedback contains information, and it is the responsibility of committers to turn that information into actions. This can mean improving the implementation, simplifying the workflow, clarifying the documentation, or noting a duplicate request. Making the actions we take clear helps communicate this philosophy to our growing user community and encourages high-quality feedback.<br />
<br />
* If users do not provide enough information or do not take the time to provide accurate information, they should be prompted to provide the necessary details. If they do not do so in a timely manner, the feedback is incomplete and can be resolved without taking action.<br />
<br />
* Always show respect to others in the community, whether they are making correct or incorrect assumptions about the tool or technology. When they are making incorrect assumptions it is because we have not done our job well enough, or because the platforms we build on are making it hard for us to do our job well enough. Identifying those cases is important so that we can provide feedback to those platforms and find work-arounds.<br />
<br />
* Never turn feedback or discussion away by [http://en.wikipedia.org/wiki/Flame_war#Causes_of_flaming flaming], being condescending, short, or insulting in any community communication forum. Forms of humor that work for face-to-face communication, such as sarcasm, should be avoided because they result in misinterpretation, especially when there is a language or cultural barrier. Use of emoticons is not a work-around. <br />
<br />
* Review public communication before sending. Things that are not meant to be intentionally disrespectful can come across that way. When reviewing try to shorten in order to show respect for your audience's time.<br />
<br />
=== Applying Patches ===<br />
<br />
* Make sure to update <code>mylyn-iplog.csv</code> with an entry for each bug that is resolved by patch. Note that each patch should not contain more than 250 lines of code of unique and seprately usable functionality. For larger patches we need to invoke the IP Review process.<br />
<br />
* Contributors frequently write quick patches in order to get something working for them. It is the responsibility of the committer to either encourage the contributor to improve the modularity and test coverage of the patch or to do those themselves if this aligns with the projects' priorities. Failing to do so can reduce the overall quality of the code and failing to get sufficient test coverage reduces our ability to evolve the code.<br />
<br />
=== Web site authoring ===<br />
* Create a new CVS location: :pserver:dev.eclipse.org:/cvsroot/org.eclipse<br />
* Check out www/mylar as a project <br />
* To push documentation from org.eclipse.mylar.doc to the web site use the targets in mylar/build.xml<br />
<br />
=== Building a distribution ===<br />
* Using PDE Build support to create a Mylar distribution from HEAD, using a plain Eclipse 3.2<br />
** org.eclipse.mylar-feature/feature.xml -> Overview -> change version number to current date (e.g. 0.4.7.v20060125-0800)<br />
*** On Plug-ins tab -> Versions... -> Force feature version into plug-in and fragment manifests <br />
*** Repeat above for org.eclipse.mylar-bugzilla-feature.xml <br />
** org.eclipse.mylar-site/e3.2/site.xml<br />
*** Delete old features (grayed out) <br />
*** Add new mylar-bugzilla and mylar features <br />
*** Hit Build All (if this fails restart Eclipse and try again) <br />
* To install, add the path of org.eclipse.mylar-site/e3.2/site.xml as a local update site <br />
* Bugzilla support can be built independently of the Mylar UI by checking out the following projects mylar.bugzilla.core, mylar.bugzilla.ui, mylar.tasklist, mylar.core <br />
<br />
Merging and building the 3.1 branch:<br />
* Right-click the org.eclipse.mylar.java, mylar.ide, and mylar.xml project, Team -> Switch to Another Branch..., then Refresh the Branches and select e_3_1 <br />
* The list of files that should not be overwritten is in: org.eclipse.mylar-site/merge.text <br />
Deploying:<br />
* Instructions are in org.eclipse.mylar-site/release.txt<br />
<br />
== Sandbox ==<br />
<br />
Update site: download.eclipse.org/tools/mylyn/update/dev/extras<br />
<br />
The sandbox is a set of CVS projects and feature contributors use for experimentation. These features are not intended to be used for daily development. Sandbox features include experimental connectors and bridges, experimental UI features, and developer tools. To use sandbox tools either check them out of CVS from the <code>org.eclipse.mylyn/sandbox</code> directory, or install them using the update site above. Please note that some Sandbox tools may have external dependencies, listed in a readme.txt file.<br />
<br />
=== Dev tools ===<br />
<br />
* '''Introspect Object''' (action): displays the class and other relevant information (e.g. degree-of-interest, task synchronization state) of any object visible in the workbench. Appears at the end of the context menu for any view that accepts an object contributions.<br />
<br />
* '''Interest Level Decorator''': displays the floating point interest level of elements. Enable via ''Decorators'' preference page.<br />
<br />
=== Experimental tools ===<br />
<br />
The following experimental views can be opened via the ''Mylar Sandbox'' view category or accessed via the ''Mylar -> Sandbox'' preference page.<br />
<br />
* '''Context Search''': automatically finds and displays elements that are structurally related to landmarks in the active . These elements become part of the task context and have a predicted degree-of-interest.<br />
<br />
* '''Context Hierarchy''': displays the Java hierarchy of all landmark elements.<br />
<br />
* '''Predicted interested for Java errors''': potentially useful, but tends to overload the Package Explorer. If you find this useful for long-term use condiser commenting on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=107542 bug 107542].<br />
<br />
== Tips and Tricks ==<br />
<br />
=== User support ===<br />
<br />
* Every time that you find yourself formulating an answer to a bug report, email, or newsgroup post, if the answer is more than a sentence, consider updating the FAQ, User Guide, or Integrator Reference and pointing to the entry.<br />
* Every time that resolving a bug does not result in a code change that addresses the problem or clarifies the UI, update the FAQ or User Guide to make sure that users can self-diagnose the problem. This is particularly important for bugs marked INVALID or WORKSFORME.<br />
<br />
=== Code ===<br />
<br />
* For error handling use <code>MylarStatusHandler</code>.<br />
* Use <code>WorkbenchJob</code> for running jobs that should only run when the workbench is active. Not doing this can cause errors on workbench shutdown (e.g. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178409 bug 178409)].<br />
* When using <code>String.toLowerCase()</code>, use <code>String.toLowerCase(Locale.ENGLISH)</code> to ensure locale safety (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168652 bug 168652]).<br />
* Do not use <code>@Override</code> annotations on implementing methods, only on overriding methods. Doing so violates Java 5 ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=173171 bug 173171]).<br />
* Use DateFormat with extra caution. It is not thread-safe and should not be saved to fields in classes that can be used from multiple threads (UI, asynchonous execution, or jobs).<br />
* For the sake of multi-monitor setups, use <code>getMonitor()</code> instead of <code>getDisplay()</code> when you want to position a UI element on a specific coordinate of the screen.<br />
<br />
=== Bugzilla ===<br />
<br />
* '''Query setup''': If you are added to the cc list on a report that is not picked up by your usual queries it may go unnoticed. One trick is to create a query for ALL products except the product you usually work in (and hence have queries for) and set the cc field of the query to your id. Now you will be notified of anybody adding you to the cc of a product you don't usually monitor.<br />
<br />
=== JDT ===<br />
<br />
* '''Including Platform plug-ins in search''': Java search (Ctrl+H > Java Search) will include all plugins in your Plugin-in Dependencies. If you want to search other plugins as well, open the Plug-ins view, right click on the desired plugin(s) and choose 'Add to Java Search'. That plugin will now always be included in your java searches.<br />
<br />
=== Debugging ===<br />
<br />
* '''Plug-ins fail to load''': verify that plug-in dependencies are met via the ''Validate Plug-in Set'' button on the launch configuration ''Plug-ins'' tab.<br />
* '''Startup failure''': If you get an <code>IStartup</code> failure message or a <code>ClassNotFoundException</code> on startup this is often the result of some step in the activation of the plug-in failing.<br />
** Attempt to find the earliest exception thrown within the in the plug-in's activation process. For example, this could occur in <code>TasksUiPlugin.start()</code> or <code>TasksUiPlugin.<init></code>.<br />
** If the cause of the failure is not straightforward, the problem could be due to a class loading race condition. This can sometimes be verified by trying a different VM like IBM's or BEA's and checking if that resolves the problem. If this is the case, please file a bug.<br />
* '''Getting a thread dump''': <br />
** Run Eclipse with the <code>-debug</code> option (or use <code>java.exe</code> instead <code>javaw.exe</code> on windows), then<br />
*** On Windows: Hit a <code>Ctrl-Break</code> few times on the console window during that long synchronization to capture the thread dump<br />
*** On Linux: Use <code>Ctrl-\</code> on the console or send SIG_QUIT signal: <code>kill -SIGQUIT ''pid''</code><br />
** Use <code>[http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jps.html jps]</code> to find the PIDs of Java processes and <code>[http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jstack.html jstack]</code> to show the stack trace of Java processes: <code>jstack ''pid''</code><br />
*** Supported starting JDK 5 for UNIX / JDK 6 for Windows<br />
** See this [http://blogs.sun.com/alanb/entry/jstack Weblog on jstack]<br />
** Also see [http://weblogs.java.net/blog/mandychung/archive/2005/11/thread_dump_and_1.html Thread Dump and Concurrency Locks] for more details.<br />
* '''Startup problems and deadlocks''': for a diagnosis of a potential problem see diagnosis on https://bugs.eclipse.org/bugs/show_bug.cgi?id=177048#c3<br />
<br />
=== Migrating Eclipse milestones ===<br />
<br />
To migrate between Eclipse 3.3M4 and 3.3M5 (as of I20070205-1824):<br />
<br />
* Get latest milestone or integration build: http://download.eclipse.org/eclipse/downloads/<br />
<br />
* Unzip two copies of it, one for bootstrapping and one for setting as your Target Platform in your bootstrap workspace. If you get two workspaces when you launch a test workspace, delete the "configuration" directory of the Target Platform. Note this bug may be fixed by<br />
3.3M5 ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172975 bug 172975]).<br />
<br />
* To synch you may need to delete the known_hosts file if CVS connections were failing (file path is in: ''Preferences -> Team -> CVS -> SSH2..'').<br />
<br />
* After synching, if you get conflicts in the .settings folder after launching override them (happens because CVS version was updated, and your own was automatically migrated). <br />
<br />
* As usual, update your repository credentials in the Task Repositories view.<br />
<br />
* Note that you may need to re-create your launch configurations.</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=Mylyn/SOC/2006/Trac_Connector&diff=49364Mylyn/SOC/2006/Trac Connector2007-09-06T09:20:48Z<p>Techtonik.php.net: /* Download */ - fix link</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
The goal of this [http://code.google.com/soc/ Google Summer of Code] project is to provide a [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140512 Trac connector plug-in for Mylyn]. [http://trac.edgewall.com/ Trac] is a web-based issue tracking system with an integrated wiki.<br />
<br />
The Mylyn API already supports multiple issue tracking systems, therefore the existing abstraction is used to implement a Trac connector. Trac issues are accessed remotely through a query script that outputs tab-delimited text as well as through a [http://trac-hacks.org/wiki/XmlRpcPlugin XML-RPC interface]. The XML-RPC interface has not yet been integrated into the main distribution of Trac but is available as a separate plug-in.<br />
<br />
The project has been accomplished in two iterations. The goal of the first iteration was to make the connector work with existing Trac deployments through Trac's web interface. This retrieved ticket information is used for read-only display in Mylar. Tickets can be edited through a web-browser.<br />
<br />
The second iteration focused on enhancing the support for Trac's XML-RPC interface. The XML-RPC interface allows full featured access to all ticket information and allows manipulation of tickets. The editing of tickets is done through Eclipse forms based editor.<br />
<br />
The Trac connector is now maintained in the Mylyn CVS and is shipped with the regular releases.<br />
<br />
== ChangeLog ==<br />
<br />
=== '''M1 (completed):''' ''Web linking only repository integration ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=146334 #148378])'' ===<br />
<br />
* Create and edit Trac repositories ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147817 #147817], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=148378 #148378])<br />
** Templates for common repository locations ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150677 #150677])<br />
* Data model for repository access ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147816 #147816])<br />
** Access through Trac's query script ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=148090 #148090])<br />
** Access through the Trac XML-RPC plug-in ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=148089 #148089])<br />
* Create new tasks through web-browser ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150699 #150699])<br />
* Add exiting tasks to task list ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149385 #149385])<br />
* Query repository in task list view through Bugzilla like query dialog ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149386 #149386])<br />
<br />
This milestone is available as part of the Mylar 0.6.1 release.<br />
<br />
=== '''M2 (completed):''' ''Full integration based on the Trac XML-RPC plug-in'' ===<br />
<br />
* Digest authentication ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=151077 #151077])<br />
* Handle trailing slashes in repository urls ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150890 #150890])''<br />
* Update repository attributes from task repository context menu ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=152325 #152325])<br />
* Unescape HTML entities when updating repository attributes ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=153496 #153496], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154098 #154098])<br />
* Query repositories from Eclipse search ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=153539 #153539], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154772 #154772])<br />
* Remember repository attributes ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150670 #150670])<br />
* Update repository attributes when query dialog is opened ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154347 #154347])<br />
* Attachment support and context uploading and retrieving ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=151900 #151900], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154441 #154441], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154372 #154372])<br />
* Change query urls accordingly when repository url is changed ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154798 #154798])<br />
* Authoring of reports within native Eclipse editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=151899 #151899], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=146334 #146334], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154377 #154377], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154962 #154962])<br />
* Fixed notifications for Trac task ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154379 #154379]<br />
* Check revision of XML-RPC Plugin ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154931 #154931])<br />
* Properly check for Trac repository during validation ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154464 #154464])<br />
<br />
This milestone is available as part of the Mylar 0.6.2 release.<br />
<br />
=== '''Future planning''' ===<br />
<br />
Please refer to the [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=Mylar&component=Trac&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= Eclipse Bugzilla] for bug reports and feature requests.<br />
<br />
== Download ==<br />
<br />
Please refer to the [http://www.eclipse.org/mylyn/downloads/ Mylyn download page].<br />
<br />
== Source ==<br />
<br />
Please refer to the [[Mylar Contributor Reference]] for information about how to obtain and build Mylar and its connectors.<br />
<br />
The source is available in the Mylar CVS:<br />
<br />
[http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/?root=Tools_Project http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/?root=Tools_Project]<br />
<br />
Plug-ins:<br />
<br />
* [http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.mylar/org.eclipse.mylar.trac.ui/ org.eclipse.mylar.trac.core]<br />
* [http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.mylar/org.eclipse.mylar.trac-feature/ org.eclipse.mylar.trac-feature]<br />
* [http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.mylar/org.eclipse.mylar.trac.tests/ org.eclipse.mylar.trac.tests]<br />
* [http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.mylar/org.eclipse.mylar.trac.ui/ org.eclipse.mylar.trac.ui]<br />
<br />
Project Team Set:<br />
<br />
* [http://www.eclipse.org/mylar/doc/dev/projects-trac.psf http://www.eclipse.org/mylar/doc/dev/projects-trac.psf]<br />
<br />
== Architecture ==<br />
<br />
* Core and Model: Provides Java abstraction for repository access<br />
** Abstraction for query script and XML-RPC access<br />
** (Eclipse independent) model classes that represent Trac data<br />
* UI: Tasklist classes<br />
* Tests: Tests for Core and UI<br />
<br />
For the XML-RPC calls [http://ws.apache.org/xmlrpc/ Apache XML-RPC] is used.</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=Mylyn/SOC/2006/Trac_Connector&diff=49362Mylyn/SOC/2006/Trac Connector2007-09-06T09:19:44Z<p>Techtonik.php.net: + replace Mylar with Mylyn, minor rewording</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
The goal of this [http://code.google.com/soc/ Google Summer of Code] project is to provide a [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140512 Trac connector plug-in for Mylyn]. [http://trac.edgewall.com/ Trac] is a web-based issue tracking system with an integrated wiki.<br />
<br />
The Mylyn API already supports multiple issue tracking systems, therefore the existing abstraction is used to implement a Trac connector. Trac issues are accessed remotely through a query script that outputs tab-delimited text as well as through a [http://trac-hacks.org/wiki/XmlRpcPlugin XML-RPC interface]. The XML-RPC interface has not yet been integrated into the main distribution of Trac but is available as a separate plug-in.<br />
<br />
The project has been accomplished in two iterations. The goal of the first iteration was to make the connector work with existing Trac deployments through Trac's web interface. This retrieved ticket information is used for read-only display in Mylar. Tickets can be edited through a web-browser.<br />
<br />
The second iteration focused on enhancing the support for Trac's XML-RPC interface. The XML-RPC interface allows full featured access to all ticket information and allows manipulation of tickets. The editing of tickets is done through Eclipse forms based editor.<br />
<br />
The Trac connector is now maintained in the Mylyn CVS and is shipped with the regular releases.<br />
<br />
== ChangeLog ==<br />
<br />
=== '''M1 (completed):''' ''Web linking only repository integration ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=146334 #148378])'' ===<br />
<br />
* Create and edit Trac repositories ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147817 #147817], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=148378 #148378])<br />
** Templates for common repository locations ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150677 #150677])<br />
* Data model for repository access ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147816 #147816])<br />
** Access through Trac's query script ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=148090 #148090])<br />
** Access through the Trac XML-RPC plug-in ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=148089 #148089])<br />
* Create new tasks through web-browser ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150699 #150699])<br />
* Add exiting tasks to task list ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149385 #149385])<br />
* Query repository in task list view through Bugzilla like query dialog ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149386 #149386])<br />
<br />
This milestone is available as part of the Mylar 0.6.1 release.<br />
<br />
=== '''M2 (completed):''' ''Full integration based on the Trac XML-RPC plug-in'' ===<br />
<br />
* Digest authentication ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=151077 #151077])<br />
* Handle trailing slashes in repository urls ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150890 #150890])''<br />
* Update repository attributes from task repository context menu ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=152325 #152325])<br />
* Unescape HTML entities when updating repository attributes ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=153496 #153496], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154098 #154098])<br />
* Query repositories from Eclipse search ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=153539 #153539], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154772 #154772])<br />
* Remember repository attributes ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=150670 #150670])<br />
* Update repository attributes when query dialog is opened ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154347 #154347])<br />
* Attachment support and context uploading and retrieving ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=151900 #151900], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154441 #154441], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154372 #154372])<br />
* Change query urls accordingly when repository url is changed ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154798 #154798])<br />
* Authoring of reports within native Eclipse editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=151899 #151899], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=146334 #146334], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154377 #154377], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154962 #154962])<br />
* Fixed notifications for Trac task ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154379 #154379]<br />
* Check revision of XML-RPC Plugin ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154931 #154931])<br />
* Properly check for Trac repository during validation ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=154464 #154464])<br />
<br />
This milestone is available as part of the Mylar 0.6.2 release.<br />
<br />
=== '''Future planning''' ===<br />
<br />
Please refer to the [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Technology&product=Mylar&component=Trac&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= Eclipse Bugzilla] for bug reports and feature requests.<br />
<br />
== Download ==<br />
<br />
Please refer to the [http://www.eclipse.org/mylar/dl.php Mylar download page].<br />
<br />
== Source ==<br />
<br />
Please refer to the [[Mylar Contributor Reference]] for information about how to obtain and build Mylar and its connectors.<br />
<br />
The source is available in the Mylar CVS:<br />
<br />
[http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/?root=Tools_Project http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/?root=Tools_Project]<br />
<br />
Plug-ins:<br />
<br />
* [http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.mylar/org.eclipse.mylar.trac.ui/ org.eclipse.mylar.trac.core]<br />
* [http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.mylar/org.eclipse.mylar.trac-feature/ org.eclipse.mylar.trac-feature]<br />
* [http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.mylar/org.eclipse.mylar.trac.tests/ org.eclipse.mylar.trac.tests]<br />
* [http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.mylar/org.eclipse.mylar.trac.ui/ org.eclipse.mylar.trac.ui]<br />
<br />
Project Team Set:<br />
<br />
* [http://www.eclipse.org/mylar/doc/dev/projects-trac.psf http://www.eclipse.org/mylar/doc/dev/projects-trac.psf]<br />
<br />
== Architecture ==<br />
<br />
* Core and Model: Provides Java abstraction for repository access<br />
** Abstraction for query script and XML-RPC access<br />
** (Eclipse independent) model classes that represent Trac data<br />
* UI: Tasklist classes<br />
* Tests: Tests for Core and UI<br />
<br />
For the XML-RPC calls [http://ws.apache.org/xmlrpc/ Apache XML-RPC] is used.</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=Mylyn/Contributor_Reference&diff=49360Mylyn/Contributor Reference2007-09-06T08:41:29Z<p>Techtonik.php.net: /* Manual tests */ - fix trac link</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
Also see: [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&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= helpwanted bugs]<br />
[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&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= discussion bugs]<br />
[http://www.eclipse.org/eclipse/development/index.php eclipse dev]<br />
<br />
== Conventions ==<br />
<br />
All contributions to Mylar need to be made using Mylar since it links source changes to tasks and contexts, making open development and collaboration easier. Using Mylar ensures that:<br />
* All Bugzilla reports have a corresponding task context, making them easy to reopen or pick up by you and by others.<br />
* All commits correspond to a single Bugzilla report, making it easy to navigate from changes to bugs.<br />
<br />
=== Links ===<br />
* [[Development Conventions and Guidelines | Eclipse Code Conventions]]<br />
* [[User Interface Guidelines | Eclipse User Interface Guidelines]]<br />
* [[Eclipse Doc Style Guide | Documentation Style Guidelines]]<br />
* [http://en.wikipedia.org/wiki/Eat_one's_own_dog_food Eating your own dog food (Wikipedia)]<br />
<br />
=== Bugzilla ===<br />
<br />
* Any user-reported bug should be resolved by one of: code improvements, documentation/FAQ improvements, or being marked a duplicate of another bug. All but the last require attaching a context.<br />
* Be judicious in marking bugs for LATER, because this typically communicates that the bug will never be resolved. Do this only if the bug does not fit in with the current scope of the project but is related to the mission. Otherwise mark P4/P5 and "helpwanted" to encourage a contribution that is not part of our current prioritization and plan.<br />
* When naming bugs, try to describe the use case or problem instead of the implementation unless there is no ambiguity in how the fix should be implemented. If the implementation approach helps with queries append it.<br />
** Bad: task list working set<br />
** Good: support nesting top level task list elements, e.g. via working sets<br />
<br />
=== Feature Maturity ===<br />
<br />
Mylyn features vary in UI maturity and availibility of support. The following is a guideline for what it takes to move from experimentation through to maturity. (Note that this is partially based on the [http://www.eclipse.org/projects/dev_process/development_process.php#6_2_3_Incubation Eclipse project lifecycle] and could converge further with that lifecycle if Mylyn were split into a separate incubation project or subprojects.)<br />
<br />
'''Mature''': packaged Eclipse downloads and available via main update site<br />
<br />
* UI quality: Eclipse SKD features have set a very high quality and UI consistency bar that needs to be met in order to make it possible to improve users' productivity with Eclipse.<br />
<br />
* UI simplicity: the Mylyn project's goal is to simplify and streamline the user experience. A simple and self-evident UI also helps ensure a manageable support burdeon on the component.<br />
<br />
* Availability of support: the feature must have an owner or organization with a long-term commitment to the quality of the feature and the ability to provide responsive support for feedback on that feature. <br />
<br />
* Responsiveness to feedback: the feature owner and other contributors must process and prioritize user feedback and respond to the highest priority needs in a timely manner (e.g. blockers and critical bugs need to be fixed within one release of being submitted, key enhancements help the feature evolve to meet users' needs).<br />
<br />
'''Incubation''': available via the ''Extras'' update site<br />
<br />
* High quality components that meet most but not all of the above criteria. To graduate, sufficient community feedback must be available on the quality and usability of the component (e.g. 100+ resolved bugs) and committers must vote to determine whether component meets the UI quality and simplicity guidelines.<br />
<br />
'''Sandbox''': available via the ''Extras'' update site<br />
<br />
* Unsupported components used for experimentation and not intended for daily use.<br />
<br />
* Community interest and contributions determine which experimental features move from the Sandbox into Incubation.<br />
<br />
== Workspace ==<br />
<br />
The recommended way to work with Mylar sources is by checking them out of CVS. Doing this makes it easy to try the latest changes and work with patches and ensures that you can easily browse the source code and documenation using Eclipse's facilities and avoids compilation problems such as [https://bugs.eclipse.org/bugs/show_bug.cgi?id=157375 PDE bug 157375].<br />
<br />
=== Setup ===<br />
<br />
Install Eclipse and get it configured for developing Java 5 applications.<br />
* Unless targeting a particular Eclipse release, download the latest [http://download.eclipse.org/eclipse/downloads/ Eclipse milestone release]. <br />
* Associate J2SE-1.5 with your installed JRE via the ''Window -> Preferences -> Java -> Installed JREs -> Execution Environments''. <br />
<br />
=== Checkout ===<br />
<br />
The Mylar CVS repository contains the following branches. Each can be checked via saving the linked <code>.psf</code> file locally, and then using ''File -> Import -> Team Project Set''. Use username "anonymous" and an empty password. If you are only interested in parts of Mylar, the additional projects can be deleted after the import. After the checkout you should have no errors or warnings from the Mylar projects.<br />
<br />
Note: these project sets specify anonymous <code>pserver</code> access. If that does not work for you see the [[CVS Howto]].<br />
<br />
'''Active branches:'''<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn.psf <code>HEAD</code>]: Mylyn 2.0 stream for Eclipse 3.3 (latest 3.3 milestone)<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_2_m_2_0.psf <code>e_3_2</code>]: Mylyn 2.0 stream for Eclipse 3.2 (branched projects updated with each release)<br />
'''Maintenance branches:'''<br />
Not updated unless a severe defect is found, or a request is made with sufficient reason or patch.<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_3_m_1_0.psf <code>e_3_3_m_1_0</code>]: Mylyn 1.0 stream for Eclipse 3.3 (currently supports 3.3M4 only)<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_2_m_1_0.psf <code>e_3_2_m_1_0</code>]: Mylyn 1.0 stream for Eclipse 3.2<br />
'''End-of-life branches:'''<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-compatibility.psf <code>compatibility</code>]: required for building Mylyn 2.0, prevent <code>org.eclipse.mylar</code> plug-ins from loading<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_1.psf <code>e_3_1</code>]: Mylyn 0.6 for Eclipse 3.1 <br />
'''Other:'''<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-web.psf Web site]: for updating eclipse.org/mylyn<br />
* <code>:pserver:dev.eclipse.org:/cvsroot/tools</code> can be used for manual checkout<br />
<br />
=== JUnit tests ===<br />
Each component has it's own All<Component>Tests suite. If not familiar with running PDE JUnit tests, refer to the [http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tools/launchers/eclipse_main.htm Eclipse Documentation].<br />
* Add a ''credentials.properties'' file to org.eclipse.mylyn.context.tests and put the following into it:<br />
user: <user><br />
pass: <pass><br />
* For <user> use "tests<at sign>mylyn.eclipse.org". For <pass> use "<project's name lowercase>test". If you have any trouble making this work email mylar-dev@eclipse.org.<br />
* Add the following to the test configuration under Arguments -> VM Arguments: -enableassertions -Xmx384M <br />
Test suites (in <code>org.eclipse.mylar.tests</code>):<br />
* '''<code>AllTests</code>''': all of the automatic tests, should always pass, run as a ''JUnit Plug-in Test''<br />
* '''<code>AllStandaloneTests</code>''': do not require workbench, can run as ''JUnit Test'', subset of <code>AllTests</code><br />
* '''<code>AllFragileWebTests</code>''': web connector tests, some templates may periodically fail<br />
<br />
=== Manual tests ===<br />
<br />
The manual tests can be found on the '''[[Mylyn Testing]]''' page.<br />
* Component owners are responsible for maintaining their respective manual tests and ensuring they are covered two days prior to release.<br />
<br />
Trac Connector <br />
* A Trac test repository that offers anonymous access through XML-RPC is available at http://mylyn.eclipse.org/tractest. Feel free to create or modify any tickets.<br />
<br />
=== Self-hosting ===<br />
Self-hosting, also known as working bootstrapped (i.e. self-hosted) makes [http://en.wikipedia.org/wiki/Eat_one's_own_dog_food eating your own dog food] easier and avoids having to update to dev builds. <br />
<br />
The following is an example of how to set up a bootstrap workspace, using Eclipse 3.3 on Windows and a <tt>C:/Dev</tt> workspace directory as an example.<br />
<br />
* Create a new directory for your build workspace, e.g.: <tt>C:/Dev/build-e3.3</tt><br />
* Launch Eclipse with this workspace, e.g.: <tt>C:\Apps\eclipse-3.3\eclipse.exe -data C:\Dev\build-3.3</tt><br />
* Check out Mylar from CVS into this workspace, see [[#Setup]]<br />
* Create a new Launch Configuration:<br />
** Select''Run -> Run...'' -> create a new Eclipse Application.<br />
** Call the application ''Mylar Bootstrap''.<br />
** On the ''Main'' tab, set the ''Location''<br />
*** You can use the existing workspace that you used Mylar with previously<br />
*** You can create a new workspace (e.g. <tt>C:/Dev/bootstrap</tt>)<br />
* Launching with this launch configuration will give you a second workbench with Mylar. This workbench will be created based on the target platform (the workbench you're launching from) and the plugins in <tt>C:/Dev/build-3.3</tt>.<br />
* Do your development in the runtime workspace (<tt>C:/Dev/workspace</tt>).<br />
* Whenever your changes make it into HEAD that you would like to use, close your runtime workspace (<tt>C:/Dev/workspace</tt>), update from CVS in the build workspace (<tt>C:/Dev/build-3.3</tt>), and then re-launch your runtime workspace. <br />
<br />
Notes:<br />
* The launching workspace will typically consume very little memory. <br />
* Working in bootstrap mode means you have the source code checked out at least twice, once to bootstrap Mylar, and once to actually develop.<br />
* You must have two distinct workspaces, you can't bootstrap into the same workspace as you launch from. <br />
* It is possible to run in debug mode so that the changes apply to the workspace immediately after synch, but this can cause problems with the running workspace if classes change or go missing. This is because the hot-swap virtual machine can only change method bodies, not class definitions.<br />
<br />
== Contributors ==<br />
<br />
=== Getting Started ===<br />
* Use Bugzilla for all of your communication. This helps committers track the contribution.<br />
* Before setting out to contribute to a bug report, post on the bug report describing your intention. This helps committers guide the contribution and avoids problems with patches going stale due to related work being done concurrently.<br />
* For contribution ideas see the list of [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=helpwanted&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= helpwanted bugs] to find one that interests you, file a new bug of your own, or email mylyn-dev for ideas.<br />
<br />
=== Tips ===<br />
<br />
Following these steps will help get your patches applied more quickly. <br />
# Before implementing the functionality post a brief proposal of the implementation and UI changes/additions and get a committer's feedback.<br />
# Post a patch to the core functionality with reasonable unit test coverage.<br />
# After that's applied iterate on the UI proposal if needed and the post the patch to the UI.<br />
# Note that the smaller you make patches and the more focused they are on individual and well-tested units of functionality the more quickly they will get applied.<br />
<br />
=== Patches ===<br />
<br />
'''Creating'''<br />
* Each patch should correspond to a single bug report, and a single patch should be made for each set of changes to be reviewed. <br />
* A task context should be attached to each patch to make applying and evolving it easier.<br />
* With few exceptions patches should be accompanied by a JUnit test, and in general unit tests are one of the most valuable and long-lived contributions. If you are having trouble writing a test (e.g. trickiness verifying what happens in the UI) comment on the corresponding bug report so that we can point you at similar test cases or consider extending the test harness if needed. <br />
* Minimize the amount of changes to existing code to make review easier. <br />
* Synchronize often to ensure you have the latest code. Once you start modifying resources, put the Synchronize view in Outgoing mode and press the Change Set button so that Mylar tracks the context for the patch. <br />
* Before creating a new JUnit test class class check the components test suite for similar test cases (e.g. AllTasklistTests). <br />
* Set the formatter by importing <tt>org.eclipse.mylyn/mylyn-settings-formatter.xml</tt> from the org.eclipse.mylyn project into <i>Window -> Preferences -> Java -> Code Style -> Formatter</i>. Format code using Eclipse's formatter (Ctrl+Shift+F) and ensure that no have been added. <br />
* Add an <tt>@author</tt> tag to each class that you create or make significant modification to, placed below any existing author tags and indicating the bug, e.g.: <tt>@author Rob Elves (bug 160315)</tt><br />
* Ensure that there is no console output. For logging errors use MylarStatusHandler. <br />
<br />
'''Submitting'''<br />
* Ensure there are no build errors, warnings, and that org.eclipse.mylar.tests.AllTests passes. <br />
* Do not include binary files such as GIF icons in the patch, they need to be attached separately.<br />
* Synchronize using Incoming mode and ensure that there are no conflicts, and merge them locally if there are. <br />
* Right click the task context change set (or the project containing the patch--patches should be made for a project, not a file), press ''Team -> Create Patch'' and select ''Save to clipboard''.<br />
* In the ''Attachments'' section of the ''Task Editor'' select ''Attach File...'' and use ''Clipboard'' as the source. Check off the ''Patch'' and ''Attach Context'' checkboxes in this wizard page.<br />
* Add a description of issues addressed and comment on what testing was done to validate it (e.g. unit test coverage, manual tests performed). Also indicate any changes made to the existing UI in the comment (e.g. reordering of menu actions). Also indicate if patch is intended to resolve bug report or further work is required.<br />
<br />
== Committers ==<br />
<br />
The [http://www.eclipse.org/projects/dev_process/Eclipse_Standard_TopLevel_Charter_v1.0.php Eclipse Charter] explains how developers can gain commit rights.<br />
<br />
=== Participation ===<br />
Committers should:<br />
* Sign up for all of the project mailing lists.<br />
* Read the newsgroup regularly, and respond to posts in their area of expertise.<br />
* Respond to mylar-dev email in their area of expertise.<br />
* Watch and update all wiki pages related to components that they contribute to.<br />
<br />
=== Communication ===<br />
Mylar committers are required to follow these communication guidelines. Our philosophy is that '''the user is always right''', even if it takes time to figure out how or why they are right. Our project thrives on the feedback of users, whether they are seasoned experts or newbies. Feedback defines how the tool should work, how it should be simplified, and how it should evolve. <br />
<br />
* All feedback contains information, and it is the responsibility of committers to turn that information into actions. This can mean improving the implementation, simplifying the workflow, clarifying the documentation, or noting a duplicate request. Making the actions we take clear helps communicate this philosophy to our growing user community and encourages high-quality feedback.<br />
<br />
* If users do not provide enough information or do not take the time to provide accurate information, they should be prompted to provide the necessary details. If they do not do so in a timely manner, the feedback is incomplete and can be resolved without taking action.<br />
<br />
* Always show respect to others in the community, whether they are making correct or incorrect assumptions about the tool or technology. When they are making incorrect assumptions it is because we have not done our job well enough, or because the platforms we build on are making it hard for us to do our job well enough. Identifying those cases is important so that we can provide feedback to those platforms and find work-arounds.<br />
<br />
* Never turn feedback or discussion away by [http://en.wikipedia.org/wiki/Flame_war#Causes_of_flaming flaming], being condescending, short, or insulting in any community communication forum. Forms of humor that work for face-to-face communication, such as sarcasm, should be avoided because they result in misinterpretation, especially when there is a language or cultural barrier. Use of emoticons is not a work-around. <br />
<br />
* Review public communication before sending. Things that are not meant to be intentionally disrespectful can come across that way. When reviewing try to shorten in order to show respect for your audience's time.<br />
<br />
=== Applying Patches ===<br />
<br />
* Make sure to update <code>mylyn-iplog.csv</code> with an entry for each bug that is resolved by patch. Note that each patch should not contain more than 250 lines of code of unique and seprately usable functionality. For larger patches we need to invoke the IP Review process.<br />
<br />
* Contributors frequently write quick patches in order to get something working for them. It is the responsibility of the committer to either encourage the contributor to improve the modularity and test coverage of the patch or to do those themselves if this aligns with the projects' priorities. Failing to do so can reduce the overall quality of the code and failing to get sufficient test coverage reduces our ability to evolve the code.<br />
<br />
=== Web site authoring ===<br />
* Create a new CVS location: :pserver:dev.eclipse.org:/cvsroot/org.eclipse<br />
* Check out www/mylar as a project <br />
* To push documentation from org.eclipse.mylar.doc to the web site use the targets in mylar/build.xml<br />
<br />
=== Building a distribution ===<br />
* Using PDE Build support to create a Mylar distribution from HEAD, using a plain Eclipse 3.2<br />
** org.eclipse.mylar-feature/feature.xml -> Overview -> change version number to current date (e.g. 0.4.7.v20060125-0800)<br />
*** On Plug-ins tab -> Versions... -> Force feature version into plug-in and fragment manifests <br />
*** Repeat above for org.eclipse.mylar-bugzilla-feature.xml <br />
** org.eclipse.mylar-site/e3.2/site.xml<br />
*** Delete old features (grayed out) <br />
*** Add new mylar-bugzilla and mylar features <br />
*** Hit Build All (if this fails restart Eclipse and try again) <br />
* To install, add the path of org.eclipse.mylar-site/e3.2/site.xml as a local update site <br />
* Bugzilla support can be built independently of the Mylar UI by checking out the following projects mylar.bugzilla.core, mylar.bugzilla.ui, mylar.tasklist, mylar.core <br />
<br />
Merging and building the 3.1 branch:<br />
* Right-click the org.eclipse.mylar.java, mylar.ide, and mylar.xml project, Team -> Switch to Another Branch..., then Refresh the Branches and select e_3_1 <br />
* The list of files that should not be overwritten is in: org.eclipse.mylar-site/merge.text <br />
Deploying:<br />
* Instructions are in org.eclipse.mylar-site/release.txt<br />
<br />
== Sandbox ==<br />
<br />
Update site: download.eclipse.org/tools/mylyn/update/dev/extras<br />
<br />
The sandbox is a set of CVS projects and feature contributors use for experimentation. These features are not intended to be used for daily development. Sandbox features include experimental connectors and bridges, experimental UI features, and developer tools. To use sandbox tools either check them out of CVS from the <code>org.eclipse.mylyn/sandbox</code> directory, or install them using the update site above. Please note that some Sandbox tools may have external dependencies, listed in a readme.txt file.<br />
<br />
=== Dev tools ===<br />
<br />
* '''Introspect Object''' (action): displays the class and other relevant information (e.g. degree-of-interest, task synchronization state) of any object visible in the workbench. Appears at the end of the context menu for any view that accepts an object contributions.<br />
<br />
* '''Interest Level Decorator''': displays the floating point interest level of elements. Enable via ''Decorators'' preference page.<br />
<br />
=== Experimental tools ===<br />
<br />
The following experimental views can be opened via the ''Mylar Sandbox'' view category or accessed via the ''Mylar -> Sandbox'' preference page.<br />
<br />
* '''Context Search''': automatically finds and displays elements that are structurally related to landmarks in the active . These elements become part of the task context and have a predicted degree-of-interest.<br />
<br />
* '''Context Hierarchy''': displays the Java hierarchy of all landmark elements.<br />
<br />
* '''Predicted interested for Java errors''': potentially useful, but tends to overload the Package Explorer. If you find this useful for long-term use condiser commenting on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=107542 bug 107542].<br />
<br />
== Tips and Tricks ==<br />
<br />
=== User support ===<br />
<br />
* Every time that you find yourself formulating an answer to a bug report, email, or newsgroup post, if the answer is more than a sentence, consider updating the FAQ, User Guide, or Integrator Reference and pointing to the entry.<br />
* Every time that resolving a bug does not result in a code change that addresses the problem or clarifies the UI, update the FAQ or User Guide to make sure that users can self-diagnose the problem. This is particularly important for bugs marked INVALID or WORKSFORME.<br />
<br />
=== Code ===<br />
<br />
* For error handling use <code>MylarStatusHandler</code>.<br />
* Use <code>WorkbenchJob</code> for running jobs that should only run when the workbench is active. Not doing this can cause errors on workbench shutdown (e.g. [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178409 bug 178409)].<br />
* When using <code>String.toLowerCase()</code>, use <code>String.toLowerCase(Locale.ENGLISH)</code> to ensure locale safety (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168652 bug 168652]).<br />
* Do not use <code>@Override</code> annotations on implementing methods, only on overriding methods. Doing so violates Java 5 ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=173171 bug 173171]).<br />
* Use DateFormat with extra caution. It is not thread-safe and should not be saved to fields in classes that can be used from multiple threads (UI, asynchonous execution, or jobs).<br />
* For the sake of multi-monitor setups, use <code>getMonitor()</code> instead of <code>getDisplay()</code> when you want to position a UI element on a specific coordinate of the screen.<br />
<br />
=== Bugzilla ===<br />
<br />
* '''Query setup''': If you are added to the cc list on a report that is not picked up by your usual queries it may go unnoticed. One trick is to create a query for ALL products except the product you usually work in (and hence have queries for) and set the cc field of the query to your id. Now you will be notified of anybody adding you to the cc of a product you don't usually monitor.<br />
<br />
=== JDT ===<br />
<br />
* '''Including Platform plug-ins in search''': Java search (Ctrl+H > Java Search) will include all plugins in your Plugin-in Dependencies. If you want to search other plugins as well, open the Plug-ins view, right click on the desired plugin(s) and choose 'Add to Java Search'. That plugin will now always be included in your java searches.<br />
<br />
=== Debugging ===<br />
<br />
* '''Plug-ins fail to load''': verify that plug-in dependencies are met via the ''Validate Plug-in Set'' button on the launch configuration ''Plug-ins'' tab.<br />
* '''Startup failure''': If you get an <code>IStartup</code> failure message or a <code>ClassNotFoundException</code> on startup this is often the result of some step in the activation of the plug-in failing.<br />
** Attempt to find the earliest exception thrown within the in the plug-in's activation process. For example, this could occur in <code>TasksUiPlugin.start()</code> or <code>TasksUiPlugin.<init></code>.<br />
** If the cause of the failure is not straightforward, the problem could be due to a class loading race condition. This can sometimes be verified by trying a different VM like IBM's or BEA's and checking if that resolves the problem. If this is the case, please file a bug.<br />
* '''Getting a thread dump''': <br />
** Run Eclipse with the <code>-debug</code> option (or use <code>java.exe</code> instead <code>javaw.exe</code> on windows), then<br />
*** On Windows: Hit a <code>Ctrl-Break</code> few times on the console window during that long synchronization to capture the thread dump<br />
*** On Linux: Use <code>Ctrl-\</code> on the console or send SIG_QUIT signal: <code>kill -SIGQUIT ''pid''</code><br />
** Use <code>[http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jps.html jps]</code> to find the PIDs of Java processes and <code>[http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jstack.html jstack]</code> to show the stack trace of Java processes: <code>jstack ''pid''</code><br />
*** Supported starting JDK 5 for UNIX / JDK 6 for Windows<br />
** See this [http://blogs.sun.com/alanb/entry/jstack Weblog on jstack]<br />
** Also see [http://weblogs.java.net/blog/mandychung/archive/2005/11/thread_dump_and_1.html Thread Dump and Concurrency Locks] for more details.<br />
* '''Startup problems and deadlocks''': for a diagnosis of a potential problem see diagnosis on https://bugs.eclipse.org/bugs/show_bug.cgi?id=177048#c3<br />
<br />
=== Migrating Eclipse milestones ===<br />
<br />
To migrate between Eclipse 3.3M4 and 3.3M5 (as of I20070205-1824):<br />
<br />
* Get latest milestone or integration build: http://download.eclipse.org/eclipse/downloads/<br />
<br />
* Unzip two copies of it, one for bootstrapping and one for setting as your Target Platform in your bootstrap workspace. If you get two workspaces when you launch a test workspace, delete the "configuration" directory of the Target Platform. Note this bug may be fixed by<br />
3.3M5 ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172975 bug 172975]).<br />
<br />
* To synch you may need to delete the known_hosts file if CVS connections were failing (file path is in: ''Preferences -> Team -> CVS -> SSH2..'').<br />
<br />
* After synching, if you get conflicts in the .settings folder after launching override them (happens because CVS version was updated, and your own was automatically migrated). <br />
<br />
* As usual, update your repository credentials in the Task Repositories view.<br />
<br />
* Note that you may need to re-create your launch configurations.</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=Mylyn&diff=48304Mylyn2007-08-28T12:51:37Z<p>Techtonik.php.net: /* Mylyn Development */ + update ViewVC links</p>
<hr />
<div>= Mylyn Development =<br />
See also: [http://eclipse.org/mylyn Mylyn Homepage], [[Mylyn FAQ | FAQ]], [[Mylyn User Guide | User Guide]], [https://dev.eclipse.org/mailman/listinfo/mylyn-dev Dev Mailing List], [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.mylyn/?root=Tools_Project ViewVC], [http://dev.eclipse.org/viewcvs/index.cgi/www/mylyn/?root=Eclipse_Website ViewVC for Mylyn Web], [[API Central]], [[Go_to_3.x_updates | Visual Design]]<br />
<br />
==== Planning====<br />
* [[Mylyn Meetings | Meetings]]<br />
* [[Mylyn 3.0 Plan]], <s>[[Mylyn 2.0 Plan | 2.0 Plan]]</s><br />
<br />
==== Developer Reference ====<br />
* [[Mylyn Architecture | Architecture Overview]]<br />
* [[Mylyn Contributor Reference | Contributor Reference]]: workspace setup, contributing patches, conventions<br />
* [[Mylyn Integrator Reference | Integrator Reference]]: building on and integrating with Mylyn<br />
* [[Mylyn Porting Guide | Porting Guide]]: porting from 1.0 to 2.0<br />
* [[Mylyn UI Nits | Mylyn UI Nits]]: collection of problems and proposed improvements<br />
* [[Mylyn Focused UI Design | Focused UI Design]]<br />
* [[Mylyn Testing | Testing]]<br />
<br />
==== Connectors ====<br />
* [[Mylyn Bugzilla Connector | Bugzilla Connector]]<br />
* [[Mylyn Jira Connector | Jira Connector]]<br />
* [[Mylyn Trac Connector | Trac Connector]]<br />
<br />
==== Sandbox ====<br />
* [[Mylyn Zest Visualization|Zest Viz Toolkit]]<br />
<br />
==== Google Summer of Code 2007 ====<br />
<br />
* [[Improve Mylyn's new users experiences]]<br />
* [[Mylyn Plugin for DrProject]]<br />
* [[Mylyn synchronous context sharing, based on Mylyn and ECF integration]]<br />
<br />
==== Community ====<br />
* [[Mylyn Extensions | Extensions Listing]]: add your tool if building on Mylyn<br />
* [[Mylyn Contribution Ideas | Contribution Ideas]]: for those interested in contributing to the project<br />
* [[Mylyn Related Research Projects | Related Research Projects]]: listing of research projects building on or using Mylyn<br />
* [[Mylyn Conference Submissions | Conference Submissions]]: listing of abstracts<br />
* [[Mylyn Monitor Usage Statistics | Mylyn Monitor Usage Statistics]]: live Eclipse and Mylyn usage statistics<br />
<br />
==== Archives ====<br />
* [http://code.google.com/soc/ Google Summer of Code 2006]: [[Mylyn Bugzilla Connector Enhancements|Bugzilla Enhancements]] by Jeff Pound, [[Mylyn Trac Connector|Trac Connector]] by Steffen Pingel<br />
<br />
==== Artwork ====<br />
* [[Mylyn Artwork | Artwork]]<br />
<br />
[[Category:Mylyn]]<br />
[[Category:Tools Project]]</div>Techtonik.php.nethttps://wiki.eclipse.org/index.php?title=Talk:CDT/Obsolete/Movies&diff=27859Talk:CDT/Obsolete/Movies2007-02-20T07:17:37Z<p>Techtonik.php.net: </p>
<hr />
<div>Seems like Camtasia has problems downloading 22Mb from eclipse.org Is it possible to provide downloadable movie? For example on http://video.google.com/ ? --[[User:Techtonik.php.net|techtonik]] 02:17, 20 February 2007 (EST)</div>Techtonik.php.net