https://wiki.eclipse.org/api.php?action=feedcontributions&user=Steffen.pingel.eclipse.org&feedformat=atomEclipsepedia - User contributions [en]2024-03-28T12:25:35ZUser contributionsMediaWiki 1.26.4https://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=62536Mylyn/Meetings2007-11-20T17:51:57Z<p>Steffen.pingel.eclipse.org: /* Tuesday, November 20, 10-11am PT */</p>
<hr />
<div>[[Category:Mylyn]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
[[Mylyn Meetings Archive]]<br />
<br />
=== Pending Discussion Items ===<br />
<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
* Standardize hyperlinking strategy for the Task Editor (Eugene) {{bug|203399}} <br />
* Active task and working set presentation/switching when Task List is not visible<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, November 20, 10-11am PT ====<br />
<br />
Agenda:<br />
* Usability issues with password prompting {{bug|207654}} (Steffen)<br />
* Patch applying policy (Mik)<br />
* Mentoring policy (Mik)<br />
* Tooltips design discussion<br />
* Task editor scalability UI discussion <br />
* Mylyn 2.2 planning (Mik)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
<br />
=== Past Meetings ===<br />
<br />
==== Thursday, November 15, 10-11am PT ====<br />
<br />
Agenda:<br />
* Usability issues with password prompting {{bug|207654}} (Steffen)<br />
* Arbitrary attributes discussion {{bug|199818}} (Eugene)<br />
* Templates in the task editor {{bug|201028}} (Eugene)<br />
* Numerous issues with filtering/quick unfiltering in the Package Explorer (Eugene)<br />
<br />
==== Tuesday, November 6, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn Monitor and concept of a Feedback Agent (zx)<br />
* Mylyn 3.0 planning (Mik)<br />
* Eclipse 3.2 and Mylyn 2.0 compatibility and support {{bug|205995}}, {{bug|205995}}<br />
* Manage New & Noteworthy items (Steffen)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
<br />
==== Tuesday, October 30, 10-11am PT ====<br />
<br />
Agenda:<br />
* Apache JIRA problem, {{bug|205963}}<br />
* Mylyn 3.0 planning (Mik)<br />
** Flagging pending API changes in the code (Steffen)<br />
* Manage New & Noteworthy items (Steffen)<br />
* Mylyn Monitor and concept of a Feedback Agent (zx)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Subtasks and incoming decoration mess (Eugene)<br />
* Overuse of "please fill a new bug for this" (Eugene)<br />
<br />
Minutes:<br />
* Steffen will document tags on wiki adding a tag (API30) for documenting changes proposed for 3.0 (since referencing wiki all the time is difficult)<br />
* <s>Rob to gather all subtask/incoming related bugs under one master bug report</s> {{bug|208089}}<br />
* <s>Rob to create bug report for prototypeing single viewer based editor</s> {{bug|208061}}<br />
* <s>Rob to create bug report to delay synchronization (15s proposed)</s> {{bug|208063}}<br />
<br />
==== Tuesday, October 23, 10-11am PT ====<br />
<br />
Agenda:<br />
* Apache JIRA problem, {{bug|205963}}<br />
* allow to configure labels in the task list {{bug|199345}} (Eugene)<br />
* UI and mechanism for pushing task active time to repository {{bug|205218}} (Helen)<br />
* Design discussion of ''Task Editor'' layout (Mik, Rob)<br />
* Design discussion for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Mylyn 3.0 planning (Mik)<br />
<br />
Minutes:<br />
<br />
XPlanner Time Tracking<br />
* Timing related fields shouldn't be in custom editor, ideally left in Planning Editor<br />
* Need ability to query date ranges for task activity<br />
* Provide report on time tracking based on task search (deprecate task activity report?)<br />
<br />
Task List and editors<br />
* Rob will reduce number of comments visisble and lazy load uninteresting {{bug|206568}}<br />
* Mik to post patch for task overdue simplification<br />
* Mik to comment on Eugene's custom attributes bug.<br />
<br />
Configuration refresh options discussed<br />
* Manual, User Configurable, Semi-auto (detect if large repository, if so require manual)<br />
<br />
==== Tuesday, October 16, 10-11am PT ====<br />
<br />
Agenda:<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* UI and mechanism for pushing task active time to repository {{bug|205218}} (Helen)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Mylyn 3.0 planning (Mik)<br />
* Discussions in bug reports (Eugene)<br />
<br />
==== Tuesday, October 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 3.0 planning (Mik)<br />
* Summary bug view / quick viewing of bug reports design discussion: {{bug|205669}} (Steffen)<br />
* Design discussion - bugzilla cached configuration (Rob)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
<br />
<br />
==== Tuesday, October 2, 10-11am PT ====<br />
<br />
Agenda:<br />
* 2.1 release review (Mik)<br />
* Eclipse.org bandwidth usage {{bug|196056}} {{bug|205213}} (Rob)<br />
* XPlanner update (Helen)<br />
* 3.0 plan review and bug triage (all)<br />
* Mylyn connector for mingle (Ketan)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 25, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 2.1, Europa Fall Update and Ganymede status and review of remaining items (Mik)<br />
* Update sites, linking and download redesign (Mik) {{bug|194469}}<br />
* Sandbox quality bar and policy for inclusion of features for discoverable sites in Europa Fall Update (Mik) {{bug|204560}}<br />
* Subtasks being enabled by default for Bugzilla and corresponding policies (Rob, Mik, Eugene)<br />
** artificial "grouping" vs. showing subtasks<br />
* JIRA update (Steffen)<br />
* XPlanner update (Helen)<br />
<br />
Minutes:<br />
* Update site should include historical builds as part of archive<br />
* Subtask setting to be renamed<br />
<br />
==== Tuesday, September 18, 10-11am PT ====<br />
<br />
Agenda:<br />
* Policy for adding stuff to the Sandbox, i.e. group by scheduled vs. "out of nowhere" "Incoming (Experimental)" presentation (Eugene)<br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* 3.0 planning (Mik)<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 11, 10-11am PT ====<br />
<br />
Agenda: <br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* Policy for making significant changes to open bugs' status, e.g. marking for bugday (Mik)<br />
* 3.0 planning (Mik)<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Arbitrary attributes discussion {{bug|199818 }}<br />
* Summary bug view / quick viewing of bug reports design discussion<br />
* Design discussion - bugzilla cached configuration <br />
<br />
Minutes:<br />
----<br />
<br />
<br />
==== Tuesday, September 4, 10-11am PT ====<br />
<br />
Agenda: <br />
* Missed BugDay<br />
* Summer of Code wrap-up (Jevgeni, Xiaoyang, Balazs)<br />
* Policy: <br />
** Resolving bug reports (Rob)<br />
** Reopening closed reports, i.e. AllTasks fails (Eugene)<br />
* Design discussion - bugzilla cached configuration<br />
* 2.1 and 3.0 Planning (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
<br />
Minutes:<br />
<br />
* Bug Day<br />
** We will participate in Bug Day<br />
** Need to continute to maintain/label bug day bugs<br />
** Must maintain calendar of bug day events and send announcemnts to newsgroup/mailing lists <br />
** Eugne willing to mentor on bug days<br />
<br />
*Policy<br />
** Contributions (patches) must be accompanied with summary of issues addressed by provided patch. Must also indicate if patch is intended to resolve bug report or further work required. (Rob will update Contributor Reference) <br />
** Reopening closed reports not encouraged. Mik will resolve bug#152869 - creating bugs from failed unit tests for 2.1<br />
<br />
* Builds<br />
** RC builds, dev builds as weekly milestone builds (Mik to send proposal to newsgroup to get feedback from community on this proposed change)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=61643Mylyn/Meetings2007-11-16T01:18:03Z<p>Steffen.pingel.eclipse.org: </p>
<hr />
<div>[[Category:Mylyn]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
[[Mylyn Meetings Archive]]<br />
<br />
=== Pending Discussion Items ===<br />
<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
* Active task and working set presentation/switching when Task List is not visible<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, November 20, 10-11am PT ====<br />
<br />
Agenda:<br />
* Usability issues with password prompting {{bug|207654}} (Steffen)<br />
* Bug triage (Steffen)<br />
<br />
=== Past Meetings ===<br />
<br />
==== Thursday, November 15, 10-11am PT ====<br />
<br />
Agenda:<br />
* Usability issues with password prompting {{bug|207654}} (Steffen)<br />
* Arbitrary attributes discussion {{bug|199818}} (Eugene)<br />
* Templates in the task editor {{bug|201028}} (Eugene)<br />
* Numerous issues with filtering/quick unfiltering in the Package Explorer (Eugene)<br />
<br />
==== Tuesday, November 6, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn Monitor and concept of a Feedback Agent (zx)<br />
* Mylyn 3.0 planning (Mik)<br />
* Eclipse 3.2 and Mylyn 2.0 compatibility and support {{bug|205995}}, {{bug|205995}}<br />
* Manage New & Noteworthy items (Steffen)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
<br />
==== Tuesday, October 30, 10-11am PT ====<br />
<br />
Agenda:<br />
* Apache JIRA problem, {{bug|205963}}<br />
* Mylyn 3.0 planning (Mik)<br />
** Flagging pending API changes in the code (Steffen)<br />
* Manage New & Noteworthy items (Steffen)<br />
* Mylyn Monitor and concept of a Feedback Agent (zx)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Subtasks and incoming decoration mess (Eugene)<br />
* Overuse of "please fill a new bug for this" (Eugene)<br />
<br />
Minutes:<br />
* Steffen will document tags on wiki adding a tag (API30) for documenting changes proposed for 3.0 (since referencing wiki all the time is difficult)<br />
* <s>Rob to gather all subtask/incoming related bugs under one master bug report</s> {{bug|208089}}<br />
* <s>Rob to create bug report for prototypeing single viewer based editor</s> {{bug|208061}}<br />
* <s>Rob to create bug report to delay synchronization (15s proposed)</s> {{bug|208063}}<br />
<br />
==== Tuesday, October 23, 10-11am PT ====<br />
<br />
Agenda:<br />
* Apache JIRA problem, {{bug|205963}}<br />
* allow to configure labels in the task list {{bug|199345}} (Eugene)<br />
* UI and mechanism for pushing task active time to repository {{bug|205218}} (Helen)<br />
* Design discussion of ''Task Editor'' layout (Mik, Rob)<br />
* Design discussion for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Mylyn 3.0 planning (Mik)<br />
<br />
Minutes:<br />
<br />
XPlanner Time Tracking<br />
* Timing related fields shouldn't be in custom editor, ideally left in Planning Editor<br />
* Need ability to query date ranges for task activity<br />
* Provide report on time tracking based on task search (deprecate task activity report?)<br />
<br />
Task List and editors<br />
* Rob will reduce number of comments visisble and lazy load uninteresting {{bug|206568}}<br />
* Mik to post patch for task overdue simplification<br />
* Mik to comment on Eugene's custom attributes bug.<br />
<br />
Configuration refresh options discussed<br />
* Manual, User Configurable, Semi-auto (detect if large repository, if so require manual)<br />
<br />
==== Tuesday, October 16, 10-11am PT ====<br />
<br />
Agenda:<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* UI and mechanism for pushing task active time to repository {{bug|205218}} (Helen)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Mylyn 3.0 planning (Mik)<br />
* Discussions in bug reports (Eugene)<br />
<br />
==== Tuesday, October 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 3.0 planning (Mik)<br />
* Summary bug view / quick viewing of bug reports design discussion: {{bug|205669}} (Steffen)<br />
* Design discussion - bugzilla cached configuration (Rob)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
<br />
<br />
==== Tuesday, October 2, 10-11am PT ====<br />
<br />
Agenda:<br />
* 2.1 release review (Mik)<br />
* Eclipse.org bandwidth usage {{bug|196056}} {{bug|205213}} (Rob)<br />
* XPlanner update (Helen)<br />
* 3.0 plan review and bug triage (all)<br />
* Mylyn connector for mingle (Ketan)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 25, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 2.1, Europa Fall Update and Ganymede status and review of remaining items (Mik)<br />
* Update sites, linking and download redesign (Mik) {{bug|194469}}<br />
* Sandbox quality bar and policy for inclusion of features for discoverable sites in Europa Fall Update (Mik) {{bug|204560}}<br />
* Subtasks being enabled by default for Bugzilla and corresponding policies (Rob, Mik, Eugene)<br />
** artificial "grouping" vs. showing subtasks<br />
* JIRA update (Steffen)<br />
* XPlanner update (Helen)<br />
<br />
Minutes:<br />
* Update site should include historical builds as part of archive<br />
* Subtask setting to be renamed<br />
<br />
==== Tuesday, September 18, 10-11am PT ====<br />
<br />
Agenda:<br />
* Policy for adding stuff to the Sandbox, i.e. group by scheduled vs. "out of nowhere" "Incoming (Experimental)" presentation (Eugene)<br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* 3.0 planning (Mik)<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 11, 10-11am PT ====<br />
<br />
Agenda: <br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* Policy for making significant changes to open bugs' status, e.g. marking for bugday (Mik)<br />
* 3.0 planning (Mik)<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Arbitrary attributes discussion {{bug|199818 }}<br />
* Summary bug view / quick viewing of bug reports design discussion<br />
* Design discussion - bugzilla cached configuration <br />
<br />
Minutes:<br />
----<br />
<br />
<br />
==== Tuesday, September 4, 10-11am PT ====<br />
<br />
Agenda: <br />
* Missed BugDay<br />
* Summer of Code wrap-up (Jevgeni, Xiaoyang, Balazs)<br />
* Policy: <br />
** Resolving bug reports (Rob)<br />
** Reopening closed reports, i.e. AllTasks fails (Eugene)<br />
* Design discussion - bugzilla cached configuration<br />
* 2.1 and 3.0 Planning (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
<br />
Minutes:<br />
<br />
* Bug Day<br />
** We will participate in Bug Day<br />
** Need to continute to maintain/label bug day bugs<br />
** Must maintain calendar of bug day events and send announcemnts to newsgroup/mailing lists <br />
** Eugne willing to mentor on bug days<br />
<br />
*Policy<br />
** Contributions (patches) must be accompanied with summary of issues addressed by provided patch. Must also indicate if patch is intended to resolve bug report or further work required. (Rob will update Contributor Reference) <br />
** Reopening closed reports not encouraged. Mik will resolve bug#152869 - creating bugs from failed unit tests for 2.1<br />
<br />
* Builds<br />
** RC builds, dev builds as weekly milestone builds (Mik to send proposal to newsgroup to get feedback from community on this proposed change)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=61614Mylyn/Porting Guide2007-11-15T22:10:00Z<p>Steffen.pingel.eclipse.org: /* New Tasks API */</p>
<hr />
<div>[[Category:Mylyn]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from 1.0 to 2.0 =<br />
<br />
See the <b>[[Mylyn Porting Guide 2.0]]</b><br />
<br />
= Porting from 2.0 to 3.0 =<br />
<br />
There is currently no need to port Mylyn from the 2.0 APIs since current Mylyn releases are backwards compatible. Throughout the 2.x release cycle we will be using this wiki to gather changes and suggestions for improving the APIs for 3.0.<br />
<br />
<br />
== Pending Changes for Mylyn 3.0 == <br />
Also see all tags of "API-3.0"<br />
* Rename <code>AbstractRepositoryQuery.getRepositoryKind()</code> to <code>AbstractRepositoryQuery.getConnectorKind()</code><br />
* Rename <code>IMylarMonitorLifecycleListener</code> to <code>IMonitorLifecycleListener</code><br />
* Rename <code>MockRepositoryTask</code> to <code>MockTask</code><br />
* Refactor <code>TaskActivationHistory</code> into a <code>TaskActivityManager</code> that encapsulates both activity monitoring and activation history<br />
** Remove all deprecated methods from TaskListManager<br />
* <code>AbstractTaskListPresentation</code>: make API, remove coupling to <code>TaskListView</code><br />
* <code>TaskGroup</code> and <code>TaskCategory</code>: consider for API, refactor or combine<br />
* consider merging <code>TaskList.removeFromCategory()</code> and <code>TaskList.removeFromQuery()</code><br />
* Deprecate <code>WebClientUtil.getPlatformProxy()</code><br />
* Move <code>TasksUiPlugin.getIncomingNotification(..)</code> and related private classes<br />
* <code>AbstractTask.setCompleted()</code> needs changing, it has the problematic side effect of setting the completion date to the current time. {{bug|203875}}<br />
* Remove <code>AbstractInterestManipulationAction.isRemove()</code>: deprecated<br />
* Make <code>IMonitoredWindow</code> API and put alongside <code>IContextAwareEditor</code><br />
* merge <code>AbstractRepositoryTaskEditor.createAttributeSection</code> into <code>createAttributeLayout()</code><br />
* Make API: <code>InteractionContextScaling</code><br />
* Rename <code>AbstractTask.RepositoryTaskSyncState</code> to <code>AbstractTask.SyncState</code> ("sync" is used commonly enough that we should be able to standardize on it in the API, replacing "synchronization/synchronize" where applicable).<br />
* Add <code>InteractionContextScaling</code> parameter to <code>IInteractionContextReader.readContext(..)</code><br />
* Make a subset of <code>InteractionContextManager</code> API.<br />
* Make <code>AbstractContextUiPlugin</code> API.<br />
* Make <code>TaskRepository.getUserName()</code>, <code>getHttpUser</code> and <code>getProxyUsername</code> consistent<br />
* Move highlighters stuff out of <code>ContextUiPlugin</code><br />
* Rename <code>AbstractRepositoryTaskEditor.SECTION_NAME.ATTRIBTUES_SECTION</code> ({{bug|208629}})<br />
<br />
== New Tasks API == <br />
<br />
* <code>AbstractEditQueryWizard</code><br />
** <code>getQuerySummary()</code>: added<br />
<br />
* <code>AbstractRepositoryConnector</code><br />
** <code>isRepositoryConfigurationStale(TaskRepository)</code> has been added<br />
<br />
* <code>AbstractRepositoryConnectorUi</code><br />
** <code>getNewTaskWizard(TaskRepository, TaskSelection)</code> has been added<br />
<br />
* <code>AbstractRenderingEngine</code> has been added for converting Wiki syntax to HTML<br />
<br />
* <code>AbstractRepositoryQueryPage</code><br />
** <code>setControlsEnabled(...)</code>: added - override to perform finer grain enablements if necessary<br />
<br />
* <code>AbstractRepositoryTaskEditor</code> has been extended to provide HTML preview capabilities for repositories that support Wiki syntax in ticket descriptions and comments<br />
** <code>addSelectableControl()</code>: added<br />
** <code>createReplyHyperlink()</code> is now protected (was private)<br />
** <code>DescriptionListener</code> is now protected (was private)<br />
** <code>getParentEditor()</code>: added<br />
** <code>getRenderingEngine()</code>: added<br />
** <code>removeSelectableControl()</code>: added<br />
** <code>fillToolBar(..)</code>: added<br />
<br />
* <code>AbstractUserActivityMonitor</code><br />
** <code>isEnabled()</code>: added<br />
** <code>getOriginId()</code>: added<br />
** <code>getStructureKind()</code>: added<br />
** <code>getStructureHandle()</code>: added<br />
<br />
* <code>AbstractTaskDataHandler</code><br />
** <code>cloneTaskData(RepositoryTaskData, RepositoryTaskData)</code>: added<br />
<br />
* <code>RepositoryTaskAttribute</code><br />
** task.common.user.reporter.name : added : key for full name of issue reporter<br />
** task.common.comment.author.name : added : key for full name of comment author<br />
** task.common.user.assigned.name : added : key for full name of issue assignee<br />
<br />
* <code>TaskEditor</code><br />
** class no longer final (experimental extensibility)<br />
<br />
* <code>TaskListManager</code><br />
** <code>resolveIdentifiersConflict()</code>: added<br />
** <code>removeFromQuery()</code>: added<br />
<br />
* <code>TaskSelection</code> has been added<br />
<br />
* <code>TaskTextViewerConfiguration</code> has been added (former name was RepositoryViewerConfig)<br />
<br />
== New Context API ==<br />
<br />
* <code>AbstractFocusViewAction.updateEnablementWithContextActivation()</code>: override to return false for focus actions that are not related to context activations (e.g. the Task List).<br />
<br />
* <code>AbstractFocusViewAction.setLinkingActionEnabled(boolean)</code>: should be overridden if view provides linking<br />
<br />
* <code>InteractionContextScaling.getScaling()</code>: new method, prevoiusly on subtype only<br />
<br />
== New Montior API ==<br />
<br />
* <code>MonitorUiPlugin.getMonitoredWindows()</code>: use insteand of <code>PlatformUI.getWorkbench().getWorkbenchWindows()</code><br />
* <code>MonitorUiPlugin.getLaunchingWorkbenchWindow()</code>: use to get the first active window when the monitor started.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/JIRA_Connector&diff=60164Mylyn/JIRA Connector2007-11-09T03:48:54Z<p>Steffen.pingel.eclipse.org: </p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
== Info ==<br />
* [[Mylar FAQ#JIRA_Connector | JIRA Connector FAQ]]<br />
* [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&component=Jira&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&cmdtype=doit Open Bugs]<br />
<br />
== Themes ==<br />
<br />
Themes for the [[Mylyn 3.0 Plan | Mylyn 3.0]] and Eclipse Ganyemede release cycle. Listed in order of priority.<br />
<br />
* '''Support the user community''': Maintain responsiveness to and prioritization of the [https://bugs.eclipse.org/bugs/buglist.cgi?short_desc_type=allwordssubstr&short_desc=&product=Mylar&component=Jira&long_desc_type=allwordssubstr&long_desc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&order=Importance open bugs].<br />
<br />
* '''Improve Test Suite''': Unit test coverage is currently inadequate and should match that of the Bugzilla and Trac connectors.<br />
<br />
* '''Extend Rich UI''': Need support for additional features such as custom attributes, issue history, votes and watches.<br />
<br />
* '''Integrate time tracking''': Mylyn provides task timing values and these should be integrated with JIRA time and scheduling ({{bug|173880}}).<br />
<br />
* '''Enhance workflow integration''': Support workflows beyond comment/attribute/attachment submission.<br />
<br />
* '''Improve comment display and editing''': Support for HTML display, editing, and visibility.<br />
<br />
* '''Improve representation of subtasks and dependencies''': Associations between tasks should be visible and navigable from the task editor.<br />
<br />
* '''Improve documentation''': User guide and FAQ should be updated and include screenshots.<br />
<br />
<br />
== JIRA Remote API Needs ==<br />
<br />
=== Critical ===<br />
<br />
The following are needed for the completeness or correctness of connector behavior.<br />
<br />
<s><br />
* Retrieve available workflow actions and operations for issue (based on issue type, status, current user etc).<br />
** JonathanNolen: IssueServiceImpl.getAvailableActions() already exists, according to the docs. Will this work?<br />
** SteffenPingel: That has been implemented and works.<br />
</s><br />
<br />
* Retrieve all details about custom fields from the project configuration, including values of select/multi-select/radio fields and mandatory fields required for creating new issue.<br />
** JonathanNolen: Can't find this in the docs, may need to be developed.<br />
** EK: we also need to know if field is not supposed to be shown and/or edited in the UI<br />
<br />
* Retrieve available actions for each comment (edit, delete, change visibility etc) and required metadata (i.e. list of values for selecting who can see comment).<br />
** JonathanNolen: Getting available actions on the comments doesn't seem to be available, may need to be developed. On the other hand, the JIRA API will only return to you comments that are visible by the user making the request. It shouldn't be something that Mylar needs to determine on its own.<br />
** EK: yes, but when we are adding comment we need to set visibility and for those visible comments it would be a good idea to show to whom that comment is addressed to.<br />
<br />
* Investigate if the performance of queries can be improved. It seems that results in XML format are delivered much slower than query results in the web interface ({{bug|196288}})<br />
<br />
* Investigate the overhead/performance of the XML-RPC vs. SOAP interface ({{bug|205963}}) to reduce the load on JIRA repositories.<br />
<br />
=== High Priority ===<br />
<br />
The following are needed for the completeness of the rich UI.<br />
<br />
* Retrieve and update dependencies, links and subtasks (links, etc should be present on the Issue object)<br />
<br />
* Retrieve and update votes (number of votes and whether or not the current user has voted should be present on the Issue object)<br />
<br />
* Update watch/CC status of the issue given the current user (should be present on the Issue object)<br />
<br />
* Update watch/unwatch status of an issue during an update by setting/unsetting the watched flag on the issue (allows us to reassign an issue, but continue to watch it with one call)<br />
<br />
* Retrieve issue history <br />
<br />
* Update time tracking info <br />
<br />
* Retrieve and update attachments<br />
<br />
=== Low Priority ===<br />
<br />
The following will enhance the user experience or connector implementation.<br />
<br />
* Service to get wiki macro details (for rich text editing and autocompletion)<br />
** Is it a block macro<br />
** Does it have parameters, if so, what values are possible<br />
<br />
* Service to get RPC api version (need to call this before calling anything else) - could be added to the existing getServerInfo service<br />
** We actually need to support RPC plugin versions, not Jira versions. Currently we just guess the rpc version based on the Jira version<br />
<br />
* Retrieving screen layouts given issue type, project and action (for editing custom fields on workflow transition)<br />
<br />
* Submitting query/filter and only getting keys back (not issues+comments).<br />
<br />
* Service to get issue summaries (everything but the comments) given a set of issue keys (for populating search results page at a time)<br />
<br />
* Service to get all server configuration at once (Projects/Components/Versions)<br />
<br />
* Service to get server "customization" settings (is voting enabled, attachments allowed, etc...) - currently admin only<br />
** This is needed to disable operations that are not enabled on the server<br />
<br />
* Service to get all 'meta' information at once (issue types, issue statuses, ProjectCategory, etc) - any configurable objects that apply across projects<br />
<br />
* Project object should say what category it belongs to (if any)<br />
<br />
* Service to search for issues - model this after the core services search method? ie. object based query<br />
<br />
** Allow searching by voting and watch status (I don't think these are currently stored in the GenericValue object, so aren't indexed by Lucene)<br />
** Allow searches to be saved as named queries<br />
<br />
* Service to search for users - like the issue search, just return IDs and let the caller get the details<br />
<br />
* Service to search for groups<br />
<br />
* Provide all services in wrapped doc/literal format to be WS-I compliant. Some toolkits such as XFire only support Doc/Literal web services</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=59846Mylyn/Meetings2007-11-08T00:35:00Z<p>Steffen.pingel.eclipse.org: </p>
<hr />
<div>[[Category:Mylyn]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
[[Mylyn Meetings Archive]]<br />
<br />
=== Pending Discussion Items ===<br />
<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
* Active task and working set presentation/switching when Task List is not visible<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, November 13, 10-11am PT ====<br />
<br />
Agenda:<br />
* Usability issues with password prompting {{bug|207654}} (Steffen)<br />
<br />
=== Past Meetings ===<br />
<br />
==== Tuesday, November 6, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn Monitor and concept of a Feedback Agent (zx)<br />
* Mylyn 3.0 planning (Mik)<br />
* Eclipse 3.2 and Mylyn 2.0 compatibility and support {{bug|205995}}, {{bug|205995}}<br />
* Manage New & Noteworthy items (Steffen)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
<br />
==== Tuesday, October 30, 10-11am PT ====<br />
<br />
Agenda:<br />
* Apache JIRA problem, {{bug|205963}}<br />
* Mylyn 3.0 planning (Mik)<br />
** Flagging pending API changes in the code (Steffen)<br />
* Manage New & Noteworthy items (Steffen)<br />
* Mylyn Monitor and concept of a Feedback Agent (zx)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Subtasks and incoming decoration mess (Eugene)<br />
* Overuse of "please fill a new bug for this" (Eugene)<br />
<br />
Minutes:<br />
* Steffen will document tags on wiki adding a tag (API30) for documenting changes proposed for 3.0 (since referencing wiki all the time is difficult)<br />
* <s>Rob to gather all subtask/incoming related bugs under one master bug report</s> {{bug|208089}}<br />
* <s>Rob to create bug report for prototypeing single viewer based editor</s> {{bug|208061}}<br />
* <s>Rob to create bug report to delay synchronization (15s proposed)</s> {{bug|208063}}<br />
<br />
==== Tuesday, October 23, 10-11am PT ====<br />
<br />
Agenda:<br />
* Apache JIRA problem, {{bug|205963}}<br />
* allow to configure labels in the task list {{bug|199345}} (Eugene)<br />
* UI and mechanism for pushing task active time to repository {{bug|205218}} (Helen)<br />
* Design discussion of ''Task Editor'' layout (Mik, Rob)<br />
* Design discussion for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Mylyn 3.0 planning (Mik)<br />
<br />
Minutes:<br />
<br />
XPlanner Time Tracking<br />
* Timing related fields shouldn't be in custom editor, ideally left in Planning Editor<br />
* Need ability to query date ranges for task activity<br />
* Provide report on time tracking based on task search (deprecate task activity report?)<br />
<br />
Task List and editors<br />
* Rob will reduce number of comments visisble and lazy load uninteresting {{bug|206568}}<br />
* Mik to post patch for task overdue simplification<br />
* Mik to comment on Eugene's custom attributes bug.<br />
<br />
Configuration refresh options discussed<br />
* Manual, User Configurable, Semi-auto (detect if large repository, if so require manual)<br />
<br />
==== Tuesday, October 16, 10-11am PT ====<br />
<br />
Agenda:<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* UI and mechanism for pushing task active time to repository {{bug|205218}} (Helen)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Mylyn 3.0 planning (Mik)<br />
* Discussions in bug reports (Eugene)<br />
<br />
==== Tuesday, October 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 3.0 planning (Mik)<br />
* Summary bug view / quick viewing of bug reports design discussion: {{bug|205669}} (Steffen)<br />
* Design discussion - bugzilla cached configuration (Rob)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
<br />
<br />
==== Tuesday, October 2, 10-11am PT ====<br />
<br />
Agenda:<br />
* 2.1 release review (Mik)<br />
* Eclipse.org bandwidth usage {{bug|196056}} {{bug|205213}} (Rob)<br />
* XPlanner update (Helen)<br />
* 3.0 plan review and bug triage (all)<br />
* Mylyn connector for mingle (Ketan)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 25, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 2.1, Europa Fall Update and Ganymede status and review of remaining items (Mik)<br />
* Update sites, linking and download redesign (Mik) {{bug|194469}}<br />
* Sandbox quality bar and policy for inclusion of features for discoverable sites in Europa Fall Update (Mik) {{bug|204560}}<br />
* Subtasks being enabled by default for Bugzilla and corresponding policies (Rob, Mik, Eugene)<br />
** artificial "grouping" vs. showing subtasks<br />
* JIRA update (Steffen)<br />
* XPlanner update (Helen)<br />
<br />
Minutes:<br />
* Update site should include historical builds as part of archive<br />
* Subtask setting to be renamed<br />
<br />
==== Tuesday, September 18, 10-11am PT ====<br />
<br />
Agenda:<br />
* Policy for adding stuff to the Sandbox, i.e. group by scheduled vs. "out of nowhere" "Incoming (Experimental)" presentation (Eugene)<br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* 3.0 planning (Mik)<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 11, 10-11am PT ====<br />
<br />
Agenda: <br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* Policy for making significant changes to open bugs' status, e.g. marking for bugday (Mik)<br />
* 3.0 planning (Mik)<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Arbitrary attributes discussion {{bug|199818 }}<br />
* Summary bug view / quick viewing of bug reports design discussion<br />
* Design discussion - bugzilla cached configuration <br />
<br />
Minutes:<br />
----<br />
<br />
<br />
==== Tuesday, September 4, 10-11am PT ====<br />
<br />
Agenda: <br />
* Missed BugDay<br />
* Summer of Code wrap-up (Jevgeni, Xiaoyang, Balazs)<br />
* Policy: <br />
** Resolving bug reports (Rob)<br />
** Reopening closed reports, i.e. AllTasks fails (Eugene)<br />
* Design discussion - bugzilla cached configuration<br />
* 2.1 and 3.0 Planning (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
<br />
Minutes:<br />
<br />
* Bug Day<br />
** We will participate in Bug Day<br />
** Need to continute to maintain/label bug day bugs<br />
** Must maintain calendar of bug day events and send announcemnts to newsgroup/mailing lists <br />
** Eugne willing to mentor on bug days<br />
<br />
*Policy<br />
** Contributions (patches) must be accompanied with summary of issues addressed by provided patch. Must also indicate if patch is intended to resolve bug report or further work required. (Rob will update Contributor Reference) <br />
** Reopening closed reports not encouraged. Mik will resolve bug#152869 - creating bugs from failed unit tests for 2.1<br />
<br />
* Builds<br />
** RC builds, dev builds as weekly milestone builds (Mik to send proposal to newsgroup to get feedback from community on this proposed change)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=59245Mylyn/Porting Guide2007-11-05T18:27:59Z<p>Steffen.pingel.eclipse.org: /* Pending Changes for Mylyn 3.0 */</p>
<hr />
<div>[[Category:Mylyn]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from 1.0 to 2.0 =<br />
<br />
See the <b>[[Mylyn Porting Guide 2.0]]</b><br />
<br />
= Porting from 2.0 to 3.0 =<br />
<br />
There is currently no need to port Mylyn from the 2.0 APIs since current Mylyn releases are backwards compatible. Throughout the 2.x release cycle we will be using this wiki to gather changes and suggestions for improving the APIs for 3.0.<br />
<br />
<br />
== Pending Changes for Mylyn 3.0 == <br />
Also see all tags of "API-3.0"<br />
* Rename <code>AbstractRepositoryQuery.getRepositoryKind()</code> to <code>AbstractRepositoryQuery.getConnectorKind()</code><br />
* Rename <code>IMylarMonitorLifecycleListener</code> to <code>IMonitorLifecycleListener</code><br />
* Rename <code>MockRepositoryTask</code> to <code>MockTask</code><br />
* Refactor <code>TaskActivationHistory</code> into a <code>TaskActivityManager</code> that encapsulates both activity monitoring and activation history<br />
** Remove all deprecated methods from TaskListManager<br />
* <code>AbstractTaskListPresentation</code>: make API, remove coupling to <code>TaskListView</code><br />
* <code>TaskGroup</code> and <code>TaskCategory</code>: consider for API, refactor or combine<br />
* consider merging <code>TaskList.removeFromCategory()</code> and <code>TaskList.removeFromQuery()</code><br />
* Deprecate <code>WebClientUtil.getPlatformProxy()</code><br />
* Move <code>TasksUiPlugin.getIncomingNotification(..)</code> and related private classes<br />
* <code>AbstractTask.setCompleted()</code> needs changing, it has the problematic side effect of setting the completion date to the current time. {{bug|203875}}<br />
* Remove <code>AbstractInterestManipulationAction.isRemove()</code>: deprecated<br />
* Make <code>IMonitoredWindow</code> API and put alongside <code>IContextAwareEditor</code><br />
* merge <code>AbstractRepositoryTaskEditor.createAttributeSection</code> into <code>createAttributeLayout()</code><br />
* Make API: <code>InteractionContextScaling</code><br />
* Rename <code>AbstractTask.RepositoryTaskSyncState</code> to <code>AbstractTask.SyncState</code> ("sync" is used commonly enough that we should be able to standardize on it in the API, replacing "synchronization/synchronize" where applicable).<br />
* Add <code>InteractionContextScaling</code> parameter to <code>IInteractionContextReader.readContext(..)</code><br />
* Make a subset of <code>InteractionContextManager</code> API.<br />
* Make <code>AbstractContextUiPlugin</code> API.<br />
* Make <code>TaskRepository.getUserName()</code>, <code>getHttpUser</code> and <code>getProxyUsername</code> consistent<br />
* Move highlighters stuff out of <code>ContextUiPlugin</code><br />
* Rename <code>AbstractRepositoryTaskEditor.SECTION_NAME.ATTRIBTUES_SECTION</code> ({{bug|208629}})<br />
<br />
== New Tasks API == <br />
<br />
* <code>AbstractEditQueryWizard</code><br />
** <code>getQuerySummary()</code>: added<br />
<br />
* <code>AbstractRepositoryConnector</code><br />
** <code>isRepositoryConfigurationStale(TaskRepository)</code> has been added<br />
<br />
* <code>AbstractRenderingEngine</code> has been added for converting Wiki syntax to HTML<br />
<br />
* <code>AbstractRepositoryQueryPage</code><br />
** <code>setControlsEnabled(...)</code>: added - override to perform finer grain enablements if necessary<br />
<br />
* <code>AbstractRepositoryTaskEditor</code> has been extended to provide HTML preview capabilities for repositories that support Wiki syntax in ticket descriptions and comments<br />
** <code>addSelectableControl()</code>: added<br />
** <code>createReplyHyperlink()</code> is now protected (was private)<br />
** <code>DescriptionListener</code> is now protected (was private)<br />
** <code>getParentEditor()</code>: added<br />
** <code>getRenderingEngine()</code>: added<br />
** <code>removeSelectableControl()</code>: added<br />
** <code>fillToolBar(..)</code>: added<br />
<br />
* <code>AbstractUserActivityMonitor</code><br />
** <code>isEnabled()</code>: added<br />
** <code>getOriginId()</code>: added<br />
** <code>getStructureKind()</code>: added<br />
** <code>getStructureHandle()</code>: added<br />
<br />
* <code>RepositoryTaskAttribute</code><br />
** task.common.user.reporter.name : added : key for full name of issue reporter<br />
** task.common.comment.author.name : added : key for full name of comment author<br />
** task.common.user.assigned.name : added : key for full name of issue assignee<br />
<br />
* <code>TaskEditor</code><br />
** class no longer final (experimental extensibility)<br />
<br />
* <code>TaskListManager</code><br />
** <code>resolveIdentifiersConflict()</code>: added<br />
** <code>removeFromQuery()</code>: added<br />
<br />
* <code>TaskTextViewerConfiguration</code> has been added (former name was RepositoryViewerConfig)<br />
<br />
== New Context API ==<br />
<br />
* <code>AbstractFocusViewAction.updateEnablementWithContextActivation()</code>: override to return false for focus actions that are not related to context activations (e.g. the Task List).<br />
<br />
* <code>AbstractFocusViewAction.setLinkingActionEnabled(boolean)</code>: should be overridden if view provides linking<br />
<br />
* <code>InteractionContextScaling.getScaling()</code>: new method, prevoiusly on subtype only<br />
<br />
== New Montior API ==<br />
<br />
* <code>MonitorUiPlugin.getMonitoredWindows()</code>: use insteand of <code>PlatformUI.getWorkbench().getWorkbenchWindows()</code><br />
* <code>MonitorUiPlugin.getLaunchingWorkbenchWindow()</code>: use to get the first active window when the monitor started.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/SOC/2006/Trac_Connector&diff=58734Mylyn/SOC/2006/Trac Connector2007-11-01T19:19:38Z<p>Steffen.pingel.eclipse.org: /* Architecture */</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 [[Mylyn 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.<br />
<br />
=== Tickets ===<br />
<br />
The Trac connector has three different ways to represent tasks:<br />
<br />
- TracTicket: this is the representations retrieved from the Trac<br />
repository. It is either created from the data received through XML-RPC or<br />
from the web interface. This is part of a generic API for accessing Trac<br />
repositories that does not depend on Mylyn (except for<br />
org.eclipse.mylyn.web.core).<br />
<br />
- TracTask: represents the task information in the task list. This is kept<br />
in memory at all times and contains information needed by Mylyn to<br />
represent the task in the UI. TracTasks are updated from TracTickets or<br />
from RepositoryTaskData (see TracRepositoryConnector.updateFrom*()).<br />
<br />
- RepositoryTaskData: used for offline editing and offline storage. Task<br />
data stores all information about a task in RepositoryTaskAttribute<br />
objects. These are used by the editor to create widgets for editing,<br />
determine incoming changes etc. RepositoryTaskData is created in<br />
TracTaskDataHandler from TracTickets.<br />
<br />
Attribute factories are used to map Mylyn's data model to a repository connector<br />
specific model. For example Mylyn uses the<br />
RepositoryTaskAttribute.USER_REPORTER key as the id for the attribute that<br />
specifies the reporter of a task which is mapped to the Trac specific key<br />
TracTicket.Key.REPORTER by TracAttributeFactory.<br />
<br />
[[Category:SOC]]</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Contributor_Reference&diff=58279Mylyn/Contributor Reference2007-10-31T17:08:36Z<p>Steffen.pingel.eclipse.org: /* Code */</p>
<hr />
<div>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 />
== Getting Started ==<br />
<br />
For ideas on how to contribute see the following lists of bugs and comment on any that interest you, or send a message to mylyn-dev on ways that you would like to get involved:<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=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=notregexp&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= bugday bugs]''': a short list of highly relevant bugs for getting started<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=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=helpwanted&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=notregexp&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]''': a longer list of all bugs targeted at community contributions<br />
<br />
=== Conventions ===<br />
<br />
All contributions to Mylyn need to be made using Mylyn since it links source changes to tasks and contexts, making open development and collaboration easier. Using Mylyn 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 />
==== Code ====<br />
<br />
Mylyn uses the Eclipse code conventions with these minor additions:<br />
<br />
* Tags: Mylyn uses the following tags in the code:<br />
{| border="0"<br />
|- <br />
| TODO || The following code needs to be reviewed. <br />
|-<br />
| XXX || The implementation uses a temporary work around that should be replaced by a proper solution in the future.<br />
|-<br />
| FIXME || Should only be used in very rare cases as a reminder that the marked code does not work as expected. Code marked as FIXME should not be distributed in a release.<br />
|-<br />
| API-3.0 || This API is going to change for version 3.0. Should include a description how it is going to change.<br />
|}<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 />
== Workspace ==<br />
<br />
The recommended way to work with Mylyn 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''. Note that to get rid of ''JRE association'' warnings you may need to download older JREs, e.g. from: http://java.sun.com/products/archive/<br />
<br />
=== Checkout ===<br />
<br />
The Mylyn 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 Mylyn, the additional projects can be deleted after the import. After the checkout you should have no errors or warnings from the Mylyn 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.x stream for Eclipse 3.4 (latest milestone)<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_3_m_2_x.psf <code>e_3_3_m_2_x</code>]: Mylyn 2.x stream for Eclipse 3.3 (branched projects updated with each release)<br />
<br />
'''End-of-life branches:'''<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_2_m_2_0.psf <code>e_3_2_m_2_0</code>]: Mylyn 2.0 stream for Eclipse 3.2 <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 (M4)<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 />
* [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 />
<br />
'''Other:'''<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-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 mylyn-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 Mylyn 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 ''Mylyn Bootstrap''.<br />
** On the ''Main'' tab, set the ''Location''<br />
*** You can use the existing workspace that you used Mylyn 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 Mylyn. 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 Mylyn, 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 <tt>org.eclipse.mylyn.monitor.core.StatusHandler</tt>. <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 />
=== Writing Tests ===<br />
<br />
Writing tests along with patches is key to ensuring that it is possible for committers to maintain the new functionality added by the patch. When writing tests look for the <code>All&lt;component&gt;Tests</code> class in the <code>tests</code> plug-in for that component, identify a test that is similar to the functionality that you are adding, and use that test as an example of how to add additional coverage. Tests can sometimes take longer to write then the change itself, but a committer will always be willing to assist you in designing the test or extending the mock test harness to make it easier to write.<br />
<br />
The key things to ensure is that your test covers is the addition or change to the existing functionality. For API changes it is often sufficient to have the public method covered. When writing tests for UI components, the simplest way of testing will often involve a combination of unit and black-box testing, for example, relying on other parts of the Mylyn UI to be set up (e.g. the Task List view). Consider the case of adding functionality for pre-selecting a repository in the New Task dialog, writing a test can take the following form (refer to <code>NewTaskWizardRepositorySelectionTest</code>):<br />
* Create a mock repository<br />
* Add a task to the mock repository<br />
* Set the selection on the Task List (new functionality uses this selection)<br />
* Invoke the wizard and assert that the selection was set correctly on the viewer (wizard is a black box, all we care about is the contents of the viewer)<br />
* Dispose the wizard dialog, remove the mock repository and the mock task<br />
<br />
When writing UI tests note that asynchrous updates, such as refresh, can make testing challenging. Note that several UI components have a method on them to set synchronous execution for the purpose of testing, and if such a method is lacking it can be added.<br />
<br />
=== Graphics ===<br />
<br />
If contributing a feature with icons or other graphics feel free to ask a committer to generate the graphic for you. If interested in contributing graphics you can find all of the source files (e.g. Photoshop) here: <code>org.eclipse.mylyn/graphics/ui</code>.<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 />
=== 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 />
Severities:<br />
* Use the Eclipse [https://bugs.eclipse.org/bugs/bug_status.html#bug_severity bug severity] conventions<br />
<br />
Keywords:<br />
* <code>helpwanted</code>: bugs that are beyond the current priorities for the project. Note that some bugs marked for an upcoming milestone can be marked as <code>helpwanted</code>. This indicates that the project committers would like to see the bug solved for the milestone and will actively contribute to a solution, but that the bug is more likely to be fixed in a timely manner with the help of additional contributors.<br />
<br />
* <code>bugday</code>: these are a special category of <code>helpwanted</code> bugs that are intended to be mast accessible or rewarding for new contributors interested in helping the project to tackle. See the [[Bug Day FAQ]] for more information. In order to keep this list focused on the most relevant bugs it is capped at 24 and should be reviewed periodically.<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 />
=== 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 />
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 />
=== Update Site ===<br />
<br />
download.eclipse.org/tools/mylyn/update/weekly/experimental<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 />
* '''Active Task Swither Trim Widget''': note that it cannot currently be disabled<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''' (when Eclipse hangs): <br />
** On Windows use the tool found at [http://www.adaptj.com/root/main/download the adaptj home page]:<br />
*** Follow the link and select button "Launch" and run the applet<br />
*** Select menu Process > Thread Dump<br />
*** In the combo box "Process ID" select the Java VM and click OK<br />
** Or, 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 />
** Or, on Linux: Use <code>Ctrl-\</code> on the console or send SIG_QUIT signal: <code>kill -SIGQUIT ''pid''</code><br />
** Or, with jconsole (requires 1.5 jdk, works on any OS):<br />
*** Launch <tt>eclipse -vmargs -Dcom.sun.management.jmxremote</tt><br />
*** Launch the JDK's jconsole tool. You can attach to the Java Process and copy&paste the thread dump. <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.<br />
<br />
[[Category:Mylyn]][[Category:How to Contribute]]</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/UI_Nits&diff=58087Mylyn/UI Nits2007-10-31T06:31:30Z<p>Steffen.pingel.eclipse.org: </p>
<hr />
<div>[[Category:Mylyn]] <br />
Use this document for UI items that are very minor or require discussion before being resolved via [http://eclipse.org/mylar/bugs.php bug reports].<br />
<br />
Bugs with a target milestone of an upcoming release should not be listed on this page.<br />
<br />
=== Naming to improve ===<br />
<br />
* Nesting of subtasks in Task List<br />
<br />
=== Visual design to improve ===<br />
<br />
* Provide overlay differentiation between Bugzilla tasks of normal status and local tasks<br />
<br />
=== Policies requiring refinement ===<br />
<br />
* Automatic addition of containers to task working sets<br />
* When to show keys/ids (currently shown in Task List, and in as few other places as possible)<br />
* When to show empty query nodes in the Task List (currently when there are no matches, to indicate that something could be wrong with the query, e.g. email changed)<br />
* Silent removal query hits without allowing user to review incoming change<br />
** ''Mik says: Eugene, I think you added this one, could you elaborate?''<br />
* Folding policy of comments and sections in the task editor<br />
<br />
=== Search/Navigation ===<br />
* Mark Landmark/Less Interesting, consider removing from navigation menu<br />
* (Why is the menu entry Less Interesting rather than Remove From Focus as in the context menu?)<br />
* If single task id entered for repository open tasks directly rather than searching<br />
* Add to tasklist needs to be available in sesarch results view (consider removing open repository task from Navigate menu)<br />
<br />
=== Preference Pages ===<br />
* Local Task Repository needs preference page (via Task Repository Settings page)<br />
* bug#192582 Restoring defaults not restoring all settings<br />
<br />
=== Colors ===<br />
<br />
* Change task editor incoming/conflict highlight color to be more pronounced.<br />
<br />
=== Task List ===<br />
* Sorting set to Summary but tasklist sorted by priority upon startup<br />
* Sub tasks should no longer be filtered by default<br />
* Add 'Defer a week' option to Schedule for context menu option<br />
* Improve layout of Find and bread crumb bar<br />
* Add Alt+Click tip to Focus on Active Task button tooltip<br />
* Consider adding Navigate actions (e.g. Open Repository Task) to Task List view menu<br />
* Due dates not currently not settable from context menu in task list<br />
* Tooltip: Synched vs. completed is confusing<br />
* Selecting a task obscures its active/inactive indicator<br />
* When a category is selected, the selection color shows through 4 pixels of the folder icon<br />
* Italicizing the active task to indicate synchronization shouldn't un-bold it<br />
* Active/inactive indicators overlap clipboards after Going Into a category<br />
* Attempting to rename query with right-click -> Rename has no effect<br />
* Right-click -> Copy Details on a local task copies "null: " prefix<br />
* Sort By and Task Presentation menus should have radio buttons, not checkboxes<br />
<br />
*Focus On Workweek Filter<br />
** Archive category has incoming decoration even if all incomings are shown in the tasklist and therefore not displayed in the archive (might only be for new hits)<br />
** Archive category filter is not restored to not applied upon unfocusing (the check beside the filter isn't there, but the archive isn't shown either). You have to toggle the archive filter to show the archive cateogry again.<br />
<br />
* Task search UI {{bug|204862}}<br />
<br />
==== Keybindings ====<br />
<br />
* F2: rename<br />
* F4: show tooltip<br />
* F5: synchronize<br />
* F6: go to next unread<br />
* Shift+F6: go to previous unread<br />
* F7: mark as read<br />
* Shift+F7: mark as unread<br />
* F8: mark as read and go to next unread<br />
* Esc: hide tooltip<br />
* Enter: open task<br />
* Ctrl+c: Copy details<br />
<br />
=== Notifications ===<br />
* Don't show notification for new bug reports submitted by user<br />
* Don't show notificaiton for new incoming if synched from editor<br />
* Local task icon in popup should not be bug icon<br />
* Investigate performance issue since taskdata now loaded upon popup show<br />
<br />
=== Task Editor ===<br />
* Reveal in tasklist missing from popup<br />
* Icon in tab of Local Task editor is repository task icon, should be local task icon<br />
* Assign to needs content assist in New Task Editor<br />
* Update Attributes option (button) should be available in Task Editor header<br />
* Render context attachments 'comments' in Bugzilla as links to activate context or thumbnails, not comments.<br />
* If the Description of a repository task is editable, no border is drawn to indicate this in the editor<br />
* The Summary text field of a repository task editor is always editable even if the repository task attribute is read only.<br />
* <font color=green> "Add To Task List" only appears in the context menu on the editor of an opened repository task if you have a category in your tasklist (can't add to root)</font> Uncategorized is now always available.<br />
* Uncategorized folder in "Add To Task List" context menu not decorated with Jar icon<br />
* Ampersand in task name misinterpreted as mnemonic in large heading<br />
* New Task -> Local Tasks -> Finish -> start typing the summary quickly; your typing is overwritten by "New Task"<br />
* If I close a new local task without saving, delete it.<br />
<br />
=== Planning Editor ===<br />
* Category selection should be available within Task Planning editor<br />
<br />
=== Bugzilla Connector ===<br />
<br />
* Search page too small with clean workspace settings?<br />
* Proxy settings section expanded when shouldn't be for new Task Repository?<br />
<br />
=== Hyperlinking ===<br />
<br />
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=146964 146964: editor hyperlink parsing problems and suggestions]<br />
<br />
* Depending on connector hyperlink detection is slightly different. Should unify so that same patters work among all connectors: bug#123, task#123, task 123, #123<br />
* Hyperlinks opening synchronously<br />
* Additional patterns:<br />
** #XXXX<br />
** attachment 12345<br />
* Comment linking [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164221 bug#164221]<br />
* bla blah JiraWebIssueService$2.execute(JiraWebIssueService.java:105): still linking preceeding text where only class:line in brackets should be linked<br />
* Hyperlinks should have the task's summary as the tooltip (Eclipse hyperlink limitation here?)<br />
* Premature hyperlink termination: http://wiki.eclipse.org/index.php/FAQ_How_do_I_hook_my_editor_to_the_Back_and_Forward_buttons%3F<br />
* Avoid spell checking hyperlinks<br />
<br />
=== Recommended Preferences ===<br />
<br />
* Automatically disable Platform URL hyperlink detector.<br />
* Remove default linking from prefs?<br />
<br />
=== Task Repositories View ===<br />
<br />
*(from bug#124321) Add properties page to Local Tasks repository that explains that it is automatically created and point to the Task List preference page which points the user at the data directory.<br />
<br />
=== Synchronization ===<br />
<br />
There should be no synchronous repository communication. Cases that could still be left:<br />
* Contact attach/retrieve.<br />
* Download of repository configuration after new bug created with no previous query.<br />
<br />
* Job name in Progress view is misspelled "Synchronizying queries"</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/UI_Nits&diff=58086Mylyn/UI Nits2007-10-31T06:30:51Z<p>Steffen.pingel.eclipse.org: /* Task List */</p>
<hr />
<div>[[Category:Mylyn]] <br />
Use this document for UI items that are very minor or require discussion before being resolved via [http://eclipse.org/mylar/bugs.php bug reports].<br />
<br />
Bugs with a target milestone of an upcoming release should not be listed on this page.<br />
<br />
=== Naming to improve ===<br />
<br />
* Nesting of subtasks in Task List<br />
<br />
=== Visual design to improve ===<br />
<br />
* Provide overlay differentiation between Bugzilla tasks of normal status and local tasks<br />
<br />
=== Policies requiring refinement ===<br />
<br />
* Automatic addition of containers to task working sets<br />
* When to show keys/ids (currently shown in Task List, and in as few other places as possible)<br />
* When to show empty query nodes in the Task List (currently when there are no matches, to indicate that something could be wrong with the query, e.g. email changed)<br />
* Silent removal query hits without allowing user to review incoming change<br />
** ''Mik says: Eugene, I think you added this one, could you elaborate?''<br />
* Folding policy of comments and sections in the task editor<br />
<br />
=== Search/Navigation ===<br />
* Mark Landmark/Less Interesting, consider removing from navigation menu<br />
* (Why is the menu entry Less Interesting rather than Remove From Focus as in the context menu?)<br />
* If single task id entered for repository open tasks directly rather than searching<br />
* Add to tasklist needs to be available in sesarch results view (consider removing open repository task from Navigate menu)<br />
<br />
=== Preference Pages ===<br />
* Local Task Repository needs preference page (via Task Repository Settings page)<br />
* bug#192582 Restoring defaults not restoring all settings<br />
<br />
=== Colors ===<br />
<br />
* Change task editor incoming/conflict highlight color to be more pronounced.<br />
<br />
=== Task List ===<br />
* Sorting set to Summary but tasklist sorted by priority upon startup<br />
* Sub tasks should no longer be filtered by default<br />
* Add 'Defer a week' option to Schedule for context menu option<br />
* Improve layout of Find and bread crumb bar<br />
* Add Alt+Click tip to Focus on Active Task button tooltip<br />
* Consider adding Navigate actions (e.g. Open Repository Task) to Task List view menu<br />
* Due dates not currently not settable from context menu in task list<br />
* Tooltip: Synched vs. completed is confusing<br />
* Selecting a task obscures its active/inactive indicator<br />
* When a category is selected, the selection color shows through 4 pixels of the folder icon<br />
* Italicizing the active task to indicate synchronization shouldn't un-bold it<br />
* Active/inactive indicators overlap clipboards after Going Into a category<br />
* Attempting to rename query with right-click -> Rename has no effect<br />
* Right-click -> Copy Details on a local task copies "null: " prefix<br />
* Sort By and Task Presentation menus should have radio buttons, not checkboxes<br />
<br />
*Focus On Workweek Filter<br />
** Archive category has incoming decoration even if all incomings are shown in the tasklist and therefore not displayed in the archive (might only be for new hits)<br />
** Archive category filter is not restored to not applied upon unfocusing (the check beside the filter isn't there, but the archive isn't shown either). You have to toggle the archive filter to show the archive cateogry again.<br />
<br />
* Task search UI {{bug|204862}}<br />
<br />
== Keybindings ==<br />
<br />
* F2: rename<br />
* F4: show tooltip<br />
* F5: synchronize<br />
* F6: go to next unread<br />
* Shift+F6: go to previous unread<br />
* F7: mark as read<br />
* Shift+F7: mark as unread<br />
* F8: mark as read and go to next unread<br />
* Esc: hide tooltip<br />
* Enter: open task<br />
* Ctrl+c: Copy details<br />
<br />
=== Notifications ===<br />
* Don't show notification for new bug reports submitted by user<br />
* Don't show notificaiton for new incoming if synched from editor<br />
* Local task icon in popup should not be bug icon<br />
* Investigate performance issue since taskdata now loaded upon popup show<br />
<br />
=== Task Editor ===<br />
* Reveal in tasklist missing from popup<br />
* Icon in tab of Local Task editor is repository task icon, should be local task icon<br />
* Assign to needs content assist in New Task Editor<br />
* Update Attributes option (button) should be available in Task Editor header<br />
* Render context attachments 'comments' in Bugzilla as links to activate context or thumbnails, not comments.<br />
* If the Description of a repository task is editable, no border is drawn to indicate this in the editor<br />
* The Summary text field of a repository task editor is always editable even if the repository task attribute is read only.<br />
* <font color=green> "Add To Task List" only appears in the context menu on the editor of an opened repository task if you have a category in your tasklist (can't add to root)</font> Uncategorized is now always available.<br />
* Uncategorized folder in "Add To Task List" context menu not decorated with Jar icon<br />
* Ampersand in task name misinterpreted as mnemonic in large heading<br />
* New Task -> Local Tasks -> Finish -> start typing the summary quickly; your typing is overwritten by "New Task"<br />
* If I close a new local task without saving, delete it.<br />
<br />
=== Planning Editor ===<br />
* Category selection should be available within Task Planning editor<br />
<br />
=== Bugzilla Connector ===<br />
<br />
* Search page too small with clean workspace settings?<br />
* Proxy settings section expanded when shouldn't be for new Task Repository?<br />
<br />
=== Hyperlinking ===<br />
<br />
[https://bugs.eclipse.org/bugs/show_bug.cgi?id=146964 146964: editor hyperlink parsing problems and suggestions]<br />
<br />
* Depending on connector hyperlink detection is slightly different. Should unify so that same patters work among all connectors: bug#123, task#123, task 123, #123<br />
* Hyperlinks opening synchronously<br />
* Additional patterns:<br />
** #XXXX<br />
** attachment 12345<br />
* Comment linking [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164221 bug#164221]<br />
* bla blah JiraWebIssueService$2.execute(JiraWebIssueService.java:105): still linking preceeding text where only class:line in brackets should be linked<br />
* Hyperlinks should have the task's summary as the tooltip (Eclipse hyperlink limitation here?)<br />
* Premature hyperlink termination: http://wiki.eclipse.org/index.php/FAQ_How_do_I_hook_my_editor_to_the_Back_and_Forward_buttons%3F<br />
* Avoid spell checking hyperlinks<br />
<br />
=== Recommended Preferences ===<br />
<br />
* Automatically disable Platform URL hyperlink detector.<br />
* Remove default linking from prefs?<br />
<br />
=== Task Repositories View ===<br />
<br />
*(from bug#124321) Add properties page to Local Tasks repository that explains that it is automatically created and point to the Task List preference page which points the user at the data directory.<br />
<br />
=== Synchronization ===<br />
<br />
There should be no synchronous repository communication. Cases that could still be left:<br />
* Contact attach/retrieve.<br />
* Download of repository configuration after new bug created with no previous query.<br />
<br />
* Job name in Progress view is misspelled "Synchronizying queries"</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Contributor_Reference&diff=58022Mylyn/Contributor Reference2007-10-30T23:54:41Z<p>Steffen.pingel.eclipse.org: /* Conventions */</p>
<hr />
<div>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 />
== Getting Started ==<br />
<br />
For ideas on how to contribute see the following lists of bugs and comment on any that interest you, or send a message to mylyn-dev on ways that you would like to get involved:<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=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=notregexp&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= bugday bugs]''': a short list of highly relevant bugs for getting started<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=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=helpwanted&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=notregexp&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]''': a longer list of all bugs targeted at community contributions<br />
<br />
=== Conventions ===<br />
<br />
All contributions to Mylyn need to be made using Mylyn since it links source changes to tasks and contexts, making open development and collaboration easier. Using Mylyn 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 />
==== Code ====<br />
<br />
Mylyn uses the Eclipse code conventions with these minor additions:<br />
<br />
* Tags: Mylyn uses the following tags in the code:<br />
** TODO: The following code needs to be reviewed.<br />
** XXX: The implementation uses a temporary work around that should be replaced by a proper solution in the future.<br />
** FIXME: Should only be used in very rare cases as a reminder that the marked code does not work as expected. Code marked as FIXME should not be distributed in a release.<br />
** API30: This API is going to change for version 3.0. Should include a description how it is going to change.<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 />
== Workspace ==<br />
<br />
The recommended way to work with Mylyn 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''. Note that to get rid of ''JRE association'' warnings you may need to download older JREs, e.g. from: http://java.sun.com/products/archive/<br />
<br />
=== Checkout ===<br />
<br />
The Mylyn 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 Mylyn, the additional projects can be deleted after the import. After the checkout you should have no errors or warnings from the Mylyn 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.x stream for Eclipse 3.4 (latest milestone)<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_3_m_2_x.psf <code>e_3_3_m_2_x</code>]: Mylyn 2.x stream for Eclipse 3.3 (branched projects updated with each release)<br />
<br />
'''End-of-life branches:'''<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_2_m_2_0.psf <code>e_3_2_m_2_0</code>]: Mylyn 2.0 stream for Eclipse 3.2 <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 (M4)<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 />
* [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 />
<br />
'''Other:'''<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-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 mylyn-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 Mylyn 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 ''Mylyn Bootstrap''.<br />
** On the ''Main'' tab, set the ''Location''<br />
*** You can use the existing workspace that you used Mylyn 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 Mylyn. 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 Mylyn, 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 <tt>org.eclipse.mylyn.monitor.core.StatusHandler</tt>. <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 />
=== Writing Tests ===<br />
<br />
Writing tests along with patches is key to ensuring that it is possible for committers to maintain the new functionality added by the patch. When writing tests look for the <code>All&lt;component&gt;Tests</code> class in the <code>tests</code> plug-in for that component, identify a test that is similar to the functionality that you are adding, and use that test as an example of how to add additional coverage. Tests can sometimes take longer to write then the change itself, but a committer will always be willing to assist you in designing the test or extending the mock test harness to make it easier to write.<br />
<br />
The key things to ensure is that your test covers is the addition or change to the existing functionality. For API changes it is often sufficient to have the public method covered. When writing tests for UI components, the simplest way of testing will often involve a combination of unit and black-box testing, for example, relying on other parts of the Mylyn UI to be set up (e.g. the Task List view). Consider the case of adding functionality for pre-selecting a repository in the New Task dialog, writing a test can take the following form (refer to <code>NewTaskWizardRepositorySelectionTest</code>):<br />
* Create a mock repository<br />
* Add a task to the mock repository<br />
* Set the selection on the Task List (new functionality uses this selection)<br />
* Invoke the wizard and assert that the selection was set correctly on the viewer (wizard is a black box, all we care about is the contents of the viewer)<br />
* Dispose the wizard dialog, remove the mock repository and the mock task<br />
<br />
When writing UI tests note that asynchrous updates, such as refresh, can make testing challenging. Note that several UI components have a method on them to set synchronous execution for the purpose of testing, and if such a method is lacking it can be added.<br />
<br />
=== Graphics ===<br />
<br />
If contributing a feature with icons or other graphics feel free to ask a committer to generate the graphic for you. If interested in contributing graphics you can find all of the source files (e.g. Photoshop) here: <code>org.eclipse.mylyn/graphics/ui</code>.<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 />
=== 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 />
Severities:<br />
* Use the Eclipse [https://bugs.eclipse.org/bugs/bug_status.html#bug_severity bug severity] conventions<br />
<br />
Keywords:<br />
* <code>helpwanted</code>: bugs that are beyond the current priorities for the project. Note that some bugs marked for an upcoming milestone can be marked as <code>helpwanted</code>. This indicates that the project committers would like to see the bug solved for the milestone and will actively contribute to a solution, but that the bug is more likely to be fixed in a timely manner with the help of additional contributors.<br />
<br />
* <code>bugday</code>: these are a special category of <code>helpwanted</code> bugs that are intended to be mast accessible or rewarding for new contributors interested in helping the project to tackle. See the [[Bug Day FAQ]] for more information. In order to keep this list focused on the most relevant bugs it is capped at 24 and should be reviewed periodically.<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 />
=== 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 />
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 />
=== Update Site ===<br />
<br />
download.eclipse.org/tools/mylyn/update/weekly/experimental<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 />
* '''Active Task Swither Trim Widget''': note that it cannot currently be disabled<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''' (when Eclipse hangs): <br />
** On Windows use the tool found at [http://www.adaptj.com/root/main/download the adaptj home page]:<br />
*** Follow the link and select button "Launch" and run the applet<br />
*** Select menu Process > Thread Dump<br />
*** In the combo box "Process ID" select the Java VM and click OK<br />
** Or, 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 />
** Or, on Linux: Use <code>Ctrl-\</code> on the console or send SIG_QUIT signal: <code>kill -SIGQUIT ''pid''</code><br />
** Or, with jconsole (requires 1.5 jdk, works on any OS):<br />
*** Launch <tt>eclipse -vmargs -Dcom.sun.management.jmxremote</tt><br />
*** Launch the JDK's jconsole tool. You can attach to the Java Process and copy&paste the thread dump. <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.<br />
<br />
[[Category:Mylyn]][[Category:How to Contribute]]</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Contributor_Reference&diff=58021Mylyn/Contributor Reference2007-10-30T23:38:26Z<p>Steffen.pingel.eclipse.org: /* Patches */</p>
<hr />
<div>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 />
== Getting Started ==<br />
<br />
For ideas on how to contribute see the following lists of bugs and comment on any that interest you, or send a message to mylyn-dev on ways that you would like to get involved:<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=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=bugday&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=notregexp&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= bugday bugs]''': a short list of highly relevant bugs for getting started<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=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=helpwanted&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailtype1=substring&email1=&emailtype2=notregexp&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]''': a longer list of all bugs targeted at community contributions<br />
<br />
=== Conventions ===<br />
<br />
All contributions to Mylyn need to be made using Mylyn since it links source changes to tasks and contexts, making open development and collaboration easier. Using Mylyn 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 />
== Workspace ==<br />
<br />
The recommended way to work with Mylyn 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''. Note that to get rid of ''JRE association'' warnings you may need to download older JREs, e.g. from: http://java.sun.com/products/archive/<br />
<br />
=== Checkout ===<br />
<br />
The Mylyn 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 Mylyn, the additional projects can be deleted after the import. After the checkout you should have no errors or warnings from the Mylyn 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.x stream for Eclipse 3.4 (latest milestone)<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_3_m_2_x.psf <code>e_3_3_m_2_x</code>]: Mylyn 2.x stream for Eclipse 3.3 (branched projects updated with each release)<br />
<br />
'''End-of-life branches:'''<br />
* [http://www.eclipse.org/mylyn/doc/dev/mylyn-e_3_2_m_2_0.psf <code>e_3_2_m_2_0</code>]: Mylyn 2.0 stream for Eclipse 3.2 <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 (M4)<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 />
* [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 />
<br />
'''Other:'''<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-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 mylyn-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 Mylyn 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 ''Mylyn Bootstrap''.<br />
** On the ''Main'' tab, set the ''Location''<br />
*** You can use the existing workspace that you used Mylyn 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 Mylyn. 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 Mylyn, 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 <tt>org.eclipse.mylyn.monitor.core.StatusHandler</tt>. <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 />
=== Writing Tests ===<br />
<br />
Writing tests along with patches is key to ensuring that it is possible for committers to maintain the new functionality added by the patch. When writing tests look for the <code>All&lt;component&gt;Tests</code> class in the <code>tests</code> plug-in for that component, identify a test that is similar to the functionality that you are adding, and use that test as an example of how to add additional coverage. Tests can sometimes take longer to write then the change itself, but a committer will always be willing to assist you in designing the test or extending the mock test harness to make it easier to write.<br />
<br />
The key things to ensure is that your test covers is the addition or change to the existing functionality. For API changes it is often sufficient to have the public method covered. When writing tests for UI components, the simplest way of testing will often involve a combination of unit and black-box testing, for example, relying on other parts of the Mylyn UI to be set up (e.g. the Task List view). Consider the case of adding functionality for pre-selecting a repository in the New Task dialog, writing a test can take the following form (refer to <code>NewTaskWizardRepositorySelectionTest</code>):<br />
* Create a mock repository<br />
* Add a task to the mock repository<br />
* Set the selection on the Task List (new functionality uses this selection)<br />
* Invoke the wizard and assert that the selection was set correctly on the viewer (wizard is a black box, all we care about is the contents of the viewer)<br />
* Dispose the wizard dialog, remove the mock repository and the mock task<br />
<br />
When writing UI tests note that asynchrous updates, such as refresh, can make testing challenging. Note that several UI components have a method on them to set synchronous execution for the purpose of testing, and if such a method is lacking it can be added.<br />
<br />
=== Graphics ===<br />
<br />
If contributing a feature with icons or other graphics feel free to ask a committer to generate the graphic for you. If interested in contributing graphics you can find all of the source files (e.g. Photoshop) here: <code>org.eclipse.mylyn/graphics/ui</code>.<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 />
=== 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 />
Severities:<br />
* Use the Eclipse [https://bugs.eclipse.org/bugs/bug_status.html#bug_severity bug severity] conventions<br />
<br />
Keywords:<br />
* <code>helpwanted</code>: bugs that are beyond the current priorities for the project. Note that some bugs marked for an upcoming milestone can be marked as <code>helpwanted</code>. This indicates that the project committers would like to see the bug solved for the milestone and will actively contribute to a solution, but that the bug is more likely to be fixed in a timely manner with the help of additional contributors.<br />
<br />
* <code>bugday</code>: these are a special category of <code>helpwanted</code> bugs that are intended to be mast accessible or rewarding for new contributors interested in helping the project to tackle. See the [[Bug Day FAQ]] for more information. In order to keep this list focused on the most relevant bugs it is capped at 24 and should be reviewed periodically.<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 />
=== 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 />
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 />
=== Update Site ===<br />
<br />
download.eclipse.org/tools/mylyn/update/weekly/experimental<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 />
* '''Active Task Swither Trim Widget''': note that it cannot currently be disabled<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''' (when Eclipse hangs): <br />
** On Windows use the tool found at [http://www.adaptj.com/root/main/download the adaptj home page]:<br />
*** Follow the link and select button "Launch" and run the applet<br />
*** Select menu Process > Thread Dump<br />
*** In the combo box "Process ID" select the Java VM and click OK<br />
** Or, 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 />
** Or, on Linux: Use <code>Ctrl-\</code> on the console or send SIG_QUIT signal: <code>kill -SIGQUIT ''pid''</code><br />
** Or, with jconsole (requires 1.5 jdk, works on any OS):<br />
*** Launch <tt>eclipse -vmargs -Dcom.sun.management.jmxremote</tt><br />
*** Launch the JDK's jconsole tool. You can attach to the Java Process and copy&paste the thread dump. <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.<br />
<br />
[[Category:Mylyn]][[Category:How to Contribute]]</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=57719Mylyn/Meetings2007-10-30T06:27:55Z<p>Steffen.pingel.eclipse.org: /* Tuesday, October 30, 10-11am PT */</p>
<hr />
<div>[[Category:Mylyn]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
[[Mylyn Meetings Archive]]<br />
<br />
=== Pending Discussion Items ===<br />
<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
* Active task and working set presentation/switching when Task List is not visible<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, October 30, 10-11am PT ====<br />
<br />
Agenda:<br />
* Apache JIRA problem, {{bug|205963}}<br />
* Mylyn 3.0 planning (Mik)<br />
** Flagging pending API changes in the code (Steffen)<br />
* Manage New & Noteworthy items (Steffen)<br />
* Mylyn Monitor and concept of a Feedback Agent (zx)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Subtasks and incoming decoration mess (Eugene)<br />
<br />
=== Past Meetings ===<br />
<br />
==== Tuesday, October 23, 10-11am PT ====<br />
<br />
Agenda:<br />
* Apache JIRA problem, {{bug|205963}}<br />
* allow to configure labels in the task list {{bug|199345}} (Eugene)<br />
* UI and mechanism for pushing task active time to repository {{bug|205218}} (Helen)<br />
* Design discussion of ''Task Editor'' layout (Mik, Rob)<br />
* Design discussion for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Mylyn 3.0 planning (Mik)<br />
<br />
Minutes:<br />
<br />
XPlanner Time Tracking<br />
* Timing related fields shouldn't be in custom editor, ideally left in Planning Editor<br />
* Need ability to query date ranges for task activity<br />
* Provide report on time tracking based on task search (deprecate task activity report?)<br />
<br />
Task List and editors<br />
* Rob will reduce number of comments visisble and lazy load uninteresting<br />
* Mik to post patch for task overdue simplification<br />
* Mik to comment on Eugene's custom attributes bug.<br />
<br />
Configuration refresh options discussed<br />
* Manual, User Configurable, Semi-auto (detect if large repository, if so require manual)<br />
<br />
==== Tuesday, October 16, 10-11am PT ====<br />
<br />
Agenda:<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* UI and mechanism for pushing task active time to repository {{bug|205218}} (Helen)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Mylyn 3.0 planning (Mik)<br />
* Discussions in bug reports (Eugene)<br />
<br />
==== Tuesday, October 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 3.0 planning (Mik)<br />
* Summary bug view / quick viewing of bug reports design discussion: {{bug|205669}} (Steffen)<br />
* Design discussion - bugzilla cached configuration (Rob)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
<br />
<br />
==== Tuesday, October 2, 10-11am PT ====<br />
<br />
Agenda:<br />
* 2.1 release review (Mik)<br />
* Eclipse.org bandwidth usage {{bug|196056}} {{bug|205213}} (Rob)<br />
* XPlanner update (Helen)<br />
* 3.0 plan review and bug triage (all)<br />
* Mylyn connector for mingle (Ketan)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 25, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 2.1, Europa Fall Update and Ganymede status and review of remaining items (Mik)<br />
* Update sites, linking and download redesign (Mik) {{bug|194469}}<br />
* Sandbox quality bar and policy for inclusion of features for discoverable sites in Europa Fall Update (Mik) {{bug|204560}}<br />
* Subtasks being enabled by default for Bugzilla and corresponding policies (Rob, Mik, Eugene)<br />
** artificial "grouping" vs. showing subtasks<br />
* JIRA update (Steffen)<br />
* XPlanner update (Helen)<br />
<br />
Minutes:<br />
* Update site should include historical builds as part of archive<br />
* Subtask setting to be renamed<br />
<br />
==== Tuesday, September 18, 10-11am PT ====<br />
<br />
Agenda:<br />
* Policy for adding stuff to the Sandbox, i.e. group by scheduled vs. "out of nowhere" "Incoming (Experimental)" presentation (Eugene)<br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* 3.0 planning (Mik)<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 11, 10-11am PT ====<br />
<br />
Agenda: <br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* Policy for making significant changes to open bugs' status, e.g. marking for bugday (Mik)<br />
* 3.0 planning (Mik)<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Arbitrary attributes discussion {{bug|199818 }}<br />
* Summary bug view / quick viewing of bug reports design discussion<br />
* Design discussion - bugzilla cached configuration <br />
<br />
Minutes:<br />
----<br />
<br />
<br />
==== Tuesday, September 4, 10-11am PT ====<br />
<br />
Agenda: <br />
* Missed BugDay<br />
* Summer of Code wrap-up (Jevgeni, Xiaoyang, Balazs)<br />
* Policy: <br />
** Resolving bug reports (Rob)<br />
** Reopening closed reports, i.e. AllTasks fails (Eugene)<br />
* Design discussion - bugzilla cached configuration<br />
* 2.1 and 3.0 Planning (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
<br />
Minutes:<br />
<br />
* Bug Day<br />
** We will participate in Bug Day<br />
** Need to continute to maintain/label bug day bugs<br />
** Must maintain calendar of bug day events and send announcemnts to newsgroup/mailing lists <br />
** Eugne willing to mentor on bug days<br />
<br />
*Policy<br />
** Contributions (patches) must be accompanied with summary of issues addressed by provided patch. Must also indicate if patch is intended to resolve bug report or further work required. (Rob will update Contributor Reference) <br />
** Reopening closed reports not encouraged. Mik will resolve bug#152869 - creating bugs from failed unit tests for 2.1<br />
<br />
* Builds<br />
** RC builds, dev builds as weekly milestone builds (Mik to send proposal to newsgroup to get feedback from community on this proposed change)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=57018Mylyn/Porting Guide2007-10-25T20:44:01Z<p>Steffen.pingel.eclipse.org: /* Pending Changes for Mylyn 3.0 */</p>
<hr />
<div>[[Category:Mylyn]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from 1.0 to 2.0 =<br />
<br />
See the <b>[[Mylyn Porting Guide 2.0]]</b><br />
<br />
= Porting from 2.0 to 3.0 =<br />
<br />
There is currently no need to port Mylyn from the 2.0 APIs since current Mylyn releases are backwards compatible. Throughout the 2.x release cycle we will be using this wiki to gather changes and suggestions for improving the APIs for 3.0.<br />
<br />
<br />
== Pending Changes for Mylyn 3.0 == <br />
* Rename <code>AbstractRepositoryQuery.getRepositoryKind()</code> to <code>AbstractRepositoryQuery.getConnectorKind()</code><br />
* Rename <code>IMylarMonitorLifecycleListener</code> to <code>IMonitorLifecycleListener</code><br />
* Rename <code>MockRepositoryTask</code> to <code>MockTask</code><br />
* Refactor <code>TaskActivationHistory</code> into a <code>TaskActivityManager</code> that encapsulates both activity monitoring and activation history<br />
** Remove all deprecated methods from TaskListManager<br />
* <code>AbstractTaskListPresentation</code>: make API, remove coupling to <code>TaskListView</code><br />
* <code>TaskGroup</code> and <code>TaskCategory</code>: consider for API, refactor or combine<br />
* consider merging <code>TaskList.removeFromCategory()</code> and <code>TaskList.removeFromQuery()</code><br />
* Deprecate <code>WebClientUtil.getPlatformProxy()</code><br />
* Move <code>TasksUiPlugin.getIncomingNotification(..)</code> and related private classes<br />
* <code>AbstractTask.setCompleted()</code> needs changing, it has the problematic side effect of setting the completion date to the current time. {{bug|203875}}<br />
* Remove <code>AbstractInterestManipulationAction.isRemove()</code>: deprecated<br />
* Make <code>IMonitoredWindow</code> API and put alongside <code>IContextAwareEditor</code><br />
* merge <code>AbstractRepositoryTaskEditor.createAttributeSection</code> into <code>createAttributeLayout()</code><br />
* Make API: <code>InteractionContextScaling</code><br />
* Rename <code>AbstractTask.RepositoryTaskSyncState</code> to <code>AbstractTask.SyncState</code> ("sync" is used commonly enough that we should be able to standardize on it in the API, replacing "synchronization/synchronize" where applicable).<br />
* Add <code>InteractionContextScaling</code> parameter to <code>IInteractionContextReader.readContext(..)</code><br />
* Make a subset of <code>InteractionContextManager</code> API.<br />
* Make <code>TaskRepository.getUserName()</code>, <code>getHttpUser</code> and <code>getProxyUsername</code> consistent<br />
<br />
== New Tasks API == <br />
<br />
* <code>AbstractEditQueryWizard</code><br />
** <code>getQuerySummary()</code>: added<br />
<br />
* <code>AbstractRepositoryConnector</code><br />
** <code>isRepositoryConfigurationStale(TaskRepository)</code> has been added<br />
<br />
* <code>AbstractRenderingEngine</code> has been added for converting Wiki syntax to HTML<br />
<br />
* <code>AbstractRepositoryQueryPage</code><br />
** <code>setControlsEnabled(...)</code>: added - override to perform finer grain enablements if necessary<br />
<br />
* <code>AbstractRepositoryTaskEditor</code> has been extended to provide HTML preview capabilities for repositories that support Wiki syntax in ticket descriptions and comments<br />
** <code>addSelectableControl()</code>: added<br />
** <code>createReplyHyperlink()</code> is now protected (was private)<br />
** <code>DescriptionListener</code> is now protected (was private)<br />
** <code>getParentEditor()</code>: added<br />
** <code>getRenderingEngine()</code>: added<br />
** <code>removeSelectableControl()</code>: added<br />
** <code>fillToolBar(..)</code>: added<br />
<br />
* <code>AbstractUserActivityMonitor</code><br />
** <code>isEnabled()</code>: added<br />
** <code>getOriginId()</code>: added<br />
** <code>getStructureKind()</code>: added<br />
** <code>getStructureHandle()</code>: added<br />
<br />
* <code>RepositoryTaskAttribute</code><br />
** task.common.user.reporter.name : added : key for full name of issue reporter<br />
** task.common.comment.author.name : added : key for full name of comment author<br />
** task.common.user.assigned.name : added : key for full name of issue assignee<br />
<br />
* <code>TaskEditor</code><br />
** class no longer final (experimental extensibility)<br />
<br />
* <code>TaskListManager</code><br />
** <code>resolveIdentifiersConflict()</code>: added<br />
** <code>removeFromQuery()</code>: added<br />
<br />
* <code>TaskTextViewerConfiguration</code> has been added (former name was RepositoryViewerConfig)<br />
<br />
== New Context API ==<br />
<br />
* <code>AbstractFocusViewAction.updateEnablementWithContextActivation()</code>: override to return false for focus actions that are not related to context activations (e.g. the Task List).<br />
<br />
* <code>AbstractFocusViewAction.setLinkingActionEnabled(boolean)</code>: should be overridden if view provides linking<br />
<br />
* <code>InteractionContextScaling.getScaling()</code>: new method, prevoiusly on subtype only<br />
<br />
== New Montior API ==<br />
<br />
* <code>MonitorUiPlugin.getMonitoredWindows()</code>: use insteand of <code>PlatformUI.getWorkbench().getWorkbenchWindows()</code><br />
* <code>MonitorUiPlugin.getLaunchingWorkbenchWindow()</code>: use to get the first active window when the monitor started.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=57015Mylyn/Porting Guide2007-10-25T20:42:31Z<p>Steffen.pingel.eclipse.org: /* Pending Changes for Mylyn 3.0 */</p>
<hr />
<div>[[Category:Mylyn]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from 1.0 to 2.0 =<br />
<br />
See the <b>[[Mylyn Porting Guide 2.0]]</b><br />
<br />
= Porting from 2.0 to 3.0 =<br />
<br />
There is currently no need to port Mylyn from the 2.0 APIs since current Mylyn releases are backwards compatible. Throughout the 2.x release cycle we will be using this wiki to gather changes and suggestions for improving the APIs for 3.0.<br />
<br />
<br />
== Pending Changes for Mylyn 3.0 == <br />
* Rename <code>AbstractRepositoryQuery.getRepositoryKind()</code> to <code>AbstractRepositoryQuery.getConnectorKind()</code><br />
* Rename <code>IMylarMonitorLifecycleListener</code> to <code>IMonitorLifecycleListener</code><br />
* Rename <code>MockRepositoryTask</code> to <code>MockTask</code><br />
* Refactor <code>TaskActivationHistory</code> into a <code>TaskActivityManager</code> that encapsulates both activity monitoring and activation history<br />
** Remove all deprecated methods from TaskListManager<br />
* <code>AbstractTaskListPresentation</code>: make API, remove coupling to <code>TaskListView</code><br />
* <code>TaskGroup</code> and <code>TaskCategory</code>: consider for API, refactor or combine<br />
* consider merging <code>TaskList.removeFromCategory()</code> and <code>TaskList.removeFromQuery()</code><br />
* Deprecate <code>WebClientUtil.getPlatformProxy()</code><br />
* Move <code>TasksUiPlugin.getIncomingNotification(..)</code> and related private classes<br />
* <code>AbstractTask.setCompleted()</code> needs changing, it has the problematic side effect of setting the completion date to the current time. {{bug|203875}}<br />
* Remove <code>AbstractInterestManipulationAction.isRemove()</code>: deprecated<br />
* Make <code>IMonitoredWindow</code> API and put alongside <code>IContextAwareEditor</code><br />
* merge <code>AbstractRepositoryTaskEditor.createAttributeSection</code> into <code>createAttributeLayout()</code><br />
* Make API: <code>InteractionContextScaling</code><br />
* Rename <code>AbstractTask.RepositoryTaskSyncState</code> to <code>AbstractTask.SyncState</code> ("sync" is used commonly enough that we should be able to standardize on it in the API, replacing "synchronization/synchronize" where applicable).<br />
* Add <code>InteractionContextScaling</code> parameter to <code>IInteractionContextReader.readContext(..)</code><br />
* Make a subset of <code>InteractionContextManager</code> API.<br />
* Make <code>TaskRepository.getUserName()</code>, <code>getHttpUser</code> and <code>getProxyUsername</code><br />
<br />
== New Tasks API == <br />
<br />
* <code>AbstractEditQueryWizard</code><br />
** <code>getQuerySummary()</code>: added<br />
<br />
* <code>AbstractRepositoryConnector</code><br />
** <code>isRepositoryConfigurationStale(TaskRepository)</code> has been added<br />
<br />
* <code>AbstractRenderingEngine</code> has been added for converting Wiki syntax to HTML<br />
<br />
* <code>AbstractRepositoryQueryPage</code><br />
** <code>setControlsEnabled(...)</code>: added - override to perform finer grain enablements if necessary<br />
<br />
* <code>AbstractRepositoryTaskEditor</code> has been extended to provide HTML preview capabilities for repositories that support Wiki syntax in ticket descriptions and comments<br />
** <code>addSelectableControl()</code>: added<br />
** <code>createReplyHyperlink()</code> is now protected (was private)<br />
** <code>DescriptionListener</code> is now protected (was private)<br />
** <code>getParentEditor()</code>: added<br />
** <code>getRenderingEngine()</code>: added<br />
** <code>removeSelectableControl()</code>: added<br />
** <code>fillToolBar(..)</code>: added<br />
<br />
* <code>AbstractUserActivityMonitor</code><br />
** <code>isEnabled()</code>: added<br />
** <code>getOriginId()</code>: added<br />
** <code>getStructureKind()</code>: added<br />
** <code>getStructureHandle()</code>: added<br />
<br />
* <code>RepositoryTaskAttribute</code><br />
** task.common.user.reporter.name : added : key for full name of issue reporter<br />
** task.common.comment.author.name : added : key for full name of comment author<br />
** task.common.user.assigned.name : added : key for full name of issue assignee<br />
<br />
* <code>TaskEditor</code><br />
** class no longer final (experimental extensibility)<br />
<br />
* <code>TaskListManager</code><br />
** <code>resolveIdentifiersConflict()</code>: added<br />
** <code>removeFromQuery()</code>: added<br />
<br />
* <code>TaskTextViewerConfiguration</code> has been added (former name was RepositoryViewerConfig)<br />
<br />
== New Context API ==<br />
<br />
* <code>AbstractFocusViewAction.updateEnablementWithContextActivation()</code>: override to return false for focus actions that are not related to context activations (e.g. the Task List).<br />
<br />
* <code>AbstractFocusViewAction.setLinkingActionEnabled(boolean)</code>: should be overridden if view provides linking<br />
<br />
* <code>InteractionContextScaling.getScaling()</code>: new method, prevoiusly on subtype only<br />
<br />
== New Montior API ==<br />
<br />
* <code>MonitorUiPlugin.getMonitoredWindows()</code>: use insteand of <code>PlatformUI.getWorkbench().getWorkbenchWindows()</code><br />
* <code>MonitorUiPlugin.getLaunchingWorkbenchWindow()</code>: use to get the first active window when the monitor started.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=56618Mylyn/Meetings2007-10-24T00:15:12Z<p>Steffen.pingel.eclipse.org: /* Tuesday, October 30, 10-11am PT */</p>
<hr />
<div>[[Category:Mylyn]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
[[Mylyn Meetings Archive]]<br />
<br />
=== Pending Discussion Items ===<br />
<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
* Active task and working set presentation/switching when Task List is not visible<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, October 30, 10-11am PT ====<br />
<br />
Agenda:<br />
* Apache JIRA problem, {{bug|205963}}<br />
* Mylyn 3.0 planning (Mik)<br />
* Manage New & Noteworthy items (Steffen)<br />
<br />
=== Past Meetings ===<br />
<br />
==== Tuesday, October 23, 10-11am PT ====<br />
<br />
Agenda:<br />
* Apache JIRA problem, {{bug|205963}}<br />
* allow to configure labels in the task list {{bug|199345}} (Eugene)<br />
* UI and mechanism for pushing task active time to repository {{bug|205218}} (Helen)<br />
* Design discussion of ''Task Editor'' layout (Mik, Rob)<br />
* Design discussion for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Mylyn 3.0 planning (Mik)<br />
<br />
Minutes:<br />
<br />
XPlanner Time Tracking<br />
* Timing related fields shouldn't be in custom editor, ideally left in Planning Editor<br />
* Need ability to query date ranges for task activity<br />
* Provide report on time tracking based on task search (deprecate task activity report?)<br />
<br />
Task List and editors<br />
* Rob will reduce number of comments visisble and lazy load uninteresting<br />
* Mik to post patch for task overdue simplification<br />
* Mik to comment on Eugene's custom attributes bug.<br />
<br />
Configuration refresh options discussed<br />
* Manual, User Configurable, Semi-auto (detect if large repository, if so require manual)<br />
<br />
==== Tuesday, October 16, 10-11am PT ====<br />
<br />
Agenda:<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* UI and mechanism for pushing task active time to repository {{bug|205218}} (Helen)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
* Mylyn 3.0 planning (Mik)<br />
* Discussions in bug reports (Eugene)<br />
<br />
==== Tuesday, October 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 3.0 planning (Mik)<br />
* Summary bug view / quick viewing of bug reports design discussion: {{bug|205669}} (Steffen)<br />
* Design discussion - bugzilla cached configuration (Rob)<br />
* Proposal for simplifying the overdue notions for Scheduled for and Due dates (Mik)<br />
<br />
<br />
==== Tuesday, October 2, 10-11am PT ====<br />
<br />
Agenda:<br />
* 2.1 release review (Mik)<br />
* Eclipse.org bandwidth usage {{bug|196056}} {{bug|205213}} (Rob)<br />
* XPlanner update (Helen)<br />
* 3.0 plan review and bug triage (all)<br />
* Mylyn connector for mingle (Ketan)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 25, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 2.1, Europa Fall Update and Ganymede status and review of remaining items (Mik)<br />
* Update sites, linking and download redesign (Mik) {{bug|194469}}<br />
* Sandbox quality bar and policy for inclusion of features for discoverable sites in Europa Fall Update (Mik) {{bug|204560}}<br />
* Subtasks being enabled by default for Bugzilla and corresponding policies (Rob, Mik, Eugene)<br />
** artificial "grouping" vs. showing subtasks<br />
* JIRA update (Steffen)<br />
* XPlanner update (Helen)<br />
<br />
Minutes:<br />
* Update site should include historical builds as part of archive<br />
* Subtask setting to be renamed<br />
<br />
==== Tuesday, September 18, 10-11am PT ====<br />
<br />
Agenda:<br />
* Policy for adding stuff to the Sandbox, i.e. group by scheduled vs. "out of nowhere" "Incoming (Experimental)" presentation (Eugene)<br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* 3.0 planning (Mik)<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 11, 10-11am PT ====<br />
<br />
Agenda: <br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* Policy for making significant changes to open bugs' status, e.g. marking for bugday (Mik)<br />
* 3.0 planning (Mik)<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Arbitrary attributes discussion {{bug|199818 }}<br />
* Summary bug view / quick viewing of bug reports design discussion<br />
* Design discussion - bugzilla cached configuration <br />
<br />
Minutes:<br />
----<br />
<br />
<br />
==== Tuesday, September 4, 10-11am PT ====<br />
<br />
Agenda: <br />
* Missed BugDay<br />
* Summer of Code wrap-up (Jevgeni, Xiaoyang, Balazs)<br />
* Policy: <br />
** Resolving bug reports (Rob)<br />
** Reopening closed reports, i.e. AllTasks fails (Eugene)<br />
* Design discussion - bugzilla cached configuration<br />
* 2.1 and 3.0 Planning (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
<br />
Minutes:<br />
<br />
* Bug Day<br />
** We will participate in Bug Day<br />
** Need to continute to maintain/label bug day bugs<br />
** Must maintain calendar of bug day events and send announcemnts to newsgroup/mailing lists <br />
** Eugne willing to mentor on bug days<br />
<br />
*Policy<br />
** Contributions (patches) must be accompanied with summary of issues addressed by provided patch. Must also indicate if patch is intended to resolve bug report or further work required. (Rob will update Contributor Reference) <br />
** Reopening closed reports not encouraged. Mik will resolve bug#152869 - creating bugs from failed unit tests for 2.1<br />
<br />
* Builds<br />
** RC builds, dev builds as weekly milestone builds (Mik to send proposal to newsgroup to get feedback from community on this proposed change)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=55623Mylyn/Porting Guide2007-10-17T21:11:00Z<p>Steffen.pingel.eclipse.org: /* Pending Changes for Mylyn 3.0 */</p>
<hr />
<div>[[Category:Mylyn]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from 1.0 to 2.0 =<br />
<br />
See the <b>[[Mylyn Porting Guide 2.0]]</b><br />
<br />
= Porting from 2.0 to 3.0 =<br />
<br />
There is currently no need to port Mylyn from the 2.0 APIs since current Mylyn releases are backwards compatible. Throughout the 2.x release cycle we will be using this wiki to gather changes and suggestions for improving the APIs for 3.0.<br />
<br />
<br />
== Pending Changes for Mylyn 3.0 == <br />
* Rename <code>AbstractRepositoryQuery.getRepositoryKind()</code> to <code>AbstractRepositoryQuery.getConnectorKind()</code><br />
* Rename <code>IMylarMonitorLifecycleListener</code> to <code>IMonitorLifecycleListener</code><br />
* Rename <code>MockRepositoryTask</code> to <code>MockTask</code><br />
* Refactor <code>TaskActivationHistory</code> into a <code>TaskActivityManager</code> that encapsulates both activity monitoring and activation history<br />
** Remove all deprecated methods from TaskListManager<br />
* <code>AbstractTaskListPresentation</code>: make API, remove coupling to <code>TaskListView</code><br />
* <code>TaskGroup</code> and <code>TaskCategory</code>: consider for API, refactor or combine<br />
* consider merging <code>TaskList.removeFromCategory()</code> and <code>TaskList.removeFromQuery()</code><br />
* Deprecate <code>WebClientUtil.getPlatformProxy()</code><br />
* Move <code>TasksUiPlugin.getIncomingNotification(..)</code> and related private classes<br />
* <code>AbstractTask.setCompleted()</code> needs changing, it has the problematic side effect of setting the completion date to the current time. {{bug|203875}}<br />
* Remove <code>AbstractInterestManipulationAction.isRemove()</code>: deprecated<br />
* Make <code>IMonitoredWindow</code> API and put alongside <code>IContextAwareEditor</code><br />
* merge <code>AbstractRepositoryTaskEditor.createAttributeSection</code> into <code>createAttributeLayout()</code><br />
* Make API: <code>InteractionContextScaling</code><br />
* Rename <code>AbstractTask.RepositoryTaskSyncState</code> to <code>AbstractTask.SynchronizationState</code><br />
<br />
== New Tasks API == <br />
<br />
* <code>AbstractEditQueryWizard</code><br />
** <code>getQuerySummary()</code>: added<br />
<br />
* <code>AbstractRepositoryConnector</code><br />
** <code>isRepositoryConfigurationStale(TaskRepository)</code> has been added<br />
<br />
* <code>AbstractRenderingEngine</code> has been added for converting Wiki syntax to HTML<br />
<br />
* <code>AbstractRepositoryQueryPage</code><br />
** <code>setControlsEnabled(...)</code>: added - override to perform finer grain enablements if necessary<br />
<br />
* <code>AbstractRepositoryTaskEditor</code> has been extended to provide HTML preview capabilities for repositories that support Wiki syntax in ticket descriptions and comments<br />
** <code>addSelectableControl()</code>: added<br />
** <code>createReplyHyperlink()</code> is now protected (was private)<br />
** <code>DescriptionListener</code> is now protected (was private)<br />
** <code>getParentEditor()</code>: added<br />
** <code>getRenderingEngine()</code>: added<br />
** <code>removeSelectableControl()</code>: added<br />
** <code>fillToolBar(..)</code>: added<br />
<br />
* <code>AbstractUserActivityMonitor</code><br />
** <code>isEnabled()</code>: added<br />
** <code>getOriginId()</code>: added<br />
** <code>getStructureKind()</code>: added<br />
** <code>getStructureHandle()</code>: added<br />
<br />
* <code>RepositoryTaskAttribute</code><br />
** task.common.user.reporter.name : added : key for full name of issue reporter<br />
** task.common.comment.author.name : added : key for full name of comment author<br />
** task.common.user.assigned.name : added : key for full name of issue assignee<br />
<br />
* <code>TaskEditor</code><br />
** class no longer final (experimental extensibility)<br />
<br />
* <code>TaskListManager</code><br />
** <code>resolveIdentifiersConflict()</code>: added<br />
** <code>removeFromQuery()</code>: added<br />
<br />
* <code>TaskTextViewerConfiguration</code> has been added (former name was RepositoryViewerConfig)<br />
<br />
== New Context API ==<br />
<br />
* <code>AbstractFocusViewAction.updateEnablementWithContextActivation()</code>: override to return false for focus actions that are not related to context activations (e.g. the Task List).<br />
<br />
* <code>AbstractFocusViewAction.setLinkingActionEnabled(boolean)</code>: should be overridden if view provides linking<br />
<br />
* <code>InteractionContextScaling.getScaling()</code>: new method, prevoiusly on subtype only<br />
<br />
== New Montior API ==<br />
<br />
* <code>MonitorUiPlugin.getMonitoredWindows()</code>: use insteand of <code>PlatformUI.getWorkbench().getWorkbenchWindows()</code><br />
* <code>MonitorUiPlugin.getLaunchingWorkbenchWindow()</code>: use to get the first active window when the monitor started.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/FAQ&diff=55279Mylyn/FAQ2007-10-16T02:00:26Z<p>Steffen.pingel.eclipse.org: /* Task List */</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
[[Mylyn User Guide]], <br />
[http://eclipse.org/mylyn Mylyn Home],<br />
[http://wiki.eclipse.org/index.php?title=Special:Userlogin&returnto=Special:Userlogout Log in to edit]<br />
<br />
For instructions on [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Download_Mylar downloading] [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installation installing] and [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuration configuring] <br />
Mylyn, see the [[Mylyn User Guide]]. For instructions on developing and contributing to Mylyn, see the [[Mylyn Contributor Reference]].<br />
<br />
= Installation =<br />
<br />
== What versions of Eclipse are supported? ==<br />
<br />
See the [http://eclipse.org/mylyn/dl.php download page].<br />
<br />
Mylyn also relies on a web browser that works with the Standard Widget Toolkit; Windows and MacOS users are fine, but Linux users might have to download another browser. See [http://www.eclipse.org/swt/faq.php#browserlinux the SWT Browser guide] for which browsers will work. See [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux installing browser on Linux] for installation instructions.<br />
<br />
== What version of Java is required? ==<br />
<br />
Mylyn needs the '''Java 5''' virtual machine.<br />
<br />
To check the version of the Java virtual machine that Eclipse was launched with to to ''Help -> About Eclipse SDK -> Configuration Details'' and verify that the java.vm.version is 1.5. <br />
<br />
Mac users should refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
* If you do not have Java 5, you can download it from [http://72.5.124.55/javase/downloads/index.jsp Sun's web site]. <br />
* If you have more than one VM, you need to specify that Eclipse should use the JDK1.5 VM. <br />
<br />
In Unix, set the environment variable <code>JAVA_HOME</code> to the root of the JDK1.5 installation and/or set the <code>PATH</code> variable to put the JDK1.5 executable directory before any other VM executable directories. For example, under <code>bash</code> in Unix:<br />
export JAVA_HOME="''(location of JDK1.5 root)''"<br />
export PATH=$JAVA_HOME/bin:$PATH<br />
<br />
<b>We do [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140955 not recommend] using JDK 1.6 on Eclipse 3.1.</b> (It works fine with Eclipse 3.2 or 3.3.) To use JDK 1.6 on Eclipse 3.1, you must add the following line to your <code>config.ini</code>file:<br />
<code><br />
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,<br />
J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6<br />
</code><br />
<br />
== What version of Mylyn is distributed with the Eclipse downloads? ==<br />
<br />
The [http://www.eclipse.org/downloads/ default Eclipse downloads] contain the following Mylyn redistributions. Since the redistributed versions can be missing important bug fixes or feature additions, we recommend using the [http://www.eclipse.org/mylyn/downloads latest version of Mylyn].<br />
<br />
* Eclipse IDE for Java Developers: all of Mylyn except Team integration (e.g. automatic change sets) integration. Install the Eclipse CVS integration and then install the latest Mylyn build to get this component.<br />
<br />
* Eclipse IDE for Java EE Developers: all of Mylyn redistribution, install manually<br />
<br />
* Eclipse IDE for C/C++ Developers: no Mylyn redistribution, install manually<br />
<br />
* Eclipse for RCP/Plug-in Developers: all of Mylyn redistributed<br />
<br />
* Eclipse Classic: no Mylyn redistribution, install manually<br />
<br />
== My tasks or queries disappeared, what do I do? ==<br />
<br />
This happens if Mylyn failed to install. First ensure that you have a correct install by following the instructions in the next section. After that, if you still do not see your tasks use the ''Task List'' view menu -> ''Restore Tasks From History...'' command (also available via ''File -> Import -> Task List''.<br />
<br />
== Installation Troubleshooting ==<br />
<br />
''' Java Persistence API Tools error when updating the JEE Eclipse Package '''<br />
<br />
If you are trying to install additional features and get this error you have hit [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194959 bug 194959] which should be resolved soon. The work-around is to check off the ''Europa Discovery Site'' and install the first two components of the ''Data Tools Platform''.<br />
<br />
''' Update failures '''<br />
<br />
On Eclipse versions earlier than 3.3 (final) use '''only the "Search for new features.."''' option when updating Mylyn. If you use "Search for updates..." the Update Manager will allow a partial install that can cause Mylyn to fail to start, and you will need to run update again. See the ''feature configuration problem'' section below for details. If you encounter this problemm consider voting for Platform [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132450 bug 132450].<br />
<br />
''' Startup exceptions '''<br />
<br />
If you see startup errors or warnings such as <code>BundleException</code> or timeout messages restart Eclipse with the <code>-clean</code> flag either on the command line, in your shortcut link, or by temporarily it into the <code>eclipse/eclipse.ini</code> file. If that does not resolve the problem please [http://www.eclipse.org/mylar/bugs.php file a bug].<br />
<br />
''' Incompatible VM (e.g. JDK 1.4) '''<br />
<br />
If you are using the wrong VM, you'll see errors like the following in your log file. <br />
<code><br />
Root exception: java.lang.UnsupportedClassVersionError:<br />
org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)<br />
</code><br />
<br />
See [[#Download_and_configure_Java_5_or_6|Configure Java]] to fix this problem.<br />
<br />
''' Incompatible version of Eclipse '''<br />
<br />
Separate versions and update sites exist [http://eclipse.org/mylyn/dl.php for Eclipse 3.1 and 3.2]), in which case you may see errors like the following in your <code><workspace>/.metadata/.log </code>file or in a Mylyn view:<br />
<code><br />
java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()<br />
The activator org.eclipse.mylar.java.MylarJavaPlugin for bundle org.eclipse.mylar.java is invalid<br />
</code><br />
<br />
''' Mylyn feature configuration problem '''<br />
<br />
If the above do not address the issue, the easiest thing to do is uninstall any old versions and update to the latest Mylyn. Your tasks won't be lost, because by default they are stored in the <code><workspace>/.metadata/.mylyn</code> folder which will be read next time Mylyn starts correctly. <br />
* First, uninstall the old version of Mylyn using ''Help -> Software Updates -> Manage Configuration''. <br />
* You need to Disable all Mylyn features by right-clicking them.<br />
* Allow Eclipse to restart after the last is disabled.<br />
* After restart, ensure that the 3rd toolbar button is pressed (figure below) so that you see the disabled features to uninstall.<br />
* Uninstall all the disabled features using the popup menu. <br />
<br />
If you don't uninstall, the the Update Manager will think that you have the latest and tell you that there are no updates. <br />
<br />
<b>Note: manually removing the plug-ins and features can lead to configuration errors.</b> <br />
<br />
After uninstalling, update Eclipse by adding the correct update site specified at on the [http://eclipse.org/mylar/dl.php download page], and after that automatically or manually updating will install the correct version.<br />
<br />
[[Image:mylar-eclipse-manage-configuration.gif]]<br />
<br />
'''What do I need to do in installation to be able to use Mylyn task management features with bug/task/issue trackers?'''<br />
<br />
When you install, make sure that you select a connector for your bug/task/issue tracking software. For example, to use Bugzilla, you have to install the Bugzilla connector component.<br />
<br />
'''I've installed Mylyn ; why can't I see anything different?'''<br />
<br />
The two most likely possibilities are:<br />
# You don't have any Mylyn views open. Select ''Window -> Show View -> Other'', then select ''Mylyn'' and you should see the available Mylyn Views. <br />
# If you still don't see anything, then perhaps you aren't using the JDK1.5 VM (or later). See [[Mylyn_Installation_Guide#Download_and_configure_Java|configuring Java]].<br />
<br />
<br />
'''What does the error "Network connection problems encountered during search" mean?'''<br />
<br />
If you get that message while trying to download Mylyn, it means that Eclipse couldn't find the location you entered. This might be because you copied something incorrectly (watch for extra characters -- even extra spaces can cause errors), or because the site went down. You may be able to see if the site is up or down by copying the URL into your Web browser.<br />
<br />
'''What does the "Update manager failure" message mean? '''<br />
<br />
It means that Eclipse could not access the update site, or that it got confused about the configuration state of your Eclipse. First try updating again to see if the update site is accessible. <br />
<br />
If you are trying to update the JIRA connector you can also try de-selecting that feature in case the <code>Tigris.org</code> update site is not accessible. Using ''Search for new features to install..'' when installing can help to avoid this problem. If that does not work see the feature configuration troubleshooting below. <br />
<br />
'''What does "Could not create Browser page: No more handles (<code>java.lang.UnsatisfiedLinkError: ...</code>)" mean?'''<br />
<br />
It probably means that you are running Linux and don't have Eclipse and a Web browser configured to work together. See [[http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux| installing a browser on Linux]].<br />
<br />
'''When downloading, why do I get a warning that the feature was unsigned?'''<br />
<br />
Signing plugins requires extra administrative details with <code>eclipse.org</code> which most plug-ins seek to avoid. <br />
<br />
'''N.B.''': Security issues with features should not be underestimated. Eclipse allows users to download new functionality from remote servers. A rogue plug-in can act as a perfect Trojan horse. It can look innocent enough and provide useful function while spawning threads in the background with full access to the local file system and the Internet (if connected). Beware of installing features from update sites you do not trust.<br />
<br />
'''What does "<code>Root exception: java.lang.UnsupportedClassVersionError: org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)</code>" mean?'''<br />
<br />
It probably means that the virtual machine is JDK1.4 or lower. See [[Mylyn_Installation_Guide#Download_and_configure_Java| download and configure Java]].<br />
<br />
'''Why am I getting messages in my <code><workspace>/.metadata/.log</code> or my Mylyn view that say things like <code>"java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()"</code> and "The activator <code>org.eclipse.mylar.java.MylarJavaPlugin</code> for bundle <code>org.eclipse.mylar.java</code> is invalid"?'''<br />
<br />
This probably means that your Mylyn download version didn't match your Eclipse download version. Note that [http://eclipse.org/mylar/dl.php the download site] has different downloads for Eclipse 3.1 and Eclipse 3.2.<br />
<br />
To fix this problem, see the [[Mylyn_Uninstallation_Guide| uninstallation guide]], then re-install from [http://eclipse.org/mylar/dl.php the correct download site].<br />
<br />
'''What does "Could not create Bugzilla editor input" and "<code>java.io.IOException</code>: SAX2 driver class <code>org.apache.xerces.parsers.SAXParser</code> not found" mean?'''<br />
<br />
It probably means that you are on MacOS, and for some reason are missing Xerces from the Mac JDK1.5. You will probably need to add it to your default classpath. Please refer to and comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=144287 bug 144287] if you see this problem.<br />
<br />
To ensure that you are using the 1.5 VM refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
'''I've just updated to Mylyn 2.0 and I don't see any tasks in my Task List'''<br />
<br />
As part of the update to Mylyn 2.0 the old data folder has been migrated to <workspace folder>/.metadata/.mylyn from the old location <workspace folder>/.mylar. IF for some reason migration failed (.mylar folder still exists), simply shut down Eclipse and manually move your old <workspace folder>/.mylar folder to <workspace folder>/.metadata/.mylyn (note the name change to .mylyn)<br />
<br />
== Configuration Troubleshooting == <br />
<br />
'''How can I change the number of editors left open before Mylyn starts closing editors?'''<br />
<br />
Turn off or increase the number of editors to leave open using ''Preferences -> General -> Editors -> Number of opened editors before closing''. Since Mylyn will manage the open editors with task activation, this number can be set higher or you can disable automatic closing entirely.<br />
<br />
'''Do I need the Outline View when running Mylyn?'''<br />
<br />
No, not really. The Package Explorer and folded signatures should provide enough context for you. If, at some point, you really need to see an Outline View, you can always enter (Ctrl+O) to show the in-place Outline View.<br />
<br />
'''What does the message "content assist proposals no longer appear" mean?'''<br />
<br />
This usually happens when uninstalling when using Eclipse 3.2. Make sure that the "Java Completions" and "Java Types" proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
'''Why do I get errors like "HTTP Response Code 407" or "Proxy Authentication Error" when accessing repositories through a proxy server?'''<br />
<br />
It is likely that you need to configure these proxy server settings. Select ''Window -> Preferences -> Install/Update'', and update the section in the "Proxy settings" section of the form.<br />
<br />
'''I can't use <code>Ctrl+Alt+Shift+Arrow Up</code> for'' Mark as Landmark''. What do I do?<br />
<br />
This is usually a Linux/GNOME problem, where the Gnome keyboard shortcuts are interfering with the Eclipse shortcuts. Go to the Keyboard shortcuts (which might be something like ''Desktop -> Control Centre -> Keyboard Shortcuts'' or ''System -> Preferences -> Keyboard Shortcuts'') and disable both of these shortcuts:<br />
* Move one workspace up<br />
* Move one workspace down<br />
<br />
See also: [[Mylyn_User_Guide#Keyboard_mappings_on_Linux| keyboard mappings on Linux]].<br />
<br />
'''How do I turn on spell checking?'''<br />
<br />
See [[Mylyn_User_Guide#Spell_Checking| spell checking]].<br />
<br />
== Uninstall troubleshooting ==<br />
<br />
When '''uninstalling in Eclipse''' Mylyn via the ''Help -> Software Updates -> Manage Configuration'' dialog you will need to uninstall dependencies first (e.g. Bugzilla Connector, Subclipse integration) and then uninstall the core Mylyn features.<br />
<br />
When '''uninstalling manually''' by deleting all of the Mylyn plug-ins and features from the <code>eclipse/plugins</code> and <code>eclipse/features</code> directory make sure to delete all of the plug-ins and then restart Eclipse with the -clean option (e.g. by inserting it into a shortcut or the <code>eclipse.ini</code> file.<br />
<br />
On '''Eclipse 3.1:''' you may need to reset the Java editor to be default for <code>.java</code> again via: ''Preferences -> General -> Editors -> File Associations''<br />
<br />
On '''Eclipse 3.2:''' if after uninstalling '''content assist proposals no longer appear''' you need to ensure that the ''Java Completions'' and ''Java Types'' proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
== I am seeing <code>java.lang.OutOfMemoryError: PermGen space </code>errors, what's wrong? ==<br />
<br />
If your Eclipse crashes, or you see the above error after installing Mylyn or other plug-ins, you have most likely hit the infamous MaxPermSize bug. This is not a Mylyn specific problem, but a general Eclipse problem that is often triggered on Eclipse 3.2 and later, if you have many plug-ins installed and are using a Sun JVM. <br />
<br />
To fix it simply add the following to your launch arguments. This is usually to your shortcut, or to the <tt>eclipse/configuration/config.ini</tt> file:<br />
<br />
-XX:MaxPermSize=128M<br />
<br />
If you are using a large number of plug-ins (e.g. WTP) you may need to increase the number to more than 128M. <br />
<br />
For more information see the [[FAQ How do I increase the permgen size available to Eclipse? | Eclispe FAQ entry]]. Details of the problem are on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250 Platform bug 92250].<br />
<br />
== What is Mylyn's performance profile? ==<br />
<br />
Mylyn should have '''no noticeable effect''' on Eclipse's speed or memory usage, no matter how large your workspace is. You do not need to increase the amount of memory Eclipse runs with to use Mylyn. Any performance issue should be [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Mylyn reported as a bug]. <br />
<br />
The current '''performance profile''' is:<br />
<br />
# Mylyn only runs if a task is active, and has no impact on Eclipse if no task is active.<br />
# Task context models have negligible memory overhead. <br />
# When a task is active, additional view refresh is required to update the views based on interest model changes. This should not be noticeable on Windows where refresh is very quick, but could be more noticeable on other platforms.<br />
# The time to activate a task context is dominated by the time it takes Eclipse to open the editors in the context. You can set the preference for how many editors to open in the Mylyn preference page (e.g. setting to 1 will dramatically reduce activation time, but also remove the benefit of having open editors correspond to the task context). You can also turn off editor management entirely in the Mylyn Tasks view pull-down.<br />
# Eclipse startup is slowed down by (4) if a task is active when Eclipse is shut down.<br />
# The low priority background searches that the Active Search view runs can be noticeable on slower machines.<br />
<br />
If you are seeing performance problems, this is either a bug or caused by other performance problems in Eclipse. If you are performance problems we suggest increasing the amount of memory available to Eclipse. This is especially useful for very large Java project workspaces, on which the size of JDT's element cache will grow proportionally to the amount of available memory. The setting we recommend for launching workspaces with a couple hundred large projects is:<br />
<br />
-Xmx768M -XX:MaxPermSize=128M<br />
<br />
= Task List =<br />
<br />
== Why won't the Archive category disappear? ==<br />
<br />
The ''Archive'' category will automatically appear if a task needs to be shown, but is not in any query or category. <br />
In order to ensure that you do not miss reminders or notifications the following tasks will always be shown in the Task List, even if they have been removed from a category or a query:<br />
* Tasks scheduled for this week or overdue. Remove these by using the ''Schedule'' pop-up menu option to defer them to a future week or to clear the schedule.<br />
* Repository tasks that have incoming changes, such as comments. Remove these by reading them or marking them as "read" via the ''Mark -> Read'' pop-up menu.<br />
<br />
== The Archive category contains many irrelevant tasks, how do I clean it up? ==<br />
<br />
If you created very broad queries you could end up with thousands of tasks in the Archive category. Other than clearing the <tt>workspace/.metadata/.mylyn/tasklist.xml.zip</tt> and <code>workspace/.metadata/.mylyn/offline</code> folder (note that this will entirely reset your Task List) the easiest option is to:<br />
* Clean up your queries to include only tasks of interest (note that including completed/resolved tasks is recommended).<br />
* Turn off ''Focus on Workweek'' in the ''Task List''.<br />
* Turn off the ''Filter Archive Category'' option in the ''Task List'' view menu.<br />
* Delete all of the unneeded tasks from within the Archive category. Note that if the tasks are not matched by queries they will be deleted permanently and any local notes or scheduling information that you have added to them will be lost.<br />
<br />
== How does Mylyn count the active time for a task? ==<br />
<br />
Whenever you work on a task, Mylyn accumulates the time you spend actively working on a task. This time can be viewed in the ''Personal Planning'' section of the ''Task Editor''. When you are not interacting with Eclipse, the timing automatically times out after 3 minutes by default. This means that activity outside of Eclipse will not be captured when you work on the task and that the timings in Mylyn are a lower bound of the total time spent on the task (capturing timings for work done outside of Eclipse involves OS specific extensions).<br />
<br />
== How do I prevent long-running tasks from adding to the progress bar? ==<br />
<br />
If you have many long-running or recurring tasks scheduled for this week, they can affect the ''Task List'' weekly progress bar. This can be misleading as they may never be completed. The current work-around to prevent long-running tasks from being included in the weekly progress bar is to schedule their estimated time to be 0 (zero). Alternatively, you can schedule only the amount of time you plan on spending on that task this week.<br />
<br />
== Does the Task List replace the Eclipse Tasks view? ==<br />
<br />
The SDK's ''Tasks'' view is used for showing markers such as 'todo' tags which indicate a local problem with a resource, similar to a compiler warning. As such, these 'tasks' are at a much lower level of granularity than Mylyn's tasks, and one task could involve cleaning up multiple todos. In order to make working with only the markers in a particular task context, e.g. for clean-up before committing, the ''Apply Mylyn'' filter is available for both the ''Problems'' and the ''Tasks'' views.<br />
<br />
== What if I use multiple workspaces? ==<br />
<br />
Mylyn's support for multiple workspaces is currently limited (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130658 bug 130658] for a discussion) because the Task List is considered to be specific to the person, and not to the workspace. We recommend configuring your Eclipse workspace to use working sets instead of relying on multiple workspaces. <br />
* John O'Shea's blog: [http://www.xlml.com/aehso/2007/02/02/eclipse-workspaces-containing-projects-with-overlapping-locations-and-mylar/ Eclipse workspaces containing projects with overlapping locations, and Mylar]<br />
<br />
If using a single workspace is not possible you can do the following:<br />
* In ''Preferences -> Mylyn -> Task List'' set the ''Data Directory'' to be a shared location, and do this for both workspaces.<br />
* Be sure to avoid launching both Eclipse workspaces at the same time, as changes in one workspaces could overwrite the Task List in the other workspace.<br />
* If you upgrade Eclipse or move your workspace and don't see your tasks, check the ''Data Directory'' setting.<br />
<br />
== How do I export my task and repository data? ==<br />
<br />
Export via File > Export > Mylyn > Task Data<br />
<br />
== Why does Mylyn use the term "task"? ==<br />
<br />
There are many work items that make up the developer's workday. Many issue trackers and project management tools refer to these as: bugs, defects, actions, tickets, stories, enhancements, and the list goes on. We refer to all such work items as "tasks" because the word tasks is short and commonly used in time management tools. Task Repository connectors can customize the presentation of tasks, for example, indicating which is a defect and which is an action item.<br />
<br />
== Why are closed tasks not greyed out on Linux? ==<br />
<br />
If you are running Eclipse from KDE go to KControl -> GTK Styles and Fonts and select "Use another style" in the GTK Styles section ({{bug|206399}}).<br />
<br />
= Task Editor =<br />
<br />
== When I submit a new bug to eclipse.org the priority isn't updated? ==<br />
<br />
Eclipse.org's Bugzilla repository forces all new bug reports to priority 3 (P3) regardless of what is selected in Mylyn. Eventually we will disable this field in the new bug editor for bugs.eclipse.org and provide a tooltip with explanation ( {{bug|204630}} ).<br />
<br />
== Why am I seeing strange boxes where I expect to see proper characters? ==<br />
<br />
If for example you aren't seeing the proper single quote chacters in the summary of [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=197644 bug#197644]], check that the encoding is set correctly for the repository in the asociated Task Repositories view (Properties > Additional Settings > Character Encoding). For bugs.eclipse.org/bugs set your charcter encoding to ''ISO-8859-1''.<br />
<br />
= Task Repositories =<br />
<br />
== What if I'm not using a Task Repository? ==<br />
<br />
Mylyn does not require the use a of a task repository and can be used entirely with the ''Local Tasks'' repository that it comes bundled with. However, if working with a team, a shared ''Task Repository'' provides the key infrastructure needed to let your team work in a Task-Focused way via Mylyn's collaborative facilities.<br />
<br />
Those not currently using another supported ''Task Repository'' should consider the repositories currently [http://www.eclipse.org/mylyn/downloads/ supported by Mylyn] as well as those supported by the [http://wiki.eclipse.org/index.php/Mylyn_Extensions third party Mylyn extensions].<br />
<br />
== What if Mylyn doesn't support my task/bug/issue/ticket repository? ==<br />
<br />
To see support for your repository faster, do a search of the open repository connector requests and [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Bconnector%5D&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=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= vote for the corresponding bug] if your tracker is there, or [http://www.eclipse.org/mylar/bugs.php create a new bug]. <br />
<br />
[[Mylyn_User_Guide#Generic_Web_Repository_Connector|Generic Repository Connector]], allows creating Queries to the web-based issue tracking repositories and get list of issues from the web UI into the Task List.<br />
<br />
It is also possible to link a ''local task'' with the web page in web-based repository via the Mylyn Web integration.<br />
<br />
'''To create a task from any web-based repository:'''<br />
<br />
* Drag the URL from the address bar of the browser, or from a hyperlink in a bug listing to the ''Mylyn Tasks'' view. This will create a task for the bug, link it to the page, and populate the description with the title of the corresponding page. '''In Mozilla:''' simply drag the URL. '''In Internet Explorer:''' you must have <code>Ctrl</code> pressed in order for Eclipse to recognize the drop.<br />
* '''Alternatively,''' you can copy the URL, press the ''New Task'' button on the ''Mylyn Tasks'' view. This has the same effect as above but you can edit the description after retrieving it.<br />
* Opening the task will now open the corresponding issue. You can also <code>right+click</code> the task and select ''Open in External Browser''.<br />
<br />
[[Image:mylar-tasklist-weblink-editor.gif]]<br />
<br />
== Why were my repository credentials reset? ==<br />
<br />
If you upgrade Eclipse or your Java VM, you will need to reset your credentials in the ''Task Repositories'' view because these are stored in the secure Eclipse workbench keyring. Also see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=149607 bug 149607]. If you are migrating '''from Eclipse 3.2 to 3.3''' note that you will need to use a different update site, which is listed here: http://eclipse.org/mylyn/dl.php<br />
<br />
== Why are my updated repository attributes not showing up? ==<br />
<br />
Your server's repository attributes can change frequently, for example, there can be a new "milestone" or "version" added to the Bugzilla repository with each release. When the ''Preferences -> Mylyn -> Task List -> Synchronization'' setting is enabled, every 10th synchronization will update the attributes from the repository. If you do not have this setting enabled, your can force the update via the ''Update Attributes'' action on the task repositories' context menu in the ''Task Repositories'' view. Note that you will need to reopen a task editor to see the updated attributes. If you instead update via the button on the ''Attributes'' section of the ''Task Editor'' the attribute settings will be reloaded without needing to reopen.<br />
<br />
== Authentication Troubleshooting ==<br />
<br />
You must ensure repository credentials are filled out correctly. Refer to the diagram below:<br />
<br />
[[image: AuthenticationTroubleshooting2.png|right]]<br />
<br />
# Enter the repository URL (i.e. https://bugs.eclipse.org/bugs) and an optional label<br />
# Credentials<br />
#* Usually email address and password <br />
#* Some sites, such as <code>dev.eclipse.org</code>, use anonymous logon with password left blank.<br />
#Http Authentication (optional)<br />
#* Some sites are protected by either BASIC or DIGEST http authentication. If this is the case, enter appropriate credentials here.<br />
#* One way to test if the site requires http authentication is to point your browser at the repository. If you are presented with an authentication dialog popup, the site is likely protected by http authentication.<br />
#Proxy Server Configuration (optional)<br />
#* By default Mylyn uses the Platform's Install/Update proxy settings. Uncheck this box if you wish to use an alternative proxy.<br />
#* If the proxy requires authentication, this is where you enable and enter your proxy credentials.<br />
#* If you are experiencing connection problems, ensure your Install/Update proxy settings are valid or the repository specific settings are correct<br />
#* Mylyn has been tested with HTTP proxy servers. Currently SOCKS is not supported.<br />
#Validate Settings <br />
#*Press the ''validate'' button to test the settings<br />
#*If you are seeing errors like "HTTP Response Code 407" or "Proxy Authentication Error" it is likely that you need to configure proxy settas as described above.<br />
#*If your sever uses a certificate and fails to connect, e.g. you see exceptions <tt>sun.security.validator.ValidatorException: PKIX path building failed</tt> then you need to point Eclipse at your certificate, see below.<br />
<br />
=== Certificate authentication ===<br />
<br />
In order to use client certificates for authentication you need to create a Java keystore and import your existing certificate to it. This command will import your certificate from /tmp/certificate.pem and create a keystore in /path/to/.eclipsekeystore. <br />
<br />
keytool -import -keystore /path/to/.eclipsekeystore -file /tmp/certificate.pem<br />
<br />
See [http://java.sun.com/j2se/1.5.0/docs/guide/security/SecurityToolsSummary.html this page] for links to the keytool documentation.<br />
<br />
Add the path to the keystore to your eclipse.ini in your eclipse install directory: <br />
<br />
-Djavax.net.ssl.keyStore=/path/to/.eclipsekeystore<br />
<br />
If your keystore is protected by a password add that as well:<br />
<br />
-Djavax.net.ssl.keyStorePassword=123456<br />
<br />
More [http://ahtik.com/blog/2006/05/11/fixing-eclipse-mylar-jira-integration/ instructions on this blog].<br />
<br />
=== NTLM authentication ===<br />
<br />
For NTLM authentication to work a special format for the username needs to be used where ''DOMAIN'' needs to be replaced by the Windows login domain: <br />
<br />
DOMAIN\username <br />
<br />
The built-in NTLM support of the JDK which is used by Eclipse does '''not work''' with Mylyn since it uses the HttpClient library to access repositories. Limitations in regard to NTLM authentication are documented in the [http://wiki.apache.org/jakarta-httpclient/FrequentlyAskedNTLMQuestions NTLM FAQ] and also discussion on {{bug|201911}}.<br />
<br />
* If your repository uses MS NTLM authentication and only standard http authentication is being passed to the repository this can result when the local hostname cannot be resolved. Ensure your machine's hostname is set correctly and resolves to a valid address.<br />
* It is not possible to use NTLM authentication for the proxy as well as for the repository.<br />
<br />
If NTLM authentication fails the '''[http://ntlmaps.sourceforge.net/ NTLM Authorization Proxy Server]''' has been reported to '''work''' with Mylyn.<br />
<br />
== Why are task hyperlinks not working? ==<br />
<br />
For task hyperlinks in textual editors (e.g. Java editor) and other text viewers (e.g. History view comments) you must associate the project that contains the resource to the task repository. <br />
<br />
:''Project association can also come from 3rd party metadata trough the contrubuted [[Mylar_Integrator_Reference#Mapping_from_projects_to_Task_Repositories|extension point]]. [http://subclipse.tigris.org/ Subclipse] and [http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Mylyn Maven integration for Eclipse] plugins contributing it. See few more details [http://jroller.com/page/eu?entry=linking_projects_from_the_eclipse here].''<br />
<br />
Note that to view a hyperlink you must hold down the <code>Ctrl</code> key when hovering over the reference to the task. References to tasks are connector specific and the common reference is found on the top left of the task editor and other conventions tend to follow those used in the web UI (e.g. "bug 123" for Bugzilla, "ABC-123" for JIRA).<br />
<br />
[[Image:mylyn-project-repository-association.gif]]<br />
<br />
= Bugzilla Connector =<br />
<br />
== What versions are supported? ==<br />
<br />
We recommend using the latest [http://www.bugzilla.org/download/ release] of Bugzilla.<br />
<br />
* '''Bugzilla 2.18.6 is the lowest version of Bugzilla supported'''. If you are getting errors that indicate failure to update attributes this may be an indication that the Bugzilla server is not supported (< 2.18.6).<br />
<br />
*If you are using '''Bugzilla 2.18''' and are getting '''mid-air collisions''' this is likely due to incorrectly formatted timestamp field in the underlying bugs database table ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149513 bug 149513]). This can be resolved by upgrading to Bugzilla 2.20 or later.<br />
<br />
== Why are queries failing? ==<br />
<br />
*If '''queries are not working''' correctly ensure that you have the right Bugzilla server version selected for the corresponding repository: ''Task Repositories (View) ->'' right+click the repository ''-> Properties''. For supported versions see the [http://www.eclipse.org/mylar/dl.php download page]. If the repository is still not functioning it may be due to authentication or connectivity problems. If that does not resolve the problem please post a message to the newsgroup or [http://www.eclipse.org/mylar/bugs.php submit a bug].<br />
<br />
== Why do I see my old username? ==<br />
<br />
If you change the username/email address on your Bugzilla account you may notice that some tasks still have the old username/email. Explicitly synchronize the task via the ''Task List'' popup menu or ''Task Editor'' toobar in order to update your username.<br />
<br />
== Why do tasks fail to open? ==<br />
<br />
*If upon opening a bug, the Bugzilla tab only displays a warning "'''Could not download task data, possibly due to timeout or connectivity problem. Please check connection and try again.'''", ensure that your repository is returning XML data by pointing your browser to <code><your-repository-url>/show_bug.cgi?id=1&ctype=xml</code> to show the contents of bug 1 in XML form. The Bugzilla client requires that bugs be accessible in XML form. If the repository doesn't support xml then it is likely that the repository is too old (Mylyn currently supports Bugzilla 2.18 and later).<br />
<br />
* If '''reports fail to load''' or '''reports fail to synchronize''' (task description remains ''italic''), check the error log for a "'''File not found'''" error pointing to <code>bugzilla.dtd</code> or a "'''Failed to retrieve products from server'''" error message, these can result when <br />
** the <code>urlbase</code> parameter is not set on the bugzilla server<br />
** your <code>urlbase</code> parameter is incorrect, e.g. it contains <code>index.cgi</code><br />
** your bugzilla installation is missing the <code>bugzilla.dtd</code> file. See: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=161759 bug#161759]<br />
<br />
<br />
* If '''attributes are missing options''' in the bug editor (ie. missing a recently added milestone, [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155431 bug# 155431]):<br />
** Update attributes by choosing ''Update Attributes'' from the context menu in the ''Task Repositories'' view<br />
** Synchronize the task in the Task List<br />
** Reopen the task - new options should be available.<br />
<br />
== Why do tasks fail to submit? ==<br />
<br />
* '''Error upon submit: unable to make any match for name/email entered.''' If your bugzilla is configured for user names rather than full email address the QA Contact field will cause the submit to fail ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=166555 bug# 166555]). To resolve, select 'Local users enabled' option on the Repository Configuration page. <br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your account's username and password and are not using the HTTP authentication fields instead.<br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your bugzilla instance's cookie domain under the required settings. The cookie domain must lead with a dot.<br />
<br />
* If '''attachments are failing to submit''' and you see that after processing the attachment, the bugzilla bug shows a size of "bytes" (no numbers), your database may be dropping the packet sending the file. '''On MySQL''', check the [http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html max_allowed_packet directive]. You may see errors like: <code>DBD::mysql::st execute</code> failed: Got a packet bigger than 'max_allowed_packet' bytes [for Statement "INSERT INTO attach_data (id, thedata) VALUES (38, ?)"] at <code>/path/to/bugzilla/attachment.cgi</code> line 993. Also, '''check the maximum attachment size''' in ''Bugzilla Parameters -> Attachments''.<br />
<br />
* If a submit fails with an '''Invalid Username or Password''' error even though repository settings do validate, make sure that cookies could be set. See also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175502 bug 175502]<br />
<br />
== What time zone is used in the task editor? ==<br />
<br />
*The '''times''' that appear in the Bugzilla bug editor (ie. created, modified) '''are local to the server hosting the Bugzilla repository''', not your local machine's time zone. <br />
<br />
== Known limitations ==<br />
<br />
* The <code>usermatchmode</code> is not currently supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168204 bug 168204]) and as such full email addresses need to be used.<br />
<br />
* The <code>usevisibilitygroups</code> parameter is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=180876 bug#180876]). Group assignment will currently be lost if updated using the Bugzilla rich task editor.<br />
<br />
* Version 1.0 of Mylyn presents an error message upon new comment submission to RedHat's public Bugzilla repository. The comment is in fact posted. This issue is resolved in Mylyn 2.0M2 and higher. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=183251 bug#183251])<br />
<br />
= JIRA Connector =<br />
<br />
If you see errors like the following, work around this by opening repository ''Properties Page'' and clicking OK (bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169102 169102]).<br />
<br />
org.tigris.jira.core.service.exceptions.AuthenticationException<br />
at org.tigris.jira.internal.core.service.soap.SoapJiraService.getProjectsNoSchemes(SoapJiraService.java:204)<br />
<br />
== What are the server requirements? ==<br />
<br />
The '''JIRA SOAP/RPC services have to be running on the JIRA server''':<br />
<br />
* Jira 3.3.3 or higher (3.7 or higher for attachment retrieval)<br />
* Jira RPC plugin 1.4.3 or higher<br />
<br />
Latest information also available on the [http://www.eclipse.org/mylar/dl.php download page].<br />
<br />
Related Resources:<br />
<br />
* [http://confluence.atlassian.com/display/JIRA/JIRA+Development+Hub Jira Development Wiki]<br />
* [http://confluence.atlassian.com/pages/viewpage.action?pageId=1035 Jira RPC Plugin Overview]<br />
<br />
== Why can't I connect? ==<br />
<br />
* If you get a <code>org.tigris.jira.core.service.exceptions.ServiceUnavailableException</code> you need to turn on the JIRA SOAP/RPC services on the server.<br />
* Similarly, if you get a "Processing instructions are not allowed within SOAP messages" message, ensure that SOAP/RPC services are on.<br />
* If you get a '''503''' error code verify that the SOAP/RPC interface is enabled.<br />
* If you get a '''403''' error code verify that the SOAP/RPC interface is enabled, and also check your authentication mechanism. If the server is using NTLM authentication, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156397 bug 156937] for diagnosis steps.<br />
* If you see an '''"unrecognized priority" message''' in the ''Error Log'', the problem is that the JIRA Connector does not support customized priorities so the priority value specified in that message will not correspond to the priority icons visible in the Task List.<br />
* If you are being '''prompted for your log-in credentials''' by the Browser tab of the task editor or the new task editor, this is because without rich editor support the connector is using the web-based UI instead of logging in on your behalf as is done with a rich task editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142869 bug 142869]).<br />
* If you get a <CODE>AuthenticationException</code> and a query won't synchronize, use Task Repositories (view) -> Properties (on the repository) -> Validate Settings. This will clear the connection if it died.<br />
<br />
== Why do I get a "JIRA connector requires server 3.3.3 or later" message? ==<br />
<br />
Version 2.0 of the Jira connector misinterprets version 3.10 as being lower than version 3.3.3. This is fixed in version 2.1 of the connector. Mylyn 2.1 is not compatible with Eclipse 3.2, but Eclipse 3.2/Mylyn 2.0 users can download a later version of the Jira connector from the weekly build download site; the latest Jira connector supports Mylyn 2.0 and Eclipse 3.2. If you get a NullPointerException from the update manager, make sure you've only searched the weekly download Extras site; don't search the 2.0 site at the same time.<br />
<!-- HEAVILY OUTDATED. PLUGIN NOW USES COMMON PROXY INFRASTRUCTURE<br />
== Why can't I synchronize when using a proxy server? ==<br />
<br />
* Proxy configuration is '''based on the normal Java HTTP system properties''', which can be configured either by launching Eclipse with <code>-vmargs</code> and using the following settings, or by putting these settings into the or by putting the following into the <code>eclipse/eclipse.ini</code> file (after -vmags):<br />
-Dhttp.proxyHost=<host> <br />
-Dhttp.proxyPort=<port><br />
* Make sure that when using these settings you do not enable the proxy settings on the ''Install/Update'' preference page, since they may override these settings.<br />
* If you are using '''SSL''', you will also need to set the <code>https.proxyHost</code> and <code>https.proxyPort</code>. <br />
* Authentication is configured with the <code>http.proxyUser</code> and <code>http.proxyPassword</code> system properties (also for SSL)<br />
* You can also use <code>http.nonProxyHosts</code> system property to enumerate hosts that should not be proxied. Note that matching is implemented on the exact host name used for JIRA server and patterns are not supported. --><br />
<br />
== Known limitations ==<br />
* Attachment retrieval (including retrieval of the task context and attachment list in the task editor) require JIRA 3.7 or above ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=169757 bug 169757])<br />
<!-- * NTLM authentication is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172395 bug 172395]) --><br />
* Customized priorities are not currently supported, so all issues with a customized priority will have the default priority level ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=165518 bug 165518]).<br />
* blank but editable custom fields doesn't appear in the RSS data, and as result we can't show them for editing<br />
* because of JIRA api limitations, we can support custom fields in the task editor, but not in the new custom task editor<br />
<!-- * On JIRA 3.6.x private filters saved on the server can fail to retrieve results ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=174328 bug 174328]). The work-around is to create a custom query in Mylyn using the form-based query designer or to share the filter in JIRA. --><br />
* Mylyn only allows the usage of US-ASCII characters in the filename when uploading an attachment ({{bug|203663}})<br />
<br />
== How can I enable compression for SOAP messages? ==<br />
<br />
If your repository has lots of projects and components you can speed up the download of the repository configuration by enabling compression. <br />
<br />
* Add a filter-mapping to your JIRA server configuration: [http://jira.atlassian.com/browse/JRA-10353].<br />
* Enable compression in your global JIRA configuration.<br />
* Check the compression setting for your task repository in Mylyn versions 2.0M2 and later.<br />
<br />
== Reporting issues ==<br />
<br />
Since JIRA can be heavily customized there is a chance that some particular customizations may not work, so if you can't connect to your proprietary repository it is a good idea to try the following public repositories to make sure you have working configuration:<br />
<br />
* http://jira.codehaus.org<br />
* http://issues.apache.org/jira/<br />
* http://opensource.atlassian.com/projects/spring <br />
<br />
If you can't get query results, you could try to call "Open with Browser" on query node in the Task List view and then save link "Current view: XML" and attach it to the bug report.<br />
<br />
Even if query don't work you could try "Open Repository Task" from your JIRA repository node on the Task Repositories view and check if you can open JIRA task editor for that issue. Same for the Task search (Ctrl-H, Task Search)<br />
<br />
To investigate various error you may need to enable debug tracing. To do that you need to create the <code>.options</code> file with the following content:<br />
<br />
<pre><br />
org.eclipse.mylyn.jira.ui/connector=true<br />
org.eclipse.mylyn.jira.ui/dataHandler=true<br />
</pre><br />
<br />
and then add the following options to the Eclipse command line (or eclipse.ini file):<br />
<br />
<pre><br />
-debug <path to the .options file>/.options<br />
</pre><br />
<br />
The additional logging will go into the regular Eclipse log and the Error Log view<br />
<br />
== Why do I get errors about an unexpected redirect when submitting an issue? ==<br />
<br />
Please go to the repository properties and validate the repository. If errors about circular redirects are logged in your Eclipse error log your JIRA server or proxy might be misconfigured. <br />
<br />
In some cases unexpected redirects can be caused by a JIRA server accessed via Apache and mod_jk (using the AJP/1.3 Tomcat connector). Some server configurations may benefit from the 'proxyHost', 'proxyPort', 'scheme' and 'secure' settings on the AJP Connector in the Tomcat server configuration.<br />
<br />
Please see {{bug|202834}} for a more details.<br />
<br />
= Trac Connector =<br />
<br />
== What are the server requirements? ==<br />
<br />
The Trac connector offers two access methods:<br />
<br />
'''XML-RPC''' (recommended)<br />
<br />
Requirements:<br />
* Trac 0.10<br />
* [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] rev. 1950<br />
<br />
This access method offers editing of tasks in a rich editor, attachment support and offline editing. It requires the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] for Trac to be enabled for the accessed repository. The XmlRpcPlugin provides a remote interface to the Trac repository and is distributed separately from Trac (see [http://trac.edgewall.org/ticket/217 #217]). See these [http://trac-hacks.org/wiki/XmlRpcPlugin#Installation install instructions] for requirements and documentation.<br />
<br />
'''Web''' <br />
<br />
Requirements:<br />
* Trac 0.9 or later<br />
<br />
In this mode the standard Trac web interface is used for repository access. Tickets may be created and edited through a web browser. Offline editing and attachments are not supported.<br />
<br />
== Recommended Trac version ==<br />
<br />
Mylyn should work with any stable release Trac release that is version 0.9.x or 0.10.x (see below for known limitations). Mylyn works best when used with Trac's XML-RPC Plugin (see above) but we do not recommend a particular Trac version. <br />
<br />
The Trac connector tests are run against these Trac versions:<br />
<br />
* Trac 0.10.4, XML-RPC Plugin rev. 1950<br />
* Trac 0.9.6<br />
<br />
See {{bug|175211}} for details about Trac 0.11 support.<br />
<br />
== Why do I get an HTTP Error 500 Internal server error when creating a ticket that contains non-ASCII characters? ==<br />
<br />
Problems related to character encodings have been reported when Trac is run with Python 2.3. Upgrading to Python 2.4 may help to resolve this. Please comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=188363 bug #188363] if you encounter an internal server error when creating a ticket that contains non-ASCII characters.<br />
<br />
== Known limitations ==<br />
<br />
* Trac 0.10.1 <br />
** Known incompatibility with Trac XML-RPC Plugin. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164272 bug 164272] for details.<br />
* Trac 0.10.3 <br />
** Known incompatibility with old versions of the Trac HttpAuthPlugin (fixed in revision 1890 or later). The plug-in enables basic auth for XML-RPC when Trac AccountManagerPlugin for form based authentication is used. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168413 bug 168413] for details.<br />
* Trac 0.11<br />
** Currently untested.<br />
** Known incompatibility with Trac XML-RPC Plugin See [http://trac-hacks.org/wiki/XmlRpcPlugin] for details.<br />
<br />
== Why are tasks opened in a web browser and not in the rich editor? ==<br />
<br />
Please make sure that the access type in the repository properties is set to XML-RPC. This requires Trac 0.10 and XML-RPC (see above).<br />
<br />
== Which URLs does Mylyn access in a Trac repository? ==<br />
<br />
XML-RPC:<br />
<br />
* The expected URL is either /xmlrpc or /login/xmlrpc (if login credentials are provided)<br />
<br />
Web:<br />
<br />
* Authentication: /login <br />
* Querying: /query?format=tab...<br />
* Synchronizing ticket details: /ticket/...<br />
* Getting repository configuration to populate query dialog: /query or /newticket<br />
<br />
The web mode relies on screen scraping and is likely to fail if the design<br />
(i.e. HTML output) of the Trac repository is heavily customized.<br />
<br />
= Generic Web Repository Connector =<br />
<br />
== Where can I find the web repository connector ==<br />
<br />
It is available from the extensions update page. Please see http://www.eclipse.org/mylyn/downloads/<br />
<br />
== Why can't I connect using one of the existing templates? ==<br />
<br />
<br />
The Web Repository Connector have a Preview option in Advanced Configuration section on the Query preferences. If you get an error or preview table does not show expected list of tasks you can use Query Pattern like (.+?)(\n) to see content of the retrieved page and compare it with the source of the web page for the same url loaded into the web browser.<br />
<br />
If that does not help then you could use the wget tool (on Windows it available as a standalone command line tool and also included with Cygwin).<br />
<br />
Run the following command:<br />
<br />
<pre>wget -v -d -o query.log -O query.html "http://your.query.url"</pre><br />
<br />
If repository require basic http auth, you'll need to use ''--http-user=USER'' and ''--http-password=PASS'' options.<br />
<br />
Then open file ''query.html'' in the web browser and check if it show list of issues you need to fetch from the web server. If it does have correct list, then there could be a problem with query pattern used for parsing. <br />
<br />
A popular mistake is an unmasked '?' that separates request parameters in the url). For example:<br />
<br />
<pre><a href="show_bug.cgi\?id\=(.+?)">.+?<span class="summary">(.+?)</span></pre><br />
<br />
If ''query.html'' does not show expected list of issues you can check ''query.log'' for server responses and try to identify if server require authentication, redirecting your requests somewhere or issue any other errors.<br />
<br />
== Known limitations ==<br />
<br />
* In Mylyn 1.0: if a web server responds by requesting a redirect to an absolute URL while fetching a resource, the connector falsely prepends "/" to the URL and the request will fail. The workaround is to use final url where redirect is pointing to (you can find it as describe above). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=167282 bug 167282] for details.<br />
<br />
= Task-Focused UI =<br />
<br />
== What is the Task-Focused UI? ==<br />
<br />
When you activate a task, Mylyn automatically maintains a task context by monitoring your interaction. The task context provides a predictable degree-of-interest weighting of the relevance of the elements and relations that you work with to the task-at-hand (as described in the [http://kerstens.org/mik/publications/2006-11-mylar-fse.pdf Foundations of Software Engineering conference paper]). The Task-Focuse UI is the mechanism by which Mylyn presents Mylyn the task-context model in order to reduce information overload and to automate the manaul management of UI elements like editors and change sets. Examples:<br />
* Filtering, decoration and expansion management in views<br />
* Automatic folding in editors<br />
* Ranking in content assist<br />
* Editor management<br />
* Perspective management<br />
* Change set management<br />
<br />
== Why do files disappear from Focused views when I close them? ==<br />
<br />
By default Mylyn automatically manages the set of open files to match the task context, so that you don't have to. This ensures that the editor list (viewable via mechanisms like Ctrl+E) corresponds to what you in views like the ''Package Explorer'' when they are in Focused mode. When you close a file manually, you express that it is uninteresting, and as such it will be removed from the task context. It will also disappear from the corresponding automatically managed change sets for the same reason. This behavior can be turned off via ''Preferences -> Mylyn -> Context -> Manage open editors to match task context''. However, it is highly recommended since Mylyn will prevent the number of editors from bloating by automatically closing editors for elements that have decayed in interest, and always keep the editors for interesting elements open.<br />
<br />
<br />
== Why did all my editor tabs disappear? ==<br />
<br />
When you deactivate a task, all editors will be closed, and then when you reactivate the task all the windows will be open again. Try it, it's fun. <br />
<br />
Mylyn actively manages your open editors with task context. It takes some getting used to, but enables switching between tasks when you are multitasking without cluttering your editor tabs. This editor management can be disabled via ''Window -> Preferences -> Mylyn -> Context''. However, before disabling it consider reading the ''"Managing open editors..."'' section of [http://www-128.ibm.com/developerworks/java/library/j-mylar2/index.html#N10116 Task-focused programming with Mylar].<br />
<br />
== How do I get rid of an element if it is not interesting? ==<br />
<br />
When a view is focused elements will disappear on their own if they are not repeatedly selected via a mechanism called interest decay. Note that decay does not use the wall clock, but instead relies on the number of selections that you have made when working on that task to determine which elements disappear. This helps make it feel very predictable.<br />
<br />
If you want want to force one or more elements to disappear from the context use the '''Remove from Focus''' action on the context menu. Note that the element will still be part of the task context since it was previously part of the interaction. <br />
<br />
If you want to permanently delete the element from the interaction history use the '''Remove from Context''' action on the '''Context''' tab of the '''Task Editor'''. For example, if a company private element was part of a task context that is to be shared with a public repository, this action can be used to clean it up before sharing. Note that elements will be removed from the task context recursively.<br />
<br />
== Which Focused UI features can I turn off? ==<br />
<br />
'''All of them.''' When no task is active neither are any of Mylyn's features. When working with task contexts Mylyn's Focused UI features are all optional and in general configurable. While many find it the key benefit of Mylyn, the entire Focused UI is optional and can be uninstalled via ''Help -> Software Updates -> Manage Configuration''.<br />
<br />
The following table summarizes how the key features can be toggled:<br />
<br />
<table><br />
<tr><br />
<td>'''UI Mechanism'''</td><br />
<td>'''Example/description'''</td><br />
<td>'''Toggle using'''</td><br />
</tr><br />
<tr><br />
<td>Interest filtering</td><br />
<td>Package Explorer</td><br />
<td>''Apply Mylyn'' button on view toolbar</td><br />
</tr><br />
<tr><br />
<td>Automatic toggling of filtering</td><br />
<td>Package Explorer</td><br />
<td>''Preferences -> Mylar -> Context -> Toggle focused mode..</td><br />
</tr><br />
<tr><br />
<td>Interest decoration</td><br />
<td>Bolding of landmark elements</td><br />
<td>''Preferences -&gt; General -&gt; Appearance -&gt; Label Decoration''</td><br />
</tr><br />
<tr><br />
<td>Content assist</td><br />
<td>Ranking of interesting elements</td><br />
<td>Eclipse 3.2: ''Java -&gt; Editor -&gt; Content Assist -&gt; Work in Progress -&gt;'' turn off Mylyn, turn on Java</td><br />
</tr><br />
<tr><br />
<td>Active change sets</td><br />
<td>Grouping of changes by tasks</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Team''</td><br />
</tr><br />
<tr><br />
<td>Editor management</td><br />
<td>Auto opening/closing of editors</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Editor Management''</td><br />
</tr><br />
<tr><br />
<td>Active views</td><br />
<td>Active Search and Hierarchy</td><br />
<td>Only on if view is active</td><br />
</tr><br />
</table><br />
<br />
For additional configuration options see the ''Mylyn'' and ''General -> Appearance'' preference pages.<br />
<br />
<br />
<br />
== What happened to the Active Search and Active Hierarchy views? ==<br />
<br />
These views were not included in the Mylyn 1.0 release because they never made it beyond the experimental phase. <br />
* The ''Active Search'' view has not been sufficiently tuned to adapt to the lifecycle of a task context, and as a result requires manual manipulation of the degree-of-separation scope as you work on long-running tasks. Otherwise it becomes overloaded with elements. In addition, it is not yet clear whether an additional view is the right UI for this facility, and it is hard to find room for an additional view of this size on screen resolutions of 1600x1200 and smaller.<br />
* The ''Active Hierarchy'' view is also hard to allocate space for, especially when using the in-place hierarchy (Ctrl+T) on a landmark can be a quick way to see the relevant part of the task context's hierarchy.<br />
<br />
These features still show promise in displaying task context and saving repetitive searches, so we have not removed them. They have instead moved to the Mylyn Sandbox, and can be used and experimented with by following the [http://wiki.eclipse.org/index.php/Mylyn_Contributor_Reference#Sandbox instructions on the Contributors page]. For feedback on these views please use the corresponding bug reports or newsgroup.<br />
<br />
= Java Development =<br />
<br />
== Content assist troubleshooting ==<br />
<br />
Mylyn uses custom Content Assist processors in order to rank and separate the elements in the current task context. To see proposals ranked according to interest you must have only the ''Type Proposals (Mylyn)'' kinds checkbox enabled in the list below, otherwise you will see duplicates. '''If you do not see any proposals, check this list''' to ensure that either the Mylyn or the plain proposals are enabled. '''To do this automatically''', run ''New -> Mylyn -> Recommended Preferences''. Or you can select them manually as in the preference page below. <br />
<br />
[[Image:mylar-content-assist-prefs.gif]]<br />
<br />
'''Why do I see duplicate proposals?'''<br />
<br />
Ensure that you have only the ''(Mylyn)'' proposals kinds enabled in ''Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced'', otherwise you will see duplicates.<br />
<br />
If you use proposals via Ctrl+Shift+Space instead of the typical Ctrl+Space you will see duplicates. Vote for JDT/Text [https://bugs.eclipse.org/bugs/show_bug.cgi?id=147781 bug 147781] if you use this mechanism. Also see: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=129080 bug 129080]<br />
<br />
'''Why do I get an error message when using content assist?'''<br />
<br />
If after invoking Content Assist you see an error message dialog that states:<br />
The extension took too long to return from the 'computeCompletionProposals()' operation<br />
this is most likely due to something interrupting the proposal operation (e.g. garbage collection). Ignore it if it does not recur, increase Eclipse's memory if it does (e.g via <code>-Xmx384M</code> command line argument). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=141457 bug 141457] for more details. <br />
<br />
Note that Mylyn should only add a trivial amount of overhead to content assist computation, however, the standard content assist mechanism will not report timeouts of this sort (i.e. taking longer than 5s to compute proposals). If the system that you are working on is so large that increasing memeory does not reduce the timings to avoid the message, you could also consider disabling the Mylyn-specific content assist, as described above, but if doing so please comment on {{bug|141457}}.<br />
<br />
[[Image:mylyn-content-assist-timeout.gif]]<br />
<br />
== Why do interesting elements not show in the Project Explorer? ==<br />
<br />
The ''Package Presentation -> Hierarchical'' mode is not supported on the ''Project Explorer'' view in Eclipse 3.2 through 3.3M3 and possibly later versions (https://bugs.eclipse.org/bugs/show_bug.cgi?id=161362 bug 161362). Use the view menu to set ''Package Presentation -> Flat'' as a work-around.<br />
<br />
== How do I stop declarations from showing in the Package Explorer? ==<br />
<br />
If you don't like Mylyn's constant showing of Java members in the ''Package Explorer'', select the drop-down menu, then ''Filters...'' and enable the ''Mylyn Java Declarations Filter''. It will then stick in the menu in case you want to toggle between modes. Note that this will hide interest information about members that aren't in your current file (e.g. showing you which methods are landmarks) so this mode is not recommended, but can be useful for <code>1024x768</code> screen resolutions.<br />
<br />
[[Image:mylar-java-filtering-declarations.gif]]<br />
<br />
== Why does nothing show up in the Active Search or Active Hierarchy? ==<br />
<br />
As you work, elements become Landmarks (bold decoration), and these elements populate the ''Active Search'' and ''Active Hierarchy'' views. To force an element to populate the views manually, make it a Landmark by <code>right+clicking</code> or hitting <code>Ctrl+Alt+Shift+UpArrow</code>.<br />
<br />
== Known limitations ==<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=106678 Bug 106678]: The Project Explorer's Hierarchical Java package presentation layout is not supported on Eclipse 3.3Mx, and interesting elements will be hidden if enabled. Work-around is to use the default Flat package presentation.<br />
<br />
= Team Support =<br />
<br />
== Why does task change set not appear when I modify files? ==<br />
<br />
A task change set should appear if you activate a task and modify a file connected to a compatible source repository (e.g. CVS, SVN). If it does not try the following:<br />
<br />
* Ensure you have installed the [http://www.eclipse.org/mylyn/downloads/ ''Mylyn Bridge: Eclipse SDK'' feature]. Note that this feature is not currently distributed with the Java-only Eclipse download ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191793 bug 191793] ).<br />
<br />
* Verify that the [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuring_the_Synchronize_view_for_change_sets configured ''Synchronize View'' is configured for change sets].<br />
<br />
If the above are working but the change set appears to be missing relevant files:<br />
<br />
* You may be seeing the ''Synchronize'' view's refresh problem ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142395 bug 142395]). Toggle from ''Incoming/Ougtoing'' to ''Incoming'' mode and back again to refresh the view.<br />
<br />
* If the files or change set are still missing deactivate and reactivate the task to force a full refresh.<br />
<br />
== Why do files disappear from the change set when I close them? ==<br />
<br />
If you have the ''Preferences -> Mylyn -> Context -> Manage open editors to match task context'' option enabled, Mylyn will perform editor management so that you don't have to. Closing a file makes it less interesting, and causes it to disappear from the active task context, and hence from the change set. This option prevents you from having to manage the set of open files, will automatically close editors for files that become uninteresting, and will ensure that the open editors match the task context.<br />
<br />
== Why am I missing elements when I retrieve someone else's context? ==<br />
<br />
To identify elements within a project, Mylyn relies on the name of the project being consistent across workspaces. If the project name in the workspace that the context was created with is different than its name in your workspace, the task context will not show elements within that project ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164058 bug 164058]). The other case where context can be lost is if the elements change names outside of the workspace ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164243 bug 164243]).<br />
<br />
The work-around is to use the same project names across your team's workspaces. We recommend the following two approaches for standardizing on project names:<br />
* Use '''Team Project Sets''': these are a very useful Eclipse facility that allows your entire team to check out numerous projects from version control by importing a single file. Create a project set via ''File -> Export -> Team Project Set'', host this file somewhere accessible, then have others import vai ''File -> Import -> Team Project Set''.<br />
* Have developers check out projects into their workspace without renaming them. The above is a shortcut for doing this. If alphabetical sort order in the ''Package Explorer'' is a problem, organize your projects via ''Project Explorer -> view menu -> Top Level Elements -> Working Sets''.<br />
<br />
= Misc =<br />
<br />
<br />
<br />
== How does Mylyn relate to IBM's Jazz? ==<br />
<br />
At the EclipseCon and JavaONE 2006 conferences IBM demonstrated previews of Jazz, a collaborative team server and Eclipse-based client. Articles have remarked on the similarities between Mylyn and Jazz because both integrate tasks into Eclipse (Jazz's "work items" and Mylyn's "tasks"), and both provide change sets grouped by task. But there are both significant differences and complementary aspects to the two approaches. A key goal of Mylyn is to provide an open source framework to support integration of task management with ''existing issue trackers and source repositories''. According to the presentations, components that come with Jazz include include a ''next-generation issue tracker and source repository'' and related lifecycle management tools such as project health. In addition, a driving and unique goal of Mylyn is to focus the UI around a usage-based and degree-of-interested weighted task context, which is complementary to the Jazz platform. Just as it integrates with Mylyn's Task List, Mylyn's Task Focused UI and task context model components are possible to integrate with other kinds of task management systems, such as the one provided by Jazz.<br />
<br />
Update: at EclipseCon 2007 the IBM Jazz team showed a Mylyn connector for Jazz.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/FAQ&diff=55276Mylyn/FAQ2007-10-16T00:22:06Z<p>Steffen.pingel.eclipse.org: /* Authentication Troubleshooting */</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
[[Mylyn User Guide]], <br />
[http://eclipse.org/mylyn Mylyn Home],<br />
[http://wiki.eclipse.org/index.php?title=Special:Userlogin&returnto=Special:Userlogout Log in to edit]<br />
<br />
For instructions on [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Download_Mylar downloading] [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installation installing] and [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuration configuring] <br />
Mylyn, see the [[Mylyn User Guide]]. For instructions on developing and contributing to Mylyn, see the [[Mylyn Contributor Reference]].<br />
<br />
= Installation =<br />
<br />
== What versions of Eclipse are supported? ==<br />
<br />
See the [http://eclipse.org/mylyn/dl.php download page].<br />
<br />
Mylyn also relies on a web browser that works with the Standard Widget Toolkit; Windows and MacOS users are fine, but Linux users might have to download another browser. See [http://www.eclipse.org/swt/faq.php#browserlinux the SWT Browser guide] for which browsers will work. See [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux installing browser on Linux] for installation instructions.<br />
<br />
== What version of Java is required? ==<br />
<br />
Mylyn needs the '''Java 5''' virtual machine.<br />
<br />
To check the version of the Java virtual machine that Eclipse was launched with to to ''Help -> About Eclipse SDK -> Configuration Details'' and verify that the java.vm.version is 1.5. <br />
<br />
Mac users should refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
* If you do not have Java 5, you can download it from [http://72.5.124.55/javase/downloads/index.jsp Sun's web site]. <br />
* If you have more than one VM, you need to specify that Eclipse should use the JDK1.5 VM. <br />
<br />
In Unix, set the environment variable <code>JAVA_HOME</code> to the root of the JDK1.5 installation and/or set the <code>PATH</code> variable to put the JDK1.5 executable directory before any other VM executable directories. For example, under <code>bash</code> in Unix:<br />
export JAVA_HOME="''(location of JDK1.5 root)''"<br />
export PATH=$JAVA_HOME/bin:$PATH<br />
<br />
<b>We do [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140955 not recommend] using JDK 1.6 on Eclipse 3.1.</b> (It works fine with Eclipse 3.2 or 3.3.) To use JDK 1.6 on Eclipse 3.1, you must add the following line to your <code>config.ini</code>file:<br />
<code><br />
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,<br />
J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6<br />
</code><br />
<br />
== What version of Mylyn is distributed with the Eclipse downloads? ==<br />
<br />
The [http://www.eclipse.org/downloads/ default Eclipse downloads] contain the following Mylyn redistributions. Since the redistributed versions can be missing important bug fixes or feature additions, we recommend using the [http://www.eclipse.org/mylyn/downloads latest version of Mylyn].<br />
<br />
* Eclipse IDE for Java Developers: all of Mylyn except Team integration (e.g. automatic change sets) integration. Install the Eclipse CVS integration and then install the latest Mylyn build to get this component.<br />
<br />
* Eclipse IDE for Java EE Developers: all of Mylyn redistribution, install manually<br />
<br />
* Eclipse IDE for C/C++ Developers: no Mylyn redistribution, install manually<br />
<br />
* Eclipse for RCP/Plug-in Developers: all of Mylyn redistributed<br />
<br />
* Eclipse Classic: no Mylyn redistribution, install manually<br />
<br />
== My tasks or queries disappeared, what do I do? ==<br />
<br />
This happens if Mylyn failed to install. First ensure that you have a correct install by following the instructions in the next section. After that, if you still do not see your tasks use the ''Task List'' view menu -> ''Restore Tasks From History...'' command (also available via ''File -> Import -> Task List''.<br />
<br />
== Installation Troubleshooting ==<br />
<br />
''' Java Persistence API Tools error when updating the JEE Eclipse Package '''<br />
<br />
If you are trying to install additional features and get this error you have hit [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194959 bug 194959] which should be resolved soon. The work-around is to check off the ''Europa Discovery Site'' and install the first two components of the ''Data Tools Platform''.<br />
<br />
''' Update failures '''<br />
<br />
On Eclipse versions earlier than 3.3 (final) use '''only the "Search for new features.."''' option when updating Mylyn. If you use "Search for updates..." the Update Manager will allow a partial install that can cause Mylyn to fail to start, and you will need to run update again. See the ''feature configuration problem'' section below for details. If you encounter this problemm consider voting for Platform [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132450 bug 132450].<br />
<br />
''' Startup exceptions '''<br />
<br />
If you see startup errors or warnings such as <code>BundleException</code> or timeout messages restart Eclipse with the <code>-clean</code> flag either on the command line, in your shortcut link, or by temporarily it into the <code>eclipse/eclipse.ini</code> file. If that does not resolve the problem please [http://www.eclipse.org/mylar/bugs.php file a bug].<br />
<br />
''' Incompatible VM (e.g. JDK 1.4) '''<br />
<br />
If you are using the wrong VM, you'll see errors like the following in your log file. <br />
<code><br />
Root exception: java.lang.UnsupportedClassVersionError:<br />
org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)<br />
</code><br />
<br />
See [[#Download_and_configure_Java_5_or_6|Configure Java]] to fix this problem.<br />
<br />
''' Incompatible version of Eclipse '''<br />
<br />
Separate versions and update sites exist [http://eclipse.org/mylyn/dl.php for Eclipse 3.1 and 3.2]), in which case you may see errors like the following in your <code><workspace>/.metadata/.log </code>file or in a Mylyn view:<br />
<code><br />
java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()<br />
The activator org.eclipse.mylar.java.MylarJavaPlugin for bundle org.eclipse.mylar.java is invalid<br />
</code><br />
<br />
''' Mylyn feature configuration problem '''<br />
<br />
If the above do not address the issue, the easiest thing to do is uninstall any old versions and update to the latest Mylyn. Your tasks won't be lost, because by default they are stored in the <code><workspace>/.metadata/.mylyn</code> folder which will be read next time Mylyn starts correctly. <br />
* First, uninstall the old version of Mylyn using ''Help -> Software Updates -> Manage Configuration''. <br />
* You need to Disable all Mylyn features by right-clicking them.<br />
* Allow Eclipse to restart after the last is disabled.<br />
* After restart, ensure that the 3rd toolbar button is pressed (figure below) so that you see the disabled features to uninstall.<br />
* Uninstall all the disabled features using the popup menu. <br />
<br />
If you don't uninstall, the the Update Manager will think that you have the latest and tell you that there are no updates. <br />
<br />
<b>Note: manually removing the plug-ins and features can lead to configuration errors.</b> <br />
<br />
After uninstalling, update Eclipse by adding the correct update site specified at on the [http://eclipse.org/mylar/dl.php download page], and after that automatically or manually updating will install the correct version.<br />
<br />
[[Image:mylar-eclipse-manage-configuration.gif]]<br />
<br />
'''What do I need to do in installation to be able to use Mylyn task management features with bug/task/issue trackers?'''<br />
<br />
When you install, make sure that you select a connector for your bug/task/issue tracking software. For example, to use Bugzilla, you have to install the Bugzilla connector component.<br />
<br />
'''I've installed Mylyn ; why can't I see anything different?'''<br />
<br />
The two most likely possibilities are:<br />
# You don't have any Mylyn views open. Select ''Window -> Show View -> Other'', then select ''Mylyn'' and you should see the available Mylyn Views. <br />
# If you still don't see anything, then perhaps you aren't using the JDK1.5 VM (or later). See [[Mylyn_Installation_Guide#Download_and_configure_Java|configuring Java]].<br />
<br />
<br />
'''What does the error "Network connection problems encountered during search" mean?'''<br />
<br />
If you get that message while trying to download Mylyn, it means that Eclipse couldn't find the location you entered. This might be because you copied something incorrectly (watch for extra characters -- even extra spaces can cause errors), or because the site went down. You may be able to see if the site is up or down by copying the URL into your Web browser.<br />
<br />
'''What does the "Update manager failure" message mean? '''<br />
<br />
It means that Eclipse could not access the update site, or that it got confused about the configuration state of your Eclipse. First try updating again to see if the update site is accessible. <br />
<br />
If you are trying to update the JIRA connector you can also try de-selecting that feature in case the <code>Tigris.org</code> update site is not accessible. Using ''Search for new features to install..'' when installing can help to avoid this problem. If that does not work see the feature configuration troubleshooting below. <br />
<br />
'''What does "Could not create Browser page: No more handles (<code>java.lang.UnsatisfiedLinkError: ...</code>)" mean?'''<br />
<br />
It probably means that you are running Linux and don't have Eclipse and a Web browser configured to work together. See [[http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux| installing a browser on Linux]].<br />
<br />
'''When downloading, why do I get a warning that the feature was unsigned?'''<br />
<br />
Signing plugins requires extra administrative details with <code>eclipse.org</code> which most plug-ins seek to avoid. <br />
<br />
'''N.B.''': Security issues with features should not be underestimated. Eclipse allows users to download new functionality from remote servers. A rogue plug-in can act as a perfect Trojan horse. It can look innocent enough and provide useful function while spawning threads in the background with full access to the local file system and the Internet (if connected). Beware of installing features from update sites you do not trust.<br />
<br />
'''What does "<code>Root exception: java.lang.UnsupportedClassVersionError: org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)</code>" mean?'''<br />
<br />
It probably means that the virtual machine is JDK1.4 or lower. See [[Mylyn_Installation_Guide#Download_and_configure_Java| download and configure Java]].<br />
<br />
'''Why am I getting messages in my <code><workspace>/.metadata/.log</code> or my Mylyn view that say things like <code>"java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()"</code> and "The activator <code>org.eclipse.mylar.java.MylarJavaPlugin</code> for bundle <code>org.eclipse.mylar.java</code> is invalid"?'''<br />
<br />
This probably means that your Mylyn download version didn't match your Eclipse download version. Note that [http://eclipse.org/mylar/dl.php the download site] has different downloads for Eclipse 3.1 and Eclipse 3.2.<br />
<br />
To fix this problem, see the [[Mylyn_Uninstallation_Guide| uninstallation guide]], then re-install from [http://eclipse.org/mylar/dl.php the correct download site].<br />
<br />
'''What does "Could not create Bugzilla editor input" and "<code>java.io.IOException</code>: SAX2 driver class <code>org.apache.xerces.parsers.SAXParser</code> not found" mean?'''<br />
<br />
It probably means that you are on MacOS, and for some reason are missing Xerces from the Mac JDK1.5. You will probably need to add it to your default classpath. Please refer to and comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=144287 bug 144287] if you see this problem.<br />
<br />
To ensure that you are using the 1.5 VM refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
'''I've just updated to Mylyn 2.0 and I don't see any tasks in my Task List'''<br />
<br />
As part of the update to Mylyn 2.0 the old data folder has been migrated to <workspace folder>/.metadata/.mylyn from the old location <workspace folder>/.mylar. IF for some reason migration failed (.mylar folder still exists), simply shut down Eclipse and manually move your old <workspace folder>/.mylar folder to <workspace folder>/.metadata/.mylyn (note the name change to .mylyn)<br />
<br />
== Configuration Troubleshooting == <br />
<br />
'''How can I change the number of editors left open before Mylyn starts closing editors?'''<br />
<br />
Turn off or increase the number of editors to leave open using ''Preferences -> General -> Editors -> Number of opened editors before closing''. Since Mylyn will manage the open editors with task activation, this number can be set higher or you can disable automatic closing entirely.<br />
<br />
'''Do I need the Outline View when running Mylyn?'''<br />
<br />
No, not really. The Package Explorer and folded signatures should provide enough context for you. If, at some point, you really need to see an Outline View, you can always enter (Ctrl+O) to show the in-place Outline View.<br />
<br />
'''What does the message "content assist proposals no longer appear" mean?'''<br />
<br />
This usually happens when uninstalling when using Eclipse 3.2. Make sure that the "Java Completions" and "Java Types" proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
'''Why do I get errors like "HTTP Response Code 407" or "Proxy Authentication Error" when accessing repositories through a proxy server?'''<br />
<br />
It is likely that you need to configure these proxy server settings. Select ''Window -> Preferences -> Install/Update'', and update the section in the "Proxy settings" section of the form.<br />
<br />
'''I can't use <code>Ctrl+Alt+Shift+Arrow Up</code> for'' Mark as Landmark''. What do I do?<br />
<br />
This is usually a Linux/GNOME problem, where the Gnome keyboard shortcuts are interfering with the Eclipse shortcuts. Go to the Keyboard shortcuts (which might be something like ''Desktop -> Control Centre -> Keyboard Shortcuts'' or ''System -> Preferences -> Keyboard Shortcuts'') and disable both of these shortcuts:<br />
* Move one workspace up<br />
* Move one workspace down<br />
<br />
See also: [[Mylyn_User_Guide#Keyboard_mappings_on_Linux| keyboard mappings on Linux]].<br />
<br />
'''How do I turn on spell checking?'''<br />
<br />
See [[Mylyn_User_Guide#Spell_Checking| spell checking]].<br />
<br />
== Uninstall troubleshooting ==<br />
<br />
When '''uninstalling in Eclipse''' Mylyn via the ''Help -> Software Updates -> Manage Configuration'' dialog you will need to uninstall dependencies first (e.g. Bugzilla Connector, Subclipse integration) and then uninstall the core Mylyn features.<br />
<br />
When '''uninstalling manually''' by deleting all of the Mylyn plug-ins and features from the <code>eclipse/plugins</code> and <code>eclipse/features</code> directory make sure to delete all of the plug-ins and then restart Eclipse with the -clean option (e.g. by inserting it into a shortcut or the <code>eclipse.ini</code> file.<br />
<br />
On '''Eclipse 3.1:''' you may need to reset the Java editor to be default for <code>.java</code> again via: ''Preferences -> General -> Editors -> File Associations''<br />
<br />
On '''Eclipse 3.2:''' if after uninstalling '''content assist proposals no longer appear''' you need to ensure that the ''Java Completions'' and ''Java Types'' proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
== I am seeing <code>java.lang.OutOfMemoryError: PermGen space </code>errors, what's wrong? ==<br />
<br />
If your Eclipse crashes, or you see the above error after installing Mylyn or other plug-ins, you have most likely hit the infamous MaxPermSize bug. This is not a Mylyn specific problem, but a general Eclipse problem that is often triggered on Eclipse 3.2 and later, if you have many plug-ins installed and are using a Sun JVM. <br />
<br />
To fix it simply add the following to your launch arguments. This is usually to your shortcut, or to the <tt>eclipse/configuration/config.ini</tt> file:<br />
<br />
-XX:MaxPermSize=128M<br />
<br />
If you are using a large number of plug-ins (e.g. WTP) you may need to increase the number to more than 128M. <br />
<br />
For more information see the [[FAQ How do I increase the permgen size available to Eclipse? | Eclispe FAQ entry]]. Details of the problem are on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250 Platform bug 92250].<br />
<br />
== What is Mylyn's performance profile? ==<br />
<br />
Mylyn should have '''no noticeable effect''' on Eclipse's speed or memory usage, no matter how large your workspace is. You do not need to increase the amount of memory Eclipse runs with to use Mylyn. Any performance issue should be [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Mylyn reported as a bug]. <br />
<br />
The current '''performance profile''' is:<br />
<br />
# Mylyn only runs if a task is active, and has no impact on Eclipse if no task is active.<br />
# Task context models have negligible memory overhead. <br />
# When a task is active, additional view refresh is required to update the views based on interest model changes. This should not be noticeable on Windows where refresh is very quick, but could be more noticeable on other platforms.<br />
# The time to activate a task context is dominated by the time it takes Eclipse to open the editors in the context. You can set the preference for how many editors to open in the Mylyn preference page (e.g. setting to 1 will dramatically reduce activation time, but also remove the benefit of having open editors correspond to the task context). You can also turn off editor management entirely in the Mylyn Tasks view pull-down.<br />
# Eclipse startup is slowed down by (4) if a task is active when Eclipse is shut down.<br />
# The low priority background searches that the Active Search view runs can be noticeable on slower machines.<br />
<br />
If you are seeing performance problems, this is either a bug or caused by other performance problems in Eclipse. If you are performance problems we suggest increasing the amount of memory available to Eclipse. This is especially useful for very large Java project workspaces, on which the size of JDT's element cache will grow proportionally to the amount of available memory. The setting we recommend for launching workspaces with a couple hundred large projects is:<br />
<br />
-Xmx768M -XX:MaxPermSize=128M<br />
<br />
= Task List =<br />
<br />
== Why won't the Archive category disappear? ==<br />
<br />
The ''Archive'' category will automatically appear if a task needs to be shown, but is not in any query or category. <br />
In order to ensure that you do not miss reminders or notifications the following tasks will always be shown in the Task List, even if they have been removed from a category or a query:<br />
* Tasks scheduled for this week or overdue. Remove these by using the ''Schedule'' pop-up menu option to defer them to a future week or to clear the schedule.<br />
* Repository tasks that have incoming changes, such as comments. Remove these by reading them or marking them as "read" via the ''Mark -> Read'' pop-up menu.<br />
<br />
== The Archive category contains many irrelevant tasks, how do I clean it up? ==<br />
<br />
If you created very broad queries you could end up with thousands of tasks in the Archive category. Other than clearing the <tt>workspace/.metadata/.mylyn/tasklist.xml.zip</tt> and <code>workspace/.metadata/.mylyn/offline</code> folder (note that this will entirely reset your Task List) the easiest option is to:<br />
* Clean up your queries to include only tasks of interest (note that including completed/resolved tasks is recommended).<br />
* Turn off ''Focus on Workweek'' in the ''Task List''.<br />
* Turn off the ''Filter Archive Category'' option in the ''Task List'' view menu.<br />
* Delete all of the unneeded tasks from within the Archive category. Note that if the tasks are not matched by queries they will be deleted permanently and any local notes or scheduling information that you have added to them will be lost.<br />
<br />
== How does Mylyn count the active time for a task? ==<br />
<br />
Whenever you work on a task, Mylyn accumulates the time you spend actively working on a task. This time can be viewed in the ''Personal Planning'' section of the ''Task Editor''. When you are not interacting with Eclipse, the timing automatically times out after 3 minutes by default. This means that activity outside of Eclipse will not be captured when you work on the task and that the timings in Mylyn are a lower bound of the total time spent on the task (capturing timings for work done outside of Eclipse involves OS specific extensions).<br />
<br />
== How do I prevent long-running tasks from adding to the progress bar? ==<br />
<br />
If you have many long-running or recurring tasks scheduled for this week, they can affect the ''Task List'' weekly progress bar. This can be misleading as they may never be completed. The current work-around to prevent long-running tasks from being included in the weekly progress bar is to schedule their estimated time to be 0 (zero). Alternatively, you can schedule only the amount of time you plan on spending on that task this week.<br />
<br />
== Does the Task List replace the Eclipse Tasks view? ==<br />
<br />
The SDK's ''Tasks'' view is used for showing markers such as 'todo' tags which indicate a local problem with a resource, similar to a compiler warning. As such, these 'tasks' are at a much lower level of granularity than Mylyn's tasks, and one task could involve cleaning up multiple todos. In order to make working with only the markers in a particular task context, e.g. for clean-up before committing, the ''Apply Mylyn'' filter is available for both the ''Problems'' and the ''Tasks'' views.<br />
<br />
== What if I use multiple workspaces? ==<br />
<br />
Mylyn's support for multiple workspaces is currently limited (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130658 bug 130658] for a discussion) because the Task List is considered to be specific to the person, and not to the workspace. We recommend configuring your Eclipse workspace to use working sets instead of relying on multiple workspaces. <br />
* John O'Shea's blog: [http://www.xlml.com/aehso/2007/02/02/eclipse-workspaces-containing-projects-with-overlapping-locations-and-mylar/ Eclipse workspaces containing projects with overlapping locations, and Mylar]<br />
<br />
If using a single workspace is not possible you can do the following:<br />
* In ''Preferences -> Mylyn -> Task List'' set the ''Data Directory'' to be a shared location, and do this for both workspaces.<br />
* Be sure to avoid launching both Eclipse workspaces at the same time, as changes in one workspaces could overwrite the Task List in the other workspace.<br />
* If you upgrade Eclipse or move your workspace and don't see your tasks, check the ''Data Directory'' setting.<br />
<br />
== How do I export my task and repository data? ==<br />
<br />
Export via File > Export > Mylyn > Task Data<br />
<br />
== Why does Mylyn use the term "task"? ==<br />
<br />
There are many work items that make up the developer's workday. Many issue trackers and project management tools refer to these as: bugs, defects, actions, tickets, stories, enhancements, and the list goes on. We refer to all such work items as "tasks" because the word tasks is short and commonly used in time management tools. Task Repository connectors can customize the presentation of tasks, for example, indicating which is a defect and which is an action item.<br />
<br />
= Task Editor =<br />
<br />
== When I submit a new bug to eclipse.org the priority isn't updated? ==<br />
<br />
Eclipse.org's Bugzilla repository forces all new bug reports to priority 3 (P3) regardless of what is selected in Mylyn. Eventually we will disable this field in the new bug editor for bugs.eclipse.org and provide a tooltip with explanation ( {{bug|204630}} ).<br />
<br />
== Why am I seeing strange boxes where I expect to see proper characters? ==<br />
<br />
If for example you aren't seeing the proper single quote chacters in the summary of [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=197644 bug#197644]], check that the encoding is set correctly for the repository in the asociated Task Repositories view (Properties > Additional Settings > Character Encoding). For bugs.eclipse.org/bugs set your charcter encoding to ''ISO-8859-1''.<br />
<br />
= Task Repositories =<br />
<br />
== What if I'm not using a Task Repository? ==<br />
<br />
Mylyn does not require the use a of a task repository and can be used entirely with the ''Local Tasks'' repository that it comes bundled with. However, if working with a team, a shared ''Task Repository'' provides the key infrastructure needed to let your team work in a Task-Focused way via Mylyn's collaborative facilities.<br />
<br />
Those not currently using another supported ''Task Repository'' should consider the repositories currently [http://www.eclipse.org/mylyn/downloads/ supported by Mylyn] as well as those supported by the [http://wiki.eclipse.org/index.php/Mylyn_Extensions third party Mylyn extensions].<br />
<br />
== What if Mylyn doesn't support my task/bug/issue/ticket repository? ==<br />
<br />
To see support for your repository faster, do a search of the open repository connector requests and [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Bconnector%5D&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=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= vote for the corresponding bug] if your tracker is there, or [http://www.eclipse.org/mylar/bugs.php create a new bug]. <br />
<br />
[[Mylyn_User_Guide#Generic_Web_Repository_Connector|Generic Repository Connector]], allows creating Queries to the web-based issue tracking repositories and get list of issues from the web UI into the Task List.<br />
<br />
It is also possible to link a ''local task'' with the web page in web-based repository via the Mylyn Web integration.<br />
<br />
'''To create a task from any web-based repository:'''<br />
<br />
* Drag the URL from the address bar of the browser, or from a hyperlink in a bug listing to the ''Mylyn Tasks'' view. This will create a task for the bug, link it to the page, and populate the description with the title of the corresponding page. '''In Mozilla:''' simply drag the URL. '''In Internet Explorer:''' you must have <code>Ctrl</code> pressed in order for Eclipse to recognize the drop.<br />
* '''Alternatively,''' you can copy the URL, press the ''New Task'' button on the ''Mylyn Tasks'' view. This has the same effect as above but you can edit the description after retrieving it.<br />
* Opening the task will now open the corresponding issue. You can also <code>right+click</code> the task and select ''Open in External Browser''.<br />
<br />
[[Image:mylar-tasklist-weblink-editor.gif]]<br />
<br />
== Why were my repository credentials reset? ==<br />
<br />
If you upgrade Eclipse or your Java VM, you will need to reset your credentials in the ''Task Repositories'' view because these are stored in the secure Eclipse workbench keyring. Also see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=149607 bug 149607]. If you are migrating '''from Eclipse 3.2 to 3.3''' note that you will need to use a different update site, which is listed here: http://eclipse.org/mylyn/dl.php<br />
<br />
== Why are my updated repository attributes not showing up? ==<br />
<br />
Your server's repository attributes can change frequently, for example, there can be a new "milestone" or "version" added to the Bugzilla repository with each release. When the ''Preferences -> Mylyn -> Task List -> Synchronization'' setting is enabled, every 10th synchronization will update the attributes from the repository. If you do not have this setting enabled, your can force the update via the ''Update Attributes'' action on the task repositories' context menu in the ''Task Repositories'' view. Note that you will need to reopen a task editor to see the updated attributes. If you instead update via the button on the ''Attributes'' section of the ''Task Editor'' the attribute settings will be reloaded without needing to reopen.<br />
<br />
== Authentication Troubleshooting ==<br />
<br />
You must ensure repository credentials are filled out correctly. Refer to the diagram below:<br />
<br />
[[image: AuthenticationTroubleshooting2.png|right]]<br />
<br />
# Enter the repository URL (i.e. https://bugs.eclipse.org/bugs) and an optional label<br />
# Credentials<br />
#* Usually email address and password <br />
#* Some sites, such as <code>dev.eclipse.org</code>, use anonymous logon with password left blank.<br />
#Http Authentication (optional)<br />
#* Some sites are protected by either BASIC or DIGEST http authentication. If this is the case, enter appropriate credentials here.<br />
#* One way to test if the site requires http authentication is to point your browser at the repository. If you are presented with an authentication dialog popup, the site is likely protected by http authentication.<br />
#Proxy Server Configuration (optional)<br />
#* By default Mylyn uses the Platform's Install/Update proxy settings. Uncheck this box if you wish to use an alternative proxy.<br />
#* If the proxy requires authentication, this is where you enable and enter your proxy credentials.<br />
#* If you are experiencing connection problems, ensure your Install/Update proxy settings are valid or the repository specific settings are correct<br />
#* Mylyn has been tested with HTTP proxy servers. Currently SOCKS is not supported.<br />
#Validate Settings <br />
#*Press the ''validate'' button to test the settings<br />
#*If you are seeing errors like "HTTP Response Code 407" or "Proxy Authentication Error" it is likely that you need to configure proxy settas as described above.<br />
#*If your sever uses a certificate and fails to connect, e.g. you see exceptions <tt>sun.security.validator.ValidatorException: PKIX path building failed</tt> then you need to point Eclipse at your certificate, see below.<br />
<br />
=== Certificate authentication ===<br />
<br />
In order to use client certificates for authentication you need to create a Java keystore and import your existing certificate to it. This command will import your certificate from /tmp/certificate.pem and create a keystore in /path/to/.eclipsekeystore. <br />
<br />
keytool -import -keystore /path/to/.eclipsekeystore -file /tmp/certificate.pem<br />
<br />
See [http://java.sun.com/j2se/1.5.0/docs/guide/security/SecurityToolsSummary.html this page] for links to the keytool documentation.<br />
<br />
Add the path to the keystore to your eclipse.ini in your eclipse install directory: <br />
<br />
-Djavax.net.ssl.keyStore=/path/to/.eclipsekeystore<br />
<br />
If your keystore is protected by a password add that as well:<br />
<br />
-Djavax.net.ssl.keyStorePassword=123456<br />
<br />
More [http://ahtik.com/blog/2006/05/11/fixing-eclipse-mylar-jira-integration/ instructions on this blog].<br />
<br />
=== NTLM authentication ===<br />
<br />
For NTLM authentication to work a special format for the username needs to be used where ''DOMAIN'' needs to be replaced by the Windows login domain: <br />
<br />
DOMAIN\username <br />
<br />
The built-in NTLM support of the JDK which is used by Eclipse does '''not work''' with Mylyn since it uses the HttpClient library to access repositories. Limitations in regard to NTLM authentication are documented in the [http://wiki.apache.org/jakarta-httpclient/FrequentlyAskedNTLMQuestions NTLM FAQ] and also discussion on {{bug|201911}}.<br />
<br />
* If your repository uses MS NTLM authentication and only standard http authentication is being passed to the repository this can result when the local hostname cannot be resolved. Ensure your machine's hostname is set correctly and resolves to a valid address.<br />
* It is not possible to use NTLM authentication for the proxy as well as for the repository.<br />
<br />
If NTLM authentication fails the '''[http://ntlmaps.sourceforge.net/ NTLM Authorization Proxy Server]''' has been reported to '''work''' with Mylyn.<br />
<br />
== Why are task hyperlinks not working? ==<br />
<br />
For task hyperlinks in textual editors (e.g. Java editor) and other text viewers (e.g. History view comments) you must associate the project that contains the resource to the task repository. <br />
<br />
:''Project association can also come from 3rd party metadata trough the contrubuted [[Mylar_Integrator_Reference#Mapping_from_projects_to_Task_Repositories|extension point]]. [http://subclipse.tigris.org/ Subclipse] and [http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Mylyn Maven integration for Eclipse] plugins contributing it. See few more details [http://jroller.com/page/eu?entry=linking_projects_from_the_eclipse here].''<br />
<br />
Note that to view a hyperlink you must hold down the <code>Ctrl</code> key when hovering over the reference to the task. References to tasks are connector specific and the common reference is found on the top left of the task editor and other conventions tend to follow those used in the web UI (e.g. "bug 123" for Bugzilla, "ABC-123" for JIRA).<br />
<br />
[[Image:mylyn-project-repository-association.gif]]<br />
<br />
= Bugzilla Connector =<br />
<br />
== What versions are supported? ==<br />
<br />
We recommend using the latest [http://www.bugzilla.org/download/ release] of Bugzilla.<br />
<br />
* '''Bugzilla 2.18.6 is the lowest version of Bugzilla supported'''. If you are getting errors that indicate failure to update attributes this may be an indication that the Bugzilla server is not supported (< 2.18.6).<br />
<br />
*If you are using '''Bugzilla 2.18''' and are getting '''mid-air collisions''' this is likely due to incorrectly formatted timestamp field in the underlying bugs database table ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149513 bug 149513]). This can be resolved by upgrading to Bugzilla 2.20 or later.<br />
<br />
== Why are queries failing? ==<br />
<br />
*If '''queries are not working''' correctly ensure that you have the right Bugzilla server version selected for the corresponding repository: ''Task Repositories (View) ->'' right+click the repository ''-> Properties''. For supported versions see the [http://www.eclipse.org/mylar/dl.php download page]. If the repository is still not functioning it may be due to authentication or connectivity problems. If that does not resolve the problem please post a message to the newsgroup or [http://www.eclipse.org/mylar/bugs.php submit a bug].<br />
<br />
== Why do I see my old username? ==<br />
<br />
If you change the username/email address on your Bugzilla account you may notice that some tasks still have the old username/email. Explicitly synchronize the task via the ''Task List'' popup menu or ''Task Editor'' toobar in order to update your username.<br />
<br />
== Why do tasks fail to open? ==<br />
<br />
*If upon opening a bug, the Bugzilla tab only displays a warning "'''Could not download task data, possibly due to timeout or connectivity problem. Please check connection and try again.'''", ensure that your repository is returning XML data by pointing your browser to <code><your-repository-url>/show_bug.cgi?id=1&ctype=xml</code> to show the contents of bug 1 in XML form. The Bugzilla client requires that bugs be accessible in XML form. If the repository doesn't support xml then it is likely that the repository is too old (Mylyn currently supports Bugzilla 2.18 and later).<br />
<br />
* If '''reports fail to load''' or '''reports fail to synchronize''' (task description remains ''italic''), check the error log for a "'''File not found'''" error pointing to <code>bugzilla.dtd</code> or a "'''Failed to retrieve products from server'''" error message, these can result when <br />
** the <code>urlbase</code> parameter is not set on the bugzilla server<br />
** your <code>urlbase</code> parameter is incorrect, e.g. it contains <code>index.cgi</code><br />
** your bugzilla installation is missing the <code>bugzilla.dtd</code> file. See: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=161759 bug#161759]<br />
<br />
<br />
* If '''attributes are missing options''' in the bug editor (ie. missing a recently added milestone, [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155431 bug# 155431]):<br />
** Update attributes by choosing ''Update Attributes'' from the context menu in the ''Task Repositories'' view<br />
** Synchronize the task in the Task List<br />
** Reopen the task - new options should be available.<br />
<br />
== Why do tasks fail to submit? ==<br />
<br />
* '''Error upon submit: unable to make any match for name/email entered.''' If your bugzilla is configured for user names rather than full email address the QA Contact field will cause the submit to fail ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=166555 bug# 166555]). To resolve, select 'Local users enabled' option on the Repository Configuration page. <br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your account's username and password and are not using the HTTP authentication fields instead.<br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your bugzilla instance's cookie domain under the required settings. The cookie domain must lead with a dot.<br />
<br />
* If '''attachments are failing to submit''' and you see that after processing the attachment, the bugzilla bug shows a size of "bytes" (no numbers), your database may be dropping the packet sending the file. '''On MySQL''', check the [http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html max_allowed_packet directive]. You may see errors like: <code>DBD::mysql::st execute</code> failed: Got a packet bigger than 'max_allowed_packet' bytes [for Statement "INSERT INTO attach_data (id, thedata) VALUES (38, ?)"] at <code>/path/to/bugzilla/attachment.cgi</code> line 993. Also, '''check the maximum attachment size''' in ''Bugzilla Parameters -> Attachments''.<br />
<br />
* If a submit fails with an '''Invalid Username or Password''' error even though repository settings do validate, make sure that cookies could be set. See also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175502 bug 175502]<br />
<br />
== What time zone is used in the task editor? ==<br />
<br />
*The '''times''' that appear in the Bugzilla bug editor (ie. created, modified) '''are local to the server hosting the Bugzilla repository''', not your local machine's time zone. <br />
<br />
== Known limitations ==<br />
<br />
* The <code>usermatchmode</code> is not currently supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168204 bug 168204]) and as such full email addresses need to be used.<br />
<br />
* The <code>usevisibilitygroups</code> parameter is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=180876 bug#180876]). Group assignment will currently be lost if updated using the Bugzilla rich task editor.<br />
<br />
* Version 1.0 of Mylyn presents an error message upon new comment submission to RedHat's public Bugzilla repository. The comment is in fact posted. This issue is resolved in Mylyn 2.0M2 and higher. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=183251 bug#183251])<br />
<br />
= JIRA Connector =<br />
<br />
If you see errors like the following, work around this by opening repository ''Properties Page'' and clicking OK (bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169102 169102]).<br />
<br />
org.tigris.jira.core.service.exceptions.AuthenticationException<br />
at org.tigris.jira.internal.core.service.soap.SoapJiraService.getProjectsNoSchemes(SoapJiraService.java:204)<br />
<br />
== What are the server requirements? ==<br />
<br />
The '''JIRA SOAP/RPC services have to be running on the JIRA server''':<br />
<br />
* Jira 3.3.3 or higher (3.7 or higher for attachment retrieval)<br />
* Jira RPC plugin 1.4.3 or higher<br />
<br />
Latest information also available on the [http://www.eclipse.org/mylar/dl.php download page].<br />
<br />
Related Resources:<br />
<br />
* [http://confluence.atlassian.com/display/JIRA/JIRA+Development+Hub Jira Development Wiki]<br />
* [http://confluence.atlassian.com/pages/viewpage.action?pageId=1035 Jira RPC Plugin Overview]<br />
<br />
== Why can't I connect? ==<br />
<br />
* If you get a <code>org.tigris.jira.core.service.exceptions.ServiceUnavailableException</code> you need to turn on the JIRA SOAP/RPC services on the server.<br />
* Similarly, if you get a "Processing instructions are not allowed within SOAP messages" message, ensure that SOAP/RPC services are on.<br />
* If you get a '''503''' error code verify that the SOAP/RPC interface is enabled.<br />
* If you get a '''403''' error code verify that the SOAP/RPC interface is enabled, and also check your authentication mechanism. If the server is using NTLM authentication, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156397 bug 156937] for diagnosis steps.<br />
* If you see an '''"unrecognized priority" message''' in the ''Error Log'', the problem is that the JIRA Connector does not support customized priorities so the priority value specified in that message will not correspond to the priority icons visible in the Task List.<br />
* If you are being '''prompted for your log-in credentials''' by the Browser tab of the task editor or the new task editor, this is because without rich editor support the connector is using the web-based UI instead of logging in on your behalf as is done with a rich task editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142869 bug 142869]).<br />
* If you get a <CODE>AuthenticationException</code> and a query won't synchronize, use Task Repositories (view) -> Properties (on the repository) -> Validate Settings. This will clear the connection if it died.<br />
<br />
== Why do I get a "JIRA connector requires server 3.3.3 or later" message? ==<br />
<br />
Version 2.0 of the Jira connector misinterprets version 3.10 as being lower than version 3.3.3. This is fixed in version 2.1 of the connector. Mylyn 2.1 is not compatible with Eclipse 3.2, but Eclipse 3.2/Mylyn 2.0 users can download a later version of the Jira connector from the weekly build download site; the latest Jira connector supports Mylyn 2.0 and Eclipse 3.2. If you get a NullPointerException from the update manager, make sure you've only searched the weekly download Extras site; don't search the 2.0 site at the same time.<br />
<!-- HEAVILY OUTDATED. PLUGIN NOW USES COMMON PROXY INFRASTRUCTURE<br />
== Why can't I synchronize when using a proxy server? ==<br />
<br />
* Proxy configuration is '''based on the normal Java HTTP system properties''', which can be configured either by launching Eclipse with <code>-vmargs</code> and using the following settings, or by putting these settings into the or by putting the following into the <code>eclipse/eclipse.ini</code> file (after -vmags):<br />
-Dhttp.proxyHost=<host> <br />
-Dhttp.proxyPort=<port><br />
* Make sure that when using these settings you do not enable the proxy settings on the ''Install/Update'' preference page, since they may override these settings.<br />
* If you are using '''SSL''', you will also need to set the <code>https.proxyHost</code> and <code>https.proxyPort</code>. <br />
* Authentication is configured with the <code>http.proxyUser</code> and <code>http.proxyPassword</code> system properties (also for SSL)<br />
* You can also use <code>http.nonProxyHosts</code> system property to enumerate hosts that should not be proxied. Note that matching is implemented on the exact host name used for JIRA server and patterns are not supported. --><br />
<br />
== Known limitations ==<br />
* Attachment retrieval (including retrieval of the task context and attachment list in the task editor) require JIRA 3.7 or above ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=169757 bug 169757])<br />
<!-- * NTLM authentication is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172395 bug 172395]) --><br />
* Customized priorities are not currently supported, so all issues with a customized priority will have the default priority level ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=165518 bug 165518]).<br />
* blank but editable custom fields doesn't appear in the RSS data, and as result we can't show them for editing<br />
* because of JIRA api limitations, we can support custom fields in the task editor, but not in the new custom task editor<br />
<!-- * On JIRA 3.6.x private filters saved on the server can fail to retrieve results ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=174328 bug 174328]). The work-around is to create a custom query in Mylyn using the form-based query designer or to share the filter in JIRA. --><br />
* Mylyn only allows the usage of US-ASCII characters in the filename when uploading an attachment ({{bug|203663}})<br />
<br />
== How can I enable compression for SOAP messages? ==<br />
<br />
If your repository has lots of projects and components you can speed up the download of the repository configuration by enabling compression. <br />
<br />
* Add a filter-mapping to your JIRA server configuration: [http://jira.atlassian.com/browse/JRA-10353].<br />
* Enable compression in your global JIRA configuration.<br />
* Check the compression setting for your task repository in Mylyn versions 2.0M2 and later.<br />
<br />
== Reporting issues ==<br />
<br />
Since JIRA can be heavily customized there is a chance that some particular customizations may not work, so if you can't connect to your proprietary repository it is a good idea to try the following public repositories to make sure you have working configuration:<br />
<br />
* http://jira.codehaus.org<br />
* http://issues.apache.org/jira/<br />
* http://opensource.atlassian.com/projects/spring <br />
<br />
If you can't get query results, you could try to call "Open with Browser" on query node in the Task List view and then save link "Current view: XML" and attach it to the bug report.<br />
<br />
Even if query don't work you could try "Open Repository Task" from your JIRA repository node on the Task Repositories view and check if you can open JIRA task editor for that issue. Same for the Task search (Ctrl-H, Task Search)<br />
<br />
To investigate various error you may need to enable debug tracing. To do that you need to create the <code>.options</code> file with the following content:<br />
<br />
<pre><br />
org.eclipse.mylyn.jira.ui/connector=true<br />
org.eclipse.mylyn.jira.ui/dataHandler=true<br />
</pre><br />
<br />
and then add the following options to the Eclipse command line (or eclipse.ini file):<br />
<br />
<pre><br />
-debug <path to the .options file>/.options<br />
</pre><br />
<br />
The additional logging will go into the regular Eclipse log and the Error Log view<br />
<br />
== Why do I get errors about an unexpected redirect when submitting an issue? ==<br />
<br />
Please go to the repository properties and validate the repository. If errors about circular redirects are logged in your Eclipse error log your JIRA server or proxy might be misconfigured. <br />
<br />
In some cases unexpected redirects can be caused by a JIRA server accessed via Apache and mod_jk (using the AJP/1.3 Tomcat connector). Some server configurations may benefit from the 'proxyHost', 'proxyPort', 'scheme' and 'secure' settings on the AJP Connector in the Tomcat server configuration.<br />
<br />
Please see {{bug|202834}} for a more details.<br />
<br />
= Trac Connector =<br />
<br />
== What are the server requirements? ==<br />
<br />
The Trac connector offers two access methods:<br />
<br />
'''XML-RPC''' (recommended)<br />
<br />
Requirements:<br />
* Trac 0.10<br />
* [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] rev. 1950<br />
<br />
This access method offers editing of tasks in a rich editor, attachment support and offline editing. It requires the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] for Trac to be enabled for the accessed repository. The XmlRpcPlugin provides a remote interface to the Trac repository and is distributed separately from Trac (see [http://trac.edgewall.org/ticket/217 #217]). See these [http://trac-hacks.org/wiki/XmlRpcPlugin#Installation install instructions] for requirements and documentation.<br />
<br />
'''Web''' <br />
<br />
Requirements:<br />
* Trac 0.9 or later<br />
<br />
In this mode the standard Trac web interface is used for repository access. Tickets may be created and edited through a web browser. Offline editing and attachments are not supported.<br />
<br />
== Recommended Trac version ==<br />
<br />
Mylyn should work with any stable release Trac release that is version 0.9.x or 0.10.x (see below for known limitations). Mylyn works best when used with Trac's XML-RPC Plugin (see above) but we do not recommend a particular Trac version. <br />
<br />
The Trac connector tests are run against these Trac versions:<br />
<br />
* Trac 0.10.4, XML-RPC Plugin rev. 1950<br />
* Trac 0.9.6<br />
<br />
See {{bug|175211}} for details about Trac 0.11 support.<br />
<br />
== Why do I get an HTTP Error 500 Internal server error when creating a ticket that contains non-ASCII characters? ==<br />
<br />
Problems related to character encodings have been reported when Trac is run with Python 2.3. Upgrading to Python 2.4 may help to resolve this. Please comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=188363 bug #188363] if you encounter an internal server error when creating a ticket that contains non-ASCII characters.<br />
<br />
== Known limitations ==<br />
<br />
* Trac 0.10.1 <br />
** Known incompatibility with Trac XML-RPC Plugin. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164272 bug 164272] for details.<br />
* Trac 0.10.3 <br />
** Known incompatibility with old versions of the Trac HttpAuthPlugin (fixed in revision 1890 or later). The plug-in enables basic auth for XML-RPC when Trac AccountManagerPlugin for form based authentication is used. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168413 bug 168413] for details.<br />
* Trac 0.11<br />
** Currently untested.<br />
** Known incompatibility with Trac XML-RPC Plugin See [http://trac-hacks.org/wiki/XmlRpcPlugin] for details.<br />
<br />
== Why are tasks opened in a web browser and not in the rich editor? ==<br />
<br />
Please make sure that the access type in the repository properties is set to XML-RPC. This requires Trac 0.10 and XML-RPC (see above).<br />
<br />
== Which URLs does Mylyn access in a Trac repository? ==<br />
<br />
XML-RPC:<br />
<br />
* The expected URL is either /xmlrpc or /login/xmlrpc (if login credentials are provided)<br />
<br />
Web:<br />
<br />
* Authentication: /login <br />
* Querying: /query?format=tab...<br />
* Synchronizing ticket details: /ticket/...<br />
* Getting repository configuration to populate query dialog: /query or /newticket<br />
<br />
The web mode relies on screen scraping and is likely to fail if the design<br />
(i.e. HTML output) of the Trac repository is heavily customized.<br />
<br />
= Generic Web Repository Connector =<br />
<br />
== Where can I find the web repository connector ==<br />
<br />
It is available from the extensions update page. Please see http://www.eclipse.org/mylyn/downloads/<br />
<br />
== Why can't I connect using one of the existing templates? ==<br />
<br />
<br />
The Web Repository Connector have a Preview option in Advanced Configuration section on the Query preferences. If you get an error or preview table does not show expected list of tasks you can use Query Pattern like (.+?)(\n) to see content of the retrieved page and compare it with the source of the web page for the same url loaded into the web browser.<br />
<br />
If that does not help then you could use the wget tool (on Windows it available as a standalone command line tool and also included with Cygwin).<br />
<br />
Run the following command:<br />
<br />
<pre>wget -v -d -o query.log -O query.html "http://your.query.url"</pre><br />
<br />
If repository require basic http auth, you'll need to use ''--http-user=USER'' and ''--http-password=PASS'' options.<br />
<br />
Then open file ''query.html'' in the web browser and check if it show list of issues you need to fetch from the web server. If it does have correct list, then there could be a problem with query pattern used for parsing. <br />
<br />
A popular mistake is an unmasked '?' that separates request parameters in the url). For example:<br />
<br />
<pre><a href="show_bug.cgi\?id\=(.+?)">.+?<span class="summary">(.+?)</span></pre><br />
<br />
If ''query.html'' does not show expected list of issues you can check ''query.log'' for server responses and try to identify if server require authentication, redirecting your requests somewhere or issue any other errors.<br />
<br />
== Known limitations ==<br />
<br />
* In Mylyn 1.0: if a web server responds by requesting a redirect to an absolute URL while fetching a resource, the connector falsely prepends "/" to the URL and the request will fail. The workaround is to use final url where redirect is pointing to (you can find it as describe above). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=167282 bug 167282] for details.<br />
<br />
= Task-Focused UI =<br />
<br />
== What is the Task-Focused UI? ==<br />
<br />
When you activate a task, Mylyn automatically maintains a task context by monitoring your interaction. The task context provides a predictable degree-of-interest weighting of the relevance of the elements and relations that you work with to the task-at-hand (as described in the [http://kerstens.org/mik/publications/2006-11-mylar-fse.pdf Foundations of Software Engineering conference paper]). The Task-Focuse UI is the mechanism by which Mylyn presents Mylyn the task-context model in order to reduce information overload and to automate the manaul management of UI elements like editors and change sets. Examples:<br />
* Filtering, decoration and expansion management in views<br />
* Automatic folding in editors<br />
* Ranking in content assist<br />
* Editor management<br />
* Perspective management<br />
* Change set management<br />
<br />
== Why do files disappear from Focused views when I close them? ==<br />
<br />
By default Mylyn automatically manages the set of open files to match the task context, so that you don't have to. This ensures that the editor list (viewable via mechanisms like Ctrl+E) corresponds to what you in views like the ''Package Explorer'' when they are in Focused mode. When you close a file manually, you express that it is uninteresting, and as such it will be removed from the task context. It will also disappear from the corresponding automatically managed change sets for the same reason. This behavior can be turned off via ''Preferences -> Mylyn -> Context -> Manage open editors to match task context''. However, it is highly recommended since Mylyn will prevent the number of editors from bloating by automatically closing editors for elements that have decayed in interest, and always keep the editors for interesting elements open.<br />
<br />
<br />
== Why did all my editor tabs disappear? ==<br />
<br />
When you deactivate a task, all editors will be closed, and then when you reactivate the task all the windows will be open again. Try it, it's fun. <br />
<br />
Mylyn actively manages your open editors with task context. It takes some getting used to, but enables switching between tasks when you are multitasking without cluttering your editor tabs. This editor management can be disabled via ''Window -> Preferences -> Mylyn -> Context''. However, before disabling it consider reading the ''"Managing open editors..."'' section of [http://www-128.ibm.com/developerworks/java/library/j-mylar2/index.html#N10116 Task-focused programming with Mylar].<br />
<br />
== How do I get rid of an element if it is not interesting? ==<br />
<br />
When a view is focused elements will disappear on their own if they are not repeatedly selected via a mechanism called interest decay. Note that decay does not use the wall clock, but instead relies on the number of selections that you have made when working on that task to determine which elements disappear. This helps make it feel very predictable.<br />
<br />
If you want want to force one or more elements to disappear from the context use the '''Remove from Focus''' action on the context menu. Note that the element will still be part of the task context since it was previously part of the interaction. <br />
<br />
If you want to permanently delete the element from the interaction history use the '''Remove from Context''' action on the '''Context''' tab of the '''Task Editor'''. For example, if a company private element was part of a task context that is to be shared with a public repository, this action can be used to clean it up before sharing. Note that elements will be removed from the task context recursively.<br />
<br />
== Which Focused UI features can I turn off? ==<br />
<br />
'''All of them.''' When no task is active neither are any of Mylyn's features. When working with task contexts Mylyn's Focused UI features are all optional and in general configurable. While many find it the key benefit of Mylyn, the entire Focused UI is optional and can be uninstalled via ''Help -> Software Updates -> Manage Configuration''.<br />
<br />
The following table summarizes how the key features can be toggled:<br />
<br />
<table><br />
<tr><br />
<td>'''UI Mechanism'''</td><br />
<td>'''Example/description'''</td><br />
<td>'''Toggle using'''</td><br />
</tr><br />
<tr><br />
<td>Interest filtering</td><br />
<td>Package Explorer</td><br />
<td>''Apply Mylyn'' button on view toolbar</td><br />
</tr><br />
<tr><br />
<td>Automatic toggling of filtering</td><br />
<td>Package Explorer</td><br />
<td>''Preferences -> Mylar -> Context -> Toggle focused mode..</td><br />
</tr><br />
<tr><br />
<td>Interest decoration</td><br />
<td>Bolding of landmark elements</td><br />
<td>''Preferences -&gt; General -&gt; Appearance -&gt; Label Decoration''</td><br />
</tr><br />
<tr><br />
<td>Content assist</td><br />
<td>Ranking of interesting elements</td><br />
<td>Eclipse 3.2: ''Java -&gt; Editor -&gt; Content Assist -&gt; Work in Progress -&gt;'' turn off Mylyn, turn on Java</td><br />
</tr><br />
<tr><br />
<td>Active change sets</td><br />
<td>Grouping of changes by tasks</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Team''</td><br />
</tr><br />
<tr><br />
<td>Editor management</td><br />
<td>Auto opening/closing of editors</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Editor Management''</td><br />
</tr><br />
<tr><br />
<td>Active views</td><br />
<td>Active Search and Hierarchy</td><br />
<td>Only on if view is active</td><br />
</tr><br />
</table><br />
<br />
For additional configuration options see the ''Mylyn'' and ''General -> Appearance'' preference pages.<br />
<br />
<br />
<br />
== What happened to the Active Search and Active Hierarchy views? ==<br />
<br />
These views were not included in the Mylyn 1.0 release because they never made it beyond the experimental phase. <br />
* The ''Active Search'' view has not been sufficiently tuned to adapt to the lifecycle of a task context, and as a result requires manual manipulation of the degree-of-separation scope as you work on long-running tasks. Otherwise it becomes overloaded with elements. In addition, it is not yet clear whether an additional view is the right UI for this facility, and it is hard to find room for an additional view of this size on screen resolutions of 1600x1200 and smaller.<br />
* The ''Active Hierarchy'' view is also hard to allocate space for, especially when using the in-place hierarchy (Ctrl+T) on a landmark can be a quick way to see the relevant part of the task context's hierarchy.<br />
<br />
These features still show promise in displaying task context and saving repetitive searches, so we have not removed them. They have instead moved to the Mylyn Sandbox, and can be used and experimented with by following the [http://wiki.eclipse.org/index.php/Mylyn_Contributor_Reference#Sandbox instructions on the Contributors page]. For feedback on these views please use the corresponding bug reports or newsgroup.<br />
<br />
= Java Development =<br />
<br />
== Content assist troubleshooting ==<br />
<br />
Mylyn uses custom Content Assist processors in order to rank and separate the elements in the current task context. To see proposals ranked according to interest you must have only the ''Type Proposals (Mylyn)'' kinds checkbox enabled in the list below, otherwise you will see duplicates. '''If you do not see any proposals, check this list''' to ensure that either the Mylyn or the plain proposals are enabled. '''To do this automatically''', run ''New -> Mylyn -> Recommended Preferences''. Or you can select them manually as in the preference page below. <br />
<br />
[[Image:mylar-content-assist-prefs.gif]]<br />
<br />
'''Why do I see duplicate proposals?'''<br />
<br />
Ensure that you have only the ''(Mylyn)'' proposals kinds enabled in ''Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced'', otherwise you will see duplicates.<br />
<br />
If you use proposals via Ctrl+Shift+Space instead of the typical Ctrl+Space you will see duplicates. Vote for JDT/Text [https://bugs.eclipse.org/bugs/show_bug.cgi?id=147781 bug 147781] if you use this mechanism. Also see: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=129080 bug 129080]<br />
<br />
'''Why do I get an error message when using content assist?'''<br />
<br />
If after invoking Content Assist you see an error message dialog that states:<br />
The extension took too long to return from the 'computeCompletionProposals()' operation<br />
this is most likely due to something interrupting the proposal operation (e.g. garbage collection). Ignore it if it does not recur, increase Eclipse's memory if it does (e.g via <code>-Xmx384M</code> command line argument). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=141457 bug 141457] for more details. <br />
<br />
Note that Mylyn should only add a trivial amount of overhead to content assist computation, however, the standard content assist mechanism will not report timeouts of this sort (i.e. taking longer than 5s to compute proposals). If the system that you are working on is so large that increasing memeory does not reduce the timings to avoid the message, you could also consider disabling the Mylyn-specific content assist, as described above, but if doing so please comment on {{bug|141457}}.<br />
<br />
[[Image:mylyn-content-assist-timeout.gif]]<br />
<br />
== Why do interesting elements not show in the Project Explorer? ==<br />
<br />
The ''Package Presentation -> Hierarchical'' mode is not supported on the ''Project Explorer'' view in Eclipse 3.2 through 3.3M3 and possibly later versions (https://bugs.eclipse.org/bugs/show_bug.cgi?id=161362 bug 161362). Use the view menu to set ''Package Presentation -> Flat'' as a work-around.<br />
<br />
== How do I stop declarations from showing in the Package Explorer? ==<br />
<br />
If you don't like Mylyn's constant showing of Java members in the ''Package Explorer'', select the drop-down menu, then ''Filters...'' and enable the ''Mylyn Java Declarations Filter''. It will then stick in the menu in case you want to toggle between modes. Note that this will hide interest information about members that aren't in your current file (e.g. showing you which methods are landmarks) so this mode is not recommended, but can be useful for <code>1024x768</code> screen resolutions.<br />
<br />
[[Image:mylar-java-filtering-declarations.gif]]<br />
<br />
== Why does nothing show up in the Active Search or Active Hierarchy? ==<br />
<br />
As you work, elements become Landmarks (bold decoration), and these elements populate the ''Active Search'' and ''Active Hierarchy'' views. To force an element to populate the views manually, make it a Landmark by <code>right+clicking</code> or hitting <code>Ctrl+Alt+Shift+UpArrow</code>.<br />
<br />
== Known limitations ==<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=106678 Bug 106678]: The Project Explorer's Hierarchical Java package presentation layout is not supported on Eclipse 3.3Mx, and interesting elements will be hidden if enabled. Work-around is to use the default Flat package presentation.<br />
<br />
= Team Support =<br />
<br />
== Why does task change set not appear when I modify files? ==<br />
<br />
A task change set should appear if you activate a task and modify a file connected to a compatible source repository (e.g. CVS, SVN). If it does not try the following:<br />
<br />
* Ensure you have installed the [http://www.eclipse.org/mylyn/downloads/ ''Mylyn Bridge: Eclipse SDK'' feature]. Note that this feature is not currently distributed with the Java-only Eclipse download ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191793 bug 191793] ).<br />
<br />
* Verify that the [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuring_the_Synchronize_view_for_change_sets configured ''Synchronize View'' is configured for change sets].<br />
<br />
If the above are working but the change set appears to be missing relevant files:<br />
<br />
* You may be seeing the ''Synchronize'' view's refresh problem ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142395 bug 142395]). Toggle from ''Incoming/Ougtoing'' to ''Incoming'' mode and back again to refresh the view.<br />
<br />
* If the files or change set are still missing deactivate and reactivate the task to force a full refresh.<br />
<br />
== Why do files disappear from the change set when I close them? ==<br />
<br />
If you have the ''Preferences -> Mylyn -> Context -> Manage open editors to match task context'' option enabled, Mylyn will perform editor management so that you don't have to. Closing a file makes it less interesting, and causes it to disappear from the active task context, and hence from the change set. This option prevents you from having to manage the set of open files, will automatically close editors for files that become uninteresting, and will ensure that the open editors match the task context.<br />
<br />
== Why am I missing elements when I retrieve someone else's context? ==<br />
<br />
To identify elements within a project, Mylyn relies on the name of the project being consistent across workspaces. If the project name in the workspace that the context was created with is different than its name in your workspace, the task context will not show elements within that project ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164058 bug 164058]). The other case where context can be lost is if the elements change names outside of the workspace ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164243 bug 164243]).<br />
<br />
The work-around is to use the same project names across your team's workspaces. We recommend the following two approaches for standardizing on project names:<br />
* Use '''Team Project Sets''': these are a very useful Eclipse facility that allows your entire team to check out numerous projects from version control by importing a single file. Create a project set via ''File -> Export -> Team Project Set'', host this file somewhere accessible, then have others import vai ''File -> Import -> Team Project Set''.<br />
* Have developers check out projects into their workspace without renaming them. The above is a shortcut for doing this. If alphabetical sort order in the ''Package Explorer'' is a problem, organize your projects via ''Project Explorer -> view menu -> Top Level Elements -> Working Sets''.<br />
<br />
= Misc =<br />
<br />
<br />
<br />
== How does Mylyn relate to IBM's Jazz? ==<br />
<br />
At the EclipseCon and JavaONE 2006 conferences IBM demonstrated previews of Jazz, a collaborative team server and Eclipse-based client. Articles have remarked on the similarities between Mylyn and Jazz because both integrate tasks into Eclipse (Jazz's "work items" and Mylyn's "tasks"), and both provide change sets grouped by task. But there are both significant differences and complementary aspects to the two approaches. A key goal of Mylyn is to provide an open source framework to support integration of task management with ''existing issue trackers and source repositories''. According to the presentations, components that come with Jazz include include a ''next-generation issue tracker and source repository'' and related lifecycle management tools such as project health. In addition, a driving and unique goal of Mylyn is to focus the UI around a usage-based and degree-of-interested weighted task context, which is complementary to the Jazz platform. Just as it integrates with Mylyn's Task List, Mylyn's Task Focused UI and task context model components are possible to integrate with other kinds of task management systems, such as the one provided by Jazz.<br />
<br />
Update: at EclipseCon 2007 the IBM Jazz team showed a Mylyn connector for Jazz.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=53873Mylyn/Meetings2007-10-08T18:52:29Z<p>Steffen.pingel.eclipse.org: /* Pending Discussion Items */</p>
<hr />
<div>[[Category:Mylyn]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
[[Mylyn Meetings Archive]]<br />
<br />
=== Pending Discussion Items ===<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
* Active task and working set presentation/switching when Task List is not visible<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Arbitrary attributes discussion {{bug|199818 }}<br />
* Design discussion - bugzilla cached configuration (Rob)<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, October 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Summary bug view / quick viewing of bug reports design discussion: {{bug|205669}} (Steffen)<br />
<br />
Minutes:<br />
----<br />
<br />
=== Past Meetings ===<br />
<br />
==== Tuesday, October 2, 10-11am PT ====<br />
<br />
Agenda:<br />
* 2.1 release review (Mik)<br />
* Eclipse.org bandwidth usage {{bug|196056}} {{bug|205213}} (Rob)<br />
* XPlanner update (Helen)<br />
* 3.0 plan review and bug triage (all)<br />
* Mylyn connector for mingle (Ketan)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 25, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 2.1, Europa Fall Update and Ganymede status and review of remaining items (Mik)<br />
* Update sites, linking and download redesign (Mik) {{bug|194469}}<br />
* Sandbox quality bar and policy for inclusion of features for discoverable sites in Europa Fall Update (Mik) {{bug|204560}}<br />
* Subtasks being enabled by default for Bugzilla and corresponding policies (Rob, Mik, Eugene)<br />
** artificial "grouping" vs. showing subtasks<br />
* JIRA update (Steffen)<br />
* XPlanner update (Helen)<br />
<br />
Minutes:<br />
* Update site should include historical builds as part of archive<br />
* Subtask setting to be renamed<br />
<br />
==== Tuesday, September 18, 10-11am PT ====<br />
<br />
Agenda:<br />
* Policy for adding stuff to the Sandbox, i.e. group by scheduled vs. "out of nowhere" "Incoming (Experimental)" presentation (Eugene)<br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* 3.0 planning (Mik)<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 11, 10-11am PT ====<br />
<br />
Agenda: <br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* Policy for making significant changes to open bugs' status, e.g. marking for bugday (Mik)<br />
* 3.0 planning (Mik)<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Arbitrary attributes discussion {{bug|199818 }}<br />
* Summary bug view / quick viewing of bug reports design discussion<br />
* Design discussion - bugzilla cached configuration <br />
<br />
Minutes:<br />
----<br />
<br />
<br />
==== Tuesday, September 4, 10-11am PT ====<br />
<br />
Agenda: <br />
* Missed BugDay<br />
* Summer of Code wrap-up (Jevgeni, Xiaoyang, Balazs)<br />
* Policy: <br />
** Resolving bug reports (Rob)<br />
** Reopening closed reports, i.e. AllTasks fails (Eugene)<br />
* Design discussion - bugzilla cached configuration<br />
* 2.1 and 3.0 Planning (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
<br />
Minutes:<br />
<br />
* Bug Day<br />
** We will participate in Bug Day<br />
** Need to continute to maintain/label bug day bugs<br />
** Must maintain calendar of bug day events and send announcemnts to newsgroup/mailing lists <br />
** Eugne willing to mentor on bug days<br />
<br />
*Policy<br />
** Contributions (patches) must be accompanied with summary of issues addressed by provided patch. Must also indicate if patch is intended to resolve bug report or further work required. (Rob will update Contributor Reference) <br />
** Reopening closed reports not encouraged. Mik will resolve bug#152869 - creating bugs from failed unit tests for 2.1<br />
<br />
* Builds<br />
** RC builds, dev builds as weekly milestone builds (Mik to send proposal to newsgroup to get feedback from community on this proposed change)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=53872Mylyn/Meetings2007-10-08T18:51:49Z<p>Steffen.pingel.eclipse.org: /* Tuesday, October 9, 10-11am PT */</p>
<hr />
<div>[[Category:Mylyn]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
[[Mylyn Meetings Archive]]<br />
<br />
=== Pending Discussion Items ===<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
* Active task and working set presentation/switching when Task List is not visible<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Arbitrary attributes discussion {{bug|199818 }}<br />
* Design discussion - bugzilla cached configuration (Rob) <br />
* Summary bug view / quick viewing of bug reports design discussion<br />
* Trajectory and best home for org.eclipse.mylyn.trac.wiki (Mik, Steffen)<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, October 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Summary bug view / quick viewing of bug reports design discussion: {{bug|205669}} (Steffen)<br />
<br />
Minutes:<br />
----<br />
<br />
=== Past Meetings ===<br />
<br />
==== Tuesday, October 2, 10-11am PT ====<br />
<br />
Agenda:<br />
* 2.1 release review (Mik)<br />
* Eclipse.org bandwidth usage {{bug|196056}} {{bug|205213}} (Rob)<br />
* XPlanner update (Helen)<br />
* 3.0 plan review and bug triage (all)<br />
* Mylyn connector for mingle (Ketan)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 25, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 2.1, Europa Fall Update and Ganymede status and review of remaining items (Mik)<br />
* Update sites, linking and download redesign (Mik) {{bug|194469}}<br />
* Sandbox quality bar and policy for inclusion of features for discoverable sites in Europa Fall Update (Mik) {{bug|204560}}<br />
* Subtasks being enabled by default for Bugzilla and corresponding policies (Rob, Mik, Eugene)<br />
** artificial "grouping" vs. showing subtasks<br />
* JIRA update (Steffen)<br />
* XPlanner update (Helen)<br />
<br />
Minutes:<br />
* Update site should include historical builds as part of archive<br />
* Subtask setting to be renamed<br />
<br />
==== Tuesday, September 18, 10-11am PT ====<br />
<br />
Agenda:<br />
* Policy for adding stuff to the Sandbox, i.e. group by scheduled vs. "out of nowhere" "Incoming (Experimental)" presentation (Eugene)<br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* 3.0 planning (Mik)<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 11, 10-11am PT ====<br />
<br />
Agenda: <br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* Policy for making significant changes to open bugs' status, e.g. marking for bugday (Mik)<br />
* 3.0 planning (Mik)<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Arbitrary attributes discussion {{bug|199818 }}<br />
* Summary bug view / quick viewing of bug reports design discussion<br />
* Design discussion - bugzilla cached configuration <br />
<br />
Minutes:<br />
----<br />
<br />
<br />
==== Tuesday, September 4, 10-11am PT ====<br />
<br />
Agenda: <br />
* Missed BugDay<br />
* Summer of Code wrap-up (Jevgeni, Xiaoyang, Balazs)<br />
* Policy: <br />
** Resolving bug reports (Rob)<br />
** Reopening closed reports, i.e. AllTasks fails (Eugene)<br />
* Design discussion - bugzilla cached configuration<br />
* 2.1 and 3.0 Planning (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
<br />
Minutes:<br />
<br />
* Bug Day<br />
** We will participate in Bug Day<br />
** Need to continute to maintain/label bug day bugs<br />
** Must maintain calendar of bug day events and send announcemnts to newsgroup/mailing lists <br />
** Eugne willing to mentor on bug days<br />
<br />
*Policy<br />
** Contributions (patches) must be accompanied with summary of issues addressed by provided patch. Must also indicate if patch is intended to resolve bug report or further work required. (Rob will update Contributor Reference) <br />
** Reopening closed reports not encouraged. Mik will resolve bug#152869 - creating bugs from failed unit tests for 2.1<br />
<br />
* Builds<br />
** RC builds, dev builds as weekly milestone builds (Mik to send proposal to newsgroup to get feedback from community on this proposed change)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=53871Mylyn/Meetings2007-10-08T18:51:22Z<p>Steffen.pingel.eclipse.org: /* Tuesday, October 9, 10-11am PT */</p>
<hr />
<div>[[Category:Mylyn]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
[[Mylyn Meetings Archive]]<br />
<br />
=== Pending Discussion Items ===<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
* Active task and working set presentation/switching when Task List is not visible<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Arbitrary attributes discussion {{bug|199818 }}<br />
* Design discussion - bugzilla cached configuration (Rob) <br />
* Summary bug view / quick viewing of bug reports design discussion<br />
* Trajectory and best home for org.eclipse.mylyn.trac.wiki (Mik, Steffen)<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, October 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Summary bug view / quick viewing of bug reports design discussion: {{bug|205669}}} (Steffen)<br />
<br />
Minutes:<br />
----<br />
<br />
=== Past Meetings ===<br />
<br />
==== Tuesday, October 2, 10-11am PT ====<br />
<br />
Agenda:<br />
* 2.1 release review (Mik)<br />
* Eclipse.org bandwidth usage {{bug|196056}} {{bug|205213}} (Rob)<br />
* XPlanner update (Helen)<br />
* 3.0 plan review and bug triage (all)<br />
* Mylyn connector for mingle (Ketan)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 25, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylyn 2.1, Europa Fall Update and Ganymede status and review of remaining items (Mik)<br />
* Update sites, linking and download redesign (Mik) {{bug|194469}}<br />
* Sandbox quality bar and policy for inclusion of features for discoverable sites in Europa Fall Update (Mik) {{bug|204560}}<br />
* Subtasks being enabled by default for Bugzilla and corresponding policies (Rob, Mik, Eugene)<br />
** artificial "grouping" vs. showing subtasks<br />
* JIRA update (Steffen)<br />
* XPlanner update (Helen)<br />
<br />
Minutes:<br />
* Update site should include historical builds as part of archive<br />
* Subtask setting to be renamed<br />
<br />
==== Tuesday, September 18, 10-11am PT ====<br />
<br />
Agenda:<br />
* Policy for adding stuff to the Sandbox, i.e. group by scheduled vs. "out of nowhere" "Incoming (Experimental)" presentation (Eugene)<br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* 3.0 planning (Mik)<br />
* {{bug|203399}} standardize hyperlinking strategy for the Task Editor (Eugene)<br />
<br />
Minutes:<br />
----<br />
<br />
==== Tuesday, September 11, 10-11am PT ====<br />
<br />
Agenda: <br />
* Review of all bugs scheduled for Mylyn 2.1 (all)<br />
* Policy for making significant changes to open bugs' status, e.g. marking for bugday (Mik)<br />
* 3.0 planning (Mik)<br />
* Design discussion: queries, categories, groupings and recommended settings {{bug|175318}} (Mik)<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
* Arbitrary attributes discussion {{bug|199818 }}<br />
* Summary bug view / quick viewing of bug reports design discussion<br />
* Design discussion - bugzilla cached configuration <br />
<br />
Minutes:<br />
----<br />
<br />
<br />
==== Tuesday, September 4, 10-11am PT ====<br />
<br />
Agenda: <br />
* Missed BugDay<br />
* Summer of Code wrap-up (Jevgeni, Xiaoyang, Balazs)<br />
* Policy: <br />
** Resolving bug reports (Rob)<br />
** Reopening closed reports, i.e. AllTasks fails (Eugene)<br />
* Design discussion - bugzilla cached configuration<br />
* 2.1 and 3.0 Planning (Mik)<br />
* Arbitrary attributes discussion {{bug|199818}}<br />
* Visualization of entries that don't match queries {{bug|201157}} (Eugene)<br />
<br />
Minutes:<br />
<br />
* Bug Day<br />
** We will participate in Bug Day<br />
** Need to continute to maintain/label bug day bugs<br />
** Must maintain calendar of bug day events and send announcemnts to newsgroup/mailing lists <br />
** Eugne willing to mentor on bug days<br />
<br />
*Policy<br />
** Contributions (patches) must be accompanied with summary of issues addressed by provided patch. Must also indicate if patch is intended to resolve bug report or further work required. (Rob will update Contributor Reference) <br />
** Reopening closed reports not encouraged. Mik will resolve bug#152869 - creating bugs from failed unit tests for 2.1<br />
<br />
* Builds<br />
** RC builds, dev builds as weekly milestone builds (Mik to send proposal to newsgroup to get feedback from community on this proposed change)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/FAQ&diff=51163Mylyn/FAQ2007-09-19T20:12:40Z<p>Steffen.pingel.eclipse.org: /* Known limitations */</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
[[Mylyn User Guide]], <br />
[http://eclipse.org/mylyn Mylyn Home],<br />
[http://wiki.eclipse.org/index.php?title=Special:Userlogin&returnto=Special:Userlogout Log in to edit]<br />
<br />
For instructions on [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Download_Mylar downloading] [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installation installing] and [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuration configuring] <br />
Mylyn, see the [[Mylyn User Guide]]. For instructions on developing and contributing to Mylyn, see the [[Mylyn Contributor Reference]].<br />
<br />
= Installation =<br />
<br />
== What versions of Eclipse are supported? ==<br />
<br />
See the [http://eclipse.org/mylyn/dl.php download page].<br />
<br />
Mylyn also relies on a web browser that works with the Standard Widget Toolkit; Windows and MacOS users are fine, but Linux users might have to download another browser. See [http://www.eclipse.org/swt/faq.php#browserlinux the SWT Browser guide] for which browsers will work. See [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux installing browser on Linux] for installation instructions.<br />
<br />
== What version of Java is required? ==<br />
<br />
Mylyn needs the '''Java 5''' virtual machine.<br />
<br />
To check the version of the Java virtual machine that Eclipse was launched with to to ''Help -> About Eclipse SDK -> Configuration Details'' and verify that the java.vm.version is 1.5. <br />
<br />
Mac users should refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
* If you do not have Java 5, you can download it from [http://72.5.124.55/javase/downloads/index.jsp Sun's web site]. <br />
* If you have more than one VM, you need to specify that Eclipse should use the JDK1.5 VM. <br />
<br />
In Unix, set the environment variable <code>JAVA_HOME</code> to the root of the JDK1.5 installation and/or set the <code>PATH</code> variable to put the JDK1.5 executable directory before any other VM executable directories. For example, under <code>bash</code> in Unix:<br />
export JAVA_HOME="''(location of JDK1.5 root)''"<br />
export PATH=$JAVA_HOME/bin:$PATH<br />
<br />
<b>We do [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140955 not recommend] using JDK 1.6 on Eclipse 3.1.</b> (It works fine with Eclipse 3.2 or 3.3.) To use JDK 1.6 on Eclipse 3.1, you must add the following line to your <code>config.ini</code>file:<br />
<code><br />
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,<br />
J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6<br />
</code><br />
<br />
== What version of Mylyn is distributed with the Eclipse downloads? ==<br />
<br />
The [http://www.eclipse.org/downloads/ default Eclipse downloads] contain the following Mylyn redistributions. Since the redistributed versions can be missing important bug fixes or feature additions, we recommend using the [http://www.eclipse.org/mylyn/downloads latest version of Mylyn].<br />
<br />
* Eclipse IDE for Java Developers: all of Mylyn except Team integration (e.g. automatic change sets) integration. Install the Eclipse CVS integration and then install the latest Mylyn build to get this component.<br />
<br />
* Eclipse IDE for Java EE Developers: all of Mylyn redistribution, install manually<br />
<br />
* Eclipse IDE for C/C++ Developers: no Mylyn redistribution, install manually<br />
<br />
* Eclipse for RCP/Plug-in Developers: all of Mylyn redistributed<br />
<br />
* Eclipse Classic: no Mylyn redistribution, install manually<br />
<br />
== My tasks or queries disappeared, what do I do? ==<br />
<br />
This happens if Mylyn failed to install. First ensure that you have a correct install by following the instructions in the next section. After that, if you still do not see your tasks use the ''Task List'' view menu -> ''Restore Tasks From History...'' command (also available via ''File -> Import -> Task List''.<br />
<br />
== Installation Troubleshooting ==<br />
<br />
''' Java Persistence API Tools error when updating the JEE Eclipse Package '''<br />
<br />
If you are trying to install additional features and get this error you have hit [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194959 bug 194959] which should be resolved soon. The work-around is to check off the ''Europa Discovery Site'' and install the first two components of the ''Data Tools Platform''.<br />
<br />
''' Update failures '''<br />
<br />
On Eclipse versions earlier than 3.3 (final) use '''only the "Search for new features.."''' option when updating Mylyn. If you use "Search for updates..." the Update Manager will allow a partial install that can cause Mylyn to fail to start, and you will need to run update again. See the ''feature configuration problem'' section below for details. If you encounter this problemm consider voting for Platform [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132450 bug 132450].<br />
<br />
''' Startup exceptions '''<br />
<br />
If you see startup errors or warnings such as <code>BundleException</code> or timeout messages restart Eclipse with the <code>-clean</code> flag either on the command line, in your shortcut link, or by temporarily it into the <code>eclipse/eclipse.ini</code> file. If that does not resolve the problem please [http://www.eclipse.org/mylar/bugs.php file a bug].<br />
<br />
''' Incompatible VM (e.g. JDK 1.4) '''<br />
<br />
If you are using the wrong VM, you'll see errors like the following in your log file. <br />
<code><br />
Root exception: java.lang.UnsupportedClassVersionError:<br />
org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)<br />
</code><br />
<br />
See [[#Download_and_configure_Java_5_or_6|Configure Java]] to fix this problem.<br />
<br />
''' Incompatible version of Eclipse '''<br />
<br />
Separate versions and update sites exist [http://eclipse.org/mylyn/dl.php for Eclipse 3.1 and 3.2]), in which case you may see errors like the following in your <code><workspace>/.metadata/.log </code>file or in a Mylyn view:<br />
<code><br />
java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()<br />
The activator org.eclipse.mylar.java.MylarJavaPlugin for bundle org.eclipse.mylar.java is invalid<br />
</code><br />
<br />
''' Mylyn feature configuration problem '''<br />
<br />
If the above do not address the issue, the easiest thing to do is uninstall any old versions and update to the latest Mylyn. Your tasks won't be lost, because by default they are stored in the <code><workspace>/.metadata/.mylyn</code> folder which will be read next time Mylyn starts correctly. <br />
* First, uninstall the old version of Mylyn using ''Help -> Software Updates -> Manage Configuration''. <br />
* You need to Disable all Mylyn features by right-clicking them.<br />
* Allow Eclipse to restart after the last is disabled.<br />
* After restart, ensure that the 3rd toolbar button is pressed (figure below) so that you see the disabled features to uninstall.<br />
* Uninstall all the disabled features using the popup menu. <br />
<br />
If you don't uninstall, the the Update Manager will think that you have the latest and tell you that there are no updates. <br />
<br />
<b>Note: manually removing the plug-ins and features can lead to configuration errors.</b> <br />
<br />
After uninstalling, update Eclipse by adding the correct update site specified at on the [http://eclipse.org/mylar/dl.php download page], and after that automatically or manually updating will install the correct version.<br />
<br />
[[Image:mylar-eclipse-manage-configuration.gif]]<br />
<br />
'''What do I need to do in installation to be able to use Mylyn task management features with bug/task/issue trackers?'''<br />
<br />
When you install, make sure that you select a connector for your bug/task/issue tracking software. For example, to use Bugzilla, you have to install the Bugzilla connector component.<br />
<br />
'''I've installed Mylyn ; why can't I see anything different?'''<br />
<br />
The two most likely possibilities are:<br />
# You don't have any Mylyn views open. Select ''Window -> Show View -> Other'', then select ''Mylyn'' and you should see the available Mylyn Views. <br />
# If you still don't see anything, then perhaps you aren't using the JDK1.5 VM (or later). See [[Mylyn_Installation_Guide#Download_and_configure_Java|configuring Java]].<br />
<br />
<br />
'''What does the error "Network connection problems encountered during search" mean?'''<br />
<br />
If you get that message while trying to download Mylyn, it means that Eclipse couldn't find the location you entered. This might be because you copied something incorrectly (watch for extra characters -- even extra spaces can cause errors), or because the site went down. You may be able to see if the site is up or down by copying the URL into your Web browser.<br />
<br />
'''What does the "Update manager failure" message mean? '''<br />
<br />
It means that Eclipse could not access the update site, or that it got confused about the configuration state of your Eclipse. First try updating again to see if the update site is accessible. <br />
<br />
If you are trying to update the JIRA connector you can also try de-selecting that feature in case the <code>Tigris.org</code> update site is not accessible. Using ''Search for new features to install..'' when installing can help to avoid this problem. If that does not work see the feature configuration troubleshooting below. <br />
<br />
'''What does "Could not create Browser page: No more handles (<code>java.lang.UnsatisfiedLinkError: ...</code>)" mean?'''<br />
<br />
It probably means that you are running Linux and don't have Eclipse and a Web browser configured to work together. See [[http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux| installing a browser on Linux]].<br />
<br />
'''When downloading, why do I get a warning that the feature was unsigned?'''<br />
<br />
Signing plugins requires extra administrative details with <code>eclipse.org</code> which most plug-ins seek to avoid. <br />
<br />
'''N.B.''': Security issues with features should not be underestimated. Eclipse allows users to download new functionality from remote servers. A rogue plug-in can act as a perfect Trojan horse. It can look innocent enough and provide useful function while spawning threads in the background with full access to the local file system and the Internet (if connected). Beware of installing features from update sites you do not trust.<br />
<br />
'''What does "<code>Root exception: java.lang.UnsupportedClassVersionError: org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)</code>" mean?'''<br />
<br />
It probably means that the virtual machine is JDK1.4 or lower. See [[Mylyn_Installation_Guide#Download_and_configure_Java| download and configure Java]].<br />
<br />
'''Why am I getting messages in my <code><workspace>/.metadata/.log</code> or my Mylyn view that say things like <code>"java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()"</code> and "The activator <code>org.eclipse.mylar.java.MylarJavaPlugin</code> for bundle <code>org.eclipse.mylar.java</code> is invalid"?'''<br />
<br />
This probably means that your Mylyn download version didn't match your Eclipse download version. Note that [http://eclipse.org/mylar/dl.php the download site] has different downloads for Eclipse 3.1 and Eclipse 3.2.<br />
<br />
To fix this problem, see the [[Mylyn_Uninstallation_Guide| uninstallation guide]], then re-install from [http://eclipse.org/mylar/dl.php the correct download site].<br />
<br />
'''What does "Could not create Bugzilla editor input" and "<code>java.io.IOException</code>: SAX2 driver class <code>org.apache.xerces.parsers.SAXParser</code> not found" mean?'''<br />
<br />
It probably means that you are on MacOS, and for some reason are missing Xerces from the Mac JDK1.5. You will probably need to add it to your default classpath. Please refer to and comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=144287 bug 144287] if you see this problem.<br />
<br />
To ensure that you are using the 1.5 VM refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
'''I've just updated to Mylyn 2.0 and I don't see any tasks in my Task List'''<br />
<br />
As part of the update to Mylyn 2.0 the old data folder has been migrated to <workspace folder>/.metadata/.mylyn from the old location <workspace folder>/.mylar. IF for some reason migration failed (.mylar folder still exists), simply shut down Eclipse and manually move your old <workspace folder>/.mylar folder to <workspace folder>/.metadata/.mylyn (note the name change to .mylyn)<br />
<br />
== Configuration Troubleshooting == <br />
<br />
'''How can I change the number of editors left open before Mylyn starts closing editors?'''<br />
<br />
Turn off or increase the number of editors to leave open using ''Preferences -> General -> Editors -> Number of opened editors before closing''. Since Mylyn will manage the open editors with task activation, this number can be set higher or you can disable automatic closing entirely.<br />
<br />
'''Do I need the Outline View when running Mylyn?'''<br />
<br />
No, not really. The Package Explorer and folded signatures should provide enough context for you. If, at some point, you really need to see an Outline View, you can always enter (Ctrl+O) to show the in-place Outline View.<br />
<br />
'''What does the message "content assist proposals no longer appear" mean?'''<br />
<br />
This usually happens when uninstalling when using Eclipse 3.2. Make sure that the "Java Completions" and "Java Types" proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
'''Why do I get errors like "HTTP Response Code 407" or "Proxy Authentication Error" when accessing repositories through a proxy server?'''<br />
<br />
It is likely that you need to configure these proxy server settings. Select ''Window -> Preferences -> Install/Update'', and update the section in the "Proxy settings" section of the form.<br />
<br />
'''I can't use <code>Ctrl+Alt+Shift+Arrow Up</code> for'' Mark as Landmark''. What do I do?<br />
<br />
This is usually a Linux/GNOME problem, where the Gnome keyboard shortcuts are interfering with the Eclipse shortcuts. Go to the Keyboard shortcuts (which might be something like ''Desktop -> Control Centre -> Keyboard Shortcuts'' or ''System -> Preferences -> Keyboard Shortcuts'') and disable both of these shortcuts:<br />
* Move one workspace up<br />
* Move one workspace down<br />
<br />
See also: [[Mylyn_User_Guide#Keyboard_mappings_on_Linux| keyboard mappings on Linux]].<br />
<br />
'''How do I turn on spell checking?'''<br />
<br />
See [[Mylyn_User_Guide#Spell_Checking| spell checking]].<br />
<br />
== Uninstall troubleshooting ==<br />
<br />
When '''uninstalling in Eclipse''' Mylyn via the ''Help -> Software Updates -> Manage Configuration'' dialog you will need to uninstall dependencies first (e.g. Bugzilla Connector, Subclipse integration) and then uninstall the core Mylyn features.<br />
<br />
When '''uninstalling manually''' by deleting all of the Mylyn plug-ins and features from the <code>eclipse/plugins</code> and <code>eclipse/features</code> directory make sure to delete all of the plug-ins and then restart Eclipse with the -clean option (e.g. by inserting it into a shortcut or the <code>eclipse.ini</code> file.<br />
<br />
On '''Eclipse 3.1:''' you may need to reset the Java editor to be default for <code>.java</code> again via: ''Preferences -> General -> Editors -> File Associations''<br />
<br />
On '''Eclipse 3.2:''' if after uninstalling '''content assist proposals no longer appear''' you need to ensure that the ''Java Completions'' and ''Java Types'' proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
== I am seeing <code>java.lang.OutOfMemoryError: PermGen space </code>errors, what's wrong? ==<br />
<br />
If your Eclipse crashes, or you see the above error after installing Mylyn or other plug-ins, you have most likely hit the infamous MaxPermSize bug. This is not a Mylyn specific problem, but a general Eclipse problem that is often triggered on Eclipse 3.2 and later, if you have many plug-ins installed and are using a Sun JVM. <br />
<br />
To fix it simply add the following to your launch arguments. This is usually to your shortcut, or to the <tt>eclipse/configuration/config.ini</tt> file:<br />
<br />
-XX:MaxPermSize=128M<br />
<br />
If you are using a large number of plug-ins (e.g. WTP) you may need to increase the number to more than 128M. <br />
<br />
Details of the problem are on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250 Platform bug 92250].<br />
<br />
= Task List =<br />
<br />
== Why won't the Archive category disappear? ==<br />
<br />
The ''Archive'' category will automatically appear if a task needs to be shown, but is not in any query or category. <br />
In order to ensure that you do not miss reminders or notifications the following tasks will always be shown in the Task List, even if they have been removed from a category or a query:<br />
* Tasks scheduled for this week or overdue. Remove these by using the ''Schedule'' pop-up menu option to defer them to a future week or to clear the schedule.<br />
* Repository tasks that have incoming changes, such as comments. Remove these by reading them or marking them as "read" via the ''Mark -> Read'' pop-up menu.<br />
<br />
== The Archive category contains many irrelevant tasks, how do I clean it up? ==<br />
<br />
If you created very broad queries you could end up with thousands of tasks in the Archive category. Other than clearing the <tt>workspace/.metadata/.mylyn/tasklist.xml.zip</tt> and <code>workspace/.metadata/.mylyn/offline</code> folder (note that this will entirely reset your Task List) the easiest option is to:<br />
* Clean up your queries to include only tasks of interest (note that including completed/resolved tasks is recommended).<br />
* Turn off ''Focus on Workweek'' in the ''Task List''.<br />
* Turn off the ''Filter Archive Category'' option in the ''Task List'' view menu.<br />
* Delete all of the unneeded tasks from within the Archive category. Note that if the tasks are not matched by queries they will be deleted permanently and any local notes or scheduling information that you have added to them will be lost.<br />
<br />
== How does Mylyn count the active time for a task? ==<br />
<br />
Whenever you work on a task, Mylyn accumulates the time you spend actively working on a task. This time can be viewed in the ''Personal Planning'' section of the ''Task Editor''. When you are not interacting with Eclipse, the timing automatically times out after 3 minutes by default. This means that activity outside of Eclipse will not be captured when you work on the task and that the timings in Mylyn are a lower bound of the total time spent on the task (capturing timings for work done outside of Eclipse involves OS specific extensions).<br />
<br />
== How do I prevent long-running tasks from adding to the progress bar? ==<br />
<br />
If you have many long-running or recurring tasks scheduled for this week, they can affect the ''Task List'' weekly progress bar. This can be misleading as they may never be completed. The current work-around to prevent long-running tasks from being included in the weekly progress bar is to schedule their estimated time to be 0 (zero). Alternatively, you can schedule only the amount of time you plan on spending on that task this week.<br />
<br />
== Does the Task List replace the Eclipse Tasks view? ==<br />
<br />
The SDK's ''Tasks'' view is used for showing markers such as 'todo' tags which indicate a local problem with a resource, similar to a compiler warning. As such, these 'tasks' are at a much lower level of granularity than Mylyn's tasks, and one task could involve cleaning up multiple todos. In order to make working with only the markers in a particular task context, e.g. for clean-up before committing, the ''Apply Mylyn'' filter is available for both the ''Problems'' and the ''Tasks'' views.<br />
<br />
== What if I use multiple workspaces? ==<br />
<br />
Mylyn's support for multiple workspaces is currently limited (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130658 bug 130658] for a discussion) because the Task List is considered to be specific to the person, and not to the workspace. We recommend configuring your Eclipse workspace to use working sets instead of relying on multiple workspaces. <br />
* John O'Shea's blog: [http://www.xlml.com/aehso/2007/02/02/eclipse-workspaces-containing-projects-with-overlapping-locations-and-mylar/ Eclipse workspaces containing projects with overlapping locations, and Mylar]<br />
<br />
If using a single workspace is not possible you can do the following:<br />
* In ''Preferences -> Mylyn -> Task List'' set the ''Data Directory'' to be a shared location, and do this for both workspaces.<br />
* Be sure to avoid launching both Eclipse workspaces at the same time, as changes in one workspaces could overwrite the Task List in the other workspace.<br />
* If you upgrade Eclipse or move your workspace and don't see your tasks, check the ''Data Directory'' setting.<br />
<br />
== How do I export my task and repository data? ==<br />
<br />
Export via File > Export > Mylyn > Task Data<br />
<br />
== Why does Mylyn use the term "task"? ==<br />
<br />
There are many work items that make up the developer's workday. Many issue trackers and project management tools refer to these as: bugs, defects, actions, tickets, stories, enhancements, and the list goes on. We refer to all such work items as "tasks" because the word tasks is short and commonly used in time management tools. Task Repository connectors can customize the presentation of tasks, for example, indicating which is a defect and which is an action item.<br />
<br />
= Task Editor =<br />
<br />
== Why am I seeing strange boxes where I expect to see proper characters? ==<br />
<br />
If for example you aren't seeing the proper single quote chacters in the summary of [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=197644 bug#197644]], check that the encoding is set correctly for the repository in the asociated Task Repositories view (Properties > Additional Settings > Character Encoding). For bugs.eclipse.org/bugs set your charcter encoding to ''ISO-8859-1''.<br />
<br />
= Task Repositories =<br />
<br />
== What if Mylyn doesn't support my task/bug/issue/ticket repository? ==<br />
<br />
To see support for your repository faster, do a search of the open repository connector requests and [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Bconnector%5D&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=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= vote for the corresponding bug] if your tracker is there, or [http://www.eclipse.org/mylar/bugs.php create a new bug]. <br />
<br />
[[Mylyn_User_Guide#Generic_Web_Repository_Connector|Generic Repository Connector]], allows creating Queries to the web-based issue tracking repositories and get list of issues from the web UI into the Task List.<br />
<br />
It is also possible to link a ''local task'' with the web page in web-based repository via the Mylyn Web integration.<br />
<br />
'''To create a task from any web-based repository:'''<br />
<br />
* Drag the URL from the address bar of the browser, or from a hyperlink in a bug listing to the ''Mylyn Tasks'' view. This will create a task for the bug, link it to the page, and populate the description with the title of the corresponding page. '''In Mozilla:''' simply drag the URL. '''In Internet Explorer:''' you must have <code>Ctrl</code> pressed in order for Eclipse to recognize the drop.<br />
* '''Alternatively,''' you can copy the URL, press the ''New Task'' button on the ''Mylyn Tasks'' view. This has the same effect as above but you can edit the description after retrieving it.<br />
* Opening the task will now open the corresponding issue. You can also <code>right+click</code> the task and select ''Open in External Browser''.<br />
<br />
[[Image:mylar-tasklist-weblink-editor.gif]]<br />
<br />
== Why were my repository credentials reset? ==<br />
<br />
If you upgrade Eclipse or your Java VM, you will need to reset your credentials in the ''Task Repositories'' view because these are stored in the secure Eclipse workbench keyring. Also see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=149607 bug 149607]. If you are migrating '''from Eclipse 3.2 to 3.3''' note that you will need to use a different update site, which is listed here: http://eclipse.org/mylyn/dl.php<br />
<br />
== Why are my updated repository attributes not showing up? ==<br />
<br />
Your server's repository attributes can change frequently, for example, there can be a new "milestone" or "version" added to the Bugzilla repository with each release. When the ''Preferences -> Mylyn -> Task List -> Synchronization'' setting is enabled, every 10th synchronization will update the attributes from the repository. If you do not have this setting enabled, your can force the update via the ''Update Attributes'' action on the task repositories' context menu in the ''Task Repositories'' view. Note that you will need to reopen a task editor to see the updated attributes. If you instead update via the button on the ''Attributes'' section of the ''Task Editor'' the attribute settings will be reloaded without needing to reopen.<br />
<br />
== Authentication Troubleshooting ==<br />
<br />
You must ensure repository credentials are filled out correctly. Refer to the diagram below:<br />
<br />
[[image: AuthenticationTroubleshooting2.png|right]]<br />
<br />
# Enter the repository URL (i.e. https://bugs.eclipse.org/bugs) and an optional label<br />
# Credentials<br />
#* Usually email address and password <br />
#* Some sites, such as <code>dev.eclipse.org</code>, use anonymous logon with password left blank.<br />
#Http Authentication (optional)<br />
#* Some sites are protected by either BASIC or DIGEST http authentication. If this is the case, enter appropriate credentials here.<br />
#* One way to test if the site requires http authentication is to point your browser at the repository. If you are presented with an authentication dialog popup, the site is likely protected by http authentication.<br />
#Proxy Server Configuration (optional)<br />
#* By default Mylyn uses the Platform's Install/Update proxy settings. Uncheck this box if you wish to use an alternative proxy.<br />
#* If the proxy requires authentication, this is where you enable and enter your proxy credentials.<br />
#* If you are experiencing connection problems, ensure your Install/Update proxy settings are valid or the repository specific settings are correct<br />
#* Mylyn has been tested with HTTP proxy servers. Currently SOCKS is not supported.<br />
#Validate Settings <br />
#*Press the ''validate'' button to test the settings<br />
#*If you are seeing errors like "HTTP Response Code 407" or "Proxy Authentication Error" it is likely that you need to configure proxy settas as described above.<br />
#*If your sever uses a certificate and fails to connect, e.g. you see exceptions <tt>sun.security.validator.ValidatorException: PKIX path building failed</tt> then you need to point Eclipse at your certificate, see the [http://ahtik.com/blog/2006/05/11/fixing-eclipse-mylar-jira-integration/ instructions on this blog].<br />
<br clear="all" /><br />
<br />
=== NTLM authentication ===<br />
<br />
For NTLM authentication to work a special format for the username needs to be used where ''DOMAIN'' needs to be replaced by the Windows login domain: <br />
<br />
DOMAIN\username <br />
<br />
The built-in NTLM support of the JDK which is used by Eclipse does '''not work''' with Mylyn since it uses the HttpClient library to access repositories. Limitations in regard to NTLM authentication are documented in the [http://wiki.apache.org/jakarta-httpclient/FrequentlyAskedNTLMQuestions NTLM FAQ] and also discussion on {{bug|201911}}.<br />
<br />
* If your repository uses MS NTLM authentication and only standard http authentication is being passed to the repository this can result when the local hostname cannot be resolved. Ensure your machine's hostname is set correctly and resolves to a valid address.<br />
* It is not possible to use NTLM authentication for the proxy as well as for the repository.<br />
<br />
If NTLM authentication fails the '''[http://ntlmaps.sourceforge.net/ NTLM Authorization Proxy Server]''' has been reported to '''work''' with Mylyn.<br />
<br />
== Why are task hyperlinks not working? ==<br />
<br />
For task hyperlinks in textual editors (e.g. Java editor) and other text viewers (e.g. History view comments) you must associate the project that contains the resource to the task repository. <br />
<br />
:''Project association can also come from 3rd party metadata trough the contrubuted [[Mylar_Integrator_Reference#Mapping_from_projects_to_Task_Repositories|extension point]]. [http://subclipse.tigris.org/ Subclipse] and [http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Mylyn Maven integration for Eclipse] plugins contributing it. See few more details [http://jroller.com/page/eu?entry=linking_projects_from_the_eclipse here].''<br />
<br />
Note that to view a hyperlink you must hold down the <code>Ctrl</code> key when hovering over the reference to the task. References to tasks are connector specific and the common reference is found on the top left of the task editor and other conventions tend to follow those used in the web UI (e.g. "bug 123" for Bugzilla, "ABC-123" for JIRA).<br />
<br />
[[Image:mylyn-project-repository-association.gif]]<br />
<br />
= Bugzilla Connector =<br />
<br />
== What versions are supported? ==<br />
<br />
We recommend using the latest [http://www.bugzilla.org/download/ release] of Bugzilla.<br />
<br />
* '''Bugzilla 2.18.6 is the lowest version of Bugzilla supported'''. If you are getting errors that indicate failure to update attributes this may be an indication that the Bugzilla server is not supported (< 2.18.6).<br />
<br />
*If you are using '''Bugzilla 2.18''' and are getting '''mid-air collisions''' this is likely due to incorrectly formatted timestamp field in the underlying bugs database table ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149513 bug 149513]). This can be resolved by upgrading to Bugzilla 2.20 or later.<br />
<br />
== Why are queries failing? ==<br />
<br />
*If '''queries are not working''' correctly ensure that you have the right Bugzilla server version selected for the corresponding repository: ''Task Repositories (View) ->'' right+click the repository ''-> Properties''. For supported versions see the [http://www.eclipse.org/mylar/dl.php download page]. If the repository is still not functioning it may be due to authentication or connectivity problems. If that does not resolve the problem please post a message to the newsgroup or [http://www.eclipse.org/mylar/bugs.php submit a bug].<br />
<br />
== Why do I see my old username? ==<br />
<br />
If you change the username/email address on your Bugzilla account you may notice that some tasks still have the old username/email. Explicitly synchronize the task via the ''Task List'' popup menu or ''Task Editor'' toobar in order to update your username.<br />
<br />
== Why do tasks fail to open? ==<br />
<br />
*If upon opening a bug, the Bugzilla tab only displays a warning "'''Could not download task data, possibly due to timeout or connectivity problem. Please check connection and try again.'''", ensure that your repository is returning XML data by pointing your browser to <code><your-repository-url>/show_bug.cgi?id=1&ctype=xml</code> to show the contents of bug 1 in XML form. The Bugzilla client requires that bugs be accessible in XML form. If the repository doesn't support xml then it is likely that the repository is too old (Mylyn currently supports Bugzilla 2.18 and later).<br />
<br />
* If '''reports fail to load''' or '''reports fail to synchronize''' (task description remains ''italic''), check the error log for a "'''File not found'''" error pointing to <code>bugzilla.dtd</code> or a "'''Failed to retrieve products from server'''" error message - these result when the <code>urlbase</code> parameter is not set on the bugzilla server, or your bugzilla installation is missing the <code>bugzilla.dtd</code> file. See: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=161759 bug#161759]<br />
<br />
* If '''attributes are missing options''' in the bug editor (ie. missing a recently added milestone, [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155431 bug# 155431]):<br />
** Update attributes by choosing ''Update Attributes'' from the context menu in the ''Task Repositories'' view<br />
** Synchronize the task in the Task List<br />
** Reopen the task - new options should be available.<br />
<br />
== Why do tasks fail to submit? ==<br />
<br />
* '''Error upon submit: unable to make any match for name/email entered.''' If your bugzilla is configured for user names rather than full email address the QA Contact field will cause the submit to fail ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=166555 bug# 166555]). To resolve, select 'Local users enabled' option on the Repository Configuration page. <br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your account's username and password and are not using the HTTP authentication fields instead.<br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your bugzilla instance's cookie domain under the required settings. The cookie domain must lead with a dot.<br />
<br />
* If '''attachments are failing to submit''' and you see that after processing the attachment, the bugzilla bug shows a size of "bytes" (no numbers), your database may be dropping the packet sending the file. '''On MySQL''', check the [http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html max_allowed_packet directive]. You may see errors like: <code>DBD::mysql::st execute</code> failed: Got a packet bigger than 'max_allowed_packet' bytes [for Statement "INSERT INTO attach_data (id, thedata) VALUES (38, ?)"] at <code>/path/to/bugzilla/attachment.cgi</code> line 993. Also, '''check the maximum attachment size''' in ''Bugzilla Parameters -> Attachments''.<br />
<br />
* If a submit fails with an '''Invalid Username or Password''' error even though repository settings do validate, make sure that cookies could be set. See also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175502 bug 175502]<br />
<br />
== What time zone is used in the task editor? ==<br />
<br />
*The '''times''' that appear in the Bugzilla bug editor (ie. created, modified) '''are local to the server hosting the Bugzilla repository''', not your local machine's time zone. <br />
<br />
== Known limitations ==<br />
<br />
* The <code>usermatchmode</code> is not currently supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168204 bug 168204]) and as such full email addresses need to be used.<br />
<br />
* The <code>usevisibilitygroups</code> parameter is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=180876 bug#180876]). Group assignment will currently be lost if updated using the Bugzilla rich task editor.<br />
<br />
* Version 1.0 of Mylyn presents an error message upon new comment submission to RedHat's public Bugzilla repository. The comment is in fact posted. This issue is resolved in Mylyn 2.0M2 and higher. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=183251 bug#183251])<br />
<br />
= JIRA Connector =<br />
<br />
If you see errors like the following, work around this by opening repository ''Properties Page'' and clicking OK (bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169102 169102]).<br />
<br />
org.tigris.jira.core.service.exceptions.AuthenticationException<br />
at org.tigris.jira.internal.core.service.soap.SoapJiraService.getProjectsNoSchemes(SoapJiraService.java:204)<br />
<br />
== What are the server requirements? ==<br />
<br />
The '''JIRA SOAP/RPC services have to be running on the JIRA server''':<br />
<br />
* Jira 3.3.3 or higher (3.7 or higher for attachment retrieval)<br />
* Jira RPC plugin 1.4.3 or higher<br />
<br />
Latest information also available on the [http://www.eclipse.org/mylar/dl.php download page].<br />
<br />
Related Resources:<br />
<br />
* [http://confluence.atlassian.com/display/JIRA/JIRA+Development+Hub Jira Development Wiki]<br />
* [http://confluence.atlassian.com/pages/viewpage.action?pageId=1035 Jira RPC Plugin Overview]<br />
<br />
== Why can't I connect? ==<br />
<br />
* If you get a <code>org.tigris.jira.core.service.exceptions.ServiceUnavailableException</code> you need to turn on the JIRA SOAP/RPC services on the server.<br />
* Similarly, if you get a "Processing instructions are not allowed within SOAP messages" message, ensure that SOAP/RPC services are on.<br />
* If you get a '''503''' error code verify that the SOAP/RPC interface is enabled.<br />
* If you get a '''403''' error code verify that the SOAP/RPC interface is enabled, and also check your authentication mechanism. If the server is using NTLM authentication, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156397 bug 156937] for diagnosis steps.<br />
* If you see an '''"unrecognized priority" message''' in the ''Error Log'', the problem is that the JIRA Connector does not support customized priorities so the priority value specified in that message will not correspond to the priority icons visible in the Task List.<br />
* If you are being '''prompted for your log-in credentials''' by the Browser tab of the task editor or the new task editor, this is because without rich editor support the connector is using the web-based UI instead of logging in on your behalf as is done with a rich task editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142869 bug 142869]).<br />
* If you get a <CODE>AuthenticationException</code> and a query won't synchronize, use Task Repositories (view) -> Properties (on the repository) -> Validate Settings. This will clear the connection if it died.<br />
<br />
<!-- HEAVILY OUTDATED. PLUGIN NOW USES COMMON PROXY INFRASTRUCTURE<br />
== Why can't I synchronize when using a proxy server? ==<br />
<br />
* Proxy configuration is '''based on the normal Java HTTP system properties''', which can be configured either by launching Eclipse with <code>-vmargs</code> and using the following settings, or by putting these settings into the or by putting the following into the <code>eclipse/eclipse.ini</code> file (after -vmags):<br />
-Dhttp.proxyHost=<host> <br />
-Dhttp.proxyPort=<port><br />
* Make sure that when using these settings you do not enable the proxy settings on the ''Install/Update'' preference page, since they may override these settings.<br />
* If you are using '''SSL''', you will also need to set the <code>https.proxyHost</code> and <code>https.proxyPort</code>. <br />
* Authentication is configured with the <code>http.proxyUser</code> and <code>http.proxyPassword</code> system properties (also for SSL)<br />
* You can also use <code>http.nonProxyHosts</code> system property to enumerate hosts that should not be proxied. Note that matching is implemented on the exact host name used for JIRA server and patterns are not supported. --><br />
<br />
== Known limitations ==<br />
* Attachment retrieval (including retrieval of the task context and attachment list in the task editor) require JIRA 3.7 or above ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=169757 bug 169757])<br />
<!-- * NTLM authentication is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172395 bug 172395]) --><br />
* Customized priorities are not currently supported, so all issues with a customized priority will have the default priority level ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=165518 bug 165518]).<br />
* blank but editable custom fields doesn't appear in the RSS data, and as result we can't show them for editing<br />
* because of JIRA api limitations, we can support custom fields in the task editor, but not in the new custom task editor<br />
<!-- * On JIRA 3.6.x private filters saved on the server can fail to retrieve results ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=174328 bug 174328]). The work-around is to create a custom query in Mylyn using the form-based query designer or to share the filter in JIRA. --><br />
* Mylyn only allows the usage of US-ASCII characters in the filename when uploading an attachment ({{bug|203663}})<br />
<br />
== How can I enable compression for SOAP messages? ==<br />
<br />
If your repository has lots of projects and components you can speed up the download of the repository configuration by enabling compression. <br />
<br />
* Add a filter-mapping to your JIRA server configuration: [http://jira.atlassian.com/browse/JRA-10353].<br />
* Enable compression in your global JIRA configuration.<br />
* Check the compression setting for your task repository in Mylyn versions 2.0M2 and later.<br />
<br />
== Reporting issues ==<br />
<br />
Since JIRA can be heavily customized there is a chance that some particular customizations may not work, so if you can't connect to your proprietary repository it is a good idea to try the following public repositories to make sure you have working configuration:<br />
<br />
* http://jira.codehaus.org<br />
* http://issues.apache.org/jira/<br />
* http://opensource.atlassian.com/projects/spring <br />
<br />
If you can't get query results, you could try to call "Open with Browser" on query node in the Task List view and then save link "Current view: XML" and attach it to the bug report.<br />
<br />
Even if query don't work you could try "Open Repository Task" from your JIRA repository node on the Task Repositories view and check if you can open JIRA task editor for that issue. Same for the Task search (Ctrl-H, Task Search)<br />
<br />
To investigate various error you may need to enable debug tracing. To do that you need to create the <code>.options</code> file with the following content:<br />
<br />
<pre><br />
org.eclipse.mylyn.jira.ui/connector=true<br />
org.eclipse.mylyn.jira.ui/dataHandler=true<br />
</pre><br />
<br />
and then add the following options to the Eclipse command line (or eclipse.ini file):<br />
<br />
<pre><br />
-debug <path to the .options file>/.options<br />
</pre><br />
<br />
The additional logging will go into the regular Eclipse log and the Error Log view<br />
<br />
== Why do I get errors about an unexpected redirect when submitting an issue? ==<br />
<br />
Please go to the repository properties and validate the repository. If errors about circular redirects are logged in your Eclipse error log your JIRA server or proxy might be misconfigured. <br />
<br />
In some cases unexpected redirects can be caused by a JIRA server accessed via Apache and mod_jk (using the AJP/1.3 Tomcat connector). Some server configurations may benefit from the 'proxyHost', 'proxyPort', 'scheme' and 'secure' settings on the AJP Connector in the Tomcat server configuration.<br />
<br />
Please see {{bug|202834}} for a more details.<br />
<br />
= Trac Connector =<br />
<br />
== What are the server requirements? ==<br />
<br />
The Trac connector offers two access methods:<br />
<br />
'''XML-RPC''' (recommended)<br />
<br />
Requirements:<br />
* Trac 0.10<br />
* [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] rev. 1950<br />
<br />
This access method offers editing of tasks in a rich editor, attachment support and offline editing. It requires the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] for Trac to be enabled for the accessed repository. The XmlRpcPlugin provides a remote interface to the Trac repository and is distributed separately from Trac (see [http://trac.edgewall.org/ticket/217 #217]). See these [http://trac-hacks.org/wiki/XmlRpcPlugin#Installation install instructions] for requirements and documentation.<br />
<br />
'''Web''' <br />
<br />
Requirements:<br />
* Trac 0.9 or later<br />
<br />
In this mode the standard Trac web interface is used for repository access. Tickets may be created and edited through a web browser. Offline editing and attachments are not supported.<br />
<br />
== Recommended Trac version ==<br />
<br />
Mylyn should work with any stable release Trac release that is version 0.9.x or 0.10.x (see below for known limitations). Mylyn works best when used with Trac's XML-RPC Plugin (see above) but we do not recommend a particular Trac version. <br />
<br />
The Trac connector tests are run against these Trac versions:<br />
<br />
* Trac 0.10.4, XML-RPC Plugin rev. 1950<br />
* Trac 0.9.6<br />
<br />
See {{bug|175211}} for details about Trac 0.11 support.<br />
<br />
== Why do I get an HTTP Error 500 Internal server error when creating a ticket that contains non-ASCII characters? ==<br />
<br />
Problems related to character encodings have been reported when Trac is run with Python 2.3. Upgrading to Python 2.4 may help to resolve this. Please comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=188363 bug #188363] if you encounter an internal server error when creating a ticket that contains non-ASCII characters.<br />
<br />
== Known limitations ==<br />
<br />
* Trac 0.10.1 <br />
** Known incompatibility with Trac XML-RPC Plugin. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164272 bug 164272] for details.<br />
* Trac 0.10.3 <br />
** Known incompatibility with old versions of the Trac HttpAuthPlugin (fixed in revision 1890 or later). The plug-in enables basic auth for XML-RPC when Trac AccountManagerPlugin for form based authentication is used. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168413 bug 168413] for details.<br />
* Trac 0.11<br />
** Currently untested.<br />
** Known incompatibility with Trac XML-RPC Plugin See [http://trac-hacks.org/wiki/XmlRpcPlugin] for details.<br />
<br />
== Why are tasks opened in a web browser and not in the rich editor? ==<br />
<br />
Please make sure that the access type in the repository properties is set to XML-RPC. This requires Trac 0.10 and XML-RPC (see above).<br />
<br />
== Which URLs does Mylyn access in a Trac repository? ==<br />
<br />
XML-RPC:<br />
<br />
* The expected URL is either /xmlrpc or /login/xmlrpc (if login credentials are provided)<br />
<br />
Web:<br />
<br />
* Authentication: /login <br />
* Querying: /query?format=tab...<br />
* Synchronizing ticket details: /ticket/...<br />
* Getting repository configuration to populate query dialog: /query or /newticket<br />
<br />
The web mode relies on screen scraping and is likely to fail if the design<br />
(i.e. HTML output) of the Trac repository is heavily customized.<br />
<br />
= Generic Web Repository Connector =<br />
<br />
== Where can I find the web repository connector ==<br />
<br />
It is available from the extensions update page. Please see http://www.eclipse.org/mylyn/downloads/<br />
<br />
== Why can't I connect using one of the existing templates? ==<br />
<br />
<br />
The Web Repository Connector have a Preview option in Advanced Configuration section on the Query preferences. If you get an error or preview table does not show expected list of tasks you can use Query Pattern like (.+?)(\n) to see content of the retrieved page and compare it with the source of the web page for the same url loaded into the web browser.<br />
<br />
If that does not help then you could use the wget tool (on Windows it available as a standalone command line tool and also included with Cygwin).<br />
<br />
Run the following command:<br />
<br />
<pre>wget -v -d -o query.log -O query.html "http://your.query.url"</pre><br />
<br />
If repository require basic http auth, you'll need to use ''--http-user=USER'' and ''--http-password=PASS'' options.<br />
<br />
Then open file ''query.html'' in the web browser and check if it show list of issues you need to fetch from the web server. If it does have correct list, then there could be a problem with query pattern used for parsing. <br />
<br />
A popular mistake is an unmasked '?' that separates request parameters in the url). For example:<br />
<br />
<pre><a href="show_bug.cgi\?id\=(.+?)">.+?<span class="summary">(.+?)</span></pre><br />
<br />
If ''query.html'' does not show expected list of issues you can check ''query.log'' for server responses and try to identify if server require authentication, redirecting your requests somewhere or issue any other errors.<br />
<br />
== Known limitations ==<br />
<br />
* In Mylyn 1.0: if a web server responds by requesting a redirect to an absolute URL while fetching a resource, the connector falsely prepends "/" to the URL and the request will fail. The workaround is to use final url where redirect is pointing to (you can find it as describe above). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=167282 bug 167282] for details.<br />
<br />
= Task-Focused UI =<br />
<br />
== What is the Task-Focused UI? ==<br />
<br />
When you activate a task, Mylyn automatically maintains a task context by monitoring your interaction. The task context provides a predictable degree-of-interest weighting of the relevance of the elements and relations that you work with to the task-at-hand (as described in the [http://kerstens.org/mik/publications/2006-11-mylar-fse.pdf Foundations of Software Engineering conference paper]). The Task-Focuse UI is the mechanism by which Mylyn presents Mylyn the task-context model in order to reduce information overload and to automate the manaul management of UI elements like editors and change sets. Examples:<br />
* Filtering, decoration and expansion management in views<br />
* Automatic folding in editors<br />
* Ranking in content assist<br />
* Editor management<br />
* Perspective management<br />
* Change set management<br />
<br />
== Why do files disappear from Focused views when I close them? ==<br />
<br />
By default Mylyn automatically manages the set of open files to match the task context, so that you don't have to. This ensures that the editor list (viewable via mechanisms like Ctrl+E) corresponds to what you in views like the ''Package Explorer'' when they are in Focused mode. When you close a file manually, you express that it is uninteresting, and as such it will be removed from the task context. It will also disappear from the corresponding automatically managed change sets for the same reason. This behavior can be turned off via ''Preferences -> Mylyn -> Context -> Manage open editors to match task context''. However, it is highly recommended since Mylyn will prevent the number of editors from bloating by automatically closing editors for elements that have decayed in interest, and always keep the editors for interesting elements open.<br />
<br />
<br />
== Why did all my editor tabs disappear? ==<br />
<br />
When you deactivate a task, all editors will be closed, and then when you reactivate the task all the windows will be open again. Try it, it's fun. <br />
<br />
Mylyn actively manages your open editors with task context. It takes some getting used to, but enables switching between tasks when you are multitasking without cluttering your editor tabs. This editor management can be disabled via ''Window -> Preferences -> Mylyn -> Context''. However, before disabling it consider reading the ''"Managing open editors..."'' section of [http://www-128.ibm.com/developerworks/java/library/j-mylar2/index.html#N10116 Task-focused programming with Mylar].<br />
<br />
== How do I get rid of an element if it is not interesting? ==<br />
<br />
When a view is focused elements will disappear on their own if they are not repeatedly selected via a mechanism called interest decay. Note that decay does not use the wall clock, but instead relies on the number of selections that you have made when working on that task to determine which elements disappear. This helps make it feel very predictable.<br />
<br />
If you want want to force one or more elements to disappear from the context use the '''Remove from Focus''' action on the context menu. Note that the element will still be part of the task context since it was previously part of the interaction. <br />
<br />
If you want to permanently delete the element from the interaction history use the '''Remove from Context''' action on the '''Context''' tab of the '''Task Editor'''. For example, if a company private element was part of a task context that is to be shared with a public repository, this action can be used to clean it up before sharing. Note that elements will be removed from the task context recursively.<br />
<br />
== Which Focused UI features can I turn off? ==<br />
<br />
'''All of them.''' When no task is active neither are any of Mylyn's features. When working with task contexts Mylyn's Focused UI features are all optional and in general configurable. While many find it the key benefit of Mylyn, the entire Focused UI is optional and can be uninstalled via ''Help -> Software Updates -> Manage Configuration''.<br />
<br />
The following table summarizes how the key features can be toggled:<br />
<br />
<table><br />
<tr><br />
<td>'''UI Mechanism'''</td><br />
<td>'''Example/description'''</td><br />
<td>'''Toggle using'''</td><br />
</tr><br />
<tr><br />
<td>Interest filtering</td><br />
<td>Package Explorer</td><br />
<td>''Apply Mylyn'' button on view toolbar</td><br />
</tr><br />
<tr><br />
<td>Automatic toggling of filtering</td><br />
<td>Package Explorer</td><br />
<td>''Preferences -> Mylar -> Context -> Toggle focused mode..</td><br />
</tr><br />
<tr><br />
<td>Interest decoration</td><br />
<td>Bolding of landmark elements</td><br />
<td>''Preferences -&gt; General -&gt; Appearance -&gt; Label Decoration''</td><br />
</tr><br />
<tr><br />
<td>Content assist</td><br />
<td>Ranking of interesting elements</td><br />
<td>Eclipse 3.2: ''Java -&gt; Editor -&gt; Content Assist -&gt; Work in Progress -&gt;'' turn off Mylyn, turn on Java</td><br />
</tr><br />
<tr><br />
<td>Active change sets</td><br />
<td>Grouping of changes by tasks</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Team''</td><br />
</tr><br />
<tr><br />
<td>Editor management</td><br />
<td>Auto opening/closing of editors</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Editor Management''</td><br />
</tr><br />
<tr><br />
<td>Active views</td><br />
<td>Active Search and Hierarchy</td><br />
<td>Only on if view is active</td><br />
</tr><br />
</table><br />
<br />
For additional configuration options see the ''Mylyn'' and ''General -> Appearance'' preference pages.<br />
<br />
== What is the performance profile of the Focused UI? ==<br />
<br />
The goal is for Mylyn to have '''no noticeable effect''' on Eclipse's speed or memory usage.<br />
You do not need to increase the amount of memory Eclipse runs with to use Mylyn. <br />
Any performance issue should be [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Mylyn reported as a bug]. <br />
<br />
The current '''Performance Profile''' is:<br />
<br />
# Mylyn only runs if a task is active, and has no impact on Eclipse if no task is active.<br />
# Task context models have negligible memory overhead. <br />
# When a task is active, additional view refresh is required to update the views based on interest model changes. This should not be noticeable on Windows where refresh is very quick, but could be more noticeable on other platforms.<br />
# The time to activate a task context is dominated by the time it takes Eclipse to open the editors in the context. You can set the preference for how many editors to open in the Mylyn preference page (e.g. setting to 1 will dramatically reduce activation time, but also remove the benefit of having open editors correspond to the task context). You can also turn off editor management entirely in the Mylyn Tasks view pull-down.<br />
# Eclipse startup is slowed down by (4) if a task is active when Eclipse is shut down.<br />
# The low priority background searches that the Active Search view runs can be noticeable on slower machines.<br />
<br />
== What happened to the Active Search and Active Hierarchy views? ==<br />
<br />
These views were not included in the Mylyn 1.0 release because they never made it beyond the experimental phase. <br />
* The ''Active Search'' view has not been sufficiently tuned to adapt to the lifecycle of a task context, and as a result requires manual manipulation of the degree-of-separation scope as you work on long-running tasks. Otherwise it becomes overloaded with elements. In addition, it is not yet clear whether an additional view is the right UI for this facility, and it is hard to find room for an additional view of this size on screen resolutions of 1600x1200 and smaller.<br />
* The ''Active Hierarchy'' view is also hard to allocate space for, especially when using the in-place hierarchy (Ctrl+T) on a landmark can be a quick way to see the relevant part of the task context's hierarchy.<br />
<br />
These features still show promise in displaying task context and saving repetitive searches, so we have not removed them. They have instead moved to the Mylyn Sandbox, and can be used and experimented with by following the [http://wiki.eclipse.org/index.php/Mylyn_Contributor_Reference#Sandbox instructions on the Contributors page]. For feedback on these views please use the corresponding bug reports or newsgroup.<br />
<br />
= Java Development =<br />
<br />
== Content assist troubleshooting ==<br />
<br />
Mylyn uses custom Content Assist processors in order to rank and separate the elements in the current task context. To see proposals ranked according to interest you must have only the ''Type Proposals (Mylyn)'' kinds checkbox enabled in the list below, otherwise you will see duplicates. '''If you do not see any proposals, check this list''' to ensure that either the Mylyn or the plain proposals are enabled. '''To do this automatically''', run ''New -> Mylyn -> Recommended Preferences''. Or you can select them manually as in the preference page below. <br />
<br />
[[Image:mylar-content-assist-prefs.gif]]<br />
<br />
'''Why do I see duplicate proposals?'''<br />
<br />
Ensure that you have only the ''(Mylyn)'' proposals kinds enabled in ''Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced'', otherwise you will see duplicates.<br />
<br />
If you use proposals via Ctrl+Shift+Space instead of the typical Ctrl+Space you will see duplicates. Vote for JDT/Text [https://bugs.eclipse.org/bugs/show_bug.cgi?id=147781 bug 147781] if you use this mechanism. Also see: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=129080 bug 129080]<br />
<br />
'''Why do I get an error message when using content assist?'''<br />
<br />
If after invoking Content Assist you see an error message dialog that states:<br />
The extension took too long to return from the 'computeCompletionProposals()' operation<br />
this is most likely due to something interrupting the proposal operation (e.g. garbage collection). Ignore it if it does not recur, increase Eclipse's memory if it does (e.g via <code>-Xmx384M</code> command line argument). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=141457 bug 141457] for more details.<br />
<br />
== Why do interesting elements not show in the Project Explorer? ==<br />
<br />
The ''Package Presentation -> Hierarchical'' mode is not supported on the ''Project Explorer'' view in Eclipse 3.2 through 3.3M3 and possibly later versions (https://bugs.eclipse.org/bugs/show_bug.cgi?id=161362 bug 161362). Use the view menu to set ''Package Presentation -> Flat'' as a work-around.<br />
<br />
== How do I stop declarations from showing in the Package Explorer? ==<br />
<br />
If you don't like Mylyn's constant showing of Java members in the ''Package Explorer'', select the drop-down menu, then ''Filters...'' and enable the ''Mylyn Java Declarations Filter''. It will then stick in the menu in case you want to toggle between modes. Note that this will hide interest information about members that aren't in your current file (e.g. showing you which methods are landmarks) so this mode is not recommended, but can be useful for <code>1024x768</code> screen resolutions.<br />
<br />
[[Image:mylar-java-filtering-declarations.gif]]<br />
<br />
== Why does nothing show up in the Active Search or Active Hierarchy? ==<br />
<br />
As you work, elements become Landmarks (bold decoration), and these elements populate the ''Active Search'' and ''Active Hierarchy'' views. To force an element to populate the views manually, make it a Landmark by <code>right+clicking</code> or hitting <code>Ctrl+Alt+Shift+UpArrow</code>.<br />
<br />
== Known limitations ==<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=106678 Bug 106678]: The Project Explorer's Hierarchical Java package presentation layout is not supported on Eclipse 3.3Mx, and interesting elements will be hidden if enabled. Work-around is to use the default Flat package presentation.<br />
<br />
= Team Support =<br />
<br />
== Why does task change set not appear when I modify files? ==<br />
<br />
A task change set should appear if you activate a task and modify a file connected to a compatible source repository (e.g. CVS, SVN). If it does not try the following:<br />
<br />
* Ensure you have installed the [http://www.eclipse.org/mylyn/downloads/ ''Mylyn Bridge: Eclipse SDK'' feature]. Note that this feature is not currently distributed with the Java-only Eclipse download ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191793 bug 191793] ).<br />
<br />
* Verify that the [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuring_the_Synchronize_view_for_change_sets configured ''Synchronize View'' is configured for change sets].<br />
<br />
If the above are working but the change set appears to be missing relevant files:<br />
<br />
* You may be seeing the ''Synchronize'' view's refresh problem ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142395 bug 142395]). Toggle from ''Incoming/Ougtoing'' to ''Incoming'' mode and back again to refresh the view.<br />
<br />
* If the files or change set are still missing deactivate and reactivate the task to force a full refresh.<br />
<br />
== Why do files disappear from the change set when I close them? ==<br />
<br />
If you have the ''Preferences -> Mylyn -> Context -> Manage open editors to match task context'' option enabled, Mylyn will perform editor management so that you don't have to. Closing a file makes it less interesting, and causes it to disappear from the active task context, and hence from the change set. This option prevents you from having to manage the set of open files, will automatically close editors for files that become uninteresting, and will ensure that the open editors match the task context.<br />
<br />
== Why am I missing elements when I retrieve someone else's context? ==<br />
<br />
To identify elements within a project, Mylyn relies on the name of the project being consistent across workspaces. If the project name in the workspace that the context was created with is different than its name in your workspace, the task context will not show elements within that project ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164058 bug 164058]). The other case where context can be lost is if the elements change names outside of the workspace ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164243 bug 164243]).<br />
<br />
The work-around is to use the same project names across your team's workspaces. We recommend the following two approaches for standardizing on project names:<br />
* Use '''Team Project Sets''': these are a very useful Eclipse facility that allows your entire team to check out numerous projects from version control by importing a single file. Create a project set via ''File -> Export -> Team Project Set'', host this file somewhere accessible, then have others import vai ''File -> Import -> Team Project Set''.<br />
* Have developers check out projects into their workspace without renaming them. The above is a shortcut for doing this. If alphabetical sort order in the ''Package Explorer'' is a problem, organize your projects via ''Project Explorer -> view menu -> Top Level Elements -> Working Sets''.<br />
<br />
= Misc =<br />
<br />
<br />
<br />
== How does Mylyn relate to IBM's Jazz? ==<br />
<br />
At the EclipseCon and JavaONE 2006 conferences IBM demonstrated previews of Jazz, a collaborative team server and Eclipse-based client. Articles have remarked on the similarities between Mylyn and Jazz because both integrate tasks into Eclipse (Jazz's "work items" and Mylyn's "tasks"), and both provide change sets grouped by task. But there are both significant differences and complementary aspects to the two approaches. A key goal of Mylyn is to provide an open source framework to support integration of task management with ''existing issue trackers and source repositories''. According to the presentations, components that come with Jazz include include a ''next-generation issue tracker and source repository'' and related lifecycle management tools such as project health. In addition, a driving and unique goal of Mylyn is to focus the UI around a usage-based and degree-of-interested weighted task context, which is complementary to the Jazz platform. Just as it integrates with Mylyn's Task List, Mylyn's Task Focused UI and task context model components are possible to integrate with other kinds of task management systems, such as the one provided by Jazz.<br />
<br />
Update: at EclipseCon 2007 the IBM Jazz team showed a Mylyn connector for Jazz.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/FAQ&diff=51157Mylyn/FAQ2007-09-19T20:03:39Z<p>Steffen.pingel.eclipse.org: /* Known limitations */</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
[[Mylyn User Guide]], <br />
[http://eclipse.org/mylyn Mylyn Home],<br />
[http://wiki.eclipse.org/index.php?title=Special:Userlogin&returnto=Special:Userlogout Log in to edit]<br />
<br />
For instructions on [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Download_Mylar downloading] [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installation installing] and [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuration configuring] <br />
Mylyn, see the [[Mylyn User Guide]]. For instructions on developing and contributing to Mylyn, see the [[Mylyn Contributor Reference]].<br />
<br />
= Installation =<br />
<br />
== What versions of Eclipse are supported? ==<br />
<br />
See the [http://eclipse.org/mylyn/dl.php download page].<br />
<br />
Mylyn also relies on a web browser that works with the Standard Widget Toolkit; Windows and MacOS users are fine, but Linux users might have to download another browser. See [http://www.eclipse.org/swt/faq.php#browserlinux the SWT Browser guide] for which browsers will work. See [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux installing browser on Linux] for installation instructions.<br />
<br />
== What version of Java is required? ==<br />
<br />
Mylyn needs the '''Java 5''' virtual machine.<br />
<br />
To check the version of the Java virtual machine that Eclipse was launched with to to ''Help -> About Eclipse SDK -> Configuration Details'' and verify that the java.vm.version is 1.5. <br />
<br />
Mac users should refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
* If you do not have Java 5, you can download it from [http://72.5.124.55/javase/downloads/index.jsp Sun's web site]. <br />
* If you have more than one VM, you need to specify that Eclipse should use the JDK1.5 VM. <br />
<br />
In Unix, set the environment variable <code>JAVA_HOME</code> to the root of the JDK1.5 installation and/or set the <code>PATH</code> variable to put the JDK1.5 executable directory before any other VM executable directories. For example, under <code>bash</code> in Unix:<br />
export JAVA_HOME="''(location of JDK1.5 root)''"<br />
export PATH=$JAVA_HOME/bin:$PATH<br />
<br />
<b>We do [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140955 not recommend] using JDK 1.6 on Eclipse 3.1.</b> (It works fine with Eclipse 3.2 or 3.3.) To use JDK 1.6 on Eclipse 3.1, you must add the following line to your <code>config.ini</code>file:<br />
<code><br />
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,<br />
J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6<br />
</code><br />
<br />
== What version of Mylyn is distributed with the Eclipse downloads? ==<br />
<br />
The [http://www.eclipse.org/downloads/ default Eclipse downloads] contain the following Mylyn redistributions. Since the redistributed versions can be missing important bug fixes or feature additions, we recommend using the [http://www.eclipse.org/mylyn/downloads latest version of Mylyn].<br />
<br />
* Eclipse IDE for Java Developers: all of Mylyn except Team integration (e.g. automatic change sets) integration. Install the Eclipse CVS integration and then install the latest Mylyn build to get this component.<br />
<br />
* Eclipse IDE for Java EE Developers: all of Mylyn redistribution, install manually<br />
<br />
* Eclipse IDE for C/C++ Developers: no Mylyn redistribution, install manually<br />
<br />
* Eclipse for RCP/Plug-in Developers: all of Mylyn redistributed<br />
<br />
* Eclipse Classic: no Mylyn redistribution, install manually<br />
<br />
== My tasks or queries disappeared, what do I do? ==<br />
<br />
This happens if Mylyn failed to install. First ensure that you have a correct install by following the instructions in the next section. After that, if you still do not see your tasks use the ''Task List'' view menu -> ''Restore Tasks From History...'' command (also available via ''File -> Import -> Task List''.<br />
<br />
== Installation Troubleshooting ==<br />
<br />
''' Java Persistence API Tools error when updating the JEE Eclipse Package '''<br />
<br />
If you are trying to install additional features and get this error you have hit [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194959 bug 194959] which should be resolved soon. The work-around is to check off the ''Europa Discovery Site'' and install the first two components of the ''Data Tools Platform''.<br />
<br />
''' Update failures '''<br />
<br />
On Eclipse versions earlier than 3.3 (final) use '''only the "Search for new features.."''' option when updating Mylyn. If you use "Search for updates..." the Update Manager will allow a partial install that can cause Mylyn to fail to start, and you will need to run update again. See the ''feature configuration problem'' section below for details. If you encounter this problemm consider voting for Platform [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132450 bug 132450].<br />
<br />
''' Startup exceptions '''<br />
<br />
If you see startup errors or warnings such as <code>BundleException</code> or timeout messages restart Eclipse with the <code>-clean</code> flag either on the command line, in your shortcut link, or by temporarily it into the <code>eclipse/eclipse.ini</code> file. If that does not resolve the problem please [http://www.eclipse.org/mylar/bugs.php file a bug].<br />
<br />
''' Incompatible VM (e.g. JDK 1.4) '''<br />
<br />
If you are using the wrong VM, you'll see errors like the following in your log file. <br />
<code><br />
Root exception: java.lang.UnsupportedClassVersionError:<br />
org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)<br />
</code><br />
<br />
See [[#Download_and_configure_Java_5_or_6|Configure Java]] to fix this problem.<br />
<br />
''' Incompatible version of Eclipse '''<br />
<br />
Separate versions and update sites exist [http://eclipse.org/mylyn/dl.php for Eclipse 3.1 and 3.2]), in which case you may see errors like the following in your <code><workspace>/.metadata/.log </code>file or in a Mylyn view:<br />
<code><br />
java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()<br />
The activator org.eclipse.mylar.java.MylarJavaPlugin for bundle org.eclipse.mylar.java is invalid<br />
</code><br />
<br />
''' Mylyn feature configuration problem '''<br />
<br />
If the above do not address the issue, the easiest thing to do is uninstall any old versions and update to the latest Mylyn. Your tasks won't be lost, because by default they are stored in the <code><workspace>/.metadata/.mylyn</code> folder which will be read next time Mylyn starts correctly. <br />
* First, uninstall the old version of Mylyn using ''Help -> Software Updates -> Manage Configuration''. <br />
* You need to Disable all Mylyn features by right-clicking them.<br />
* Allow Eclipse to restart after the last is disabled.<br />
* After restart, ensure that the 3rd toolbar button is pressed (figure below) so that you see the disabled features to uninstall.<br />
* Uninstall all the disabled features using the popup menu. <br />
<br />
If you don't uninstall, the the Update Manager will think that you have the latest and tell you that there are no updates. <br />
<br />
<b>Note: manually removing the plug-ins and features can lead to configuration errors.</b> <br />
<br />
After uninstalling, update Eclipse by adding the correct update site specified at on the [http://eclipse.org/mylar/dl.php download page], and after that automatically or manually updating will install the correct version.<br />
<br />
[[Image:mylar-eclipse-manage-configuration.gif]]<br />
<br />
'''What do I need to do in installation to be able to use Mylyn task management features with bug/task/issue trackers?'''<br />
<br />
When you install, make sure that you select a connector for your bug/task/issue tracking software. For example, to use Bugzilla, you have to install the Bugzilla connector component.<br />
<br />
'''I've installed Mylyn ; why can't I see anything different?'''<br />
<br />
The two most likely possibilities are:<br />
# You don't have any Mylyn views open. Select ''Window -> Show View -> Other'', then select ''Mylyn'' and you should see the available Mylyn Views. <br />
# If you still don't see anything, then perhaps you aren't using the JDK1.5 VM (or later). See [[Mylyn_Installation_Guide#Download_and_configure_Java|configuring Java]].<br />
<br />
<br />
'''What does the error "Network connection problems encountered during search" mean?'''<br />
<br />
If you get that message while trying to download Mylyn, it means that Eclipse couldn't find the location you entered. This might be because you copied something incorrectly (watch for extra characters -- even extra spaces can cause errors), or because the site went down. You may be able to see if the site is up or down by copying the URL into your Web browser.<br />
<br />
'''What does the "Update manager failure" message mean? '''<br />
<br />
It means that Eclipse could not access the update site, or that it got confused about the configuration state of your Eclipse. First try updating again to see if the update site is accessible. <br />
<br />
If you are trying to update the JIRA connector you can also try de-selecting that feature in case the <code>Tigris.org</code> update site is not accessible. Using ''Search for new features to install..'' when installing can help to avoid this problem. If that does not work see the feature configuration troubleshooting below. <br />
<br />
'''What does "Could not create Browser page: No more handles (<code>java.lang.UnsatisfiedLinkError: ...</code>)" mean?'''<br />
<br />
It probably means that you are running Linux and don't have Eclipse and a Web browser configured to work together. See [[http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux| installing a browser on Linux]].<br />
<br />
'''When downloading, why do I get a warning that the feature was unsigned?'''<br />
<br />
Signing plugins requires extra administrative details with <code>eclipse.org</code> which most plug-ins seek to avoid. <br />
<br />
'''N.B.''': Security issues with features should not be underestimated. Eclipse allows users to download new functionality from remote servers. A rogue plug-in can act as a perfect Trojan horse. It can look innocent enough and provide useful function while spawning threads in the background with full access to the local file system and the Internet (if connected). Beware of installing features from update sites you do not trust.<br />
<br />
'''What does "<code>Root exception: java.lang.UnsupportedClassVersionError: org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)</code>" mean?'''<br />
<br />
It probably means that the virtual machine is JDK1.4 or lower. See [[Mylyn_Installation_Guide#Download_and_configure_Java| download and configure Java]].<br />
<br />
'''Why am I getting messages in my <code><workspace>/.metadata/.log</code> or my Mylyn view that say things like <code>"java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()"</code> and "The activator <code>org.eclipse.mylar.java.MylarJavaPlugin</code> for bundle <code>org.eclipse.mylar.java</code> is invalid"?'''<br />
<br />
This probably means that your Mylyn download version didn't match your Eclipse download version. Note that [http://eclipse.org/mylar/dl.php the download site] has different downloads for Eclipse 3.1 and Eclipse 3.2.<br />
<br />
To fix this problem, see the [[Mylyn_Uninstallation_Guide| uninstallation guide]], then re-install from [http://eclipse.org/mylar/dl.php the correct download site].<br />
<br />
'''What does "Could not create Bugzilla editor input" and "<code>java.io.IOException</code>: SAX2 driver class <code>org.apache.xerces.parsers.SAXParser</code> not found" mean?'''<br />
<br />
It probably means that you are on MacOS, and for some reason are missing Xerces from the Mac JDK1.5. You will probably need to add it to your default classpath. Please refer to and comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=144287 bug 144287] if you see this problem.<br />
<br />
To ensure that you are using the 1.5 VM refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
'''I've just updated to Mylyn 2.0 and I don't see any tasks in my Task List'''<br />
<br />
As part of the update to Mylyn 2.0 the old data folder has been migrated to <workspace folder>/.metadata/.mylyn from the old location <workspace folder>/.mylar. IF for some reason migration failed (.mylar folder still exists), simply shut down Eclipse and manually move your old <workspace folder>/.mylar folder to <workspace folder>/.metadata/.mylyn (note the name change to .mylyn)<br />
<br />
== Configuration Troubleshooting == <br />
<br />
'''How can I change the number of editors left open before Mylyn starts closing editors?'''<br />
<br />
Turn off or increase the number of editors to leave open using ''Preferences -> General -> Editors -> Number of opened editors before closing''. Since Mylyn will manage the open editors with task activation, this number can be set higher or you can disable automatic closing entirely.<br />
<br />
'''Do I need the Outline View when running Mylyn?'''<br />
<br />
No, not really. The Package Explorer and folded signatures should provide enough context for you. If, at some point, you really need to see an Outline View, you can always enter (Ctrl+O) to show the in-place Outline View.<br />
<br />
'''What does the message "content assist proposals no longer appear" mean?'''<br />
<br />
This usually happens when uninstalling when using Eclipse 3.2. Make sure that the "Java Completions" and "Java Types" proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
'''Why do I get errors like "HTTP Response Code 407" or "Proxy Authentication Error" when accessing repositories through a proxy server?'''<br />
<br />
It is likely that you need to configure these proxy server settings. Select ''Window -> Preferences -> Install/Update'', and update the section in the "Proxy settings" section of the form.<br />
<br />
'''I can't use <code>Ctrl+Alt+Shift+Arrow Up</code> for'' Mark as Landmark''. What do I do?<br />
<br />
This is usually a Linux/GNOME problem, where the Gnome keyboard shortcuts are interfering with the Eclipse shortcuts. Go to the Keyboard shortcuts (which might be something like ''Desktop -> Control Centre -> Keyboard Shortcuts'' or ''System -> Preferences -> Keyboard Shortcuts'') and disable both of these shortcuts:<br />
* Move one workspace up<br />
* Move one workspace down<br />
<br />
See also: [[Mylyn_User_Guide#Keyboard_mappings_on_Linux| keyboard mappings on Linux]].<br />
<br />
'''How do I turn on spell checking?'''<br />
<br />
See [[Mylyn_User_Guide#Spell_Checking| spell checking]].<br />
<br />
== Uninstall troubleshooting ==<br />
<br />
When '''uninstalling in Eclipse''' Mylyn via the ''Help -> Software Updates -> Manage Configuration'' dialog you will need to uninstall dependencies first (e.g. Bugzilla Connector, Subclipse integration) and then uninstall the core Mylyn features.<br />
<br />
When '''uninstalling manually''' by deleting all of the Mylyn plug-ins and features from the <code>eclipse/plugins</code> and <code>eclipse/features</code> directory make sure to delete all of the plug-ins and then restart Eclipse with the -clean option (e.g. by inserting it into a shortcut or the <code>eclipse.ini</code> file.<br />
<br />
On '''Eclipse 3.1:''' you may need to reset the Java editor to be default for <code>.java</code> again via: ''Preferences -> General -> Editors -> File Associations''<br />
<br />
On '''Eclipse 3.2:''' if after uninstalling '''content assist proposals no longer appear''' you need to ensure that the ''Java Completions'' and ''Java Types'' proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
== I am seeing <code>java.lang.OutOfMemoryError: PermGen space </code>errors, what's wrong? ==<br />
<br />
If your Eclipse crashes, or you see the above error after installing Mylyn or other plug-ins, you have most likely hit the infamous MaxPermSize bug. This is not a Mylyn specific problem, but a general Eclipse problem that is often triggered on Eclipse 3.2 and later, if you have many plug-ins installed and are using a Sun JVM. <br />
<br />
To fix it simply add the following to your launch arguments. This is usually to your shortcut, or to the <tt>eclipse/configuration/config.ini</tt> file:<br />
<br />
-XX:MaxPermSize=128M<br />
<br />
If you are using a large number of plug-ins (e.g. WTP) you may need to increase the number to more than 128M. <br />
<br />
Details of the problem are on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250 Platform bug 92250].<br />
<br />
= Task List =<br />
<br />
== Why won't the Archive category disappear? ==<br />
<br />
The ''Archive'' category will automatically appear if a task needs to be shown, but is not in any query or category. <br />
In order to ensure that you do not miss reminders or notifications the following tasks will always be shown in the Task List, even if they have been removed from a category or a query:<br />
* Tasks scheduled for this week or overdue. Remove these by using the ''Schedule'' pop-up menu option to defer them to a future week or to clear the schedule.<br />
* Repository tasks that have incoming changes, such as comments. Remove these by reading them or marking them as "read" via the ''Mark -> Read'' pop-up menu.<br />
<br />
== The Archive category contains many irrelevant tasks, how do I clean it up? ==<br />
<br />
If you created very broad queries you could end up with thousands of tasks in the Archive category. Other than clearing the <tt>workspace/.metadata/.mylyn/tasklist.xml.zip</tt> and <code>workspace/.metadata/.mylyn/offline</code> folder (note that this will entirely reset your Task List) the easiest option is to:<br />
* Clean up your queries to include only tasks of interest (note that including completed/resolved tasks is recommended).<br />
* Turn off ''Focus on Workweek'' in the ''Task List''.<br />
* Turn off the ''Filter Archive Category'' option in the ''Task List'' view menu.<br />
* Delete all of the unneeded tasks from within the Archive category. Note that if the tasks are not matched by queries they will be deleted permanently and any local notes or scheduling information that you have added to them will be lost.<br />
<br />
== How does Mylyn count the active time for a task? ==<br />
<br />
Whenever you work on a task, Mylyn accumulates the time you spend actively working on a task. This time can be viewed in the ''Personal Planning'' section of the ''Task Editor''. When you are not interacting with Eclipse, the timing automatically times out after 3 minutes by default. This means that activity outside of Eclipse will not be captured when you work on the task and that the timings in Mylyn are a lower bound of the total time spent on the task (capturing timings for work done outside of Eclipse involves OS specific extensions).<br />
<br />
== How do I prevent long-running tasks from adding to the progress bar? ==<br />
<br />
If you have many long-running or recurring tasks scheduled for this week, they can affect the ''Task List'' weekly progress bar. This can be misleading as they may never be completed. The current work-around to prevent long-running tasks from being included in the weekly progress bar is to schedule their estimated time to be 0 (zero). Alternatively, you can schedule only the amount of time you plan on spending on that task this week.<br />
<br />
== Does the Task List replace the Eclipse Tasks view? ==<br />
<br />
The SDK's ''Tasks'' view is used for showing markers such as 'todo' tags which indicate a local problem with a resource, similar to a compiler warning. As such, these 'tasks' are at a much lower level of granularity than Mylyn's tasks, and one task could involve cleaning up multiple todos. In order to make working with only the markers in a particular task context, e.g. for clean-up before committing, the ''Apply Mylyn'' filter is available for both the ''Problems'' and the ''Tasks'' views.<br />
<br />
== What if I use multiple workspaces? ==<br />
<br />
Mylyn's support for multiple workspaces is currently limited (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130658 bug 130658] for a discussion) because the Task List is considered to be specific to the person, and not to the workspace. We recommend configuring your Eclipse workspace to use working sets instead of relying on multiple workspaces. <br />
* John O'Shea's blog: [http://www.xlml.com/aehso/2007/02/02/eclipse-workspaces-containing-projects-with-overlapping-locations-and-mylar/ Eclipse workspaces containing projects with overlapping locations, and Mylar]<br />
<br />
If using a single workspace is not possible you can do the following:<br />
* In ''Preferences -> Mylyn -> Task List'' set the ''Data Directory'' to be a shared location, and do this for both workspaces.<br />
* Be sure to avoid launching both Eclipse workspaces at the same time, as changes in one workspaces could overwrite the Task List in the other workspace.<br />
* If you upgrade Eclipse or move your workspace and don't see your tasks, check the ''Data Directory'' setting.<br />
<br />
== How do I export my task and repository data? ==<br />
<br />
Export via File > Export > Mylyn > Task Data<br />
<br />
== Why does Mylyn use the term "task"? ==<br />
<br />
There are many work items that make up the developer's workday. Many issue trackers and project management tools refer to these as: bugs, defects, actions, tickets, stories, enhancements, and the list goes on. We refer to all such work items as "tasks" because the word tasks is short and commonly used in time management tools. Task Repository connectors can customize the presentation of tasks, for example, indicating which is a defect and which is an action item.<br />
<br />
= Task Editor =<br />
<br />
== Why am I seeing strange boxes where I expect to see proper characters? ==<br />
<br />
If for example you aren't seeing the proper single quote chacters in the summary of [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=197644 bug#197644]], check that the encoding is set correctly for the repository in the asociated Task Repositories view (Properties > Additional Settings > Character Encoding). For bugs.eclipse.org/bugs set your charcter encoding to ''ISO-8859-1''.<br />
<br />
= Task Repositories =<br />
<br />
== What if Mylyn doesn't support my task/bug/issue/ticket repository? ==<br />
<br />
To see support for your repository faster, do a search of the open repository connector requests and [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Bconnector%5D&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=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= vote for the corresponding bug] if your tracker is there, or [http://www.eclipse.org/mylar/bugs.php create a new bug]. <br />
<br />
[[Mylyn_User_Guide#Generic_Web_Repository_Connector|Generic Repository Connector]], allows creating Queries to the web-based issue tracking repositories and get list of issues from the web UI into the Task List.<br />
<br />
It is also possible to link a ''local task'' with the web page in web-based repository via the Mylyn Web integration.<br />
<br />
'''To create a task from any web-based repository:'''<br />
<br />
* Drag the URL from the address bar of the browser, or from a hyperlink in a bug listing to the ''Mylyn Tasks'' view. This will create a task for the bug, link it to the page, and populate the description with the title of the corresponding page. '''In Mozilla:''' simply drag the URL. '''In Internet Explorer:''' you must have <code>Ctrl</code> pressed in order for Eclipse to recognize the drop.<br />
* '''Alternatively,''' you can copy the URL, press the ''New Task'' button on the ''Mylyn Tasks'' view. This has the same effect as above but you can edit the description after retrieving it.<br />
* Opening the task will now open the corresponding issue. You can also <code>right+click</code> the task and select ''Open in External Browser''.<br />
<br />
[[Image:mylar-tasklist-weblink-editor.gif]]<br />
<br />
== Why were my repository credentials reset? ==<br />
<br />
If you upgrade Eclipse or your Java VM, you will need to reset your credentials in the ''Task Repositories'' view because these are stored in the secure Eclipse workbench keyring. Also see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=149607 bug 149607]. If you are migrating '''from Eclipse 3.2 to 3.3''' note that you will need to use a different update site, which is listed here: http://eclipse.org/mylyn/dl.php<br />
<br />
== Why are my updated repository attributes not showing up? ==<br />
<br />
Your server's repository attributes can change frequently, for example, there can be a new "milestone" or "version" added to the Bugzilla repository with each release. When the ''Preferences -> Mylyn -> Task List -> Synchronization'' setting is enabled, every 10th synchronization will update the attributes from the repository. If you do not have this setting enabled, your can force the update via the ''Update Attributes'' action on the task repositories' context menu in the ''Task Repositories'' view. Note that you will need to reopen a task editor to see the updated attributes. If you instead update via the button on the ''Attributes'' section of the ''Task Editor'' the attribute settings will be reloaded without needing to reopen.<br />
<br />
== Authentication Troubleshooting ==<br />
<br />
You must ensure repository credentials are filled out correctly. Refer to the diagram below:<br />
<br />
[[image: AuthenticationTroubleshooting2.png|right]]<br />
<br />
# Enter the repository URL (i.e. https://bugs.eclipse.org/bugs) and an optional label<br />
# Credentials<br />
#* Usually email address and password <br />
#* Some sites, such as <code>dev.eclipse.org</code>, use anonymous logon with password left blank.<br />
#Http Authentication (optional)<br />
#* Some sites are protected by either BASIC or DIGEST http authentication. If this is the case, enter appropriate credentials here.<br />
#* One way to test if the site requires http authentication is to point your browser at the repository. If you are presented with an authentication dialog popup, the site is likely protected by http authentication.<br />
#Proxy Server Configuration (optional)<br />
#* By default Mylyn uses the Platform's Install/Update proxy settings. Uncheck this box if you wish to use an alternative proxy.<br />
#* If the proxy requires authentication, this is where you enable and enter your proxy credentials.<br />
#* If you are experiencing connection problems, ensure your Install/Update proxy settings are valid or the repository specific settings are correct<br />
#* Mylyn has been tested with HTTP proxy servers. Currently SOCKS is not supported.<br />
#Validate Settings <br />
#*Press the ''validate'' button to test the settings<br />
#*If you are seeing errors like "HTTP Response Code 407" or "Proxy Authentication Error" it is likely that you need to configure proxy settas as described above.<br />
#*If your sever uses a certificate and fails to connect, e.g. you see exceptions <tt>sun.security.validator.ValidatorException: PKIX path building failed</tt> then you need to point Eclipse at your certificate, see the [http://ahtik.com/blog/2006/05/11/fixing-eclipse-mylar-jira-integration/ instructions on this blog].<br />
<br clear="all" /><br />
<br />
=== NTLM authentication ===<br />
<br />
For NTLM authentication to work a special format for the username needs to be used where ''DOMAIN'' needs to be replaced by the Windows login domain: <br />
<br />
DOMAIN\username <br />
<br />
The built-in NTLM support of the JDK which is used by Eclipse does '''not work''' with Mylyn since it uses the HttpClient library to access repositories. Limitations in regard to NTLM authentication are documented in the [http://wiki.apache.org/jakarta-httpclient/FrequentlyAskedNTLMQuestions NTLM FAQ] and also discussion on {{bug|201911}}.<br />
<br />
* If your repository uses MS NTLM authentication and only standard http authentication is being passed to the repository this can result when the local hostname cannot be resolved. Ensure your machine's hostname is set correctly and resolves to a valid address.<br />
* It is not possible to use NTLM authentication for the proxy as well as for the repository.<br />
<br />
If NTLM authentication fails the '''[http://ntlmaps.sourceforge.net/ NTLM Authorization Proxy Server]''' has been reported to '''work''' with Mylyn.<br />
<br />
== Why are task hyperlinks not working? ==<br />
<br />
For task hyperlinks in textual editors (e.g. Java editor) and other text viewers (e.g. History view comments) you must associate the project that contains the resource to the task repository. <br />
<br />
:''Project association can also come from 3rd party metadata trough the contrubuted [[Mylar_Integrator_Reference#Mapping_from_projects_to_Task_Repositories|extension point]]. [http://subclipse.tigris.org/ Subclipse] and [http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Mylyn Maven integration for Eclipse] plugins contributing it. See few more details [http://jroller.com/page/eu?entry=linking_projects_from_the_eclipse here].''<br />
<br />
Note that to view a hyperlink you must hold down the <code>Ctrl</code> key when hovering over the reference to the task. References to tasks are connector specific and the common reference is found on the top left of the task editor and other conventions tend to follow those used in the web UI (e.g. "bug 123" for Bugzilla, "ABC-123" for JIRA).<br />
<br />
[[Image:mylyn-project-repository-association.gif]]<br />
<br />
= Bugzilla Connector =<br />
<br />
== What versions are supported? ==<br />
<br />
We recommend using the latest [http://www.bugzilla.org/download/ release] of Bugzilla.<br />
<br />
* '''Bugzilla 2.18.6 is the lowest version of Bugzilla supported'''. If you are getting errors that indicate failure to update attributes this may be an indication that the Bugzilla server is not supported (< 2.18.6).<br />
<br />
*If you are using '''Bugzilla 2.18''' and are getting '''mid-air collisions''' this is likely due to incorrectly formatted timestamp field in the underlying bugs database table ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149513 bug 149513]). This can be resolved by upgrading to Bugzilla 2.20 or later.<br />
<br />
== Why are queries failing? ==<br />
<br />
*If '''queries are not working''' correctly ensure that you have the right Bugzilla server version selected for the corresponding repository: ''Task Repositories (View) ->'' right+click the repository ''-> Properties''. For supported versions see the [http://www.eclipse.org/mylar/dl.php download page]. If the repository is still not functioning it may be due to authentication or connectivity problems. If that does not resolve the problem please post a message to the newsgroup or [http://www.eclipse.org/mylar/bugs.php submit a bug].<br />
<br />
== Why do I see my old username? ==<br />
<br />
If you change the username/email address on your Bugzilla account you may notice that some tasks still have the old username/email. Explicitly synchronize the task via the ''Task List'' popup menu or ''Task Editor'' toobar in order to update your username.<br />
<br />
== Why do tasks fail to open? ==<br />
<br />
*If upon opening a bug, the Bugzilla tab only displays a warning "'''Could not download task data, possibly due to timeout or connectivity problem. Please check connection and try again.'''", ensure that your repository is returning XML data by pointing your browser to <code><your-repository-url>/show_bug.cgi?id=1&ctype=xml</code> to show the contents of bug 1 in XML form. The Bugzilla client requires that bugs be accessible in XML form. If the repository doesn't support xml then it is likely that the repository is too old (Mylyn currently supports Bugzilla 2.18 and later).<br />
<br />
* If '''reports fail to load''' or '''reports fail to synchronize''' (task description remains ''italic''), check the error log for a "'''File not found'''" error pointing to <code>bugzilla.dtd</code> or a "'''Failed to retrieve products from server'''" error message - these result when the <code>urlbase</code> parameter is not set on the bugzilla server, or your bugzilla installation is missing the <code>bugzilla.dtd</code> file. See: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=161759 bug#161759]<br />
<br />
* If '''attributes are missing options''' in the bug editor (ie. missing a recently added milestone, [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155431 bug# 155431]):<br />
** Update attributes by choosing ''Update Attributes'' from the context menu in the ''Task Repositories'' view<br />
** Synchronize the task in the Task List<br />
** Reopen the task - new options should be available.<br />
<br />
== Why do tasks fail to submit? ==<br />
<br />
* '''Error upon submit: unable to make any match for name/email entered.''' If your bugzilla is configured for user names rather than full email address the QA Contact field will cause the submit to fail ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=166555 bug# 166555]). To resolve, select 'Local users enabled' option on the Repository Configuration page. <br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your account's username and password and are not using the HTTP authentication fields instead.<br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your bugzilla instance's cookie domain under the required settings. The cookie domain must lead with a dot.<br />
<br />
* If '''attachments are failing to submit''' and you see that after processing the attachment, the bugzilla bug shows a size of "bytes" (no numbers), your database may be dropping the packet sending the file. '''On MySQL''', check the [http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html max_allowed_packet directive]. You may see errors like: <code>DBD::mysql::st execute</code> failed: Got a packet bigger than 'max_allowed_packet' bytes [for Statement "INSERT INTO attach_data (id, thedata) VALUES (38, ?)"] at <code>/path/to/bugzilla/attachment.cgi</code> line 993. Also, '''check the maximum attachment size''' in ''Bugzilla Parameters -> Attachments''.<br />
<br />
* If a submit fails with an '''Invalid Username or Password''' error even though repository settings do validate, make sure that cookies could be set. See also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175502 bug 175502]<br />
<br />
== What time zone is used in the task editor? ==<br />
<br />
*The '''times''' that appear in the Bugzilla bug editor (ie. created, modified) '''are local to the server hosting the Bugzilla repository''', not your local machine's time zone. <br />
<br />
== Known limitations ==<br />
<br />
* The <code>usermatchmode</code> is not currently supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168204 bug 168204]) and as such full email addresses need to be used.<br />
<br />
* The <code>usevisibilitygroups</code> parameter is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=180876 bug#180876]). Group assignment will currently be lost if updated using the Bugzilla rich task editor.<br />
<br />
* Version 1.0 of Mylyn presents an error message upon new comment submission to RedHat's public Bugzilla repository. The comment is in fact posted. This issue is resolved in Mylyn 2.0M2 and higher. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=183251 bug#183251])<br />
<br />
= JIRA Connector =<br />
<br />
If you see errors like the following, work around this by opening repository ''Properties Page'' and clicking OK (bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169102 169102]).<br />
<br />
org.tigris.jira.core.service.exceptions.AuthenticationException<br />
at org.tigris.jira.internal.core.service.soap.SoapJiraService.getProjectsNoSchemes(SoapJiraService.java:204)<br />
<br />
== What are the server requirements? ==<br />
<br />
The '''JIRA SOAP/RPC services have to be running on the JIRA server''':<br />
<br />
* Jira 3.3.3 or higher (3.7 or higher for attachment retrieval)<br />
* Jira RPC plugin 1.4.3 or higher<br />
<br />
Latest information also available on the [http://www.eclipse.org/mylar/dl.php download page].<br />
<br />
Related Resources:<br />
<br />
* [http://confluence.atlassian.com/display/JIRA/JIRA+Development+Hub Jira Development Wiki]<br />
* [http://confluence.atlassian.com/pages/viewpage.action?pageId=1035 Jira RPC Plugin Overview]<br />
<br />
== Why can't I connect? ==<br />
<br />
* If you get a <code>org.tigris.jira.core.service.exceptions.ServiceUnavailableException</code> you need to turn on the JIRA SOAP/RPC services on the server.<br />
* Similarly, if you get a "Processing instructions are not allowed within SOAP messages" message, ensure that SOAP/RPC services are on.<br />
* If you get a '''503''' error code verify that the SOAP/RPC interface is enabled.<br />
* If you get a '''403''' error code verify that the SOAP/RPC interface is enabled, and also check your authentication mechanism. If the server is using NTLM authentication, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156397 bug 156937] for diagnosis steps.<br />
* If you see an '''"unrecognized priority" message''' in the ''Error Log'', the problem is that the JIRA Connector does not support customized priorities so the priority value specified in that message will not correspond to the priority icons visible in the Task List.<br />
* If you are being '''prompted for your log-in credentials''' by the Browser tab of the task editor or the new task editor, this is because without rich editor support the connector is using the web-based UI instead of logging in on your behalf as is done with a rich task editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142869 bug 142869]).<br />
* If you get a <CODE>AuthenticationException</code> and a query won't synchronize, use Task Repositories (view) -> Properties (on the repository) -> Validate Settings. This will clear the connection if it died.<br />
<br />
<!-- HEAVILY OUTDATED. PLUGIN NOW USES COMMON PROXY INFRASTRUCTURE<br />
== Why can't I synchronize when using a proxy server? ==<br />
<br />
* Proxy configuration is '''based on the normal Java HTTP system properties''', which can be configured either by launching Eclipse with <code>-vmargs</code> and using the following settings, or by putting these settings into the or by putting the following into the <code>eclipse/eclipse.ini</code> file (after -vmags):<br />
-Dhttp.proxyHost=<host> <br />
-Dhttp.proxyPort=<port><br />
* Make sure that when using these settings you do not enable the proxy settings on the ''Install/Update'' preference page, since they may override these settings.<br />
* If you are using '''SSL''', you will also need to set the <code>https.proxyHost</code> and <code>https.proxyPort</code>. <br />
* Authentication is configured with the <code>http.proxyUser</code> and <code>http.proxyPassword</code> system properties (also for SSL)<br />
* You can also use <code>http.nonProxyHosts</code> system property to enumerate hosts that should not be proxied. Note that matching is implemented on the exact host name used for JIRA server and patterns are not supported. --><br />
<br />
== Known limitations ==<br />
* Attachment retrieval (including retrieval of the task context and attachment list in the task editor) require JIRA 3.7 or above ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=169757 bug 169757])<br />
<!-- * NTLM authentication is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172395 bug 172395]) --><br />
* Customized priorities are not currently supported, so all issues with a customized priority will have the default priority level ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=165518 bug 165518]).<br />
* blank but editable custom fields doesn't appear in the RSS data, and as result we can't show them for editing<br />
* because of JIRA api limitations, we can support custom fields in the task editor, but not in the new custom task editor<br />
<!-- * On JIRA 3.6.x private filters saved on the server can fail to retrieve results ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=174328 bug 174328]). The work-around is to create a custom query in Mylyn using the form-based query designer or to share the filter in JIRA. --><br />
* Mylyn only allows the usage of US-ASCII characters in the filename when uploading an attachment<br />
<br />
== How can I enable compression for SOAP messages? ==<br />
<br />
If your repository has lots of projects and components you can speed up the download of the repository configuration by enabling compression. <br />
<br />
* Add a filter-mapping to your JIRA server configuration: [http://jira.atlassian.com/browse/JRA-10353].<br />
* Enable compression in your global JIRA configuration.<br />
* Check the compression setting for your task repository in Mylyn versions 2.0M2 and later.<br />
<br />
== Reporting issues ==<br />
<br />
Since JIRA can be heavily customized there is a chance that some particular customizations may not work, so if you can't connect to your proprietary repository it is a good idea to try the following public repositories to make sure you have working configuration:<br />
<br />
* http://jira.codehaus.org<br />
* http://issues.apache.org/jira/<br />
* http://opensource.atlassian.com/projects/spring <br />
<br />
If you can't get query results, you could try to call "Open with Browser" on query node in the Task List view and then save link "Current view: XML" and attach it to the bug report.<br />
<br />
Even if query don't work you could try "Open Repository Task" from your JIRA repository node on the Task Repositories view and check if you can open JIRA task editor for that issue. Same for the Task search (Ctrl-H, Task Search)<br />
<br />
To investigate various error you may need to enable debug tracing. To do that you need to create the <code>.options</code> file with the following content:<br />
<br />
<pre><br />
org.eclipse.mylyn.jira.ui/connector=true<br />
org.eclipse.mylyn.jira.ui/dataHandler=true<br />
</pre><br />
<br />
and then add the following options to the Eclipse command line (or eclipse.ini file):<br />
<br />
<pre><br />
-debug <path to the .options file>/.options<br />
</pre><br />
<br />
The additional logging will go into the regular Eclipse log and the Error Log view<br />
<br />
== Why do I get errors about an unexpected redirect when submitting an issue? ==<br />
<br />
Please go to the repository properties and validate the repository. If errors about circular redirects are logged in your Eclipse error log your JIRA server or proxy might be misconfigured. <br />
<br />
In some cases unexpected redirects can be caused by a JIRA server accessed via Apache and mod_jk (using the AJP/1.3 Tomcat connector). Some server configurations may benefit from the 'proxyHost', 'proxyPort', 'scheme' and 'secure' settings on the AJP Connector in the Tomcat server configuration.<br />
<br />
Please see {{bug|202834}} for a more details.<br />
<br />
= Trac Connector =<br />
<br />
== What are the server requirements? ==<br />
<br />
The Trac connector offers two access methods:<br />
<br />
'''XML-RPC''' (recommended)<br />
<br />
Requirements:<br />
* Trac 0.10<br />
* [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] rev. 1950<br />
<br />
This access method offers editing of tasks in a rich editor, attachment support and offline editing. It requires the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] for Trac to be enabled for the accessed repository. The XmlRpcPlugin provides a remote interface to the Trac repository and is distributed separately from Trac (see [http://trac.edgewall.org/ticket/217 #217]). See these [http://trac-hacks.org/wiki/XmlRpcPlugin#Installation install instructions] for requirements and documentation.<br />
<br />
'''Web''' <br />
<br />
Requirements:<br />
* Trac 0.9 or later<br />
<br />
In this mode the standard Trac web interface is used for repository access. Tickets may be created and edited through a web browser. Offline editing and attachments are not supported.<br />
<br />
== Recommended Trac version ==<br />
<br />
Mylyn should work with any stable release Trac release that is version 0.9.x or 0.10.x (see below for known limitations). Mylyn works best when used with Trac's XML-RPC Plugin (see above) but we do not recommend a particular Trac version. <br />
<br />
The Trac connector tests are run against these Trac versions:<br />
<br />
* Trac 0.10.4, XML-RPC Plugin rev. 1950<br />
* Trac 0.9.6<br />
<br />
See {{bug|175211}} for details about Trac 0.11 support.<br />
<br />
== Why do I get an HTTP Error 500 Internal server error when creating a ticket that contains non-ASCII characters? ==<br />
<br />
Problems related to character encodings have been reported when Trac is run with Python 2.3. Upgrading to Python 2.4 may help to resolve this. Please comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=188363 bug #188363] if you encounter an internal server error when creating a ticket that contains non-ASCII characters.<br />
<br />
== Known limitations ==<br />
<br />
* Trac 0.10.1 <br />
** Known incompatibility with Trac XML-RPC Plugin. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164272 bug 164272] for details.<br />
* Trac 0.10.3 <br />
** Known incompatibility with old versions of the Trac HttpAuthPlugin (fixed in revision 1890 or later). The plug-in enables basic auth for XML-RPC when Trac AccountManagerPlugin for form based authentication is used. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168413 bug 168413] for details.<br />
* Trac 0.11<br />
** Currently untested.<br />
** Known incompatibility with Trac XML-RPC Plugin See [http://trac-hacks.org/wiki/XmlRpcPlugin] for details.<br />
<br />
== Why are tasks opened in a web browser and not in the rich editor? ==<br />
<br />
Please make sure that the access type in the repository properties is set to XML-RPC. This requires Trac 0.10 and XML-RPC (see above).<br />
<br />
== Which URLs does Mylyn access in a Trac repository? ==<br />
<br />
XML-RPC:<br />
<br />
* The expected URL is either /xmlrpc or /login/xmlrpc (if login credentials are provided)<br />
<br />
Web:<br />
<br />
* Authentication: /login <br />
* Querying: /query?format=tab...<br />
* Synchronizing ticket details: /ticket/...<br />
* Getting repository configuration to populate query dialog: /query or /newticket<br />
<br />
The web mode relies on screen scraping and is likely to fail if the design<br />
(i.e. HTML output) of the Trac repository is heavily customized.<br />
<br />
= Generic Web Repository Connector =<br />
<br />
== Where can I find the web repository connector ==<br />
<br />
It is available from the extensions update page. Please see http://www.eclipse.org/mylyn/downloads/<br />
<br />
== Why can't I connect using one of the existing templates? ==<br />
<br />
<br />
The Web Repository Connector have a Preview option in Advanced Configuration section on the Query preferences. If you get an error or preview table does not show expected list of tasks you can use Query Pattern like (.+?)(\n) to see content of the retrieved page and compare it with the source of the web page for the same url loaded into the web browser.<br />
<br />
If that does not help then you could use the wget tool (on Windows it available as a standalone command line tool and also included with Cygwin).<br />
<br />
Run the following command:<br />
<br />
<pre>wget -v -d -o query.log -O query.html "http://your.query.url"</pre><br />
<br />
If repository require basic http auth, you'll need to use ''--http-user=USER'' and ''--http-password=PASS'' options.<br />
<br />
Then open file ''query.html'' in the web browser and check if it show list of issues you need to fetch from the web server. If it does have correct list, then there could be a problem with query pattern used for parsing. <br />
<br />
A popular mistake is an unmasked '?' that separates request parameters in the url). For example:<br />
<br />
<pre><a href="show_bug.cgi\?id\=(.+?)">.+?<span class="summary">(.+?)</span></pre><br />
<br />
If ''query.html'' does not show expected list of issues you can check ''query.log'' for server responses and try to identify if server require authentication, redirecting your requests somewhere or issue any other errors.<br />
<br />
== Known limitations ==<br />
<br />
* In Mylyn 1.0: if a web server responds by requesting a redirect to an absolute URL while fetching a resource, the connector falsely prepends "/" to the URL and the request will fail. The workaround is to use final url where redirect is pointing to (you can find it as describe above). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=167282 bug 167282] for details.<br />
<br />
= Task-Focused UI =<br />
<br />
== What is the Task-Focused UI? ==<br />
<br />
When you activate a task, Mylyn automatically maintains a task context by monitoring your interaction. The task context provides a predictable degree-of-interest weighting of the relevance of the elements and relations that you work with to the task-at-hand (as described in the [http://kerstens.org/mik/publications/2006-11-mylar-fse.pdf Foundations of Software Engineering conference paper]). The Task-Focuse UI is the mechanism by which Mylyn presents Mylyn the task-context model in order to reduce information overload and to automate the manaul management of UI elements like editors and change sets. Examples:<br />
* Filtering, decoration and expansion management in views<br />
* Automatic folding in editors<br />
* Ranking in content assist<br />
* Editor management<br />
* Perspective management<br />
* Change set management<br />
<br />
== Why do files disappear from Focused views when I close them? ==<br />
<br />
By default Mylyn automatically manages the set of open files to match the task context, so that you don't have to. This ensures that the editor list (viewable via mechanisms like Ctrl+E) corresponds to what you in views like the ''Package Explorer'' when they are in Focused mode. When you close a file manually, you express that it is uninteresting, and as such it will be removed from the task context. It will also disappear from the corresponding automatically managed change sets for the same reason. This behavior can be turned off via ''Preferences -> Mylyn -> Context -> Manage open editors to match task context''. However, it is highly recommended since Mylyn will prevent the number of editors from bloating by automatically closing editors for elements that have decayed in interest, and always keep the editors for interesting elements open.<br />
<br />
<br />
== Why did all my editor tabs disappear? ==<br />
<br />
When you deactivate a task, all editors will be closed, and then when you reactivate the task all the windows will be open again. Try it, it's fun. <br />
<br />
Mylyn actively manages your open editors with task context. It takes some getting used to, but enables switching between tasks when you are multitasking without cluttering your editor tabs. This editor management can be disabled via ''Window -> Preferences -> Mylyn -> Context''. However, before disabling it consider reading the ''"Managing open editors..."'' section of [http://www-128.ibm.com/developerworks/java/library/j-mylar2/index.html#N10116 Task-focused programming with Mylar].<br />
<br />
== How do I get rid of an element if it is not interesting? ==<br />
<br />
When a view is focused elements will disappear on their own if they are not repeatedly selected via a mechanism called interest decay. Note that decay does not use the wall clock, but instead relies on the number of selections that you have made when working on that task to determine which elements disappear. This helps make it feel very predictable.<br />
<br />
If you want want to force one or more elements to disappear from the context use the '''Remove from Focus''' action on the context menu. Note that the element will still be part of the task context since it was previously part of the interaction. <br />
<br />
If you want to permanently delete the element from the interaction history use the '''Remove from Context''' action on the '''Context''' tab of the '''Task Editor'''. For example, if a company private element was part of a task context that is to be shared with a public repository, this action can be used to clean it up before sharing. Note that elements will be removed from the task context recursively.<br />
<br />
== Which Focused UI features can I turn off? ==<br />
<br />
'''All of them.''' When no task is active neither are any of Mylyn's features. When working with task contexts Mylyn's Focused UI features are all optional and in general configurable. While many find it the key benefit of Mylyn, the entire Focused UI is optional and can be uninstalled via ''Help -> Software Updates -> Manage Configuration''.<br />
<br />
The following table summarizes how the key features can be toggled:<br />
<br />
<table><br />
<tr><br />
<td>'''UI Mechanism'''</td><br />
<td>'''Example/description'''</td><br />
<td>'''Toggle using'''</td><br />
</tr><br />
<tr><br />
<td>Interest filtering</td><br />
<td>Package Explorer</td><br />
<td>''Apply Mylyn'' button on view toolbar</td><br />
</tr><br />
<tr><br />
<td>Automatic toggling of filtering</td><br />
<td>Package Explorer</td><br />
<td>''Preferences -> Mylar -> Context -> Toggle focused mode..</td><br />
</tr><br />
<tr><br />
<td>Interest decoration</td><br />
<td>Bolding of landmark elements</td><br />
<td>''Preferences -&gt; General -&gt; Appearance -&gt; Label Decoration''</td><br />
</tr><br />
<tr><br />
<td>Content assist</td><br />
<td>Ranking of interesting elements</td><br />
<td>Eclipse 3.2: ''Java -&gt; Editor -&gt; Content Assist -&gt; Work in Progress -&gt;'' turn off Mylyn, turn on Java</td><br />
</tr><br />
<tr><br />
<td>Active change sets</td><br />
<td>Grouping of changes by tasks</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Team''</td><br />
</tr><br />
<tr><br />
<td>Editor management</td><br />
<td>Auto opening/closing of editors</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Editor Management''</td><br />
</tr><br />
<tr><br />
<td>Active views</td><br />
<td>Active Search and Hierarchy</td><br />
<td>Only on if view is active</td><br />
</tr><br />
</table><br />
<br />
For additional configuration options see the ''Mylyn'' and ''General -> Appearance'' preference pages.<br />
<br />
== What is the performance profile of the Focused UI? ==<br />
<br />
The goal is for Mylyn to have '''no noticeable effect''' on Eclipse's speed or memory usage.<br />
You do not need to increase the amount of memory Eclipse runs with to use Mylyn. <br />
Any performance issue should be [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Mylyn reported as a bug]. <br />
<br />
The current '''Performance Profile''' is:<br />
<br />
# Mylyn only runs if a task is active, and has no impact on Eclipse if no task is active.<br />
# Task context models have negligible memory overhead. <br />
# When a task is active, additional view refresh is required to update the views based on interest model changes. This should not be noticeable on Windows where refresh is very quick, but could be more noticeable on other platforms.<br />
# The time to activate a task context is dominated by the time it takes Eclipse to open the editors in the context. You can set the preference for how many editors to open in the Mylyn preference page (e.g. setting to 1 will dramatically reduce activation time, but also remove the benefit of having open editors correspond to the task context). You can also turn off editor management entirely in the Mylyn Tasks view pull-down.<br />
# Eclipse startup is slowed down by (4) if a task is active when Eclipse is shut down.<br />
# The low priority background searches that the Active Search view runs can be noticeable on slower machines.<br />
<br />
== What happened to the Active Search and Active Hierarchy views? ==<br />
<br />
These views were not included in the Mylyn 1.0 release because they never made it beyond the experimental phase. <br />
* The ''Active Search'' view has not been sufficiently tuned to adapt to the lifecycle of a task context, and as a result requires manual manipulation of the degree-of-separation scope as you work on long-running tasks. Otherwise it becomes overloaded with elements. In addition, it is not yet clear whether an additional view is the right UI for this facility, and it is hard to find room for an additional view of this size on screen resolutions of 1600x1200 and smaller.<br />
* The ''Active Hierarchy'' view is also hard to allocate space for, especially when using the in-place hierarchy (Ctrl+T) on a landmark can be a quick way to see the relevant part of the task context's hierarchy.<br />
<br />
These features still show promise in displaying task context and saving repetitive searches, so we have not removed them. They have instead moved to the Mylyn Sandbox, and can be used and experimented with by following the [http://wiki.eclipse.org/index.php/Mylyn_Contributor_Reference#Sandbox instructions on the Contributors page]. For feedback on these views please use the corresponding bug reports or newsgroup.<br />
<br />
= Java Development =<br />
<br />
== Content assist troubleshooting ==<br />
<br />
Mylyn uses custom Content Assist processors in order to rank and separate the elements in the current task context. To see proposals ranked according to interest you must have only the ''Type Proposals (Mylyn)'' kinds checkbox enabled in the list below, otherwise you will see duplicates. '''If you do not see any proposals, check this list''' to ensure that either the Mylyn or the plain proposals are enabled. '''To do this automatically''', run ''New -> Mylyn -> Recommended Preferences''. Or you can select them manually as in the preference page below. <br />
<br />
[[Image:mylar-content-assist-prefs.gif]]<br />
<br />
'''Why do I see duplicate proposals?'''<br />
<br />
Ensure that you have only the ''(Mylyn)'' proposals kinds enabled in ''Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced'', otherwise you will see duplicates.<br />
<br />
If you use proposals via Ctrl+Shift+Space instead of the typical Ctrl+Space you will see duplicates. Vote for JDT/Text [https://bugs.eclipse.org/bugs/show_bug.cgi?id=147781 bug 147781] if you use this mechanism. Also see: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=129080 bug 129080]<br />
<br />
'''Why do I get an error message when using content assist?'''<br />
<br />
If after invoking Content Assist you see an error message dialog that states:<br />
The extension took too long to return from the 'computeCompletionProposals()' operation<br />
this is most likely due to something interrupting the proposal operation (e.g. garbage collection). Ignore it if it does not recur, increase Eclipse's memory if it does (e.g via <code>-Xmx384M</code> command line argument). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=141457 bug 141457] for more details.<br />
<br />
== Why do interesting elements not show in the Project Explorer? ==<br />
<br />
The ''Package Presentation -> Hierarchical'' mode is not supported on the ''Project Explorer'' view in Eclipse 3.2 through 3.3M3 and possibly later versions (https://bugs.eclipse.org/bugs/show_bug.cgi?id=161362 bug 161362). Use the view menu to set ''Package Presentation -> Flat'' as a work-around.<br />
<br />
== How do I stop declarations from showing in the Package Explorer? ==<br />
<br />
If you don't like Mylyn's constant showing of Java members in the ''Package Explorer'', select the drop-down menu, then ''Filters...'' and enable the ''Mylyn Java Declarations Filter''. It will then stick in the menu in case you want to toggle between modes. Note that this will hide interest information about members that aren't in your current file (e.g. showing you which methods are landmarks) so this mode is not recommended, but can be useful for <code>1024x768</code> screen resolutions.<br />
<br />
[[Image:mylar-java-filtering-declarations.gif]]<br />
<br />
== Why does nothing show up in the Active Search or Active Hierarchy? ==<br />
<br />
As you work, elements become Landmarks (bold decoration), and these elements populate the ''Active Search'' and ''Active Hierarchy'' views. To force an element to populate the views manually, make it a Landmark by <code>right+clicking</code> or hitting <code>Ctrl+Alt+Shift+UpArrow</code>.<br />
<br />
== Known limitations ==<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=106678 Bug 106678]: The Project Explorer's Hierarchical Java package presentation layout is not supported on Eclipse 3.3Mx, and interesting elements will be hidden if enabled. Work-around is to use the default Flat package presentation.<br />
<br />
= Team Support =<br />
<br />
== Why does task change set not appear when I modify files? ==<br />
<br />
A task change set should appear if you activate a task and modify a file connected to a compatible source repository (e.g. CVS, SVN). If it does not try the following:<br />
<br />
* Ensure you have installed the [http://www.eclipse.org/mylyn/downloads/ ''Mylyn Bridge: Eclipse SDK'' feature]. Note that this feature is not currently distributed with the Java-only Eclipse download ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191793 bug 191793] ).<br />
<br />
* Verify that the [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuring_the_Synchronize_view_for_change_sets configured ''Synchronize View'' is configured for change sets].<br />
<br />
If the above are working but the change set appears to be missing relevant files:<br />
<br />
* You may be seeing the ''Synchronize'' view's refresh problem ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142395 bug 142395]). Toggle from ''Incoming/Ougtoing'' to ''Incoming'' mode and back again to refresh the view.<br />
<br />
* If the files or change set are still missing deactivate and reactivate the task to force a full refresh.<br />
<br />
== Why do files disappear from the change set when I close them? ==<br />
<br />
If you have the ''Preferences -> Mylyn -> Context -> Manage open editors to match task context'' option enabled, Mylyn will perform editor management so that you don't have to. Closing a file makes it less interesting, and causes it to disappear from the active task context, and hence from the change set. This option prevents you from having to manage the set of open files, will automatically close editors for files that become uninteresting, and will ensure that the open editors match the task context.<br />
<br />
== Why am I missing elements when I retrieve someone else's context? ==<br />
<br />
To identify elements within a project, Mylyn relies on the name of the project being consistent across workspaces. If the project name in the workspace that the context was created with is different than its name in your workspace, the task context will not show elements within that project ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164058 bug 164058]). The other case where context can be lost is if the elements change names outside of the workspace ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164243 bug 164243]).<br />
<br />
The work-around is to use the same project names across your team's workspaces. We recommend the following two approaches for standardizing on project names:<br />
* Use '''Team Project Sets''': these are a very useful Eclipse facility that allows your entire team to check out numerous projects from version control by importing a single file. Create a project set via ''File -> Export -> Team Project Set'', host this file somewhere accessible, then have others import vai ''File -> Import -> Team Project Set''.<br />
* Have developers check out projects into their workspace without renaming them. The above is a shortcut for doing this. If alphabetical sort order in the ''Package Explorer'' is a problem, organize your projects via ''Project Explorer -> view menu -> Top Level Elements -> Working Sets''.<br />
<br />
= Misc =<br />
<br />
<br />
<br />
== How does Mylyn relate to IBM's Jazz? ==<br />
<br />
At the EclipseCon and JavaONE 2006 conferences IBM demonstrated previews of Jazz, a collaborative team server and Eclipse-based client. Articles have remarked on the similarities between Mylyn and Jazz because both integrate tasks into Eclipse (Jazz's "work items" and Mylyn's "tasks"), and both provide change sets grouped by task. But there are both significant differences and complementary aspects to the two approaches. A key goal of Mylyn is to provide an open source framework to support integration of task management with ''existing issue trackers and source repositories''. According to the presentations, components that come with Jazz include include a ''next-generation issue tracker and source repository'' and related lifecycle management tools such as project health. In addition, a driving and unique goal of Mylyn is to focus the UI around a usage-based and degree-of-interested weighted task context, which is complementary to the Jazz platform. Just as it integrates with Mylyn's Task List, Mylyn's Task Focused UI and task context model components are possible to integrate with other kinds of task management systems, such as the one provided by Jazz.<br />
<br />
Update: at EclipseCon 2007 the IBM Jazz team showed a Mylyn connector for Jazz.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/FAQ&diff=50728Mylyn/FAQ2007-09-17T17:07:01Z<p>Steffen.pingel.eclipse.org: /* JIRA Connector */</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
[[Mylyn User Guide]], <br />
[http://eclipse.org/mylyn Mylyn Home],<br />
[http://wiki.eclipse.org/index.php?title=Special:Userlogin&returnto=Special:Userlogout Log in to edit]<br />
<br />
For instructions on [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Download_Mylar downloading] [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installation installing] and [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuration configuring] <br />
Mylyn, see the [[Mylyn User Guide]]. For instructions on developing and contributing to Mylyn, see the [[Mylyn Contributor Reference]].<br />
<br />
= Installation =<br />
<br />
== What versions of Eclipse are supported? ==<br />
<br />
See the [http://eclipse.org/mylyn/dl.php download page].<br />
<br />
Mylyn also relies on a web browser that works with the Standard Widget Toolkit; Windows and MacOS users are fine, but Linux users might have to download another browser. See [http://www.eclipse.org/swt/faq.php#browserlinux the SWT Browser guide] for which browsers will work. See [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux installing browser on Linux] for installation instructions.<br />
<br />
== What version of Java is required? ==<br />
<br />
Mylyn needs the '''Java 5''' virtual machine.<br />
<br />
To check the version of the Java virtual machine that Eclipse was launched with to to ''Help -> About Eclipse SDK -> Configuration Details'' and verify that the java.vm.version is 1.5. <br />
<br />
Mac users should refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
* If you do not have Java 5, you can download it from [http://72.5.124.55/javase/downloads/index.jsp Sun's web site]. <br />
* If you have more than one VM, you need to specify that Eclipse should use the JDK1.5 VM. <br />
<br />
In Unix, set the environment variable <code>JAVA_HOME</code> to the root of the JDK1.5 installation and/or set the <code>PATH</code> variable to put the JDK1.5 executable directory before any other VM executable directories. For example, under <code>bash</code> in Unix:<br />
export JAVA_HOME="''(location of JDK1.5 root)''"<br />
export PATH=$JAVA_HOME/bin:$PATH<br />
<br />
<b>We do [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140955 not recommend] using JDK 1.6 on Eclipse 3.1.</b> (It works fine with Eclipse 3.2 or 3.3.) To use JDK 1.6 on Eclipse 3.1, you must add the following line to your <code>config.ini</code>file:<br />
<code><br />
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,<br />
J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6<br />
</code><br />
<br />
== What version of Mylyn is distributed with the Eclipse downloads? ==<br />
<br />
The [http://www.eclipse.org/downloads/ default Eclipse downloads] contain the following Mylyn redistributions. Since the redistributed versions can be missing important bug fixes or feature additions, we recommend using the [http://www.eclipse.org/mylyn/downloads latest version of Mylyn].<br />
<br />
* Eclipse IDE for Java Developers: all of Mylyn except Team integration (e.g. automatic change sets) integration. Install the Eclipse CVS integration and then install the latest Mylyn build to get this component.<br />
<br />
* Eclipse IDE for Java EE Developers: all of Mylyn redistribution, install manually<br />
<br />
* Eclipse IDE for C/C++ Developers: no Mylyn redistribution, install manually<br />
<br />
* Eclipse for RCP/Plug-in Developers: all of Mylyn redistributed<br />
<br />
* Eclipse Classic: no Mylyn redistribution, install manually<br />
<br />
== My tasks or queries disappeared, what do I do? ==<br />
<br />
This happens if Mylyn failed to install. First ensure that you have a correct install by following the instructions in the next section. After that, if you still do not see your tasks use the ''Task List'' view menu -> ''Restore Tasks From History...'' command (also available via ''File -> Import -> Task List''.<br />
<br />
== Installation Troubleshooting ==<br />
<br />
''' Java Persistence API Tools error when updating the JEE Eclipse Package '''<br />
<br />
If you are trying to install additional features and get this error you have hit [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194959 bug 194959] which should be resolved soon. The work-around is to check off the ''Europa Discovery Site'' and install the first two components of the ''Data Tools Platform''.<br />
<br />
''' Update failures '''<br />
<br />
On Eclipse versions earlier than 3.3 (final) use '''only the "Search for new features.."''' option when updating Mylyn. If you use "Search for updates..." the Update Manager will allow a partial install that can cause Mylyn to fail to start, and you will need to run update again. See the ''feature configuration problem'' section below for details. If you encounter this problemm consider voting for Platform [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132450 bug 132450].<br />
<br />
''' Startup exceptions '''<br />
<br />
If you see startup errors or warnings such as <code>BundleException</code> or timeout messages restart Eclipse with the <code>-clean</code> flag either on the command line, in your shortcut link, or by temporarily it into the <code>eclipse/eclipse.ini</code> file. If that does not resolve the problem please [http://www.eclipse.org/mylar/bugs.php file a bug].<br />
<br />
''' Incompatible VM (e.g. JDK 1.4) '''<br />
<br />
If you are using the wrong VM, you'll see errors like the following in your log file. <br />
<code><br />
Root exception: java.lang.UnsupportedClassVersionError:<br />
org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)<br />
</code><br />
<br />
See [[#Download_and_configure_Java_5_or_6|Configure Java]] to fix this problem.<br />
<br />
''' Incompatible version of Eclipse '''<br />
<br />
Separate versions and update sites exist [http://eclipse.org/mylyn/dl.php for Eclipse 3.1 and 3.2]), in which case you may see errors like the following in your <code><workspace>/.metadata/.log </code>file or in a Mylyn view:<br />
<code><br />
java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()<br />
The activator org.eclipse.mylar.java.MylarJavaPlugin for bundle org.eclipse.mylar.java is invalid<br />
</code><br />
<br />
''' Mylyn feature configuration problem '''<br />
<br />
If the above do not address the issue, the easiest thing to do is uninstall any old versions and update to the latest Mylyn. Your tasks won't be lost, because by default they are stored in the <code><workspace>/.metadata/.mylyn</code> folder which will be read next time Mylyn starts correctly. <br />
* First, uninstall the old version of Mylyn using ''Help -> Software Updates -> Manage Configuration''. <br />
* You need to Disable all Mylyn features by right-clicking them.<br />
* Allow Eclipse to restart after the last is disabled.<br />
* After restart, ensure that the 3rd toolbar button is pressed (figure below) so that you see the disabled features to uninstall.<br />
* Uninstall all the disabled features using the popup menu. <br />
<br />
If you don't uninstall, the the Update Manager will think that you have the latest and tell you that there are no updates. <br />
<br />
<b>Note: manually removing the plug-ins and features can lead to configuration errors.</b> <br />
<br />
After uninstalling, update Eclipse by adding the correct update site specified at on the [http://eclipse.org/mylar/dl.php download page], and after that automatically or manually updating will install the correct version.<br />
<br />
[[Image:mylar-eclipse-manage-configuration.gif]]<br />
<br />
'''What do I need to do in installation to be able to use Mylyn task management features with bug/task/issue trackers?'''<br />
<br />
When you install, make sure that you select a connector for your bug/task/issue tracking software. For example, to use Bugzilla, you have to install the Bugzilla connector component.<br />
<br />
'''I've installed Mylyn ; why can't I see anything different?'''<br />
<br />
The two most likely possibilities are:<br />
# You don't have any Mylyn views open. Select ''Window -> Show View -> Other'', then select ''Mylyn'' and you should see the available Mylyn Views. <br />
# If you still don't see anything, then perhaps you aren't using the JDK1.5 VM (or later). See [[Mylyn_Installation_Guide#Download_and_configure_Java|configuring Java]].<br />
<br />
<br />
'''What does the error "Network connection problems encountered during search" mean?'''<br />
<br />
If you get that message while trying to download Mylyn, it means that Eclipse couldn't find the location you entered. This might be because you copied something incorrectly (watch for extra characters -- even extra spaces can cause errors), or because the site went down. You may be able to see if the site is up or down by copying the URL into your Web browser.<br />
<br />
'''What does the "Update manager failure" message mean? '''<br />
<br />
It means that Eclipse could not access the update site, or that it got confused about the configuration state of your Eclipse. First try updating again to see if the update site is accessible. <br />
<br />
If you are trying to update the JIRA connector you can also try de-selecting that feature in case the <code>Tigris.org</code> update site is not accessible. Using ''Search for new features to install..'' when installing can help to avoid this problem. If that does not work see the feature configuration troubleshooting below. <br />
<br />
'''What does "Could not create Browser page: No more handles (<code>java.lang.UnsatisfiedLinkError: ...</code>)" mean?'''<br />
<br />
It probably means that you are running Linux and don't have Eclipse and a Web browser configured to work together. See [[http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux| installing a browser on Linux]].<br />
<br />
'''When downloading, why do I get a warning that the feature was unsigned?'''<br />
<br />
Signing plugins requires extra administrative details with <code>eclipse.org</code> which most plug-ins seek to avoid. <br />
<br />
'''N.B.''': Security issues with features should not be underestimated. Eclipse allows users to download new functionality from remote servers. A rogue plug-in can act as a perfect Trojan horse. It can look innocent enough and provide useful function while spawning threads in the background with full access to the local file system and the Internet (if connected). Beware of installing features from update sites you do not trust.<br />
<br />
'''What does "<code>Root exception: java.lang.UnsupportedClassVersionError: org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)</code>" mean?'''<br />
<br />
It probably means that the virtual machine is JDK1.4 or lower. See [[Mylyn_Installation_Guide#Download_and_configure_Java| download and configure Java]].<br />
<br />
'''Why am I getting messages in my <code><workspace>/.metadata/.log</code> or my Mylyn view that say things like <code>"java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()"</code> and "The activator <code>org.eclipse.mylar.java.MylarJavaPlugin</code> for bundle <code>org.eclipse.mylar.java</code> is invalid"?'''<br />
<br />
This probably means that your Mylyn download version didn't match your Eclipse download version. Note that [http://eclipse.org/mylar/dl.php the download site] has different downloads for Eclipse 3.1 and Eclipse 3.2.<br />
<br />
To fix this problem, see the [[Mylyn_Uninstallation_Guide| uninstallation guide]], then re-install from [http://eclipse.org/mylar/dl.php the correct download site].<br />
<br />
'''What does "Could not create Bugzilla editor input" and "<code>java.io.IOException</code>: SAX2 driver class <code>org.apache.xerces.parsers.SAXParser</code> not found" mean?'''<br />
<br />
It probably means that you are on MacOS, and for some reason are missing Xerces from the Mac JDK1.5. You will probably need to add it to your default classpath. Please refer to and comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=144287 bug 144287] if you see this problem.<br />
<br />
To ensure that you are using the 1.5 VM refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
'''I've just updated to Mylyn 2.0 and I don't see any tasks in my Task List'''<br />
<br />
As part of the update to Mylyn 2.0 the old data folder has been migrated to <workspace folder>/.metadata/.mylyn from the old location <workspace folder>/.mylar. IF for some reason migration failed (.mylar folder still exists), simply shut down Eclipse and manually move your old <workspace folder>/.mylar folder to <workspace folder>/.metadata/.mylyn (note the name change to .mylyn)<br />
<br />
== Configuration Troubleshooting == <br />
<br />
'''How can I change the number of editors left open before Mylyn starts closing editors?'''<br />
<br />
Turn off or increase the number of editors to leave open using ''Preferences -> General -> Editors -> Number of opened editors before closing''. Since Mylyn will manage the open editors with task activation, this number can be set higher or you can disable automatic closing entirely.<br />
<br />
'''Do I need the Outline View when running Mylyn?'''<br />
<br />
No, not really. The Package Explorer and folded signatures should provide enough context for you. If, at some point, you really need to see an Outline View, you can always enter (Ctrl+O) to show the in-place Outline View.<br />
<br />
'''What does the message "content assist proposals no longer appear" mean?'''<br />
<br />
This usually happens when uninstalling when using Eclipse 3.2. Make sure that the "Java Completions" and "Java Types" proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
'''Why do I get errors like "HTTP Response Code 407" or "Proxy Authentication Error" when accessing repositories through a proxy server?'''<br />
<br />
It is likely that you need to configure these proxy server settings. Select ''Window -> Preferences -> Install/Update'', and update the section in the "Proxy settings" section of the form.<br />
<br />
'''I can't use <code>Ctrl+Alt+Shift+Arrow Up</code> for'' Mark as Landmark''. What do I do?<br />
<br />
This is usually a Linux/GNOME problem, where the Gnome keyboard shortcuts are interfering with the Eclipse shortcuts. Go to the Keyboard shortcuts (which might be something like ''Desktop -> Control Centre -> Keyboard Shortcuts'' or ''System -> Preferences -> Keyboard Shortcuts'') and disable both of these shortcuts:<br />
* Move one workspace up<br />
* Move one workspace down<br />
<br />
See also: [[Mylyn_User_Guide#Keyboard_mappings_on_Linux| keyboard mappings on Linux]].<br />
<br />
'''How do I turn on spell checking?'''<br />
<br />
See [[Mylyn_User_Guide#Spell_Checking| spell checking]].<br />
<br />
== Uninstall troubleshooting ==<br />
<br />
When '''uninstalling in Eclipse''' Mylyn via the ''Help -> Software Updates -> Manage Configuration'' dialog you will need to uninstall dependencies first (e.g. Bugzilla Connector, Subclipse integration) and then uninstall the core Mylyn features.<br />
<br />
When '''uninstalling manually''' by deleting all of the Mylyn plug-ins and features from the <code>eclipse/plugins</code> and <code>eclipse/features</code> directory make sure to delete all of the plug-ins and then restart Eclipse with the -clean option (e.g. by inserting it into a shortcut or the <code>eclipse.ini</code> file.<br />
<br />
On '''Eclipse 3.1:''' you may need to reset the Java editor to be default for <code>.java</code> again via: ''Preferences -> General -> Editors -> File Associations''<br />
<br />
On '''Eclipse 3.2:''' if after uninstalling '''content assist proposals no longer appear''' you need to ensure that the ''Java Completions'' and ''Java Types'' proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
== I am seeing <code>java.lang.OutOfMemoryError: PermGen space </code>errors, what's wrong? ==<br />
<br />
If your Eclipse crashes, or you see the above error after installing Mylyn or other plug-ins, you have most likely hit the infamous MaxPermSize bug. This is not a Mylyn specific problem, but a general Eclipse problem that is often triggered on Eclipse 3.2 and later, if you have many plug-ins installed and are using a Sun JVM. <br />
<br />
To fix it simply add the following to your launch arguments. This is usually to your shortcut, or to the <tt>eclipse/configuration/config.ini</tt> file:<br />
<br />
-XX:MaxPermSize=128M<br />
<br />
If you are using a large number of plug-ins (e.g. WTP) you may need to increase the number to more than 128M. <br />
<br />
Details of the problem are on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250 Platform bug 92250].<br />
<br />
= Task List =<br />
<br />
== Why won't the Archive category disappear? ==<br />
<br />
The ''Archive'' category will automatically appear if a task needs to be shown, but is not in any query or category. <br />
In order to ensure that you do not miss reminders or notifications the following tasks will always be shown in the Task List, even if they have been removed from a category or a query:<br />
* Tasks scheduled for this week or overdue. Remove these by using the ''Schedule'' pop-up menu option to defer them to a future week or to clear the schedule.<br />
* Repository tasks that have incoming changes, such as comments. Remove these by reading them or marking them as "read" via the ''Mark -> Read'' pop-up menu.<br />
<br />
== The Archive category contains many irrelevant tasks, how do I clean it up? ==<br />
<br />
If you created very broad queries you could end up with thousands of tasks in the Archive category. Other than clearing the <tt>workspace/.metadata/.mylyn/tasklist.xml.zip</tt> and <code>workspace/.metadata/.mylyn/offline</code> folder (note that this will entirely reset your Task List) the easiest option is to:<br />
* Clean up your queries to include only tasks of interest (note that including completed/resolved tasks is recommended).<br />
* Turn off ''Focus on Workweek'' in the ''Task List''.<br />
* Turn off the ''Filter Archive Category'' option in the ''Task List'' view menu.<br />
* Delete all of the unneeded tasks from within the Archive category. Note that if the tasks are not matched by queries they will be deleted permanently and any local notes or scheduling information that you have added to them will be lost.<br />
<br />
== How does Mylyn count the active time for a task? ==<br />
<br />
Whenever you work on a task, Mylyn accumulates the time you spend actively working on a task. This time can be viewed in the ''Personal Planning'' section of the ''Task Editor''. When you are not interacting with Eclipse, the timing automatically times out after 3 minutes by default. This means that activity outside of Eclipse will not be captured when you work on the task and that the timings in Mylyn are a lower bound of the total time spent on the task (capturing timings for work done outside of Eclipse involves OS specific extensions).<br />
<br />
== How do I prevent long-running tasks from adding to the progress bar? ==<br />
<br />
If you have many long-running or recurring tasks scheduled for this week, they can affect the ''Task List'' weekly progress bar. This can be misleading as they may never be completed. The current work-around to prevent long-running tasks from being included in the weekly progress bar is to schedule their estimated time to be 0 (zero). Alternatively, you can schedule only the amount of time you plan on spending on that task this week.<br />
<br />
== Does the Task List replace the Eclipse Tasks view? ==<br />
<br />
The SDK's ''Tasks'' view is used for showing markers such as 'todo' tags which indicate a local problem with a resource, similar to a compiler warning. As such, these 'tasks' are at a much lower level of granularity than Mylyn's tasks, and one task could involve cleaning up multiple todos. In order to make working with only the markers in a particular task context, e.g. for clean-up before committing, the ''Apply Mylyn'' filter is available for both the ''Problems'' and the ''Tasks'' views.<br />
<br />
== What if I use multiple workspaces? ==<br />
<br />
Mylyn's support for multiple workspaces is currently limited (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130658 bug 130658] for a discussion) because the Task List is considered to be specific to the person, and not to the workspace. We recommend configuring your Eclipse workspace to use working sets instead of relying on multiple workspaces. <br />
* John O'Shea's blog: [http://www.xlml.com/aehso/2007/02/02/eclipse-workspaces-containing-projects-with-overlapping-locations-and-mylar/ Eclipse workspaces containing projects with overlapping locations, and Mylar]<br />
<br />
If using a single workspace is not possible you can do the following:<br />
* In ''Preferences -> Mylyn -> Task List'' set the ''Data Directory'' to be a shared location, and do this for both workspaces.<br />
* Be sure to avoid launching both Eclipse workspaces at the same time, as changes in one workspaces could overwrite the Task List in the other workspace.<br />
* If you upgrade Eclipse or move your workspace and don't see your tasks, check the ''Data Directory'' setting.<br />
<br />
== How do I export my task and repository data? ==<br />
<br />
Export via File > Export > Mylyn > Task Data<br />
<br />
== Why does Mylyn use the term "task"? ==<br />
<br />
There are many work items that make up the developer's workday. Many issue trackers and project management tools refer to these as: bugs, defects, actions, tickets, stories, enhancements, and the list goes on. We refer to all such work items as "tasks" because the word tasks is short and commonly used in time management tools. Task Repository connectors can customize the presentation of tasks, for example, indicating which is a defect and which is an action item.<br />
<br />
= Task Editor =<br />
<br />
== Why am I seeing strange boxes where I expect to see proper characters? ==<br />
<br />
If for example you aren't seeing the proper single quote chacters in the summary of [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=197644 bug#197644]], check that the encoding is set correctly for the repository in the asociated Task Repositories view (Properties > Additional Settings > Character Encoding). For bugs.eclipse.org/bugs set your charcter encoding to ''ISO-8859-1''.<br />
<br />
= Task Repositories =<br />
<br />
== What if Mylyn doesn't support my task/bug/issue/ticket repository? ==<br />
<br />
To see support for your repository faster, do a search of the open repository connector requests and [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Bconnector%5D&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=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= vote for the corresponding bug] if your tracker is there, or [http://www.eclipse.org/mylar/bugs.php create a new bug]. <br />
<br />
[[Mylyn_User_Guide#Generic_Web_Repository_Connector|Generic Repository Connector]], allows creating Queries to the web-based issue tracking repositories and get list of issues from the web UI into the Task List.<br />
<br />
It is also possible to link a ''local task'' with the web page in web-based repository via the Mylyn Web integration.<br />
<br />
'''To create a task from any web-based repository:'''<br />
<br />
* Drag the URL from the address bar of the browser, or from a hyperlink in a bug listing to the ''Mylyn Tasks'' view. This will create a task for the bug, link it to the page, and populate the description with the title of the corresponding page. '''In Mozilla:''' simply drag the URL. '''In Internet Explorer:''' you must have <code>Ctrl</code> pressed in order for Eclipse to recognize the drop.<br />
* '''Alternatively,''' you can copy the URL, press the ''New Task'' button on the ''Mylyn Tasks'' view. This has the same effect as above but you can edit the description after retrieving it.<br />
* Opening the task will now open the corresponding issue. You can also <code>right+click</code> the task and select ''Open in External Browser''.<br />
<br />
[[Image:mylar-tasklist-weblink-editor.gif]]<br />
<br />
== Why were my repository credentials reset? ==<br />
<br />
If you upgrade Eclipse or your Java VM, you will need to reset your credentials in the ''Task Repositories'' view because these are stored in the secure Eclipse workbench keyring. Also see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=149607 bug 149607]. If you are migrating '''from Eclipse 3.2 to 3.3''' note that you will need to use a different update site, which is listed here: http://eclipse.org/mylyn/dl.php<br />
<br />
== Why are my updated repository attributes not showing up? ==<br />
<br />
Your server's repository attributes can change frequently, for example, there can be a new "milestone" or "version" added to the Bugzilla repository with each release. When the ''Preferences -> Mylyn -> Task List -> Synchronization'' setting is enabled, every 10th synchronization will update the attributes from the repository. If you do not have this setting enabled, your can force the update via the ''Update Attributes'' action on the task repositories' context menu in the ''Task Repositories'' view. Note that you will need to reopen a task editor to see the updated attributes. If you instead update via the button on the ''Attributes'' section of the ''Task Editor'' the attribute settings will be reloaded without needing to reopen.<br />
<br />
== Authentication Troubleshooting ==<br />
<br />
You must ensure repository credentials are filled out correctly. Refer to the diagram below:<br />
<br />
[[image: AuthenticationTroubleshooting2.png|right]]<br />
<br />
# Enter the repository URL (i.e. https://bugs.eclipse.org/bugs) and an optional label<br />
# Credentials<br />
#* Usually email address and password <br />
#* Some sites, such as <code>dev.eclipse.org</code>, use anonymous logon with password left blank.<br />
#Http Authentication (optional)<br />
#* Some sites are protected by either BASIC or DIGEST http authentication. If this is the case, enter appropriate credentials here.<br />
#* One way to test if the site requires http authentication is to point your browser at the repository. If you are presented with an authentication dialog popup, the site is likely protected by http authentication.<br />
#Proxy Server Configuration (optional)<br />
#* By default Mylyn uses the Platform's Install/Update proxy settings. Uncheck this box if you wish to use an alternative proxy.<br />
#* If the proxy requires authentication, this is where you enable and enter your proxy credentials.<br />
#* If you are experiencing connection problems, ensure your Install/Update proxy settings are valid or the repository specific settings are correct<br />
#* Mylyn has been tested with HTTP proxy servers. Currently SOCKS is not supported.<br />
#Validate Settings <br />
#*Press the ''validate'' button to test the settings<br />
#*If you are seeing errors like "HTTP Response Code 407" or "Proxy Authentication Error" it is likely that you need to configure proxy settas as described above.<br />
#*If your sever uses a certificate and fails to connect, e.g. you see exceptions <tt>sun.security.validator.ValidatorException: PKIX path building failed</tt> then you need to point Eclipse at your certificate, see the [http://ahtik.com/blog/2006/05/11/fixing-eclipse-mylar-jira-integration/ instructions on this blog].<br />
<br clear="all" /><br />
<br />
=== NTLM authentication ===<br />
<br />
For NTLM authentication to work a special format for the username needs to be used where ''DOMAIN'' needs to be replaced by the Windows login domain: <br />
<br />
DOMAIN\username <br />
<br />
The built-in NTLM support of the JDK which is used by Eclipse does '''not work''' with Mylyn since it uses the HttpClient library to access repositories. Limitations in regard to NTLM authentication are documented in the [http://wiki.apache.org/jakarta-httpclient/FrequentlyAskedNTLMQuestions NTLM FAQ] and also discussion on {{bug|201911}}.<br />
<br />
* If your repository uses MS NTLM authentication and only standard http authentication is being passed to the repository this can result when the local hostname cannot be resolved. Ensure your machine's hostname is set correctly and resolves to a valid address.<br />
* It is not possible to use NTLM authentication for the proxy as well as for the repository.<br />
<br />
If NTLM authentication fails the '''[http://ntlmaps.sourceforge.net/ NTLM Authorization Proxy Server]''' has been reported to '''work''' with Mylyn.<br />
<br />
== Why are task hyperlinks not working? ==<br />
<br />
For task hyperlinks in textual editors (e.g. Java editor) and other text viewers (e.g. History view comments) you must associate the project that contains the resource to the task repository. <br />
<br />
:''Project association can also come from 3rd party metadata trough the contrubuted [[Mylar_Integrator_Reference#Mapping_from_projects_to_Task_Repositories|extension point]]. [http://subclipse.tigris.org/ Subclipse] and [http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Mylyn Maven integration for Eclipse] plugins contributing it. See few more details [http://jroller.com/page/eu?entry=linking_projects_from_the_eclipse here].''<br />
<br />
Note that to view a hyperlink you must hold down the <code>Ctrl</code> key when hovering over the reference to the task. References to tasks are connector specific and the common reference is found on the top left of the task editor and other conventions tend to follow those used in the web UI (e.g. "bug 123" for Bugzilla, "ABC-123" for JIRA).<br />
<br />
[[Image:mylyn-project-repository-association.gif]]<br />
<br />
= Bugzilla Connector =<br />
<br />
== What versions are supported? ==<br />
<br />
We recommend using the latest [http://www.bugzilla.org/download/ release] of Bugzilla.<br />
<br />
* '''Bugzilla 2.18.6 is the lowest version of Bugzilla supported'''. If you are getting errors that indicate failure to update attributes this may be an indication that the Bugzilla server is not supported (< 2.18.6).<br />
<br />
*If you are using '''Bugzilla 2.18''' and are getting '''mid-air collisions''' this is likely due to incorrectly formatted timestamp field in the underlying bugs database table ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149513 bug 149513]). This can be resolved by upgrading to Bugzilla 2.20 or later.<br />
<br />
== Why are queries failing? ==<br />
<br />
*If '''queries are not working''' correctly ensure that you have the right Bugzilla server version selected for the corresponding repository: ''Task Repositories (View) ->'' right+click the repository ''-> Properties''. For supported versions see the [http://www.eclipse.org/mylar/dl.php download page]. If the repository is still not functioning it may be due to authentication or connectivity problems. If that does not resolve the problem please post a message to the newsgroup or [http://www.eclipse.org/mylar/bugs.php submit a bug].<br />
<br />
== Why do I see my old username? ==<br />
<br />
If you change the username/email address on your Bugzilla account you may notice that some tasks still have the old username/email. Explicitly synchronize the task via the ''Task List'' popup menu or ''Task Editor'' toobar in order to update your username.<br />
<br />
== Why do tasks fail to open? ==<br />
<br />
*If upon opening a bug, the Bugzilla tab only displays a warning "'''Could not download task data, possibly due to timeout or connectivity problem. Please check connection and try again.'''", ensure that your repository is returning XML data by pointing your browser to <code><your-repository-url>/show_bug.cgi?id=1&ctype=xml</code> to show the contents of bug 1 in XML form. The Bugzilla client requires that bugs be accessible in XML form. If the repository doesn't support xml then it is likely that the repository is too old (Mylyn currently supports Bugzilla 2.18 and later).<br />
<br />
* If '''reports fail to load''' or '''reports fail to synchronize''' (task description remains ''italic''), check the error log for a "'''File not found'''" error pointing to <code>bugzilla.dtd</code> or a "'''Failed to retrieve products from server'''" error message - these result when the <code>urlbase</code> parameter is not set on the bugzilla server, or your bugzilla installation is missing the <code>bugzilla.dtd</code> file. See: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=161759 bug#161759]<br />
<br />
* If '''attributes are missing options''' in the bug editor (ie. missing a recently added milestone, [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155431 bug# 155431]):<br />
** Update attributes by choosing ''Update Attributes'' from the context menu in the ''Task Repositories'' view<br />
** Synchronize the task in the Task List<br />
** Reopen the task - new options should be available.<br />
<br />
== Why do tasks fail to submit? ==<br />
<br />
* '''Error upon submit: unable to make any match for name/email entered.''' If your bugzilla is configured for user names rather than full email address the QA Contact field will cause the submit to fail ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=166555 bug# 166555]). To resolve, select 'Local users enabled' option on the Repository Configuration page. <br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your account's username and password and are not using the HTTP authentication fields instead.<br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your bugzilla instance's cookie domain under the required settings. The cookie domain must lead with a dot.<br />
<br />
* If '''attachments are failing to submit''' and you see that after processing the attachment, the bugzilla bug shows a size of "bytes" (no numbers), your database may be dropping the packet sending the file. '''On MySQL''', check the [http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html max_allowed_packet directive]. You may see errors like: <code>DBD::mysql::st execute</code> failed: Got a packet bigger than 'max_allowed_packet' bytes [for Statement "INSERT INTO attach_data (id, thedata) VALUES (38, ?)"] at <code>/path/to/bugzilla/attachment.cgi</code> line 993. Also, '''check the maximum attachment size''' in ''Bugzilla Parameters -> Attachments''.<br />
<br />
* If a submit fails with an '''Invalid Username or Password''' error even though repository settings do validate, make sure that cookies could be set. See also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175502 bug 175502]<br />
<br />
== What time zone is used in the task editor? ==<br />
<br />
*The '''times''' that appear in the Bugzilla bug editor (ie. created, modified) '''are local to the server hosting the Bugzilla repository''', not your local machine's time zone. <br />
<br />
== Known limitations ==<br />
<br />
* The <code>usermatchmode</code> is not currently supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168204 bug 168204]) and as such full email addresses need to be used.<br />
<br />
* The <code>usevisibilitygroups</code> parameter is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=180876 bug#180876]). Group assignment will currently be lost if updated using the Bugzilla rich task editor.<br />
<br />
* Version 1.0 of Mylyn presents an error message upon new comment submission to RedHat's public Bugzilla repository. The comment is in fact posted. This issue is resolved in Mylyn 2.0M2 and higher. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=183251 bug#183251])<br />
<br />
= JIRA Connector =<br />
<br />
If you see errors like the following, work around this by opening repository ''Properties Page'' and clicking OK (bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169102 169102]).<br />
<br />
org.tigris.jira.core.service.exceptions.AuthenticationException<br />
at org.tigris.jira.internal.core.service.soap.SoapJiraService.getProjectsNoSchemes(SoapJiraService.java:204)<br />
<br />
== What are the server requirements? ==<br />
<br />
The '''JIRA SOAP/RPC services have to be running on the JIRA server''':<br />
<br />
* Jira 3.3.3 or higher (3.7 or higher for attachment retrieval)<br />
* Jira RPC plugin 1.4.3 or higher<br />
<br />
Latest information also available on the [http://www.eclipse.org/mylar/dl.php download page].<br />
<br />
Related Resources:<br />
<br />
* [http://confluence.atlassian.com/display/JIRA/JIRA+Development+Hub Jira Development Wiki]<br />
* [http://confluence.atlassian.com/pages/viewpage.action?pageId=1035 Jira RPC Plugin Overview]<br />
<br />
== Why can't I connect? ==<br />
<br />
* If you get a <code>org.tigris.jira.core.service.exceptions.ServiceUnavailableException</code> you need to turn on the JIRA SOAP/RPC services on the server.<br />
* Similarly, if you get a "Processing instructions are not allowed within SOAP messages" message, ensure that SOAP/RPC services are on.<br />
* If you get a '''503''' error code verify that the SOAP/RPC interface is enabled.<br />
* If you get a '''403''' error code verify that the SOAP/RPC interface is enabled, and also check your authentication mechanism. If the server is using NTLM authentication, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156397 bug 156937] for diagnosis steps.<br />
* If you see an '''"unrecognized priority" message''' in the ''Error Log'', the problem is that the JIRA Connector does not support customized priorities so the priority value specified in that message will not correspond to the priority icons visible in the Task List.<br />
* If you are being '''prompted for your log-in credentials''' by the Browser tab of the task editor or the new task editor, this is because without rich editor support the connector is using the web-based UI instead of logging in on your behalf as is done with a rich task editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142869 bug 142869]).<br />
* If you get a <CODE>AuthenticationException</code> and a query won't synchronize, use Task Repositories (view) -> Properties (on the repository) -> Validate Settings. This will clear the connection if it died.<br />
<br />
<!-- HEAVILY OUTDATED. PLUGIN NOW USES COMMON PROXY INFRASTRUCTURE<br />
== Why can't I synchronize when using a proxy server? ==<br />
<br />
* Proxy configuration is '''based on the normal Java HTTP system properties''', which can be configured either by launching Eclipse with <code>-vmargs</code> and using the following settings, or by putting these settings into the or by putting the following into the <code>eclipse/eclipse.ini</code> file (after -vmags):<br />
-Dhttp.proxyHost=<host> <br />
-Dhttp.proxyPort=<port><br />
* Make sure that when using these settings you do not enable the proxy settings on the ''Install/Update'' preference page, since they may override these settings.<br />
* If you are using '''SSL''', you will also need to set the <code>https.proxyHost</code> and <code>https.proxyPort</code>. <br />
* Authentication is configured with the <code>http.proxyUser</code> and <code>http.proxyPassword</code> system properties (also for SSL)<br />
* You can also use <code>http.nonProxyHosts</code> system property to enumerate hosts that should not be proxied. Note that matching is implemented on the exact host name used for JIRA server and patterns are not supported. --><br />
<br />
== Known limitations ==<br />
* Attachment retrieval (including retrieval of the task context and attachment list in the task editor) require JIRA 3.7 or above ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=169757 bug 169757])<br />
<!-- * NTLM authentication is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172395 bug 172395]) --><br />
* Customized priorities are not currently supported, so all issues with a customized priority will have the default priority level ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=165518 bug 165518]).<br />
* blank but editable custom fields doesn't appear in the RSS data, and as result we can't show them for editing<br />
* because of JIRA api limitations, we can support custom fields in the task editor, but not in the new custom task editor<br />
<!-- * On JIRA 3.6.x private filters saved on the server can fail to retrieve results ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=174328 bug 174328]). The work-around is to create a custom query in Mylyn using the form-based query designer or to share the filter in JIRA. --><br />
<br />
== How can I enable compression for SOAP messages? ==<br />
<br />
If your repository has lots of projects and components you can speed up the download of the repository configuration by enabling compression. <br />
<br />
* Add a filter-mapping to your JIRA server configuration: [http://jira.atlassian.com/browse/JRA-10353].<br />
* Enable compression in your global JIRA configuration.<br />
* Check the compression setting for your task repository in Mylyn versions 2.0M2 and later.<br />
<br />
== Reporting issues ==<br />
<br />
Since JIRA can be heavily customized there is a chance that some particular customizations may not work, so if you can't connect to your proprietary repository it is a good idea to try the following public repositories to make sure you have working configuration:<br />
<br />
* http://jira.codehaus.org<br />
* http://issues.apache.org/jira/<br />
* http://opensource.atlassian.com/projects/spring <br />
<br />
If you can't get query results, you could try to call "Open with Browser" on query node in the Task List view and then save link "Current view: XML" and attach it to the bug report.<br />
<br />
Even if query don't work you could try "Open Repository Task" from your JIRA repository node on the Task Repositories view and check if you can open JIRA task editor for that issue. Same for the Task search (Ctrl-H, Task Search)<br />
<br />
To investigate various error you may need to enable debug tracing. To do that you need to create the <code>.options</code> file with the following content:<br />
<br />
<pre><br />
org.eclipse.mylyn.jira.ui/connector=true<br />
org.eclipse.mylyn.jira.ui/dataHandler=true<br />
</pre><br />
<br />
and then add the following options to the Eclipse command line (or eclipse.ini file):<br />
<br />
<pre><br />
-debug <path to the .options file>/.options<br />
</pre><br />
<br />
The additional logging will go into the regular Eclipse log and the Error Log view<br />
<br />
== Why do I get errors about an unexpected redirect when submitting an issue? ==<br />
<br />
Please go to the repository properties and validate the repository. If errors about circular redirects are logged in your Eclipse error log your JIRA server or proxy might be misconfigured. Please see {{bug|202834}} for a more details.<br />
<br />
= Trac Connector =<br />
<br />
== What are the server requirements? ==<br />
<br />
The Trac connector offers two access methods:<br />
<br />
'''XML-RPC''' (recommended)<br />
<br />
Requirements:<br />
* Trac 0.10<br />
* [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] rev. 1950<br />
<br />
This access method offers editing of tasks in a rich editor, attachment support and offline editing. It requires the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] for Trac to be enabled for the accessed repository. The XmlRpcPlugin provides a remote interface to the Trac repository and is distributed separately from Trac (see [http://trac.edgewall.org/ticket/217 #217]). See these [http://trac-hacks.org/wiki/XmlRpcPlugin#Installation install instructions] for requirements and documentation.<br />
<br />
'''Web''' <br />
<br />
Requirements:<br />
* Trac 0.9 or later<br />
<br />
In this mode the standard Trac web interface is used for repository access. Tickets may be created and edited through a web browser. Offline editing and attachments are not supported.<br />
<br />
== Recommended Trac version ==<br />
<br />
Mylyn should work with any stable release Trac release that is version 0.9.x or 0.10.x (see below for known limitations). Mylyn works best when used with Trac's XML-RPC Plugin (see above) but we do not recommend a particular Trac version. <br />
<br />
The Trac connector tests are run against these Trac versions:<br />
<br />
* Trac 0.10.4, XML-RPC Plugin rev. 1950<br />
* Trac 0.9.6<br />
<br />
See {{bug|175211}} for details about Trac 0.11 support.<br />
<br />
== Why do I get an HTTP Error 500 Internal server error when creating a ticket that contains non-ASCII characters? ==<br />
<br />
Problems related to character encodings have been reported when Trac is run with Python 2.3. Upgrading to Python 2.4 may help to resolve this. Please comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=188363 bug #188363] if you encounter an internal server error when creating a ticket that contains non-ASCII characters.<br />
<br />
== Known limitations ==<br />
<br />
* Trac 0.10.1 <br />
** Known incompatibility with Trac XML-RPC Plugin. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164272 bug 164272] for details.<br />
* Trac 0.10.3 <br />
** Known incompatibility with old versions of the Trac HttpAuthPlugin (fixed in revision 1890 or later). The plug-in enables basic auth for XML-RPC when Trac AccountManagerPlugin for form based authentication is used. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168413 bug 168413] for details.<br />
* Trac 0.11<br />
** Currently untested.<br />
** Known incompatibility with Trac XML-RPC Plugin See [http://trac-hacks.org/wiki/XmlRpcPlugin] for details.<br />
<br />
== Why are tasks opened in a web browser and not in the rich editor? ==<br />
<br />
Please make sure that the access type in the repository properties is set to XML-RPC. This requires Trac 0.10 and XML-RPC (see above).<br />
<br />
== Which URLs does Mylyn access in a Trac repository? ==<br />
<br />
XML-RPC:<br />
<br />
* The expected URL is either /xmlrpc or /login/xmlrpc (if login credentials are provided)<br />
<br />
Web:<br />
<br />
* Authentication: /login <br />
* Querying: /query?format=tab...<br />
* Synchronizing ticket details: /ticket/...<br />
* Getting repository configuration to populate query dialog: /query or /newticket<br />
<br />
The web mode relies on screen scraping and is likely to fail if the design<br />
(i.e. HTML output) of the Trac repository is heavily customized.<br />
<br />
= Generic Web Repository Connector =<br />
<br />
== Where can I find the web repository connector ==<br />
<br />
It is available from the extensions update page. Please see http://www.eclipse.org/mylyn/downloads/<br />
<br />
== Why can't I connect using one of the existing templates? ==<br />
<br />
<br />
The Web Repository Connector have a Preview option in Advanced Configuration section on the Query preferences. If you get an error or preview table does not show expected list of tasks you can use Query Pattern like (.+?)(\n) to see content of the retrieved page and compare it with the source of the web page for the same url loaded into the web browser.<br />
<br />
If that does not help then you could use the wget tool (on Windows it available as a standalone command line tool and also included with Cygwin).<br />
<br />
Run the following command:<br />
<br />
<pre>wget -v -d -o query.log -O query.html "http://your.query.url"</pre><br />
<br />
If repository require basic http auth, you'll need to use ''--http-user=USER'' and ''--http-password=PASS'' options.<br />
<br />
Then open file ''query.html'' in the web browser and check if it show list of issues you need to fetch from the web server. If it does have correct list, then there could be a problem with query pattern used for parsing. <br />
<br />
A popular mistake is an unmasked '?' that separates request parameters in the url). For example:<br />
<br />
<pre><a href="show_bug.cgi\?id\=(.+?)">.+?<span class="summary">(.+?)</span></pre><br />
<br />
If ''query.html'' does not show expected list of issues you can check ''query.log'' for server responses and try to identify if server require authentication, redirecting your requests somewhere or issue any other errors.<br />
<br />
== Known limitations ==<br />
<br />
* In Mylyn 1.0: if a web server responds by requesting a redirect to an absolute URL while fetching a resource, the connector falsely prepends "/" to the URL and the request will fail. The workaround is to use final url where redirect is pointing to (you can find it as describe above). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=167282 bug 167282] for details.<br />
<br />
= Task-Focused UI =<br />
<br />
== What is the Task-Focused UI? ==<br />
<br />
When you activate a task, Mylyn automatically maintains a task context by monitoring your interaction. The task context provides a predictable degree-of-interest weighting of the relevance of the elements and relations that you work with to the task-at-hand (as described in the [http://kerstens.org/mik/publications/2006-11-mylar-fse.pdf Foundations of Software Engineering conference paper]). The Task-Focuse UI is the mechanism by which Mylyn presents Mylyn the task-context model in order to reduce information overload and to automate the manaul management of UI elements like editors and change sets. Examples:<br />
* Filtering, decoration and expansion management in views<br />
* Automatic folding in editors<br />
* Ranking in content assist<br />
* Editor management<br />
* Perspective management<br />
* Change set management<br />
<br />
== Why do files disappear from Focused views when I close them? ==<br />
<br />
By default Mylyn automatically manages the set of open files to match the task context, so that you don't have to. This ensures that the editor list (viewable via mechanisms like Ctrl+E) corresponds to what you in views like the ''Package Explorer'' when they are in Focused mode. When you close a file manually, you express that it is uninteresting, and as such it will be removed from the task context. It will also disappear from the corresponding automatically managed change sets for the same reason. This behavior can be turned off via ''Preferences -> Mylyn -> Context -> Manage open editors to match task context''. However, it is highly recommended since Mylyn will prevent the number of editors from bloating by automatically closing editors for elements that have decayed in interest, and always keep the editors for interesting elements open.<br />
<br />
<br />
== Why did all my editor tabs disappear? ==<br />
<br />
When you deactivate a task, all editors will be closed, and then when you reactivate the task all the windows will be open again. Try it, it's fun. <br />
<br />
Mylyn actively manages your open editors with task context. It takes some getting used to, but enables switching between tasks when you are multitasking without cluttering your editor tabs. This editor management can be disabled via ''Window -> Preferences -> Mylyn -> Context''. However, before disabling it consider reading the ''"Managing open editors..."'' section of [http://www-128.ibm.com/developerworks/java/library/j-mylar2/index.html#N10116 Task-focused programming with Mylar].<br />
<br />
== How do I get rid of an element if it is not interesting? ==<br />
<br />
When a view is focused elements will disappear on their own if they are not repeatedly selected via a mechanism called interest decay. Note that decay does not use the wall clock, but instead relies on the number of selections that you have made when working on that task to determine which elements disappear. This helps make it feel very predictable.<br />
<br />
If you want want to force one or more elements to disappear from the context use the '''Remove from Focus''' action on the context menu. Note that the element will still be part of the task context since it was previously part of the interaction. <br />
<br />
If you want to permanently delete the element from the interaction history use the '''Remove from Context''' action on the '''Context''' tab of the '''Task Editor'''. For example, if a company private element was part of a task context that is to be shared with a public repository, this action can be used to clean it up before sharing. Note that elements will be removed from the task context recursively.<br />
<br />
== Which Focused UI features can I turn off? ==<br />
<br />
'''All of them.''' When no task is active neither are any of Mylyn's features. When working with task contexts Mylyn's Focused UI features are all optional and in general configurable. While many find it the key benefit of Mylyn, the entire Focused UI is optional and can be uninstalled via ''Help -> Software Updates -> Manage Configuration''.<br />
<br />
The following table summarizes how the key features can be toggled:<br />
<br />
<table><br />
<tr><br />
<td>'''UI Mechanism'''</td><br />
<td>'''Example/description'''</td><br />
<td>'''Toggle using'''</td><br />
</tr><br />
<tr><br />
<td>Interest filtering</td><br />
<td>Package Explorer</td><br />
<td>''Apply Mylyn'' button on view toolbar</td><br />
</tr><br />
<tr><br />
<td>Automatic toggling of filtering</td><br />
<td>Package Explorer</td><br />
<td>''Preferences -> Mylar -> Context -> Toggle focused mode..</td><br />
</tr><br />
<tr><br />
<td>Interest decoration</td><br />
<td>Bolding of landmark elements</td><br />
<td>''Preferences -&gt; General -&gt; Appearance -&gt; Label Decoration''</td><br />
</tr><br />
<tr><br />
<td>Content assist</td><br />
<td>Ranking of interesting elements</td><br />
<td>Eclipse 3.2: ''Java -&gt; Editor -&gt; Content Assist -&gt; Work in Progress -&gt;'' turn off Mylyn, turn on Java</td><br />
</tr><br />
<tr><br />
<td>Active change sets</td><br />
<td>Grouping of changes by tasks</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Team''</td><br />
</tr><br />
<tr><br />
<td>Editor management</td><br />
<td>Auto opening/closing of editors</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Editor Management''</td><br />
</tr><br />
<tr><br />
<td>Active views</td><br />
<td>Active Search and Hierarchy</td><br />
<td>Only on if view is active</td><br />
</tr><br />
</table><br />
<br />
For additional configuration options see the ''Mylyn'' and ''General -> Appearance'' preference pages.<br />
<br />
== What is the performance profile of the Focused UI? ==<br />
<br />
The goal is for Mylyn to have '''no noticeable effect''' on Eclipse's speed or memory usage.<br />
You do not need to increase the amount of memory Eclipse runs with to use Mylyn. <br />
Any performance issue should be [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Mylyn reported as a bug]. <br />
<br />
The current '''Performance Profile''' is:<br />
<br />
# Mylyn only runs if a task is active, and has no impact on Eclipse if no task is active.<br />
# Task context models have negligible memory overhead. <br />
# When a task is active, additional view refresh is required to update the views based on interest model changes. This should not be noticeable on Windows where refresh is very quick, but could be more noticeable on other platforms.<br />
# The time to activate a task context is dominated by the time it takes Eclipse to open the editors in the context. You can set the preference for how many editors to open in the Mylyn preference page (e.g. setting to 1 will dramatically reduce activation time, but also remove the benefit of having open editors correspond to the task context). You can also turn off editor management entirely in the Mylyn Tasks view pull-down.<br />
# Eclipse startup is slowed down by (4) if a task is active when Eclipse is shut down.<br />
# The low priority background searches that the Active Search view runs can be noticeable on slower machines.<br />
<br />
== What happened to the Active Search and Active Hierarchy views? ==<br />
<br />
These views were not included in the Mylyn 1.0 release because they never made it beyond the experimental phase. <br />
* The ''Active Search'' view has not been sufficiently tuned to adapt to the lifecycle of a task context, and as a result requires manual manipulation of the degree-of-separation scope as you work on long-running tasks. Otherwise it becomes overloaded with elements. In addition, it is not yet clear whether an additional view is the right UI for this facility, and it is hard to find room for an additional view of this size on screen resolutions of 1600x1200 and smaller.<br />
* The ''Active Hierarchy'' view is also hard to allocate space for, especially when using the in-place hierarchy (Ctrl+T) on a landmark can be a quick way to see the relevant part of the task context's hierarchy.<br />
<br />
These features still show promise in displaying task context and saving repetitive searches, so we have not removed them. They have instead moved to the Mylyn Sandbox, and can be used and experimented with by following the [http://wiki.eclipse.org/index.php/Mylyn_Contributor_Reference#Sandbox instructions on the Contributors page]. For feedback on these views please use the corresponding bug reports or newsgroup.<br />
<br />
= Java Development =<br />
<br />
== Content assist troubleshooting ==<br />
<br />
Mylyn uses custom Content Assist processors in order to rank and separate the elements in the current task context. To see proposals ranked according to interest you must have only the ''Type Proposals (Mylyn)'' kinds checkbox enabled in the list below, otherwise you will see duplicates. '''If you do not see any proposals, check this list''' to ensure that either the Mylyn or the plain proposals are enabled. '''To do this automatically''', run ''New -> Mylyn -> Recommended Preferences''. Or you can select them manually as in the preference page below. <br />
<br />
[[Image:mylar-content-assist-prefs.gif]]<br />
<br />
'''Why do I see duplicate proposals?'''<br />
<br />
Ensure that you have only the ''(Mylyn)'' proposals kinds enabled in ''Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced'', otherwise you will see duplicates.<br />
<br />
If you use proposals via Ctrl+Shift+Space instead of the typical Ctrl+Space you will see duplicates. Vote for JDT/Text [https://bugs.eclipse.org/bugs/show_bug.cgi?id=147781 bug 147781] if you use this mechanism. Also see: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=129080 bug 129080]<br />
<br />
'''Why do I get an error message when using content assist?'''<br />
<br />
If after invoking Content Assist you see an error message dialog that states:<br />
The extension took too long to return from the 'computeCompletionProposals()' operation<br />
this is most likely due to something interrupting the proposal operation (e.g. garbage collection). Ignore it if it does not recur, increase Eclipse's memory if it does (e.g via <code>-Xmx384M</code> command line argument). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=141457 bug 141457] for more details.<br />
<br />
== Why do interesting elements not show in the Project Explorer? ==<br />
<br />
The ''Package Presentation -> Hierarchical'' mode is not supported on the ''Project Explorer'' view in Eclipse 3.2 through 3.3M3 and possibly later versions (https://bugs.eclipse.org/bugs/show_bug.cgi?id=161362 bug 161362). Use the view menu to set ''Package Presentation -> Flat'' as a work-around.<br />
<br />
== How do I stop declarations from showing in the Package Explorer? ==<br />
<br />
If you don't like Mylyn's constant showing of Java members in the ''Package Explorer'', select the drop-down menu, then ''Filters...'' and enable the ''Mylyn Java Declarations Filter''. It will then stick in the menu in case you want to toggle between modes. Note that this will hide interest information about members that aren't in your current file (e.g. showing you which methods are landmarks) so this mode is not recommended, but can be useful for <code>1024x768</code> screen resolutions.<br />
<br />
[[Image:mylar-java-filtering-declarations.gif]]<br />
<br />
== Why does nothing show up in the Active Search or Active Hierarchy? ==<br />
<br />
As you work, elements become Landmarks (bold decoration), and these elements populate the ''Active Search'' and ''Active Hierarchy'' views. To force an element to populate the views manually, make it a Landmark by <code>right+clicking</code> or hitting <code>Ctrl+Alt+Shift+UpArrow</code>.<br />
<br />
== Known limitations ==<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=106678 Bug 106678]: The Project Explorer's Hierarchical Java package presentation layout is not supported on Eclipse 3.3Mx, and interesting elements will be hidden if enabled. Work-around is to use the default Flat package presentation.<br />
<br />
= Team Support =<br />
<br />
== Why does task change set not appear when I modify files? ==<br />
<br />
A task change set should appear if you activate a task and modify a file connected to a compatible source repository (e.g. CVS, SVN). If it does not try the following:<br />
<br />
* Ensure you have installed the [http://www.eclipse.org/mylyn/downloads/ ''Mylyn Bridge: Eclipse SDK'' feature]. Note that this feature is not currently distributed with the Java-only Eclipse download ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191793 bug 191793] ).<br />
<br />
* Verify that the [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuring_the_Synchronize_view_for_change_sets configured ''Synchronize View'' is configured for change sets].<br />
<br />
If the above are working but the change set appears to be missing relevant files:<br />
<br />
* You may be seeing the ''Synchronize'' view's refresh problem ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142395 bug 142395]). Toggle from ''Incoming/Ougtoing'' to ''Incoming'' mode and back again to refresh the view.<br />
<br />
* If the files or change set are still missing deactivate and reactivate the task to force a full refresh.<br />
<br />
== Why do files disappear from the change set when I close them? ==<br />
<br />
If you have the ''Preferences -> Mylyn -> Context -> Manage open editors to match task context'' option enabled, Mylyn will perform editor management so that you don't have to. Closing a file makes it less interesting, and causes it to disappear from the active task context, and hence from the change set. This option prevents you from having to manage the set of open files, will automatically close editors for files that become uninteresting, and will ensure that the open editors match the task context.<br />
<br />
== Why am I missing elements when I retrieve someone else's context? ==<br />
<br />
To identify elements within a project, Mylyn relies on the name of the project being consistent across workspaces. If the project name in the workspace that the context was created with is different than its name in your workspace, the task context will not show elements within that project ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164058 bug 164058]). The other case where context can be lost is if the elements change names outside of the workspace ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164243 bug 164243]).<br />
<br />
The work-around is to use the same project names across your team's workspaces. We recommend the following two approaches for standardizing on project names:<br />
* Use '''Team Project Sets''': these are a very useful Eclipse facility that allows your entire team to check out numerous projects from version control by importing a single file. Create a project set via ''File -> Export -> Team Project Set'', host this file somewhere accessible, then have others import vai ''File -> Import -> Team Project Set''.<br />
* Have developers check out projects into their workspace without renaming them. The above is a shortcut for doing this. If alphabetical sort order in the ''Package Explorer'' is a problem, organize your projects via ''Project Explorer -> view menu -> Top Level Elements -> Working Sets''.<br />
<br />
= Misc =<br />
<br />
<br />
<br />
== How does Mylyn relate to IBM's Jazz? ==<br />
<br />
At the EclipseCon and JavaONE 2006 conferences IBM demonstrated previews of Jazz, a collaborative team server and Eclipse-based client. Articles have remarked on the similarities between Mylyn and Jazz because both integrate tasks into Eclipse (Jazz's "work items" and Mylyn's "tasks"), and both provide change sets grouped by task. But there are both significant differences and complementary aspects to the two approaches. A key goal of Mylyn is to provide an open source framework to support integration of task management with ''existing issue trackers and source repositories''. According to the presentations, components that come with Jazz include include a ''next-generation issue tracker and source repository'' and related lifecycle management tools such as project health. In addition, a driving and unique goal of Mylyn is to focus the UI around a usage-based and degree-of-interested weighted task context, which is complementary to the Jazz platform. Just as it integrates with Mylyn's Task List, Mylyn's Task Focused UI and task context model components are possible to integrate with other kinds of task management systems, such as the one provided by Jazz.<br />
<br />
Update: at EclipseCon 2007 the IBM Jazz team showed a Mylyn connector for Jazz.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/FAQ&diff=49808Mylyn/FAQ2007-09-10T05:07:35Z<p>Steffen.pingel.eclipse.org: /* NTLM authentication */</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
[[Mylyn User Guide]], <br />
[http://eclipse.org/mylyn Mylyn Home],<br />
[http://wiki.eclipse.org/index.php?title=Special:Userlogin&returnto=Special:Userlogout Log in to edit]<br />
<br />
For instructions on [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Download_Mylar downloading] [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installation installing] and [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuration configuring] <br />
Mylyn, see the [[Mylyn User Guide]]. For instructions on developing and contributing to Mylyn, see the [[Mylyn Contributor Reference]].<br />
<br />
= Installation =<br />
<br />
== What versions of Eclipse are supported? ==<br />
<br />
See the [http://eclipse.org/mylyn/dl.php download page].<br />
<br />
Mylyn also relies on a web browser that works with the Standard Widget Toolkit; Windows and MacOS users are fine, but Linux users might have to download another browser. See [http://www.eclipse.org/swt/faq.php#browserlinux the SWT Browser guide] for which browsers will work. See [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux installing browser on Linux] for installation instructions.<br />
<br />
== What version of Java is required? ==<br />
<br />
Mylyn needs the '''Java 5''' virtual machine.<br />
<br />
To check the version of the Java virtual machine that Eclipse was launched with to to ''Help -> About Eclipse SDK -> Configuration Details'' and verify that the java.vm.version is 1.5. <br />
<br />
Mac users should refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
* If you do not have Java 5, you can download it from [http://72.5.124.55/javase/downloads/index.jsp Sun's web site]. <br />
* If you have more than one VM, you need to specify that Eclipse should use the JDK1.5 VM. <br />
<br />
In Unix, set the environment variable <code>JAVA_HOME</code> to the root of the JDK1.5 installation and/or set the <code>PATH</code> variable to put the JDK1.5 executable directory before any other VM executable directories. For example, under <code>bash</code> in Unix:<br />
export JAVA_HOME="''(location of JDK1.5 root)''"<br />
export PATH=$JAVA_HOME/bin:$PATH<br />
<br />
<b>We do [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140955 not recommend] using JDK 1.6 on Eclipse 3.1.</b> (It works fine with Eclipse 3.2 or 3.3.) To use JDK 1.6 on Eclipse 3.1, you must add the following line to your <code>config.ini</code>file:<br />
<code><br />
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,<br />
J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6<br />
</code><br />
<br />
== What version of Mylyn is distributed with the Eclipse downloads? ==<br />
<br />
The [http://www.eclipse.org/downloads/ default Eclipse downloads] contain the following Mylyn redistributions. Since the redistributed versions can be missing important bug fixes or feature additions, we recommend using the [http://www.eclipse.org/mylyn/downloads latest version of Mylyn].<br />
<br />
* Eclipse IDE for Java Developers: all of Mylyn except Team integration (e.g. automatic change sets) integration. Install the Eclipse CVS integration and then install the latest Mylyn build to get this component.<br />
<br />
* Eclipse IDE for Java EE Developers: all of Mylyn redistribution, install manually<br />
<br />
* Eclipse IDE for C/C++ Developers: no Mylyn redistribution, install manually<br />
<br />
* Eclipse for RCP/Plug-in Developers: all of Mylyn redistributed<br />
<br />
* Eclipse Classic: no Mylyn redistribution, install manually<br />
<br />
== My tasks or queries disappeared, what do I do? ==<br />
<br />
This happens if Mylyn failed to install. First ensure that you have a correct install by following the instructions in the next section. After that, if you still do not see your tasks use the ''Task List'' view menu -> ''Restore Tasks From History...'' command (also available via ''File -> Import -> Task List''.<br />
<br />
== Installation Troubleshooting ==<br />
<br />
''' Java Persistence API Tools error when updating the JEE Eclipse Package '''<br />
<br />
If you are trying to install additional features and get this error you have hit [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194959 bug 194959] which should be resolved soon. The work-around is to check off the ''Europa Discovery Site'' and install the first two components of the ''Data Tools Platform''.<br />
<br />
''' Update failures '''<br />
<br />
On Eclipse versions earlier than 3.3 (final) use '''only the "Search for new features.."''' option when updating Mylyn. If you use "Search for updates..." the Update Manager will allow a partial install that can cause Mylyn to fail to start, and you will need to run update again. See the ''feature configuration problem'' section below for details. If you encounter this problemm consider voting for Platform [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132450 bug 132450].<br />
<br />
''' Startup exceptions '''<br />
<br />
If you see startup errors or warnings such as <code>BundleException</code> or timeout messages restart Eclipse with the <code>-clean</code> flag either on the command line, in your shortcut link, or by temporarily it into the <code>eclipse/eclipse.ini</code> file. If that does not resolve the problem please [http://www.eclipse.org/mylar/bugs.php file a bug].<br />
<br />
''' Incompatible VM (e.g. JDK 1.4) '''<br />
<br />
If you are using the wrong VM, you'll see errors like the following in your log file. <br />
<code><br />
Root exception: java.lang.UnsupportedClassVersionError:<br />
org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)<br />
</code><br />
<br />
See [[#Download_and_configure_Java_5_or_6|Configure Java]] to fix this problem.<br />
<br />
''' Incompatible version of Eclipse '''<br />
<br />
Separate versions and update sites exist [http://eclipse.org/mylyn/dl.php for Eclipse 3.1 and 3.2]), in which case you may see errors like the following in your <code><workspace>/.metadata/.log </code>file or in a Mylyn view:<br />
<code><br />
java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()<br />
The activator org.eclipse.mylar.java.MylarJavaPlugin for bundle org.eclipse.mylar.java is invalid<br />
</code><br />
<br />
''' Mylyn feature configuration problem '''<br />
<br />
If the above do not address the issue, the easiest thing to do is uninstall any old versions and update to the latest Mylyn. Your tasks won't be lost, because by default they are stored in the <code><workspace>/.metadata/.mylyn</code> folder which will be read next time Mylyn starts correctly. <br />
* First, uninstall the old version of Mylyn using ''Help -> Software Updates -> Manage Configuration''. <br />
* You need to Disable all Mylyn features by right-clicking them.<br />
* Allow Eclipse to restart after the last is disabled.<br />
* After restart, ensure that the 3rd toolbar button is pressed (figure below) so that you see the disabled features to uninstall.<br />
* Uninstall all the disabled features using the popup menu. <br />
<br />
If you don't uninstall, the the Update Manager will think that you have the latest and tell you that there are no updates. <br />
<br />
<b>Note: manually removing the plug-ins and features can lead to configuration errors.</b> <br />
<br />
After uninstalling, update Eclipse by adding the correct update site specified at on the [http://eclipse.org/mylar/dl.php download page], and after that automatically or manually updating will install the correct version.<br />
<br />
[[Image:mylar-eclipse-manage-configuration.gif]]<br />
<br />
'''What do I need to do in installation to be able to use Mylyn task management features with bug/task/issue trackers?'''<br />
<br />
When you install, make sure that you select a connector for your bug/task/issue tracking software. For example, to use Bugzilla, you have to install the Bugzilla connector component.<br />
<br />
'''I've installed Mylyn ; why can't I see anything different?'''<br />
<br />
The two most likely possibilities are:<br />
# You don't have any Mylyn views open. Select ''Window -> Show View -> Other'', then select ''Mylyn'' and you should see the available Mylyn Views. <br />
# If you still don't see anything, then perhaps you aren't using the JDK1.5 VM (or later). See [[Mylyn_Installation_Guide#Download_and_configure_Java|configuring Java]].<br />
<br />
<br />
'''What does the error "Network connection problems encountered during search" mean?'''<br />
<br />
If you get that message while trying to download Mylyn, it means that Eclipse couldn't find the location you entered. This might be because you copied something incorrectly (watch for extra characters -- even extra spaces can cause errors), or because the site went down. You may be able to see if the site is up or down by copying the URL into your Web browser.<br />
<br />
'''What does the "Update manager failure" message mean? '''<br />
<br />
It means that Eclipse could not access the update site, or that it got confused about the configuration state of your Eclipse. First try updating again to see if the update site is accessible. <br />
<br />
If you are trying to update the JIRA connector you can also try de-selecting that feature in case the <code>Tigris.org</code> update site is not accessible. Using ''Search for new features to install..'' when installing can help to avoid this problem. If that does not work see the feature configuration troubleshooting below. <br />
<br />
'''What does "Could not create Browser page: No more handles (<code>java.lang.UnsatisfiedLinkError: ...</code>)" mean?'''<br />
<br />
It probably means that you are running Linux and don't have Eclipse and a Web browser configured to work together. See [[http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux| installing a browser on Linux]].<br />
<br />
'''When downloading, why do I get a warning that the feature was unsigned?'''<br />
<br />
Signing plugins requires extra administrative details with <code>eclipse.org</code> which most plug-ins seek to avoid. <br />
<br />
'''N.B.''': Security issues with features should not be underestimated. Eclipse allows users to download new functionality from remote servers. A rogue plug-in can act as a perfect Trojan horse. It can look innocent enough and provide useful function while spawning threads in the background with full access to the local file system and the Internet (if connected). Beware of installing features from update sites you do not trust.<br />
<br />
'''What does "<code>Root exception: java.lang.UnsupportedClassVersionError: org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)</code>" mean?'''<br />
<br />
It probably means that the virtual machine is JDK1.4 or lower. See [[Mylyn_Installation_Guide#Download_and_configure_Java| download and configure Java]].<br />
<br />
'''Why am I getting messages in my <code><workspace>/.metadata/.log</code> or my Mylyn view that say things like <code>"java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()"</code> and "The activator <code>org.eclipse.mylar.java.MylarJavaPlugin</code> for bundle <code>org.eclipse.mylar.java</code> is invalid"?'''<br />
<br />
This probably means that your Mylyn download version didn't match your Eclipse download version. Note that [http://eclipse.org/mylar/dl.php the download site] has different downloads for Eclipse 3.1 and Eclipse 3.2.<br />
<br />
To fix this problem, see the [[Mylyn_Uninstallation_Guide| uninstallation guide]], then re-install from [http://eclipse.org/mylar/dl.php the correct download site].<br />
<br />
'''What does "Could not create Bugzilla editor input" and "<code>java.io.IOException</code>: SAX2 driver class <code>org.apache.xerces.parsers.SAXParser</code> not found" mean?'''<br />
<br />
It probably means that you are on MacOS, and for some reason are missing Xerces from the Mac JDK1.5. You will probably need to add it to your default classpath. Please refer to and comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=144287 bug 144287] if you see this problem.<br />
<br />
To ensure that you are using the 1.5 VM refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
'''I've just updated to Mylyn 2.0 and I don't see any tasks in my Task List'''<br />
<br />
As part of the update to Mylyn 2.0 the old data folder has been migrated to <workspace folder>/.metadata/.mylyn from the old location <workspace folder>/.mylar. IF for some reason migration failed (.mylar folder still exists), simply shut down Eclipse and manually move your old <workspace folder>/.mylar folder to <workspace folder>/.metadata/.mylyn (note the name change to .mylyn)<br />
<br />
== Configuration Troubleshooting == <br />
<br />
'''How can I change the number of editors left open before Mylyn starts closing editors?'''<br />
<br />
Turn off or increase the number of editors to leave open using ''Preferences -> General -> Editors -> Number of opened editors before closing''. Since Mylyn will manage the open editors with task activation, this number can be set higher or you can disable automatic closing entirely.<br />
<br />
'''Do I need the Outline View when running Mylyn?'''<br />
<br />
No, not really. The Package Explorer and folded signatures should provide enough context for you. If, at some point, you really need to see an Outline View, you can always enter (Ctrl+O) to show the in-place Outline View.<br />
<br />
'''What does the message "content assist proposals no longer appear" mean?'''<br />
<br />
This usually happens when uninstalling when using Eclipse 3.2. Make sure that the "Java Completions" and "Java Types" proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
'''Why do I get errors like "HTTP Response Code 407" or "Proxy Authentication Error" when accessing repositories through a proxy server?'''<br />
<br />
It is likely that you need to configure these proxy server settings. Select ''Window -> Preferences -> Install/Update'', and update the section in the "Proxy settings" section of the form.<br />
<br />
'''I can't use <code>Ctrl+Alt+Shift+Arrow Up</code> for'' Mark as Landmark''. What do I do?<br />
<br />
This is usually a Linux/GNOME problem, where the Gnome keyboard shortcuts are interfering with the Eclipse shortcuts. Go to the Keyboard shortcuts (which might be something like ''Desktop -> Control Centre -> Keyboard Shortcuts'' or ''System -> Preferences -> Keyboard Shortcuts'') and disable both of these shortcuts:<br />
* Move one workspace up<br />
* Move one workspace down<br />
<br />
See also: [[Mylyn_User_Guide#Keyboard_mappings_on_Linux| keyboard mappings on Linux]].<br />
<br />
'''How do I turn on spell checking?'''<br />
<br />
See [[Mylyn_User_Guide#Spell_Checking| spell checking]].<br />
<br />
== Uninstall troubleshooting ==<br />
<br />
When '''uninstalling in Eclipse''' Mylyn via the ''Help -> Software Updates -> Manage Configuration'' dialog you will need to uninstall dependencies first (e.g. Bugzilla Connector, Subclipse integration) and then uninstall the core Mylyn features.<br />
<br />
When '''uninstalling manually''' by deleting all of the Mylyn plug-ins and features from the <code>eclipse/plugins</code> and <code>eclipse/features</code> directory make sure to delete all of the plug-ins and then restart Eclipse with the -clean option (e.g. by inserting it into a shortcut or the <code>eclipse.ini</code> file.<br />
<br />
On '''Eclipse 3.1:''' you may need to reset the Java editor to be default for <code>.java</code> again via: ''Preferences -> General -> Editors -> File Associations''<br />
<br />
On '''Eclipse 3.2:''' if after uninstalling '''content assist proposals no longer appear''' you need to ensure that the ''Java Completions'' and ''Java Types'' proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
== I am seeing <code>java.lang.OutOfMemoryError: PermGen space </code>errors, what's wrong? ==<br />
<br />
If your Eclipse crashes, or you see the above error after installing Mylyn or other plug-ins, you have most likely hit the infamous MaxPermSize bug. This is not a Mylyn specific problem, but a general Eclipse problem that is often triggered on Eclipse 3.2 and later, if you have many plug-ins installed and are using a Sun JVM. <br />
<br />
To fix it simply add the following to your launch arguments. This is usually to your shortcut, or to the <tt>eclipse/configuration/config.ini</tt> file:<br />
<br />
-XX:MaxPermSize=128M<br />
<br />
If you are using a large number of plug-ins (e.g. WTP) you may need to increase the number to more than 128M. <br />
<br />
Details of the problem are on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250 Platform bug 92250].<br />
<br />
= Task List =<br />
<br />
== Why won't the Archive category disappear? ==<br />
<br />
The ''Archive'' category will automatically appear if a task needs to be shown, but is not in any query or category. <br />
In order to ensure that you do not miss reminders or notifications the following tasks will always be shown in the Task List, even if they have been removed from a category or a query:<br />
* Tasks scheduled for this week or overdue. Remove these by using the ''Schedule'' pop-up menu option to defer them to a future week or to clear the schedule.<br />
* Repository tasks that have incoming changes, such as comments. Remove these by reading them or marking them as "read" via the ''Mark -> Read'' pop-up menu.<br />
<br />
== The Archive category contains many irrelevant tasks, how do I clean it up? ==<br />
<br />
If you created very broad queries you could end up with thousands of tasks in the Archive category. Other than clearing the <tt>workspace/.metadata/.mylyn/tasklist.xml.zip</tt> and <code>workspace/.metadata/.mylyn/offline</code> folder (note that this will entirely reset your Task List) the easiest option is to:<br />
* Clean up your queries to include only tasks of interest (note that including completed/resolved tasks is recommended).<br />
* Turn off ''Focus on Workweek'' in the ''Task List''.<br />
* Turn off the ''Filter Archive Category'' option in the ''Task List'' view menu.<br />
* Delete all of the unneeded tasks from within the Archive category. Note that if the tasks are not matched by queries they will be deleted permanently and any local notes or scheduling information that you have added to them will be lost.<br />
<br />
== How does Mylyn count the active time for a task? ==<br />
<br />
Whenever you work on a task, Mylyn accumulates the time you spend actively working on a task. This time can be viewed in the ''Personal Planning'' section of the ''Task Editor''. When you are not interacting with Eclipse, the timing automatically times out after 3 minutes by default. This means that activity outside of Eclipse will not be captured when you work on the task and that the timings in Mylyn are a lower bound of the total time spent on the task (capturing timings for work done outside of Eclipse involves OS specific extensions).<br />
<br />
== How do I prevent long-running tasks from adding to the progress bar? ==<br />
<br />
If you have many long-running or recurring tasks scheduled for this week, they can affect the ''Task List'' weekly progress bar. This can be misleading as they may never be completed. The current work-around to prevent long-running tasks from being included in the weekly progress bar is to schedule their estimated time to be 0 (zero). Alternatively, you can schedule only the amount of time you plan on spending on that task this week.<br />
<br />
== Does the Task List replace the Eclipse Tasks view? ==<br />
<br />
The SDK's ''Tasks'' view is used for showing markers such as 'todo' tags which indicate a local problem with a resource, similar to a compiler warning. As such, these 'tasks' are at a much lower level of granularity than Mylyn's tasks, and one task could involve cleaning up multiple todos. In order to make working with only the markers in a particular task context, e.g. for clean-up before committing, the ''Apply Mylyn'' filter is available for both the ''Problems'' and the ''Tasks'' views.<br />
<br />
== What if I use multiple workspaces? ==<br />
<br />
Mylyn's support for multiple workspaces is currently limited (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130658 bug 130658] for a discussion) because the Task List is considered to be specific to the person, and not to the workspace. We recommend configuring your Eclipse workspace to use working sets instead of relying on multiple workspaces. <br />
* John O'Shea's blog: [http://www.xlml.com/aehso/2007/02/02/eclipse-workspaces-containing-projects-with-overlapping-locations-and-mylar/ Eclipse workspaces containing projects with overlapping locations, and Mylar]<br />
<br />
If using a single workspace is not possible you can do the following:<br />
* In ''Preferences -> Mylyn -> Task List'' set the ''Data Directory'' to be a shared location, and do this for both workspaces.<br />
* Be sure to avoid launching both Eclipse workspaces at the same time, as changes in one workspaces could overwrite the Task List in the other workspace.<br />
* If you upgrade Eclipse or move your workspace and don't see your tasks, check the ''Data Directory'' setting.<br />
<br />
== How do I export my task and repository data? ==<br />
<br />
Export via File > Export > Mylyn > Task Data<br />
<br />
== Why does Mylyn use the term "task"? ==<br />
<br />
There are many work items that make up the developer's workday. Many issue trackers and project management tools refer to these as: bugs, defects, actions, tickets, stories, enhancements, and the list goes on. We refer to all such work items as "tasks" because the word tasks is short and commonly used in time management tools. Task Repository connectors can customize the presentation of tasks, for example, indicating which is a defect and which is an action item.<br />
<br />
= Task Editor =<br />
<br />
== Why am I seeing strange boxes where I expect to see proper characters? ==<br />
<br />
If for example you aren't seeing the proper single quote chacters in the summary of [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=197644 bug#197644]], check that the encoding is set correctly for the repository in the asociated Task Repositories view (Properties > Additional Settings > Character Encoding). For bugs.eclipse.org/bugs set your charcter encoding to ''ISO-8859-1''.<br />
<br />
= Task Repositories =<br />
<br />
== What if Mylyn doesn't support my task/bug/issue/ticket repository? ==<br />
<br />
To see support for your repository faster, do a search of the open repository connector requests and [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Bconnector%5D&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=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= vote for the corresponding bug] if your tracker is there, or [http://www.eclipse.org/mylar/bugs.php create a new bug]. <br />
<br />
[[Mylyn_User_Guide#Generic_Web_Repository_Connector|Generic Repository Connector]], allows creating Queries to the web-based issue tracking repositories and get list of issues from the web UI into the Task List.<br />
<br />
It is also possible to link a ''local task'' with the web page in web-based repository via the Mylyn Web integration.<br />
<br />
'''To create a task from any web-based repository:'''<br />
<br />
* Drag the URL from the address bar of the browser, or from a hyperlink in a bug listing to the ''Mylyn Tasks'' view. This will create a task for the bug, link it to the page, and populate the description with the title of the corresponding page. '''In Mozilla:''' simply drag the URL. '''In Internet Explorer:''' you must have <code>Ctrl</code> pressed in order for Eclipse to recognize the drop.<br />
* '''Alternatively,''' you can copy the URL, press the ''New Task'' button on the ''Mylyn Tasks'' view. This has the same effect as above but you can edit the description after retrieving it.<br />
* Opening the task will now open the corresponding issue. You can also <code>right+click</code> the task and select ''Open in External Browser''.<br />
<br />
[[Image:mylar-tasklist-weblink-editor.gif]]<br />
<br />
== Why were my repository credentials reset? ==<br />
<br />
If you upgrade Eclipse or your Java VM, you will need to reset your credentials in the ''Task Repositories'' view because these are stored in the secure Eclipse workbench keyring. Also see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=149607 bug 149607]. If you are migrating '''from Eclipse 3.2 to 3.3''' note that you will need to use a different update site, which is listed here: http://eclipse.org/mylyn/dl.php<br />
<br />
== Why are my updated repository attributes not showing up? ==<br />
<br />
Your server's repository attributes can change frequently, for example, there can be a new "milestone" or "version" added to the Bugzilla repository with each release. When the ''Preferences -> Mylyn -> Task List -> Synchronization'' setting is enabled, every 10th synchronization will update the attributes from the repository. If you do not have this setting enabled, your can force the update via the ''Update Attributes'' action on the task repositories' context menu in the ''Task Repositories'' view. Note that you will need to reopen a task editor to see the updated attributes. If you instead update via the button on the ''Attributes'' section of the ''Task Editor'' the attribute settings will be reloaded without needing to reopen.<br />
<br />
== Authentication Troubleshooting ==<br />
<br />
You must ensure repository credentials are filled out correctly. Refer to the diagram below:<br />
<br />
[[image: AuthenticationTroubleshooting2.png|right]]<br />
<br />
# Enter the repository URL (i.e. https://bugs.eclipse.org/bugs) and an optional label<br />
# Credentials<br />
#* Usually email address and password <br />
#* Some sites, such as <code>dev.eclipse.org</code>, use anonymous logon with password left blank.<br />
#Http Authentication (optional)<br />
#* Some sites are protected by either BASIC or DIGEST http authentication. If this is the case, enter appropriate credentials here.<br />
#* One way to test if the site requires http authentication is to point your browser at the repository. If you are presented with an authentication dialog popup, the site is likely protected by http authentication.<br />
#Proxy Server Configuration (optional)<br />
#* By default Mylyn uses the Platform's Install/Update proxy settings. Uncheck this box if you wish to use an alternative proxy.<br />
#* If the proxy requires authentication, this is where you enable and enter your proxy credentials.<br />
#* If you are experiencing connection problems, ensure your Install/Update proxy settings are valid or the repository specific settings are correct<br />
#* Mylyn has been tested with HTTP proxy servers. Currently SOCKS is not supported.<br />
#Validate Settings <br />
#*Press the ''validate'' button to test the settings<br />
#*If you are seeing errors like "HTTP Response Code 407" or "Proxy Authentication Error" it is likely that you need to configure proxy settas as described above.<br />
#*If your sever uses a certificate and fails to connect, e.g. you see exceptions <tt>sun.security.validator.ValidatorException: PKIX path building failed</tt> then you need to point Eclipse at your certificate, see the [http://ahtik.com/blog/2006/05/11/fixing-eclipse-mylar-jira-integration/ instructions on this blog].<br />
<br clear="all" /><br />
<br />
=== NTLM authentication ===<br />
<br />
For NTLM authentication to work a special format for the username needs to be used where ''DOMAIN'' needs to be replaced by the Windows login domain: <br />
<br />
DOMAIN\username <br />
<br />
The built-in NTLM support of the JDK which is used by Eclipse does '''not work''' with Mylyn since it uses the HttpClient library to access repositories. Limitations in regard to NTLM authentication are documented in the [http://wiki.apache.org/jakarta-httpclient/FrequentlyAskedNTLMQuestions NTLM FAQ] and also discussion on {{bug|201911}}.<br />
<br />
* If your repository uses MS NTLM authentication and only standard http authentication is being passed to the repository this can result when the local hostname cannot be resolved. Ensure your machine's hostname is set correctly and resolves to a valid address.<br />
* It is not possible to use NTLM authentication for the proxy as well as for the repository.<br />
<br />
If NTLM authentication fails the '''[http://ntlmaps.sourceforge.net/ NTLM Authorization Proxy Server]''' has been reported to '''work''' with Mylyn.<br />
<br />
== Why are task hyperlinks not working? ==<br />
<br />
For task hyperlinks in textual editors (e.g. Java editor) and other text viewers (e.g. History view comments) you must associate the project that contains the resource to the task repository. <br />
<br />
:''Project association can also come from 3rd party metadata trough the contrubuted [[Mylar_Integrator_Reference#Mapping_from_projects_to_Task_Repositories|extension point]]. [http://subclipse.tigris.org/ Subclipse] and [http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Mylyn Maven integration for Eclipse] plugins contributing it. See few more details [http://jroller.com/page/eu?entry=linking_projects_from_the_eclipse here].''<br />
<br />
Note that to view a hyperlink you must hold down the <code>Ctrl</code> key when hovering over the reference to the task. References to tasks are connector specific and the common reference is found on the top left of the task editor and other conventions tend to follow those used in the web UI (e.g. "bug 123" for Bugzilla, "ABC-123" for JIRA).<br />
<br />
[[Image:mylyn-project-repository-association.gif]]<br />
<br />
= Bugzilla Connector =<br />
<br />
== What versions are supported? ==<br />
<br />
We recommend using the latest [http://www.bugzilla.org/download/ release] of Bugzilla.<br />
<br />
* '''Bugzilla 2.18.6 is the lowest version of Bugzilla supported'''. If you are getting errors that indicate failure to update attributes this may be an indication that the Bugzilla server is not supported (< 2.18.6).<br />
<br />
*If you are using '''Bugzilla 2.18''' and are getting '''mid-air collisions''' this is likely due to incorrectly formatted timestamp field in the underlying bugs database table ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149513 bug 149513]). This can be resolved by upgrading to Bugzilla 2.20 or later.<br />
<br />
== Why are queries failing? ==<br />
<br />
*If '''queries are not working''' correctly ensure that you have the right Bugzilla server version selected for the corresponding repository: ''Task Repositories (View) ->'' right+click the repository ''-> Properties''. For supported versions see the [http://www.eclipse.org/mylar/dl.php download page]. If the repository is still not functioning it may be due to authentication or connectivity problems. If that does not resolve the problem please post a message to the newsgroup or [http://www.eclipse.org/mylar/bugs.php submit a bug].<br />
<br />
== Why do tasks fail to open? ==<br />
<br />
*If upon opening a bug, the Bugzilla tab only displays a warning "'''Could not download task data, possibly due to timeout or connectivity problem. Please check connection and try again.'''", ensure that your repository is returning XML data by pointing your browser to <code><your-repository-url>/show_bug.cgi?id=1&ctype=xml</code> to show the contents of bug 1 in XML form. The Bugzilla client requires that bugs be accessible in XML form. If the repository doesn't support xml then it is likely that the repository is too old (Mylyn currently supports Bugzilla 2.18 and later).<br />
<br />
* If '''reports fail to load''' or '''reports fail to synchronize''' (task description remains ''italic''), check the error log for a "'''File not found'''" error pointing to <code>bugzilla.dtd</code> or a "'''Failed to retrieve products from server'''" error message - these result when the <code>urlbase</code> parameter is not set on the bugzilla server, or your bugzilla installation is missing the <code>bugzilla.dtd</code> file. See: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=161759 bug#161759]<br />
<br />
* If '''attributes are missing options''' in the bug editor (ie. missing a recently added milestone, [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155431 bug# 155431]):<br />
** Update attributes by choosing ''Update Attributes'' from the context menu in the ''Task Repositories'' view<br />
** Synchronize the task in the Task List<br />
** Reopen the task - new options should be available.<br />
<br />
== Why do tasks fail to submit? ==<br />
<br />
* '''Error upon submit: unable to make any match for name/email entered.''' If your bugzilla is configured for user names rather than full email address the QA Contact field will cause the submit to fail ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=166555 bug# 166555]). To resolve, select 'Local users enabled' option on the Repository Configuration page. <br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your account's username and password and are not using the HTTP authentication fields instead.<br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your bugzilla instance's cookie domain under the required settings. The cookie domain must lead with a dot.<br />
<br />
* If '''attachments are failing to submit''' and you see that after processing the attachment, the bugzilla bug shows a size of "bytes" (no numbers), your database may be dropping the packet sending the file. '''On MySQL''', check the [http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html max_allowed_packet directive]. You may see errors like: <code>DBD::mysql::st execute</code> failed: Got a packet bigger than 'max_allowed_packet' bytes [for Statement "INSERT INTO attach_data (id, thedata) VALUES (38, ?)"] at <code>/path/to/bugzilla/attachment.cgi</code> line 993. Also, '''check the maximum attachment size''' in ''Bugzilla Parameters -> Attachments''.<br />
<br />
* If a submit fails with an '''Invalid Username or Password''' error even though repository settings do validate, make sure that cookies could be set. See also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175502 bug 175502]<br />
<br />
== What time zone is used in the task editor? ==<br />
<br />
*The '''times''' that appear in the Bugzilla bug editor (ie. created, modified) '''are local to the server hosting the Bugzilla repository''', not your local machine's time zone. <br />
<br />
== Known limitations ==<br />
<br />
* The <code>usermatchmode</code> is not currently supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168204 bug 168204]) and as such full email addresses need to be used.<br />
<br />
* The <code>usevisibilitygroups</code> parameter is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=180876 bug#180876]). Group assignment will currently be lost if updated using the Bugzilla rich task editor.<br />
<br />
* Version 1.0 of Mylyn presents an error message upon new comment submission to RedHat's public Bugzilla repository. The comment is in fact posted. This issue is resolved in Mylyn 2.0M2 and higher. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=183251 bug#183251])<br />
<br />
= JIRA Connector =<br />
<br />
If you see errors like the following, work around this by opening repository ''Properties Page'' and clicking OK (bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169102 169102]).<br />
<br />
org.tigris.jira.core.service.exceptions.AuthenticationException<br />
at org.tigris.jira.internal.core.service.soap.SoapJiraService.getProjectsNoSchemes(SoapJiraService.java:204)<br />
<br />
== What are the server requirements? ==<br />
<br />
The '''JIRA SOAP/RPC services have to be running on the JIRA server''':<br />
<br />
* Jira 3.3.3 or higher (3.7 or higher for attachment retrieval)<br />
* Jira RPC plugin 1.4.3 or higher<br />
<br />
Latest information also available on the [http://www.eclipse.org/mylar/dl.php download page].<br />
<br />
Related Resources:<br />
<br />
* [http://confluence.atlassian.com/display/JIRA/JIRA+Development+Hub Jira Development Wiki]<br />
* [http://confluence.atlassian.com/pages/viewpage.action?pageId=1035 Jira RPC Plugin Overview]<br />
<br />
== Why can't I connect? ==<br />
<br />
* If you get a <code>org.tigris.jira.core.service.exceptions.ServiceUnavailableException</code> you need to turn on the JIRA SOAP/RPC services on the server.<br />
* Similarly, if you get a "Processing instructions are not allowed within SOAP messages" message, ensure that SOAP/RPC services are on.<br />
* If you get a '''503''' error code verify that the SOAP/RPC interface is enabled.<br />
* If you get a '''403''' error code verify that the SOAP/RPC interface is enabled, and also check your authentication mechanism. If the server is using NTLM authentication, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156397 bug 156937] for diagnosis steps.<br />
* If you see an '''"unrecognized priority" message''' in the ''Error Log'', the problem is that the JIRA Connector does not support customized priorities so the priority value specified in that message will not correspond to the priority icons visible in the Task List.<br />
* If you are being '''prompted for your log-in credentials''' by the Browser tab of the task editor or the new task editor, this is because without rich editor support the connector is using the web-based UI instead of logging in on your behalf as is done with a rich task editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142869 bug 142869]).<br />
* If you get a <CODE>AuthenticationException</code> and a query won't synchronize, use Task Repositories (view) -> Properties (on the repository) -> Validate Settings. This will clear the connection if it died.<br />
<br />
<!-- HEAVILY OUTDATED. PLUGIN NOW USES COMMON PROXY INFRASTRUCTURE<br />
== Why can't I synchronize when using a proxy server? ==<br />
<br />
* Proxy configuration is '''based on the normal Java HTTP system properties''', which can be configured either by launching Eclipse with <code>-vmargs</code> and using the following settings, or by putting these settings into the or by putting the following into the <code>eclipse/eclipse.ini</code> file (after -vmags):<br />
-Dhttp.proxyHost=<host> <br />
-Dhttp.proxyPort=<port><br />
* Make sure that when using these settings you do not enable the proxy settings on the ''Install/Update'' preference page, since they may override these settings.<br />
* If you are using '''SSL''', you will also need to set the <code>https.proxyHost</code> and <code>https.proxyPort</code>. <br />
* Authentication is configured with the <code>http.proxyUser</code> and <code>http.proxyPassword</code> system properties (also for SSL)<br />
* You can also use <code>http.nonProxyHosts</code> system property to enumerate hosts that should not be proxied. Note that matching is implemented on the exact host name used for JIRA server and patterns are not supported. --><br />
<br />
== Known limitations ==<br />
* Attachment retrieval (including retrieval of the task context and attachment list in the task editor) require JIRA 3.7 or above ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=169757 bug 169757])<br />
<!-- * NTLM authentication is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172395 bug 172395]) --><br />
* Customized priorities are not currently supported, so all issues with a customized priority will have the default priority level ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=165518 bug 165518]).<br />
* blank but editable custom fields doesn't appear in the RSS data, and as result we can't show them for editing<br />
* because of JIRA api limitations, we can support custom fields in the task editor, but not in the new custom task editor<br />
<!-- * On JIRA 3.6.x private filters saved on the server can fail to retrieve results ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=174328 bug 174328]). The work-around is to create a custom query in Mylyn using the form-based query designer or to share the filter in JIRA. --><br />
<br />
== How can I enable compression for SOAP messages? ==<br />
<br />
If your repository has lots of projects and components you can speed up the download of the repository configuration by enabling compression. <br />
<br />
* Add a filter-mapping to your JIRA server configuration: [http://jira.atlassian.com/browse/JRA-10353].<br />
* Enable compression in your global JIRA configuration.<br />
* Check the compression setting for your task repository in Mylyn versions 2.0M2 and later.<br />
<br />
== Reporting issues ==<br />
<br />
Since JIRA can be heavily customized there is a chance that some particular customizations may not work, so if you can't connect to your proprietary repository it is a good idea to try the following public repositories to make sure you have working configuration:<br />
<br />
* http://jira.codehaus.org<br />
* http://issues.apache.org/jira/<br />
* http://opensource.atlassian.com/projects/spring <br />
<br />
If you can't get query results, you could try to call "Open with Browser" on query node in the Task List view and then save link "Current view: XML" and attach it to the bug report.<br />
<br />
Even if query don't work you could try "Open Repository Task" from your JIRA repository node on the Task Repositories view and check if you can open JIRA task editor for that issue. Same for the Task search (Ctrl-H, Task Search)<br />
<br />
To investigate various error you may need to enable debug tracing. To do that you need to create the <code>.options</code> file with the following content:<br />
<br />
<pre><br />
org.eclipse.mylyn.jira.ui/connector=true<br />
org.eclipse.mylyn.jira.ui/dataHandler=true<br />
</pre><br />
<br />
and then add the following options to the Eclipse command line (or eclipse.ini file):<br />
<br />
<pre><br />
-debug <path to the .options file>/.options<br />
</pre><br />
<br />
The additional logging will go into the regular Eclipse log and the Error Log view<br />
<br />
= Trac Connector =<br />
<br />
== What are the server requirements? ==<br />
<br />
The Trac connector offers two access methods:<br />
<br />
'''XML-RPC''' (recommended)<br />
<br />
Requirements:<br />
* Trac 0.10<br />
* [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] rev. 1950<br />
<br />
This access method offers editing of tasks in a rich editor, attachment support and offline editing. It requires the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] for Trac to be enabled for the accessed repository. The XmlRpcPlugin provides a remote interface to the Trac repository and is distributed separately from Trac (see [http://trac.edgewall.org/ticket/217 #217]). See these [http://trac-hacks.org/wiki/XmlRpcPlugin#Installation install instructions] for requirements and documentation.<br />
<br />
'''Web''' <br />
<br />
Requirements:<br />
* Trac 0.9 or later<br />
<br />
In this mode the standard Trac web interface is used for repository access. Tickets may be created and edited through a web browser. Offline editing and attachments are not supported.<br />
<br />
== Recommended Trac version ==<br />
<br />
Mylyn should work with any stable release Trac release that is version 0.9.x or 0.10.x (see below for known limitations). Mylyn works best when used with Trac's XML-RPC Plugin (see above) but we do not recommend a particular Trac version. <br />
<br />
The Trac connector tests are run against these Trac versions:<br />
<br />
* Trac 0.10.4, XML-RPC Plugin rev. 1950<br />
* Trac 0.9.6<br />
<br />
See {{bug|175211}} for details about Trac 0.11 support.<br />
<br />
== Why do I get an HTTP Error 500 Internal server error when creating a ticket that contains non-ASCII characters? ==<br />
<br />
Problems related to character encodings have been reported when Trac is run with Python 2.3. Upgrading to Python 2.4 may help to resolve this. Please comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=188363 bug #188363] if you encounter an internal server error when creating a ticket that contains non-ASCII characters.<br />
<br />
== Known limitations ==<br />
<br />
* Trac 0.10.1 <br />
** Known incompatibility with Trac XML-RPC Plugin. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164272 bug 164272] for details.<br />
* Trac 0.10.3 <br />
** Known incompatibility with old versions of the Trac HttpAuthPlugin (fixed in revision 1890 or later). The plug-in enables basic auth for XML-RPC when Trac AccountManagerPlugin for form based authentication is used. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168413 bug 168413] for details.<br />
* Trac 0.11<br />
** Currently untested.<br />
** Known incompatibility with Trac XML-RPC Plugin See [http://trac-hacks.org/wiki/XmlRpcPlugin] for details.<br />
<br />
== Why are tasks opened in a web browser and not in the rich editor? ==<br />
<br />
Please make sure that the access type in the repository properties is set to XML-RPC. This requires Trac 0.10 and XML-RPC (see above).<br />
<br />
== Which URLs does Mylyn access in a Trac repository? ==<br />
<br />
XML-RPC:<br />
<br />
* The expected URL is either /xmlrpc or /login/xmlrpc (if login credentials are provided)<br />
<br />
Web:<br />
<br />
* Authentication: /login <br />
* Querying: /query?format=tab...<br />
* Synchronizing ticket details: /ticket/...<br />
* Getting repository configuration to populate query dialog: /query or /newticket<br />
<br />
The web mode relies on screen scraping and is likely to fail if the design<br />
(i.e. HTML output) of the Trac repository is heavily customized.<br />
<br />
= Generic Web Repository Connector =<br />
<br />
== Where can I find the web repository connector ==<br />
<br />
It is available from the extensions update page. Please see http://www.eclipse.org/mylyn/downloads/<br />
<br />
== Why can't I connect using one of the existing templates? ==<br />
<br />
<br />
The Web Repository Connector have a Preview option in Advanced Configuration section on the Query preferences. If you get an error or preview table does not show expected list of tasks you can use Query Pattern like (.+?)(\n) to see content of the retrieved page and compare it with the source of the web page for the same url loaded into the web browser.<br />
<br />
If that does not help then you could use the wget tool (on Windows it available as a standalone command line tool and also included with Cygwin).<br />
<br />
Run the following command:<br />
<br />
<pre>wget -v -d -o query.log -O query.html "http://your.query.url"</pre><br />
<br />
If repository require basic http auth, you'll need to use ''--http-user=USER'' and ''--http-password=PASS'' options.<br />
<br />
Then open file ''query.html'' in the web browser and check if it show list of issues you need to fetch from the web server. If it does have correct list, then there could be a problem with query pattern used for parsing. <br />
<br />
A popular mistake is an unmasked '?' that separates request parameters in the url). For example:<br />
<br />
<pre><a href="show_bug.cgi\?id\=(.+?)">.+?<span class="summary">(.+?)</span></pre><br />
<br />
If ''query.html'' does not show expected list of issues you can check ''query.log'' for server responses and try to identify if server require authentication, redirecting your requests somewhere or issue any other errors.<br />
<br />
== Known limitations ==<br />
<br />
* In Mylyn 1.0: if a web server responds by requesting a redirect to an absolute URL while fetching a resource, the connector falsely prepends "/" to the URL and the request will fail. The workaround is to use final url where redirect is pointing to (you can find it as describe above). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=167282 bug 167282] for details.<br />
<br />
= Task-Focused UI =<br />
<br />
== What is the Task-Focused UI? ==<br />
<br />
When you activate a task, Mylyn automatically maintains a task context by monitoring your interaction. The task context provides a predictable degree-of-interest weighting of the relevance of the elements and relations that you work with to the task-at-hand (as described in the [http://kerstens.org/mik/publications/2006-11-mylar-fse.pdf Foundations of Software Engineering conference paper]). The Task-Focuse UI is the mechanism by which Mylyn presents Mylyn the task-context model in order to reduce information overload and to automate the manaul management of UI elements like editors and change sets. Examples:<br />
* Filtering, decoration and expansion management in views<br />
* Automatic folding in editors<br />
* Ranking in content assist<br />
* Editor management<br />
* Perspective management<br />
* Change set management<br />
<br />
== Why do files disappear from Focused views when I close them? ==<br />
<br />
By default Mylyn automatically manages the set of open files to match the task context, so that you don't have to. This ensures that the editor list (viewable via mechanisms like Ctrl+E) corresponds to what you in views like the ''Package Explorer'' when they are in Focused mode. When you close a file manually, you express that it is uninteresting, and as such it will be removed from the task context. It will also disappear from the corresponding automatically managed change sets for the same reason. This behavior can be turned off via ''Preferences -> Mylyn -> Context -> Manage open editors to match task context''. However, it is highly recommended since Mylyn will prevent the number of editors from bloating by automatically closing editors for elements that have decayed in interest, and always keep the editors for interesting elements open.<br />
<br />
<br />
== Why did all my editor tabs disappear? ==<br />
<br />
When you deactivate a task, all editors will be closed, and then when you reactivate the task all the windows will be open again. Try it, it's fun. <br />
<br />
Mylyn actively manages your open editors with task context. It takes some getting used to, but enables switching between tasks when you are multitasking without cluttering your editor tabs. This editor management can be disabled via ''Window -> Preferences -> Mylyn -> Context''. However, before disabling it consider reading the ''"Managing open editors..."'' section of [http://www-128.ibm.com/developerworks/java/library/j-mylar2/index.html#N10116 Task-focused programming with Mylar].<br />
<br />
== How do I get rid of an element if it is not interesting? ==<br />
<br />
When a view is focused elements will disappear on their own if they are not repeatedly selected via a mechanism called interest decay. Note that decay does not use the wall clock, but instead relies on the number of selections that you have made when working on that task to determine which elements disappear. This helps make it feel very predictable.<br />
<br />
If you want want to force one or more elements to disappear from the context use the '''Remove from Focus''' action on the context menu. Note that the element will still be part of the task context since it was previously part of the interaction. <br />
<br />
If you want to permanently delete the element from the interaction history use the '''Remove from Context''' action on the '''Context''' tab of the '''Task Editor'''. For example, if a company private element was part of a task context that is to be shared with a public repository, this action can be used to clean it up before sharing. Note that elements will be removed from the task context recursively.<br />
<br />
== Which Focused UI features can I turn off? ==<br />
<br />
'''All of them.''' When no task is active neither are any of Mylyn's features. When working with task contexts Mylyn's Focused UI features are all optional and in general configurable. While many find it the key benefit of Mylyn, the entire Focused UI is optional and can be uninstalled via ''Help -> Software Updates -> Manage Configuration''.<br />
<br />
The following table summarizes how the key features can be toggled:<br />
<br />
<table><br />
<tr><br />
<td>'''UI Mechanism'''</td><br />
<td>'''Example/description'''</td><br />
<td>'''Toggle using'''</td><br />
</tr><br />
<tr><br />
<td>Interest filtering</td><br />
<td>Package Explorer</td><br />
<td>''Apply Mylyn'' button on view toolbar</td><br />
</tr><br />
<tr><br />
<td>Automatic toggling of filtering</td><br />
<td>Package Explorer</td><br />
<td>''Preferences -> Mylar -> Context -> Toggle focused mode..</td><br />
</tr><br />
<tr><br />
<td>Interest decoration</td><br />
<td>Bolding of landmark elements</td><br />
<td>''Preferences -&gt; General -&gt; Appearance -&gt; Label Decoration''</td><br />
</tr><br />
<tr><br />
<td>Content assist</td><br />
<td>Ranking of interesting elements</td><br />
<td>Eclipse 3.2: ''Java -&gt; Editor -&gt; Content Assist -&gt; Work in Progress -&gt;'' turn off Mylyn, turn on Java</td><br />
</tr><br />
<tr><br />
<td>Active change sets</td><br />
<td>Grouping of changes by tasks</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Team''</td><br />
</tr><br />
<tr><br />
<td>Editor management</td><br />
<td>Auto opening/closing of editors</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Editor Management''</td><br />
</tr><br />
<tr><br />
<td>Active views</td><br />
<td>Active Search and Hierarchy</td><br />
<td>Only on if view is active</td><br />
</tr><br />
</table><br />
<br />
For additional configuration options see the ''Mylyn'' and ''General -> Appearance'' preference pages.<br />
<br />
== What is the performance profile of the Focused UI? ==<br />
<br />
The goal is for Mylyn to have '''no noticeable effect''' on Eclipse's speed or memory usage.<br />
You do not need to increase the amount of memory Eclipse runs with to use Mylyn. <br />
Any performance issue should be [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Mylyn reported as a bug]. <br />
<br />
The current '''Performance Profile''' is:<br />
<br />
# Mylyn only runs if a task is active, and has no impact on Eclipse if no task is active.<br />
# Task context models have negligible memory overhead. <br />
# When a task is active, additional view refresh is required to update the views based on interest model changes. This should not be noticeable on Windows where refresh is very quick, but could be more noticeable on other platforms.<br />
# The time to activate a task context is dominated by the time it takes Eclipse to open the editors in the context. You can set the preference for how many editors to open in the Mylyn preference page (e.g. setting to 1 will dramatically reduce activation time, but also remove the benefit of having open editors correspond to the task context). You can also turn off editor management entirely in the Mylyn Tasks view pull-down.<br />
# Eclipse startup is slowed down by (4) if a task is active when Eclipse is shut down.<br />
# The low priority background searches that the Active Search view runs can be noticeable on slower machines.<br />
<br />
== What happened to the Active Search and Active Hierarchy views? ==<br />
<br />
These views were not included in the Mylyn 1.0 release because they never made it beyond the experimental phase. <br />
* The ''Active Search'' view has not been sufficiently tuned to adapt to the lifecycle of a task context, and as a result requires manual manipulation of the degree-of-separation scope as you work on long-running tasks. Otherwise it becomes overloaded with elements. In addition, it is not yet clear whether an additional view is the right UI for this facility, and it is hard to find room for an additional view of this size on screen resolutions of 1600x1200 and smaller.<br />
* The ''Active Hierarchy'' view is also hard to allocate space for, especially when using the in-place hierarchy (Ctrl+T) on a landmark can be a quick way to see the relevant part of the task context's hierarchy.<br />
<br />
These features still show promise in displaying task context and saving repetitive searches, so we have not removed them. They have instead moved to the Mylyn Sandbox, and can be used and experimented with by following the [http://wiki.eclipse.org/index.php/Mylyn_Contributor_Reference#Sandbox instructions on the Contributors page]. For feedback on these views please use the corresponding bug reports or newsgroup.<br />
<br />
= Java Development =<br />
<br />
== Content assist troubleshooting ==<br />
<br />
Mylyn uses custom Content Assist processors in order to rank and separate the elements in the current task context. To see proposals ranked according to interest you must have only the ''Type Proposals (Mylyn)'' kinds checkbox enabled in the list below, otherwise you will see duplicates. '''If you do not see any proposals, check this list''' to ensure that either the Mylyn or the plain proposals are enabled. '''To do this automatically''', run ''New -> Mylyn -> Recommended Preferences''. Or you can select them manually as in the preference page below. <br />
<br />
[[Image:mylar-content-assist-prefs.gif]]<br />
<br />
'''Why do I see duplicate proposals?'''<br />
<br />
Ensure that you have only the ''(Mylyn)'' proposals kinds enabled in ''Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced'', otherwise you will see duplicates.<br />
<br />
If you use proposals via Ctrl+Shift+Space instead of the typical Ctrl+Space you will see duplicates. Vote for JDT/Text [https://bugs.eclipse.org/bugs/show_bug.cgi?id=147781 bug 147781] if you use this mechanism. Also see: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=129080 bug 129080]<br />
<br />
'''Why do I get an error message when using content assist?'''<br />
<br />
If after invoking Content Assist you see an error message dialog that states:<br />
The extension took too long to return from the 'computeCompletionProposals()' operation<br />
this is most likely due to something interrupting the proposal operation (e.g. garbage collection). Ignore it if it does not recur, increase Eclipse's memory if it does (e.g via <code>-Xmx384M</code> command line argument). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=141457 bug 141457] for more details.<br />
<br />
== Why do interesting elements not show in the Project Explorer? ==<br />
<br />
The ''Package Presentation -> Hierarchical'' mode is not supported on the ''Project Explorer'' view in Eclipse 3.2 through 3.3M3 and possibly later versions (https://bugs.eclipse.org/bugs/show_bug.cgi?id=161362 bug 161362). Use the view menu to set ''Package Presentation -> Flat'' as a work-around.<br />
<br />
== How do I stop declarations from showing in the Package Explorer? ==<br />
<br />
If you don't like Mylyn's constant showing of Java members in the ''Package Explorer'', select the drop-down menu, then ''Filters...'' and enable the ''Mylyn Java Declarations Filter''. It will then stick in the menu in case you want to toggle between modes. Note that this will hide interest information about members that aren't in your current file (e.g. showing you which methods are landmarks) so this mode is not recommended, but can be useful for <code>1024x768</code> screen resolutions.<br />
<br />
[[Image:mylar-java-filtering-declarations.gif]]<br />
<br />
== Why does nothing show up in the Active Search or Active Hierarchy? ==<br />
<br />
As you work, elements become Landmarks (bold decoration), and these elements populate the ''Active Search'' and ''Active Hierarchy'' views. To force an element to populate the views manually, make it a Landmark by <code>right+clicking</code> or hitting <code>Ctrl+Alt+Shift+UpArrow</code>.<br />
<br />
== Known limitations ==<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=106678 Bug 106678]: The Project Explorer's Hierarchical Java package presentation layout is not supported on Eclipse 3.3Mx, and interesting elements will be hidden if enabled. Work-around is to use the default Flat package presentation.<br />
<br />
= Team Support =<br />
<br />
== Why does task change set not appear when I modify files? ==<br />
<br />
A task change set should appear if you activate a task and modify a file connected to a compatible source repository (e.g. CVS, SVN). If it does not try the following:<br />
<br />
* Ensure you have installed the [http://www.eclipse.org/mylyn/downloads/ ''Mylyn Bridge: Eclipse SDK'' feature]. Note that this feature is not currently distributed with the Java-only Eclipse download ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191793 bug 191793] ).<br />
<br />
* Verify that the [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuring_the_Synchronize_view_for_change_sets configured ''Synchronize View'' is configured for change sets].<br />
<br />
If the above are working but the change set appears to be missing relevant files:<br />
<br />
* You may be seeing the ''Synchronize'' view's refresh problem ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142395 bug 142395]). Toggle from ''Incoming/Ougtoing'' to ''Incoming'' mode and back again to refresh the view.<br />
<br />
* If the files or change set are still missing deactivate and reactivate the task to force a full refresh.<br />
<br />
== Why do files disappear from the change set when I close them? ==<br />
<br />
If you have the ''Preferences -> Mylyn -> Context -> Manage open editors to match task context'' option enabled, Mylyn will perform editor management so that you don't have to. Closing a file makes it less interesting, and causes it to disappear from the active task context, and hence from the change set. This option prevents you from having to manage the set of open files, will automatically close editors for files that become uninteresting, and will ensure that the open editors match the task context.<br />
<br />
== Why is interest lost when I retrieve someone else's context? ==<br />
<br />
To identify elements within a project, Mylyn relies on the name of the project being consistent across workspaces. If the project name in the workspace that the context was created with is different than its name in your workspace, the task context will not show elements within that project ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164058 bug 164058]). The work-around is to use the same project names across your team's workspaces.<br />
<br />
The other case where context can be lost is if the elements change names outside of the workspace ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164243 bug 164243]).<br />
<br />
= Misc =<br />
<br />
<br />
<br />
== How does Mylyn relate to IBM's Jazz? ==<br />
<br />
At the EclipseCon and JavaONE 2006 conferences IBM demonstrated previews of Jazz, a collaborative team server and Eclipse-based client. Articles have remarked on the similarities between Mylyn and Jazz because both integrate tasks into Eclipse (Jazz's "work items" and Mylyn's "tasks"), and both provide change sets grouped by task. But there are both significant differences and complementary aspects to the two approaches. A key goal of Mylyn is to provide an open source framework to support integration of task management with ''existing issue trackers and source repositories''. According to the presentations, components that come with Jazz include include a ''next-generation issue tracker and source repository'' and related lifecycle management tools such as project health. In addition, a driving and unique goal of Mylyn is to focus the UI around a usage-based and degree-of-interested weighted task context, which is complementary to the Jazz platform. Just as it integrates with Mylyn's Task List, Mylyn's Task Focused UI and task context model components are possible to integrate with other kinds of task management systems, such as the one provided by Jazz.<br />
<br />
Update: at EclipseCon 2007 the IBM Jazz team showed a Mylyn connector for Jazz.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/FAQ&diff=49807Mylyn/FAQ2007-09-10T05:06:32Z<p>Steffen.pingel.eclipse.org: /* Authentication Troubleshooting */</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
[[Mylyn User Guide]], <br />
[http://eclipse.org/mylyn Mylyn Home],<br />
[http://wiki.eclipse.org/index.php?title=Special:Userlogin&returnto=Special:Userlogout Log in to edit]<br />
<br />
For instructions on [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Download_Mylar downloading] [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installation installing] and [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuration configuring] <br />
Mylyn, see the [[Mylyn User Guide]]. For instructions on developing and contributing to Mylyn, see the [[Mylyn Contributor Reference]].<br />
<br />
= Installation =<br />
<br />
== What versions of Eclipse are supported? ==<br />
<br />
See the [http://eclipse.org/mylyn/dl.php download page].<br />
<br />
Mylyn also relies on a web browser that works with the Standard Widget Toolkit; Windows and MacOS users are fine, but Linux users might have to download another browser. See [http://www.eclipse.org/swt/faq.php#browserlinux the SWT Browser guide] for which browsers will work. See [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux installing browser on Linux] for installation instructions.<br />
<br />
== What version of Java is required? ==<br />
<br />
Mylyn needs the '''Java 5''' virtual machine.<br />
<br />
To check the version of the Java virtual machine that Eclipse was launched with to to ''Help -> About Eclipse SDK -> Configuration Details'' and verify that the java.vm.version is 1.5. <br />
<br />
Mac users should refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
* If you do not have Java 5, you can download it from [http://72.5.124.55/javase/downloads/index.jsp Sun's web site]. <br />
* If you have more than one VM, you need to specify that Eclipse should use the JDK1.5 VM. <br />
<br />
In Unix, set the environment variable <code>JAVA_HOME</code> to the root of the JDK1.5 installation and/or set the <code>PATH</code> variable to put the JDK1.5 executable directory before any other VM executable directories. For example, under <code>bash</code> in Unix:<br />
export JAVA_HOME="''(location of JDK1.5 root)''"<br />
export PATH=$JAVA_HOME/bin:$PATH<br />
<br />
<b>We do [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140955 not recommend] using JDK 1.6 on Eclipse 3.1.</b> (It works fine with Eclipse 3.2 or 3.3.) To use JDK 1.6 on Eclipse 3.1, you must add the following line to your <code>config.ini</code>file:<br />
<code><br />
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,<br />
J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6<br />
</code><br />
<br />
== What version of Mylyn is distributed with the Eclipse downloads? ==<br />
<br />
The [http://www.eclipse.org/downloads/ default Eclipse downloads] contain the following Mylyn redistributions. Since the redistributed versions can be missing important bug fixes or feature additions, we recommend using the [http://www.eclipse.org/mylyn/downloads latest version of Mylyn].<br />
<br />
* Eclipse IDE for Java Developers: all of Mylyn except Team integration (e.g. automatic change sets) integration. Install the Eclipse CVS integration and then install the latest Mylyn build to get this component.<br />
<br />
* Eclipse IDE for Java EE Developers: all of Mylyn redistribution, install manually<br />
<br />
* Eclipse IDE for C/C++ Developers: no Mylyn redistribution, install manually<br />
<br />
* Eclipse for RCP/Plug-in Developers: all of Mylyn redistributed<br />
<br />
* Eclipse Classic: no Mylyn redistribution, install manually<br />
<br />
== My tasks or queries disappeared, what do I do? ==<br />
<br />
This happens if Mylyn failed to install. First ensure that you have a correct install by following the instructions in the next section. After that, if you still do not see your tasks use the ''Task List'' view menu -> ''Restore Tasks From History...'' command (also available via ''File -> Import -> Task List''.<br />
<br />
== Installation Troubleshooting ==<br />
<br />
''' Java Persistence API Tools error when updating the JEE Eclipse Package '''<br />
<br />
If you are trying to install additional features and get this error you have hit [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194959 bug 194959] which should be resolved soon. The work-around is to check off the ''Europa Discovery Site'' and install the first two components of the ''Data Tools Platform''.<br />
<br />
''' Update failures '''<br />
<br />
On Eclipse versions earlier than 3.3 (final) use '''only the "Search for new features.."''' option when updating Mylyn. If you use "Search for updates..." the Update Manager will allow a partial install that can cause Mylyn to fail to start, and you will need to run update again. See the ''feature configuration problem'' section below for details. If you encounter this problemm consider voting for Platform [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132450 bug 132450].<br />
<br />
''' Startup exceptions '''<br />
<br />
If you see startup errors or warnings such as <code>BundleException</code> or timeout messages restart Eclipse with the <code>-clean</code> flag either on the command line, in your shortcut link, or by temporarily it into the <code>eclipse/eclipse.ini</code> file. If that does not resolve the problem please [http://www.eclipse.org/mylar/bugs.php file a bug].<br />
<br />
''' Incompatible VM (e.g. JDK 1.4) '''<br />
<br />
If you are using the wrong VM, you'll see errors like the following in your log file. <br />
<code><br />
Root exception: java.lang.UnsupportedClassVersionError:<br />
org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)<br />
</code><br />
<br />
See [[#Download_and_configure_Java_5_or_6|Configure Java]] to fix this problem.<br />
<br />
''' Incompatible version of Eclipse '''<br />
<br />
Separate versions and update sites exist [http://eclipse.org/mylyn/dl.php for Eclipse 3.1 and 3.2]), in which case you may see errors like the following in your <code><workspace>/.metadata/.log </code>file or in a Mylyn view:<br />
<code><br />
java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()<br />
The activator org.eclipse.mylar.java.MylarJavaPlugin for bundle org.eclipse.mylar.java is invalid<br />
</code><br />
<br />
''' Mylyn feature configuration problem '''<br />
<br />
If the above do not address the issue, the easiest thing to do is uninstall any old versions and update to the latest Mylyn. Your tasks won't be lost, because by default they are stored in the <code><workspace>/.metadata/.mylyn</code> folder which will be read next time Mylyn starts correctly. <br />
* First, uninstall the old version of Mylyn using ''Help -> Software Updates -> Manage Configuration''. <br />
* You need to Disable all Mylyn features by right-clicking them.<br />
* Allow Eclipse to restart after the last is disabled.<br />
* After restart, ensure that the 3rd toolbar button is pressed (figure below) so that you see the disabled features to uninstall.<br />
* Uninstall all the disabled features using the popup menu. <br />
<br />
If you don't uninstall, the the Update Manager will think that you have the latest and tell you that there are no updates. <br />
<br />
<b>Note: manually removing the plug-ins and features can lead to configuration errors.</b> <br />
<br />
After uninstalling, update Eclipse by adding the correct update site specified at on the [http://eclipse.org/mylar/dl.php download page], and after that automatically or manually updating will install the correct version.<br />
<br />
[[Image:mylar-eclipse-manage-configuration.gif]]<br />
<br />
'''What do I need to do in installation to be able to use Mylyn task management features with bug/task/issue trackers?'''<br />
<br />
When you install, make sure that you select a connector for your bug/task/issue tracking software. For example, to use Bugzilla, you have to install the Bugzilla connector component.<br />
<br />
'''I've installed Mylyn ; why can't I see anything different?'''<br />
<br />
The two most likely possibilities are:<br />
# You don't have any Mylyn views open. Select ''Window -> Show View -> Other'', then select ''Mylyn'' and you should see the available Mylyn Views. <br />
# If you still don't see anything, then perhaps you aren't using the JDK1.5 VM (or later). See [[Mylyn_Installation_Guide#Download_and_configure_Java|configuring Java]].<br />
<br />
<br />
'''What does the error "Network connection problems encountered during search" mean?'''<br />
<br />
If you get that message while trying to download Mylyn, it means that Eclipse couldn't find the location you entered. This might be because you copied something incorrectly (watch for extra characters -- even extra spaces can cause errors), or because the site went down. You may be able to see if the site is up or down by copying the URL into your Web browser.<br />
<br />
'''What does the "Update manager failure" message mean? '''<br />
<br />
It means that Eclipse could not access the update site, or that it got confused about the configuration state of your Eclipse. First try updating again to see if the update site is accessible. <br />
<br />
If you are trying to update the JIRA connector you can also try de-selecting that feature in case the <code>Tigris.org</code> update site is not accessible. Using ''Search for new features to install..'' when installing can help to avoid this problem. If that does not work see the feature configuration troubleshooting below. <br />
<br />
'''What does "Could not create Browser page: No more handles (<code>java.lang.UnsatisfiedLinkError: ...</code>)" mean?'''<br />
<br />
It probably means that you are running Linux and don't have Eclipse and a Web browser configured to work together. See [[http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux| installing a browser on Linux]].<br />
<br />
'''When downloading, why do I get a warning that the feature was unsigned?'''<br />
<br />
Signing plugins requires extra administrative details with <code>eclipse.org</code> which most plug-ins seek to avoid. <br />
<br />
'''N.B.''': Security issues with features should not be underestimated. Eclipse allows users to download new functionality from remote servers. A rogue plug-in can act as a perfect Trojan horse. It can look innocent enough and provide useful function while spawning threads in the background with full access to the local file system and the Internet (if connected). Beware of installing features from update sites you do not trust.<br />
<br />
'''What does "<code>Root exception: java.lang.UnsupportedClassVersionError: org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)</code>" mean?'''<br />
<br />
It probably means that the virtual machine is JDK1.4 or lower. See [[Mylyn_Installation_Guide#Download_and_configure_Java| download and configure Java]].<br />
<br />
'''Why am I getting messages in my <code><workspace>/.metadata/.log</code> or my Mylyn view that say things like <code>"java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()"</code> and "The activator <code>org.eclipse.mylar.java.MylarJavaPlugin</code> for bundle <code>org.eclipse.mylar.java</code> is invalid"?'''<br />
<br />
This probably means that your Mylyn download version didn't match your Eclipse download version. Note that [http://eclipse.org/mylar/dl.php the download site] has different downloads for Eclipse 3.1 and Eclipse 3.2.<br />
<br />
To fix this problem, see the [[Mylyn_Uninstallation_Guide| uninstallation guide]], then re-install from [http://eclipse.org/mylar/dl.php the correct download site].<br />
<br />
'''What does "Could not create Bugzilla editor input" and "<code>java.io.IOException</code>: SAX2 driver class <code>org.apache.xerces.parsers.SAXParser</code> not found" mean?'''<br />
<br />
It probably means that you are on MacOS, and for some reason are missing Xerces from the Mac JDK1.5. You will probably need to add it to your default classpath. Please refer to and comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=144287 bug 144287] if you see this problem.<br />
<br />
To ensure that you are using the 1.5 VM refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
'''I've just updated to Mylyn 2.0 and I don't see any tasks in my Task List'''<br />
<br />
As part of the update to Mylyn 2.0 the old data folder has been migrated to <workspace folder>/.metadata/.mylyn from the old location <workspace folder>/.mylar. IF for some reason migration failed (.mylar folder still exists), simply shut down Eclipse and manually move your old <workspace folder>/.mylar folder to <workspace folder>/.metadata/.mylyn (note the name change to .mylyn)<br />
<br />
== Configuration Troubleshooting == <br />
<br />
'''How can I change the number of editors left open before Mylyn starts closing editors?'''<br />
<br />
Turn off or increase the number of editors to leave open using ''Preferences -> General -> Editors -> Number of opened editors before closing''. Since Mylyn will manage the open editors with task activation, this number can be set higher or you can disable automatic closing entirely.<br />
<br />
'''Do I need the Outline View when running Mylyn?'''<br />
<br />
No, not really. The Package Explorer and folded signatures should provide enough context for you. If, at some point, you really need to see an Outline View, you can always enter (Ctrl+O) to show the in-place Outline View.<br />
<br />
'''What does the message "content assist proposals no longer appear" mean?'''<br />
<br />
This usually happens when uninstalling when using Eclipse 3.2. Make sure that the "Java Completions" and "Java Types" proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
'''Why do I get errors like "HTTP Response Code 407" or "Proxy Authentication Error" when accessing repositories through a proxy server?'''<br />
<br />
It is likely that you need to configure these proxy server settings. Select ''Window -> Preferences -> Install/Update'', and update the section in the "Proxy settings" section of the form.<br />
<br />
'''I can't use <code>Ctrl+Alt+Shift+Arrow Up</code> for'' Mark as Landmark''. What do I do?<br />
<br />
This is usually a Linux/GNOME problem, where the Gnome keyboard shortcuts are interfering with the Eclipse shortcuts. Go to the Keyboard shortcuts (which might be something like ''Desktop -> Control Centre -> Keyboard Shortcuts'' or ''System -> Preferences -> Keyboard Shortcuts'') and disable both of these shortcuts:<br />
* Move one workspace up<br />
* Move one workspace down<br />
<br />
See also: [[Mylyn_User_Guide#Keyboard_mappings_on_Linux| keyboard mappings on Linux]].<br />
<br />
'''How do I turn on spell checking?'''<br />
<br />
See [[Mylyn_User_Guide#Spell_Checking| spell checking]].<br />
<br />
== Uninstall troubleshooting ==<br />
<br />
When '''uninstalling in Eclipse''' Mylyn via the ''Help -> Software Updates -> Manage Configuration'' dialog you will need to uninstall dependencies first (e.g. Bugzilla Connector, Subclipse integration) and then uninstall the core Mylyn features.<br />
<br />
When '''uninstalling manually''' by deleting all of the Mylyn plug-ins and features from the <code>eclipse/plugins</code> and <code>eclipse/features</code> directory make sure to delete all of the plug-ins and then restart Eclipse with the -clean option (e.g. by inserting it into a shortcut or the <code>eclipse.ini</code> file.<br />
<br />
On '''Eclipse 3.1:''' you may need to reset the Java editor to be default for <code>.java</code> again via: ''Preferences -> General -> Editors -> File Associations''<br />
<br />
On '''Eclipse 3.2:''' if after uninstalling '''content assist proposals no longer appear''' you need to ensure that the ''Java Completions'' and ''Java Types'' proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
== I am seeing <code>java.lang.OutOfMemoryError: PermGen space </code>errors, what's wrong? ==<br />
<br />
If your Eclipse crashes, or you see the above error after installing Mylyn or other plug-ins, you have most likely hit the infamous MaxPermSize bug. This is not a Mylyn specific problem, but a general Eclipse problem that is often triggered on Eclipse 3.2 and later, if you have many plug-ins installed and are using a Sun JVM. <br />
<br />
To fix it simply add the following to your launch arguments. This is usually to your shortcut, or to the <tt>eclipse/configuration/config.ini</tt> file:<br />
<br />
-XX:MaxPermSize=128M<br />
<br />
If you are using a large number of plug-ins (e.g. WTP) you may need to increase the number to more than 128M. <br />
<br />
Details of the problem are on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250 Platform bug 92250].<br />
<br />
= Task List =<br />
<br />
== Why won't the Archive category disappear? ==<br />
<br />
The ''Archive'' category will automatically appear if a task needs to be shown, but is not in any query or category. <br />
In order to ensure that you do not miss reminders or notifications the following tasks will always be shown in the Task List, even if they have been removed from a category or a query:<br />
* Tasks scheduled for this week or overdue. Remove these by using the ''Schedule'' pop-up menu option to defer them to a future week or to clear the schedule.<br />
* Repository tasks that have incoming changes, such as comments. Remove these by reading them or marking them as "read" via the ''Mark -> Read'' pop-up menu.<br />
<br />
== The Archive category contains many irrelevant tasks, how do I clean it up? ==<br />
<br />
If you created very broad queries you could end up with thousands of tasks in the Archive category. Other than clearing the <tt>workspace/.metadata/.mylyn/tasklist.xml.zip</tt> and <code>workspace/.metadata/.mylyn/offline</code> folder (note that this will entirely reset your Task List) the easiest option is to:<br />
* Clean up your queries to include only tasks of interest (note that including completed/resolved tasks is recommended).<br />
* Turn off ''Focus on Workweek'' in the ''Task List''.<br />
* Turn off the ''Filter Archive Category'' option in the ''Task List'' view menu.<br />
* Delete all of the unneeded tasks from within the Archive category. Note that if the tasks are not matched by queries they will be deleted permanently and any local notes or scheduling information that you have added to them will be lost.<br />
<br />
== How does Mylyn count the active time for a task? ==<br />
<br />
Whenever you work on a task, Mylyn accumulates the time you spend actively working on a task. This time can be viewed in the ''Personal Planning'' section of the ''Task Editor''. When you are not interacting with Eclipse, the timing automatically times out after 3 minutes by default. This means that activity outside of Eclipse will not be captured when you work on the task and that the timings in Mylyn are a lower bound of the total time spent on the task (capturing timings for work done outside of Eclipse involves OS specific extensions).<br />
<br />
== How do I prevent long-running tasks from adding to the progress bar? ==<br />
<br />
If you have many long-running or recurring tasks scheduled for this week, they can affect the ''Task List'' weekly progress bar. This can be misleading as they may never be completed. The current work-around to prevent long-running tasks from being included in the weekly progress bar is to schedule their estimated time to be 0 (zero). Alternatively, you can schedule only the amount of time you plan on spending on that task this week.<br />
<br />
== Does the Task List replace the Eclipse Tasks view? ==<br />
<br />
The SDK's ''Tasks'' view is used for showing markers such as 'todo' tags which indicate a local problem with a resource, similar to a compiler warning. As such, these 'tasks' are at a much lower level of granularity than Mylyn's tasks, and one task could involve cleaning up multiple todos. In order to make working with only the markers in a particular task context, e.g. for clean-up before committing, the ''Apply Mylyn'' filter is available for both the ''Problems'' and the ''Tasks'' views.<br />
<br />
== What if I use multiple workspaces? ==<br />
<br />
Mylyn's support for multiple workspaces is currently limited (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130658 bug 130658] for a discussion) because the Task List is considered to be specific to the person, and not to the workspace. We recommend configuring your Eclipse workspace to use working sets instead of relying on multiple workspaces. <br />
* John O'Shea's blog: [http://www.xlml.com/aehso/2007/02/02/eclipse-workspaces-containing-projects-with-overlapping-locations-and-mylar/ Eclipse workspaces containing projects with overlapping locations, and Mylar]<br />
<br />
If using a single workspace is not possible you can do the following:<br />
* In ''Preferences -> Mylyn -> Task List'' set the ''Data Directory'' to be a shared location, and do this for both workspaces.<br />
* Be sure to avoid launching both Eclipse workspaces at the same time, as changes in one workspaces could overwrite the Task List in the other workspace.<br />
* If you upgrade Eclipse or move your workspace and don't see your tasks, check the ''Data Directory'' setting.<br />
<br />
== How do I export my task and repository data? ==<br />
<br />
Export via File > Export > Mylyn > Task Data<br />
<br />
== Why does Mylyn use the term "task"? ==<br />
<br />
There are many work items that make up the developer's workday. Many issue trackers and project management tools refer to these as: bugs, defects, actions, tickets, stories, enhancements, and the list goes on. We refer to all such work items as "tasks" because the word tasks is short and commonly used in time management tools. Task Repository connectors can customize the presentation of tasks, for example, indicating which is a defect and which is an action item.<br />
<br />
= Task Editor =<br />
<br />
== Why am I seeing strange boxes where I expect to see proper characters? ==<br />
<br />
If for example you aren't seeing the proper single quote chacters in the summary of [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=197644 bug#197644]], check that the encoding is set correctly for the repository in the asociated Task Repositories view (Properties > Additional Settings > Character Encoding). For bugs.eclipse.org/bugs set your charcter encoding to ''ISO-8859-1''.<br />
<br />
= Task Repositories =<br />
<br />
== What if Mylyn doesn't support my task/bug/issue/ticket repository? ==<br />
<br />
To see support for your repository faster, do a search of the open repository connector requests and [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Bconnector%5D&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=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= vote for the corresponding bug] if your tracker is there, or [http://www.eclipse.org/mylar/bugs.php create a new bug]. <br />
<br />
[[Mylyn_User_Guide#Generic_Web_Repository_Connector|Generic Repository Connector]], allows creating Queries to the web-based issue tracking repositories and get list of issues from the web UI into the Task List.<br />
<br />
It is also possible to link a ''local task'' with the web page in web-based repository via the Mylyn Web integration.<br />
<br />
'''To create a task from any web-based repository:'''<br />
<br />
* Drag the URL from the address bar of the browser, or from a hyperlink in a bug listing to the ''Mylyn Tasks'' view. This will create a task for the bug, link it to the page, and populate the description with the title of the corresponding page. '''In Mozilla:''' simply drag the URL. '''In Internet Explorer:''' you must have <code>Ctrl</code> pressed in order for Eclipse to recognize the drop.<br />
* '''Alternatively,''' you can copy the URL, press the ''New Task'' button on the ''Mylyn Tasks'' view. This has the same effect as above but you can edit the description after retrieving it.<br />
* Opening the task will now open the corresponding issue. You can also <code>right+click</code> the task and select ''Open in External Browser''.<br />
<br />
[[Image:mylar-tasklist-weblink-editor.gif]]<br />
<br />
== Why were my repository credentials reset? ==<br />
<br />
If you upgrade Eclipse or your Java VM, you will need to reset your credentials in the ''Task Repositories'' view because these are stored in the secure Eclipse workbench keyring. Also see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=149607 bug 149607]. If you are migrating '''from Eclipse 3.2 to 3.3''' note that you will need to use a different update site, which is listed here: http://eclipse.org/mylyn/dl.php<br />
<br />
== Why are my updated repository attributes not showing up? ==<br />
<br />
Your server's repository attributes can change frequently, for example, there can be a new "milestone" or "version" added to the Bugzilla repository with each release. When the ''Preferences -> Mylyn -> Task List -> Synchronization'' setting is enabled, every 10th synchronization will update the attributes from the repository. If you do not have this setting enabled, your can force the update via the ''Update Attributes'' action on the task repositories' context menu in the ''Task Repositories'' view. Note that you will need to reopen a task editor to see the updated attributes. If you instead update via the button on the ''Attributes'' section of the ''Task Editor'' the attribute settings will be reloaded without needing to reopen.<br />
<br />
== Authentication Troubleshooting ==<br />
<br />
You must ensure repository credentials are filled out correctly. Refer to the diagram below:<br />
<br />
[[image: AuthenticationTroubleshooting2.png|right]]<br />
<br />
# Enter the repository URL (i.e. https://bugs.eclipse.org/bugs) and an optional label<br />
# Credentials<br />
#* Usually email address and password <br />
#* Some sites, such as <code>dev.eclipse.org</code>, use anonymous logon with password left blank.<br />
#Http Authentication (optional)<br />
#* Some sites are protected by either BASIC or DIGEST http authentication. If this is the case, enter appropriate credentials here.<br />
#* One way to test if the site requires http authentication is to point your browser at the repository. If you are presented with an authentication dialog popup, the site is likely protected by http authentication.<br />
#Proxy Server Configuration (optional)<br />
#* By default Mylyn uses the Platform's Install/Update proxy settings. Uncheck this box if you wish to use an alternative proxy.<br />
#* If the proxy requires authentication, this is where you enable and enter your proxy credentials.<br />
#* If you are experiencing connection problems, ensure your Install/Update proxy settings are valid or the repository specific settings are correct<br />
#* Mylyn has been tested with HTTP proxy servers. Currently SOCKS is not supported.<br />
#Validate Settings <br />
#*Press the ''validate'' button to test the settings<br />
#*If you are seeing errors like "HTTP Response Code 407" or "Proxy Authentication Error" it is likely that you need to configure proxy settas as described above.<br />
#*If your sever uses a certificate and fails to connect, e.g. you see exceptions <tt>sun.security.validator.ValidatorException: PKIX path building failed</tt> then you need to point Eclipse at your certificate, see the [http://ahtik.com/blog/2006/05/11/fixing-eclipse-mylar-jira-integration/ instructions on this blog].<br />
<br clear="all" /><br />
<br />
=== NTLM authentication ===<br />
<br />
For NTLM authentication to work a special format for the username needs to be used where ''DOMAIN'' needs to be replaced by the Windows login domain: <br />
<br />
DOMAIN\username <br />
<br />
The built-in NTLM support of the JDK which is used by Eclipse does '''not work''' with Mylyn since it uses the HttpClient library to access repositories. Limitations in regard to NTLM authentication are documented in the [http://wiki.apache.org/jakarta-httpclient/FrequentlyAskedNTLMQuestions NTLM FAQ] and also discussion on {{bug|201911}}.<br />
<br />
* If your repository uses MS NTLM authentication and only standard http authentication is being passed to the repository this can result when the local hostname cannot be resolved. Ensure your machine's hostname is set correctly and resolves to a valid address.<br />
* It is not possible to use NTLM authentication for the proxy as well as for the repository.<br />
<br />
If NTLM authentication fails the '''[http://ntlmaps.sourceforge.net/ NTLM Authorization Proxy Server]''' has been reported to '''work''' with Mylyn.<br />
<br />
== Why are task hyperlinks not working? ==<br />
<br />
For task hyperlinks in textual editors (e.g. Java editor) and other text viewers (e.g. History view comments) you must associate the project that contains the resource to the task repository. <br />
<br />
:''Project association can also come from 3rd party metadata trough the contrubuted [[Mylar_Integrator_Reference#Mapping_from_projects_to_Task_Repositories|extension point]]. [http://subclipse.tigris.org/ Subclipse] and [http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Mylyn Maven integration for Eclipse] plugins contributing it. See few more details [http://jroller.com/page/eu?entry=linking_projects_from_the_eclipse here].''<br />
<br />
Note that to view a hyperlink you must hold down the <code>Ctrl</code> key when hovering over the reference to the task. References to tasks are connector specific and the common reference is found on the top left of the task editor and other conventions tend to follow those used in the web UI (e.g. "bug 123" for Bugzilla, "ABC-123" for JIRA).<br />
<br />
[[Image:mylyn-project-repository-association.gif]]<br />
<br />
= Bugzilla Connector =<br />
<br />
== What versions are supported? ==<br />
<br />
We recommend using the latest [http://www.bugzilla.org/download/ release] of Bugzilla.<br />
<br />
* '''Bugzilla 2.18.6 is the lowest version of Bugzilla supported'''. If you are getting errors that indicate failure to update attributes this may be an indication that the Bugzilla server is not supported (< 2.18.6).<br />
<br />
*If you are using '''Bugzilla 2.18''' and are getting '''mid-air collisions''' this is likely due to incorrectly formatted timestamp field in the underlying bugs database table ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149513 bug 149513]). This can be resolved by upgrading to Bugzilla 2.20 or later.<br />
<br />
== Why are queries failing? ==<br />
<br />
*If '''queries are not working''' correctly ensure that you have the right Bugzilla server version selected for the corresponding repository: ''Task Repositories (View) ->'' right+click the repository ''-> Properties''. For supported versions see the [http://www.eclipse.org/mylar/dl.php download page]. If the repository is still not functioning it may be due to authentication or connectivity problems. If that does not resolve the problem please post a message to the newsgroup or [http://www.eclipse.org/mylar/bugs.php submit a bug].<br />
<br />
== Why do tasks fail to open? ==<br />
<br />
*If upon opening a bug, the Bugzilla tab only displays a warning "'''Could not download task data, possibly due to timeout or connectivity problem. Please check connection and try again.'''", ensure that your repository is returning XML data by pointing your browser to <code><your-repository-url>/show_bug.cgi?id=1&ctype=xml</code> to show the contents of bug 1 in XML form. The Bugzilla client requires that bugs be accessible in XML form. If the repository doesn't support xml then it is likely that the repository is too old (Mylyn currently supports Bugzilla 2.18 and later).<br />
<br />
* If '''reports fail to load''' or '''reports fail to synchronize''' (task description remains ''italic''), check the error log for a "'''File not found'''" error pointing to <code>bugzilla.dtd</code> or a "'''Failed to retrieve products from server'''" error message - these result when the <code>urlbase</code> parameter is not set on the bugzilla server, or your bugzilla installation is missing the <code>bugzilla.dtd</code> file. See: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=161759 bug#161759]<br />
<br />
* If '''attributes are missing options''' in the bug editor (ie. missing a recently added milestone, [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155431 bug# 155431]):<br />
** Update attributes by choosing ''Update Attributes'' from the context menu in the ''Task Repositories'' view<br />
** Synchronize the task in the Task List<br />
** Reopen the task - new options should be available.<br />
<br />
== Why do tasks fail to submit? ==<br />
<br />
* '''Error upon submit: unable to make any match for name/email entered.''' If your bugzilla is configured for user names rather than full email address the QA Contact field will cause the submit to fail ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=166555 bug# 166555]). To resolve, select 'Local users enabled' option on the Repository Configuration page. <br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your account's username and password and are not using the HTTP authentication fields instead.<br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your bugzilla instance's cookie domain under the required settings. The cookie domain must lead with a dot.<br />
<br />
* If '''attachments are failing to submit''' and you see that after processing the attachment, the bugzilla bug shows a size of "bytes" (no numbers), your database may be dropping the packet sending the file. '''On MySQL''', check the [http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html max_allowed_packet directive]. You may see errors like: <code>DBD::mysql::st execute</code> failed: Got a packet bigger than 'max_allowed_packet' bytes [for Statement "INSERT INTO attach_data (id, thedata) VALUES (38, ?)"] at <code>/path/to/bugzilla/attachment.cgi</code> line 993. Also, '''check the maximum attachment size''' in ''Bugzilla Parameters -> Attachments''.<br />
<br />
* If a submit fails with an '''Invalid Username or Password''' error even though repository settings do validate, make sure that cookies could be set. See also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175502 bug 175502]<br />
<br />
== What time zone is used in the task editor? ==<br />
<br />
*The '''times''' that appear in the Bugzilla bug editor (ie. created, modified) '''are local to the server hosting the Bugzilla repository''', not your local machine's time zone. <br />
<br />
== Known limitations ==<br />
<br />
* The <code>usermatchmode</code> is not currently supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168204 bug 168204]) and as such full email addresses need to be used.<br />
<br />
* The <code>usevisibilitygroups</code> parameter is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=180876 bug#180876]). Group assignment will currently be lost if updated using the Bugzilla rich task editor.<br />
<br />
* Version 1.0 of Mylyn presents an error message upon new comment submission to RedHat's public Bugzilla repository. The comment is in fact posted. This issue is resolved in Mylyn 2.0M2 and higher. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=183251 bug#183251])<br />
<br />
= JIRA Connector =<br />
<br />
If you see errors like the following, work around this by opening repository ''Properties Page'' and clicking OK (bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169102 169102]).<br />
<br />
org.tigris.jira.core.service.exceptions.AuthenticationException<br />
at org.tigris.jira.internal.core.service.soap.SoapJiraService.getProjectsNoSchemes(SoapJiraService.java:204)<br />
<br />
== What are the server requirements? ==<br />
<br />
The '''JIRA SOAP/RPC services have to be running on the JIRA server''':<br />
<br />
* Jira 3.3.3 or higher (3.7 or higher for attachment retrieval)<br />
* Jira RPC plugin 1.4.3 or higher<br />
<br />
Latest information also available on the [http://www.eclipse.org/mylar/dl.php download page].<br />
<br />
Related Resources:<br />
<br />
* [http://confluence.atlassian.com/display/JIRA/JIRA+Development+Hub Jira Development Wiki]<br />
* [http://confluence.atlassian.com/pages/viewpage.action?pageId=1035 Jira RPC Plugin Overview]<br />
<br />
== Why can't I connect? ==<br />
<br />
* If you get a <code>org.tigris.jira.core.service.exceptions.ServiceUnavailableException</code> you need to turn on the JIRA SOAP/RPC services on the server.<br />
* Similarly, if you get a "Processing instructions are not allowed within SOAP messages" message, ensure that SOAP/RPC services are on.<br />
* If you get a '''503''' error code verify that the SOAP/RPC interface is enabled.<br />
* If you get a '''403''' error code verify that the SOAP/RPC interface is enabled, and also check your authentication mechanism. If the server is using NTLM authentication, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156397 bug 156937] for diagnosis steps.<br />
* If you see an '''"unrecognized priority" message''' in the ''Error Log'', the problem is that the JIRA Connector does not support customized priorities so the priority value specified in that message will not correspond to the priority icons visible in the Task List.<br />
* If you are being '''prompted for your log-in credentials''' by the Browser tab of the task editor or the new task editor, this is because without rich editor support the connector is using the web-based UI instead of logging in on your behalf as is done with a rich task editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142869 bug 142869]).<br />
* If you get a <CODE>AuthenticationException</code> and a query won't synchronize, use Task Repositories (view) -> Properties (on the repository) -> Validate Settings. This will clear the connection if it died.<br />
<br />
<!-- HEAVILY OUTDATED. PLUGIN NOW USES COMMON PROXY INFRASTRUCTURE<br />
== Why can't I synchronize when using a proxy server? ==<br />
<br />
* Proxy configuration is '''based on the normal Java HTTP system properties''', which can be configured either by launching Eclipse with <code>-vmargs</code> and using the following settings, or by putting these settings into the or by putting the following into the <code>eclipse/eclipse.ini</code> file (after -vmags):<br />
-Dhttp.proxyHost=<host> <br />
-Dhttp.proxyPort=<port><br />
* Make sure that when using these settings you do not enable the proxy settings on the ''Install/Update'' preference page, since they may override these settings.<br />
* If you are using '''SSL''', you will also need to set the <code>https.proxyHost</code> and <code>https.proxyPort</code>. <br />
* Authentication is configured with the <code>http.proxyUser</code> and <code>http.proxyPassword</code> system properties (also for SSL)<br />
* You can also use <code>http.nonProxyHosts</code> system property to enumerate hosts that should not be proxied. Note that matching is implemented on the exact host name used for JIRA server and patterns are not supported. --><br />
<br />
== Known limitations ==<br />
* Attachment retrieval (including retrieval of the task context and attachment list in the task editor) require JIRA 3.7 or above ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=169757 bug 169757])<br />
<!-- * NTLM authentication is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172395 bug 172395]) --><br />
* Customized priorities are not currently supported, so all issues with a customized priority will have the default priority level ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=165518 bug 165518]).<br />
* blank but editable custom fields doesn't appear in the RSS data, and as result we can't show them for editing<br />
* because of JIRA api limitations, we can support custom fields in the task editor, but not in the new custom task editor<br />
<!-- * On JIRA 3.6.x private filters saved on the server can fail to retrieve results ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=174328 bug 174328]). The work-around is to create a custom query in Mylyn using the form-based query designer or to share the filter in JIRA. --><br />
<br />
== How can I enable compression for SOAP messages? ==<br />
<br />
If your repository has lots of projects and components you can speed up the download of the repository configuration by enabling compression. <br />
<br />
* Add a filter-mapping to your JIRA server configuration: [http://jira.atlassian.com/browse/JRA-10353].<br />
* Enable compression in your global JIRA configuration.<br />
* Check the compression setting for your task repository in Mylyn versions 2.0M2 and later.<br />
<br />
== Reporting issues ==<br />
<br />
Since JIRA can be heavily customized there is a chance that some particular customizations may not work, so if you can't connect to your proprietary repository it is a good idea to try the following public repositories to make sure you have working configuration:<br />
<br />
* http://jira.codehaus.org<br />
* http://issues.apache.org/jira/<br />
* http://opensource.atlassian.com/projects/spring <br />
<br />
If you can't get query results, you could try to call "Open with Browser" on query node in the Task List view and then save link "Current view: XML" and attach it to the bug report.<br />
<br />
Even if query don't work you could try "Open Repository Task" from your JIRA repository node on the Task Repositories view and check if you can open JIRA task editor for that issue. Same for the Task search (Ctrl-H, Task Search)<br />
<br />
To investigate various error you may need to enable debug tracing. To do that you need to create the <code>.options</code> file with the following content:<br />
<br />
<pre><br />
org.eclipse.mylyn.jira.ui/connector=true<br />
org.eclipse.mylyn.jira.ui/dataHandler=true<br />
</pre><br />
<br />
and then add the following options to the Eclipse command line (or eclipse.ini file):<br />
<br />
<pre><br />
-debug <path to the .options file>/.options<br />
</pre><br />
<br />
The additional logging will go into the regular Eclipse log and the Error Log view<br />
<br />
= Trac Connector =<br />
<br />
== What are the server requirements? ==<br />
<br />
The Trac connector offers two access methods:<br />
<br />
'''XML-RPC''' (recommended)<br />
<br />
Requirements:<br />
* Trac 0.10<br />
* [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] rev. 1950<br />
<br />
This access method offers editing of tasks in a rich editor, attachment support and offline editing. It requires the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] for Trac to be enabled for the accessed repository. The XmlRpcPlugin provides a remote interface to the Trac repository and is distributed separately from Trac (see [http://trac.edgewall.org/ticket/217 #217]). See these [http://trac-hacks.org/wiki/XmlRpcPlugin#Installation install instructions] for requirements and documentation.<br />
<br />
'''Web''' <br />
<br />
Requirements:<br />
* Trac 0.9 or later<br />
<br />
In this mode the standard Trac web interface is used for repository access. Tickets may be created and edited through a web browser. Offline editing and attachments are not supported.<br />
<br />
== Recommended Trac version ==<br />
<br />
Mylyn should work with any stable release Trac release that is version 0.9.x or 0.10.x (see below for known limitations). Mylyn works best when used with Trac's XML-RPC Plugin (see above) but we do not recommend a particular Trac version. <br />
<br />
The Trac connector tests are run against these Trac versions:<br />
<br />
* Trac 0.10.4, XML-RPC Plugin rev. 1950<br />
* Trac 0.9.6<br />
<br />
See {{bug|175211}} for details about Trac 0.11 support.<br />
<br />
== Why do I get an HTTP Error 500 Internal server error when creating a ticket that contains non-ASCII characters? ==<br />
<br />
Problems related to character encodings have been reported when Trac is run with Python 2.3. Upgrading to Python 2.4 may help to resolve this. Please comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=188363 bug #188363] if you encounter an internal server error when creating a ticket that contains non-ASCII characters.<br />
<br />
== Known limitations ==<br />
<br />
* Trac 0.10.1 <br />
** Known incompatibility with Trac XML-RPC Plugin. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164272 bug 164272] for details.<br />
* Trac 0.10.3 <br />
** Known incompatibility with old versions of the Trac HttpAuthPlugin (fixed in revision 1890 or later). The plug-in enables basic auth for XML-RPC when Trac AccountManagerPlugin for form based authentication is used. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168413 bug 168413] for details.<br />
* Trac 0.11<br />
** Currently untested.<br />
** Known incompatibility with Trac XML-RPC Plugin See [http://trac-hacks.org/wiki/XmlRpcPlugin] for details.<br />
<br />
== Why are tasks opened in a web browser and not in the rich editor? ==<br />
<br />
Please make sure that the access type in the repository properties is set to XML-RPC. This requires Trac 0.10 and XML-RPC (see above).<br />
<br />
== Which URLs does Mylyn access in a Trac repository? ==<br />
<br />
XML-RPC:<br />
<br />
* The expected URL is either /xmlrpc or /login/xmlrpc (if login credentials are provided)<br />
<br />
Web:<br />
<br />
* Authentication: /login <br />
* Querying: /query?format=tab...<br />
* Synchronizing ticket details: /ticket/...<br />
* Getting repository configuration to populate query dialog: /query or /newticket<br />
<br />
The web mode relies on screen scraping and is likely to fail if the design<br />
(i.e. HTML output) of the Trac repository is heavily customized.<br />
<br />
= Generic Web Repository Connector =<br />
<br />
== Where can I find the web repository connector ==<br />
<br />
It is available from the extensions update page. Please see http://www.eclipse.org/mylyn/downloads/<br />
<br />
== Why can't I connect using one of the existing templates? ==<br />
<br />
<br />
The Web Repository Connector have a Preview option in Advanced Configuration section on the Query preferences. If you get an error or preview table does not show expected list of tasks you can use Query Pattern like (.+?)(\n) to see content of the retrieved page and compare it with the source of the web page for the same url loaded into the web browser.<br />
<br />
If that does not help then you could use the wget tool (on Windows it available as a standalone command line tool and also included with Cygwin).<br />
<br />
Run the following command:<br />
<br />
<pre>wget -v -d -o query.log -O query.html "http://your.query.url"</pre><br />
<br />
If repository require basic http auth, you'll need to use ''--http-user=USER'' and ''--http-password=PASS'' options.<br />
<br />
Then open file ''query.html'' in the web browser and check if it show list of issues you need to fetch from the web server. If it does have correct list, then there could be a problem with query pattern used for parsing. <br />
<br />
A popular mistake is an unmasked '?' that separates request parameters in the url). For example:<br />
<br />
<pre><a href="show_bug.cgi\?id\=(.+?)">.+?<span class="summary">(.+?)</span></pre><br />
<br />
If ''query.html'' does not show expected list of issues you can check ''query.log'' for server responses and try to identify if server require authentication, redirecting your requests somewhere or issue any other errors.<br />
<br />
== Known limitations ==<br />
<br />
* In Mylyn 1.0: if a web server responds by requesting a redirect to an absolute URL while fetching a resource, the connector falsely prepends "/" to the URL and the request will fail. The workaround is to use final url where redirect is pointing to (you can find it as describe above). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=167282 bug 167282] for details.<br />
<br />
= Task-Focused UI =<br />
<br />
== What is the Task-Focused UI? ==<br />
<br />
When you activate a task, Mylyn automatically maintains a task context by monitoring your interaction. The task context provides a predictable degree-of-interest weighting of the relevance of the elements and relations that you work with to the task-at-hand (as described in the [http://kerstens.org/mik/publications/2006-11-mylar-fse.pdf Foundations of Software Engineering conference paper]). The Task-Focuse UI is the mechanism by which Mylyn presents Mylyn the task-context model in order to reduce information overload and to automate the manaul management of UI elements like editors and change sets. Examples:<br />
* Filtering, decoration and expansion management in views<br />
* Automatic folding in editors<br />
* Ranking in content assist<br />
* Editor management<br />
* Perspective management<br />
* Change set management<br />
<br />
== Why do files disappear from Focused views when I close them? ==<br />
<br />
By default Mylyn automatically manages the set of open files to match the task context, so that you don't have to. This ensures that the editor list (viewable via mechanisms like Ctrl+E) corresponds to what you in views like the ''Package Explorer'' when they are in Focused mode. When you close a file manually, you express that it is uninteresting, and as such it will be removed from the task context. It will also disappear from the corresponding automatically managed change sets for the same reason. This behavior can be turned off via ''Preferences -> Mylyn -> Context -> Manage open editors to match task context''. However, it is highly recommended since Mylyn will prevent the number of editors from bloating by automatically closing editors for elements that have decayed in interest, and always keep the editors for interesting elements open.<br />
<br />
<br />
== Why did all my editor tabs disappear? ==<br />
<br />
When you deactivate a task, all editors will be closed, and then when you reactivate the task all the windows will be open again. Try it, it's fun. <br />
<br />
Mylyn actively manages your open editors with task context. It takes some getting used to, but enables switching between tasks when you are multitasking without cluttering your editor tabs. This editor management can be disabled via ''Window -> Preferences -> Mylyn -> Context''. However, before disabling it consider reading the ''"Managing open editors..."'' section of [http://www-128.ibm.com/developerworks/java/library/j-mylar2/index.html#N10116 Task-focused programming with Mylar].<br />
<br />
== How do I get rid of an element if it is not interesting? ==<br />
<br />
When a view is focused elements will disappear on their own if they are not repeatedly selected via a mechanism called interest decay. Note that decay does not use the wall clock, but instead relies on the number of selections that you have made when working on that task to determine which elements disappear. This helps make it feel very predictable.<br />
<br />
If you want want to force one or more elements to disappear from the context use the '''Remove from Focus''' action on the context menu. Note that the element will still be part of the task context since it was previously part of the interaction. <br />
<br />
If you want to permanently delete the element from the interaction history use the '''Remove from Context''' action on the '''Context''' tab of the '''Task Editor'''. For example, if a company private element was part of a task context that is to be shared with a public repository, this action can be used to clean it up before sharing. Note that elements will be removed from the task context recursively.<br />
<br />
== Which Focused UI features can I turn off? ==<br />
<br />
'''All of them.''' When no task is active neither are any of Mylyn's features. When working with task contexts Mylyn's Focused UI features are all optional and in general configurable. While many find it the key benefit of Mylyn, the entire Focused UI is optional and can be uninstalled via ''Help -> Software Updates -> Manage Configuration''.<br />
<br />
The following table summarizes how the key features can be toggled:<br />
<br />
<table><br />
<tr><br />
<td>'''UI Mechanism'''</td><br />
<td>'''Example/description'''</td><br />
<td>'''Toggle using'''</td><br />
</tr><br />
<tr><br />
<td>Interest filtering</td><br />
<td>Package Explorer</td><br />
<td>''Apply Mylyn'' button on view toolbar</td><br />
</tr><br />
<tr><br />
<td>Automatic toggling of filtering</td><br />
<td>Package Explorer</td><br />
<td>''Preferences -> Mylar -> Context -> Toggle focused mode..</td><br />
</tr><br />
<tr><br />
<td>Interest decoration</td><br />
<td>Bolding of landmark elements</td><br />
<td>''Preferences -&gt; General -&gt; Appearance -&gt; Label Decoration''</td><br />
</tr><br />
<tr><br />
<td>Content assist</td><br />
<td>Ranking of interesting elements</td><br />
<td>Eclipse 3.2: ''Java -&gt; Editor -&gt; Content Assist -&gt; Work in Progress -&gt;'' turn off Mylyn, turn on Java</td><br />
</tr><br />
<tr><br />
<td>Active change sets</td><br />
<td>Grouping of changes by tasks</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Team''</td><br />
</tr><br />
<tr><br />
<td>Editor management</td><br />
<td>Auto opening/closing of editors</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Editor Management''</td><br />
</tr><br />
<tr><br />
<td>Active views</td><br />
<td>Active Search and Hierarchy</td><br />
<td>Only on if view is active</td><br />
</tr><br />
</table><br />
<br />
For additional configuration options see the ''Mylyn'' and ''General -> Appearance'' preference pages.<br />
<br />
== What is the performance profile of the Focused UI? ==<br />
<br />
The goal is for Mylyn to have '''no noticeable effect''' on Eclipse's speed or memory usage.<br />
You do not need to increase the amount of memory Eclipse runs with to use Mylyn. <br />
Any performance issue should be [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Mylyn reported as a bug]. <br />
<br />
The current '''Performance Profile''' is:<br />
<br />
# Mylyn only runs if a task is active, and has no impact on Eclipse if no task is active.<br />
# Task context models have negligible memory overhead. <br />
# When a task is active, additional view refresh is required to update the views based on interest model changes. This should not be noticeable on Windows where refresh is very quick, but could be more noticeable on other platforms.<br />
# The time to activate a task context is dominated by the time it takes Eclipse to open the editors in the context. You can set the preference for how many editors to open in the Mylyn preference page (e.g. setting to 1 will dramatically reduce activation time, but also remove the benefit of having open editors correspond to the task context). You can also turn off editor management entirely in the Mylyn Tasks view pull-down.<br />
# Eclipse startup is slowed down by (4) if a task is active when Eclipse is shut down.<br />
# The low priority background searches that the Active Search view runs can be noticeable on slower machines.<br />
<br />
== What happened to the Active Search and Active Hierarchy views? ==<br />
<br />
These views were not included in the Mylyn 1.0 release because they never made it beyond the experimental phase. <br />
* The ''Active Search'' view has not been sufficiently tuned to adapt to the lifecycle of a task context, and as a result requires manual manipulation of the degree-of-separation scope as you work on long-running tasks. Otherwise it becomes overloaded with elements. In addition, it is not yet clear whether an additional view is the right UI for this facility, and it is hard to find room for an additional view of this size on screen resolutions of 1600x1200 and smaller.<br />
* The ''Active Hierarchy'' view is also hard to allocate space for, especially when using the in-place hierarchy (Ctrl+T) on a landmark can be a quick way to see the relevant part of the task context's hierarchy.<br />
<br />
These features still show promise in displaying task context and saving repetitive searches, so we have not removed them. They have instead moved to the Mylyn Sandbox, and can be used and experimented with by following the [http://wiki.eclipse.org/index.php/Mylyn_Contributor_Reference#Sandbox instructions on the Contributors page]. For feedback on these views please use the corresponding bug reports or newsgroup.<br />
<br />
= Java Development =<br />
<br />
== Content assist troubleshooting ==<br />
<br />
Mylyn uses custom Content Assist processors in order to rank and separate the elements in the current task context. To see proposals ranked according to interest you must have only the ''Type Proposals (Mylyn)'' kinds checkbox enabled in the list below, otherwise you will see duplicates. '''If you do not see any proposals, check this list''' to ensure that either the Mylyn or the plain proposals are enabled. '''To do this automatically''', run ''New -> Mylyn -> Recommended Preferences''. Or you can select them manually as in the preference page below. <br />
<br />
[[Image:mylar-content-assist-prefs.gif]]<br />
<br />
'''Why do I see duplicate proposals?'''<br />
<br />
Ensure that you have only the ''(Mylyn)'' proposals kinds enabled in ''Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced'', otherwise you will see duplicates.<br />
<br />
If you use proposals via Ctrl+Shift+Space instead of the typical Ctrl+Space you will see duplicates. Vote for JDT/Text [https://bugs.eclipse.org/bugs/show_bug.cgi?id=147781 bug 147781] if you use this mechanism. Also see: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=129080 bug 129080]<br />
<br />
'''Why do I get an error message when using content assist?'''<br />
<br />
If after invoking Content Assist you see an error message dialog that states:<br />
The extension took too long to return from the 'computeCompletionProposals()' operation<br />
this is most likely due to something interrupting the proposal operation (e.g. garbage collection). Ignore it if it does not recur, increase Eclipse's memory if it does (e.g via <code>-Xmx384M</code> command line argument). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=141457 bug 141457] for more details.<br />
<br />
== Why do interesting elements not show in the Project Explorer? ==<br />
<br />
The ''Package Presentation -> Hierarchical'' mode is not supported on the ''Project Explorer'' view in Eclipse 3.2 through 3.3M3 and possibly later versions (https://bugs.eclipse.org/bugs/show_bug.cgi?id=161362 bug 161362). Use the view menu to set ''Package Presentation -> Flat'' as a work-around.<br />
<br />
== How do I stop declarations from showing in the Package Explorer? ==<br />
<br />
If you don't like Mylyn's constant showing of Java members in the ''Package Explorer'', select the drop-down menu, then ''Filters...'' and enable the ''Mylyn Java Declarations Filter''. It will then stick in the menu in case you want to toggle between modes. Note that this will hide interest information about members that aren't in your current file (e.g. showing you which methods are landmarks) so this mode is not recommended, but can be useful for <code>1024x768</code> screen resolutions.<br />
<br />
[[Image:mylar-java-filtering-declarations.gif]]<br />
<br />
== Why does nothing show up in the Active Search or Active Hierarchy? ==<br />
<br />
As you work, elements become Landmarks (bold decoration), and these elements populate the ''Active Search'' and ''Active Hierarchy'' views. To force an element to populate the views manually, make it a Landmark by <code>right+clicking</code> or hitting <code>Ctrl+Alt+Shift+UpArrow</code>.<br />
<br />
== Known limitations ==<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=106678 Bug 106678]: The Project Explorer's Hierarchical Java package presentation layout is not supported on Eclipse 3.3Mx, and interesting elements will be hidden if enabled. Work-around is to use the default Flat package presentation.<br />
<br />
= Team Support =<br />
<br />
== Why does task change set not appear when I modify files? ==<br />
<br />
A task change set should appear if you activate a task and modify a file connected to a compatible source repository (e.g. CVS, SVN). If it does not try the following:<br />
<br />
* Ensure you have installed the [http://www.eclipse.org/mylyn/downloads/ ''Mylyn Bridge: Eclipse SDK'' feature]. Note that this feature is not currently distributed with the Java-only Eclipse download ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191793 bug 191793] ).<br />
<br />
* Verify that the [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuring_the_Synchronize_view_for_change_sets configured ''Synchronize View'' is configured for change sets].<br />
<br />
If the above are working but the change set appears to be missing relevant files:<br />
<br />
* You may be seeing the ''Synchronize'' view's refresh problem ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142395 bug 142395]). Toggle from ''Incoming/Ougtoing'' to ''Incoming'' mode and back again to refresh the view.<br />
<br />
* If the files or change set are still missing deactivate and reactivate the task to force a full refresh.<br />
<br />
== Why do files disappear from the change set when I close them? ==<br />
<br />
If you have the ''Preferences -> Mylyn -> Context -> Manage open editors to match task context'' option enabled, Mylyn will perform editor management so that you don't have to. Closing a file makes it less interesting, and causes it to disappear from the active task context, and hence from the change set. This option prevents you from having to manage the set of open files, will automatically close editors for files that become uninteresting, and will ensure that the open editors match the task context.<br />
<br />
== Why is interest lost when I retrieve someone else's context? ==<br />
<br />
To identify elements within a project, Mylyn relies on the name of the project being consistent across workspaces. If the project name in the workspace that the context was created with is different than its name in your workspace, the task context will not show elements within that project ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164058 bug 164058]). The work-around is to use the same project names across your team's workspaces.<br />
<br />
The other case where context can be lost is if the elements change names outside of the workspace ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164243 bug 164243]).<br />
<br />
= Misc =<br />
<br />
<br />
<br />
== How does Mylyn relate to IBM's Jazz? ==<br />
<br />
At the EclipseCon and JavaONE 2006 conferences IBM demonstrated previews of Jazz, a collaborative team server and Eclipse-based client. Articles have remarked on the similarities between Mylyn and Jazz because both integrate tasks into Eclipse (Jazz's "work items" and Mylyn's "tasks"), and both provide change sets grouped by task. But there are both significant differences and complementary aspects to the two approaches. A key goal of Mylyn is to provide an open source framework to support integration of task management with ''existing issue trackers and source repositories''. According to the presentations, components that come with Jazz include include a ''next-generation issue tracker and source repository'' and related lifecycle management tools such as project health. In addition, a driving and unique goal of Mylyn is to focus the UI around a usage-based and degree-of-interested weighted task context, which is complementary to the Jazz platform. Just as it integrates with Mylyn's Task List, Mylyn's Task Focused UI and task context model components are possible to integrate with other kinds of task management systems, such as the one provided by Jazz.<br />
<br />
Update: at EclipseCon 2007 the IBM Jazz team showed a Mylyn connector for Jazz.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/FAQ&diff=49784Mylyn/FAQ2007-09-10T03:56:46Z<p>Steffen.pingel.eclipse.org: /* Trac Connector */</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
[[Mylyn User Guide]], <br />
[http://eclipse.org/mylyn Mylyn Home],<br />
[http://wiki.eclipse.org/index.php?title=Special:Userlogin&returnto=Special:Userlogout Log in to edit]<br />
<br />
For instructions on [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Download_Mylar downloading] [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installation installing] and [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuration configuring] <br />
Mylyn, see the [[Mylyn User Guide]]. For instructions on developing and contributing to Mylyn, see the [[Mylyn Contributor Reference]].<br />
<br />
= Installation =<br />
<br />
== What versions of Eclipse are supported? ==<br />
<br />
See the [http://eclipse.org/mylyn/dl.php download page].<br />
<br />
Mylyn also relies on a web browser that works with the Standard Widget Toolkit; Windows and MacOS users are fine, but Linux users might have to download another browser. See [http://www.eclipse.org/swt/faq.php#browserlinux the SWT Browser guide] for which browsers will work. See [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux installing browser on Linux] for installation instructions.<br />
<br />
== What version of Java is required? ==<br />
<br />
Mylyn needs the '''Java 5''' virtual machine.<br />
<br />
To check the version of the Java virtual machine that Eclipse was launched with to to ''Help -> About Eclipse SDK -> Configuration Details'' and verify that the java.vm.version is 1.5. <br />
<br />
Mac users should refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
* If you do not have Java 5, you can download it from [http://72.5.124.55/javase/downloads/index.jsp Sun's web site]. <br />
* If you have more than one VM, you need to specify that Eclipse should use the JDK1.5 VM. <br />
<br />
In Unix, set the environment variable <code>JAVA_HOME</code> to the root of the JDK1.5 installation and/or set the <code>PATH</code> variable to put the JDK1.5 executable directory before any other VM executable directories. For example, under <code>bash</code> in Unix:<br />
export JAVA_HOME="''(location of JDK1.5 root)''"<br />
export PATH=$JAVA_HOME/bin:$PATH<br />
<br />
<b>We do [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140955 not recommend] using JDK 1.6 on Eclipse 3.1.</b> (It works fine with Eclipse 3.2 or 3.3.) To use JDK 1.6 on Eclipse 3.1, you must add the following line to your <code>config.ini</code>file:<br />
<code><br />
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,<br />
J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6<br />
</code><br />
<br />
== What version of Mylyn is distributed with the Eclipse downloads? ==<br />
<br />
The [http://www.eclipse.org/downloads/ default Eclipse downloads] contain the following Mylyn redistributions. Since the redistributed versions can be missing important bug fixes or feature additions, we recommend using the [http://www.eclipse.org/mylyn/downloads latest version of Mylyn].<br />
<br />
* Eclipse IDE for Java Developers: all of Mylyn except Team integration (e.g. automatic change sets) integration. Install the Eclipse CVS integration and then install the latest Mylyn build to get this component.<br />
<br />
* Eclipse IDE for Java EE Developers: all of Mylyn redistribution, install manually<br />
<br />
* Eclipse IDE for C/C++ Developers: no Mylyn redistribution, install manually<br />
<br />
* Eclipse for RCP/Plug-in Developers: all of Mylyn redistributed<br />
<br />
* Eclipse Classic: no Mylyn redistribution, install manually<br />
<br />
== My tasks or queries disappeared, what do I do? ==<br />
<br />
This happens if Mylyn failed to install. First ensure that you have a correct install by following the instructions in the next section. After that, if you still do not see your tasks use the ''Task List'' view menu -> ''Restore Tasks From History...'' command (also available via ''File -> Import -> Task List''.<br />
<br />
== Installation Troubleshooting ==<br />
<br />
''' Java Persistence API Tools error when updating the JEE Eclipse Package '''<br />
<br />
If you are trying to install additional features and get this error you have hit [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194959 bug 194959] which should be resolved soon. The work-around is to check off the ''Europa Discovery Site'' and install the first two components of the ''Data Tools Platform''.<br />
<br />
''' Update failures '''<br />
<br />
On Eclipse versions earlier than 3.3 (final) use '''only the "Search for new features.."''' option when updating Mylyn. If you use "Search for updates..." the Update Manager will allow a partial install that can cause Mylyn to fail to start, and you will need to run update again. See the ''feature configuration problem'' section below for details. If you encounter this problemm consider voting for Platform [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132450 bug 132450].<br />
<br />
''' Startup exceptions '''<br />
<br />
If you see startup errors or warnings such as <code>BundleException</code> or timeout messages restart Eclipse with the <code>-clean</code> flag either on the command line, in your shortcut link, or by temporarily it into the <code>eclipse/eclipse.ini</code> file. If that does not resolve the problem please [http://www.eclipse.org/mylar/bugs.php file a bug].<br />
<br />
''' Incompatible VM (e.g. JDK 1.4) '''<br />
<br />
If you are using the wrong VM, you'll see errors like the following in your log file. <br />
<code><br />
Root exception: java.lang.UnsupportedClassVersionError:<br />
org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)<br />
</code><br />
<br />
See [[#Download_and_configure_Java_5_or_6|Configure Java]] to fix this problem.<br />
<br />
''' Incompatible version of Eclipse '''<br />
<br />
Separate versions and update sites exist [http://eclipse.org/mylyn/dl.php for Eclipse 3.1 and 3.2]), in which case you may see errors like the following in your <code><workspace>/.metadata/.log </code>file or in a Mylyn view:<br />
<code><br />
java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()<br />
The activator org.eclipse.mylar.java.MylarJavaPlugin for bundle org.eclipse.mylar.java is invalid<br />
</code><br />
<br />
''' Mylyn feature configuration problem '''<br />
<br />
If the above do not address the issue, the easiest thing to do is uninstall any old versions and update to the latest Mylyn. Your tasks won't be lost, because by default they are stored in the <code><workspace>/.metadata/.mylyn</code> folder which will be read next time Mylyn starts correctly. <br />
* First, uninstall the old version of Mylyn using ''Help -> Software Updates -> Manage Configuration''. <br />
* You need to Disable all Mylyn features by right-clicking them.<br />
* Allow Eclipse to restart after the last is disabled.<br />
* After restart, ensure that the 3rd toolbar button is pressed (figure below) so that you see the disabled features to uninstall.<br />
* Uninstall all the disabled features using the popup menu. <br />
<br />
If you don't uninstall, the the Update Manager will think that you have the latest and tell you that there are no updates. <br />
<br />
<b>Note: manually removing the plug-ins and features can lead to configuration errors.</b> <br />
<br />
After uninstalling, update Eclipse by adding the correct update site specified at on the [http://eclipse.org/mylar/dl.php download page], and after that automatically or manually updating will install the correct version.<br />
<br />
[[Image:mylar-eclipse-manage-configuration.gif]]<br />
<br />
'''What do I need to do in installation to be able to use Mylyn task management features with bug/task/issue trackers?'''<br />
<br />
When you install, make sure that you select a connector for your bug/task/issue tracking software. For example, to use Bugzilla, you have to install the Bugzilla connector component.<br />
<br />
'''I've installed Mylyn ; why can't I see anything different?'''<br />
<br />
The two most likely possibilities are:<br />
# You don't have any Mylyn views open. Select ''Window -> Show View -> Other'', then select ''Mylyn'' and you should see the available Mylyn Views. <br />
# If you still don't see anything, then perhaps you aren't using the JDK1.5 VM (or later). See [[Mylyn_Installation_Guide#Download_and_configure_Java|configuring Java]].<br />
<br />
<br />
'''What does the error "Network connection problems encountered during search" mean?'''<br />
<br />
If you get that message while trying to download Mylyn, it means that Eclipse couldn't find the location you entered. This might be because you copied something incorrectly (watch for extra characters -- even extra spaces can cause errors), or because the site went down. You may be able to see if the site is up or down by copying the URL into your Web browser.<br />
<br />
'''What does the "Update manager failure" message mean? '''<br />
<br />
It means that Eclipse could not access the update site, or that it got confused about the configuration state of your Eclipse. First try updating again to see if the update site is accessible. <br />
<br />
If you are trying to update the JIRA connector you can also try de-selecting that feature in case the <code>Tigris.org</code> update site is not accessible. Using ''Search for new features to install..'' when installing can help to avoid this problem. If that does not work see the feature configuration troubleshooting below. <br />
<br />
'''What does "Could not create Browser page: No more handles (<code>java.lang.UnsatisfiedLinkError: ...</code>)" mean?'''<br />
<br />
It probably means that you are running Linux and don't have Eclipse and a Web browser configured to work together. See [[http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux| installing a browser on Linux]].<br />
<br />
'''When downloading, why do I get a warning that the feature was unsigned?'''<br />
<br />
Signing plugins requires extra administrative details with <code>eclipse.org</code> which most plug-ins seek to avoid. <br />
<br />
'''N.B.''': Security issues with features should not be underestimated. Eclipse allows users to download new functionality from remote servers. A rogue plug-in can act as a perfect Trojan horse. It can look innocent enough and provide useful function while spawning threads in the background with full access to the local file system and the Internet (if connected). Beware of installing features from update sites you do not trust.<br />
<br />
'''What does "<code>Root exception: java.lang.UnsupportedClassVersionError: org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)</code>" mean?'''<br />
<br />
It probably means that the virtual machine is JDK1.4 or lower. See [[Mylyn_Installation_Guide#Download_and_configure_Java| download and configure Java]].<br />
<br />
'''Why am I getting messages in my <code><workspace>/.metadata/.log</code> or my Mylyn view that say things like <code>"java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()"</code> and "The activator <code>org.eclipse.mylar.java.MylarJavaPlugin</code> for bundle <code>org.eclipse.mylar.java</code> is invalid"?'''<br />
<br />
This probably means that your Mylyn download version didn't match your Eclipse download version. Note that [http://eclipse.org/mylar/dl.php the download site] has different downloads for Eclipse 3.1 and Eclipse 3.2.<br />
<br />
To fix this problem, see the [[Mylyn_Uninstallation_Guide| uninstallation guide]], then re-install from [http://eclipse.org/mylar/dl.php the correct download site].<br />
<br />
'''What does "Could not create Bugzilla editor input" and "<code>java.io.IOException</code>: SAX2 driver class <code>org.apache.xerces.parsers.SAXParser</code> not found" mean?'''<br />
<br />
It probably means that you are on MacOS, and for some reason are missing Xerces from the Mac JDK1.5. You will probably need to add it to your default classpath. Please refer to and comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=144287 bug 144287] if you see this problem.<br />
<br />
To ensure that you are using the 1.5 VM refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
'''I've just updated to Mylyn 2.0 and I don't see any tasks in my Task List'''<br />
<br />
As part of the update to Mylyn 2.0 the old data folder has been migrated to <workspace folder>/.metadata/.mylyn from the old location <workspace folder>/.mylar. IF for some reason migration failed (.mylar folder still exists), simply shut down Eclipse and manually move your old <workspace folder>/.mylar folder to <workspace folder>/.metadata/.mylyn (note the name change to .mylyn)<br />
<br />
== Configuration Troubleshooting == <br />
<br />
'''How can I change the number of editors left open before Mylyn starts closing editors?'''<br />
<br />
Turn off or increase the number of editors to leave open using ''Preferences -> General -> Editors -> Number of opened editors before closing''. Since Mylyn will manage the open editors with task activation, this number can be set higher or you can disable automatic closing entirely.<br />
<br />
'''Do I need the Outline View when running Mylyn?'''<br />
<br />
No, not really. The Package Explorer and folded signatures should provide enough context for you. If, at some point, you really need to see an Outline View, you can always enter (Ctrl+O) to show the in-place Outline View.<br />
<br />
'''What does the message "content assist proposals no longer appear" mean?'''<br />
<br />
This usually happens when uninstalling when using Eclipse 3.2. Make sure that the "Java Completions" and "Java Types" proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
'''Why do I get errors like "HTTP Response Code 407" or "Proxy Authentication Error" when accessing repositories through a proxy server?'''<br />
<br />
It is likely that you need to configure these proxy server settings. Select ''Window -> Preferences -> Install/Update'', and update the section in the "Proxy settings" section of the form.<br />
<br />
'''I can't use <code>Ctrl+Alt+Shift+Arrow Up</code> for'' Mark as Landmark''. What do I do?<br />
<br />
This is usually a Linux/GNOME problem, where the Gnome keyboard shortcuts are interfering with the Eclipse shortcuts. Go to the Keyboard shortcuts (which might be something like ''Desktop -> Control Centre -> Keyboard Shortcuts'' or ''System -> Preferences -> Keyboard Shortcuts'') and disable both of these shortcuts:<br />
* Move one workspace up<br />
* Move one workspace down<br />
<br />
See also: [[Mylyn_User_Guide#Keyboard_mappings_on_Linux| keyboard mappings on Linux]].<br />
<br />
'''How do I turn on spell checking?'''<br />
<br />
See [[Mylyn_User_Guide#Spell_Checking| spell checking]].<br />
<br />
== Uninstall troubleshooting ==<br />
<br />
When '''uninstalling in Eclipse''' Mylyn via the ''Help -> Software Updates -> Manage Configuration'' dialog you will need to uninstall dependencies first (e.g. Bugzilla Connector, Subclipse integration) and then uninstall the core Mylyn features.<br />
<br />
When '''uninstalling manually''' by deleting all of the Mylyn plug-ins and features from the <code>eclipse/plugins</code> and <code>eclipse/features</code> directory make sure to delete all of the plug-ins and then restart Eclipse with the -clean option (e.g. by inserting it into a shortcut or the <code>eclipse.ini</code> file.<br />
<br />
On '''Eclipse 3.1:''' you may need to reset the Java editor to be default for <code>.java</code> again via: ''Preferences -> General -> Editors -> File Associations''<br />
<br />
On '''Eclipse 3.2:''' if after uninstalling '''content assist proposals no longer appear''' you need to ensure that the ''Java Completions'' and ''Java Types'' proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
== I am seeing <code>java.lang.OutOfMemoryError: PermGen space </code>errors, what's wrong? ==<br />
<br />
If your Eclipse crashes, or you see the above error after installing Mylyn or other plug-ins, you have most likely hit the infamous MaxPermSize bug. This is not a Mylyn specific problem, but a general Eclipse problem that is often triggered on Eclipse 3.2 and later, if you have many plug-ins installed and are using a Sun JVM. <br />
<br />
To fix it simply add the following to your launch arguments. This is usually to your shortcut, or to the <tt>eclipse/configuration/config.ini</tt> file:<br />
<br />
-XX:MaxPermSize=128M<br />
<br />
If you are using a large number of plug-ins (e.g. WTP) you may need to increase the number to more than 128M. <br />
<br />
Details of the problem are on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250 Platform bug 92250].<br />
<br />
= Task List =<br />
<br />
== Why won't the Archive category disappear? ==<br />
<br />
The ''Archive'' category will automatically appear if a task needs to be shown, but is not in any query or category. <br />
In order to ensure that you do not miss reminders or notifications the following tasks will always be shown in the Task List, even if they have been removed from a category or a query:<br />
* Tasks scheduled for this week or overdue. Remove these by using the ''Schedule'' pop-up menu option to defer them to a future week or to clear the schedule.<br />
* Repository tasks that have incoming changes, such as comments. Remove these by reading them or marking them as "read" via the ''Mark -> Read'' pop-up menu.<br />
<br />
== The Archive category contains many irrelevant tasks, how do I clean it up? ==<br />
<br />
If you created very broad queries you could end up with thousands of tasks in the Archive category. Other than clearing the <tt>workspace/.metadata/.mylyn/tasklist.xml.zip</tt> and <code>workspace/.metadata/.mylyn/offline</code> folder (note that this will entirely reset your Task List) the easiest option is to:<br />
* Clean up your queries to include only tasks of interest (note that including completed/resolved tasks is recommended).<br />
* Turn off ''Focus on Workweek'' in the ''Task List''.<br />
* Turn off the ''Filter Archive Category'' option in the ''Task List'' view menu.<br />
* Delete all of the unneeded tasks from within the Archive category. Note that if the tasks are not matched by queries they will be deleted permanently and any local notes or scheduling information that you have added to them will be lost.<br />
<br />
== How does Mylyn count the active time for a task? ==<br />
<br />
Whenever you work on a task, Mylyn accumulates the time you spend actively working on a task. This time can be viewed in the ''Personal Planning'' section of the ''Task Editor''. When you are not interacting with Eclipse, the timing automatically times out after 3 minutes by default. This means that activity outside of Eclipse will not be captured when you work on the task and that the timings in Mylyn are a lower bound of the total time spent on the task (capturing timings for work done outside of Eclipse involves OS specific extensions).<br />
<br />
== How do I prevent long-running tasks from adding to the progress bar? ==<br />
<br />
If you have many long-running or recurring tasks scheduled for this week, they can affect the ''Task List'' weekly progress bar. This can be misleading as they may never be completed. The current work-around to prevent long-running tasks from being included in the weekly progress bar is to schedule their estimated time to be 0 (zero). Alternatively, you can schedule only the amount of time you plan on spending on that task this week.<br />
<br />
== Does the Task List replace the Eclipse Tasks view? ==<br />
<br />
The SDK's ''Tasks'' view is used for showing markers such as 'todo' tags which indicate a local problem with a resource, similar to a compiler warning. As such, these 'tasks' are at a much lower level of granularity than Mylyn's tasks, and one task could involve cleaning up multiple todos. In order to make working with only the markers in a particular task context, e.g. for clean-up before committing, the ''Apply Mylyn'' filter is available for both the ''Problems'' and the ''Tasks'' views.<br />
<br />
== What if I use multiple workspaces? ==<br />
<br />
Mylyn's support for multiple workspaces is currently limited (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130658 bug 130658] for a discussion) because the Task List is considered to be specific to the person, and not to the workspace. We recommend configuring your Eclipse workspace to use working sets instead of relying on multiple workspaces. <br />
* John O'Shea's blog: [http://www.xlml.com/aehso/2007/02/02/eclipse-workspaces-containing-projects-with-overlapping-locations-and-mylar/ Eclipse workspaces containing projects with overlapping locations, and Mylar]<br />
<br />
If using a single workspace is not possible you can do the following:<br />
* In ''Preferences -> Mylyn -> Task List'' set the ''Data Directory'' to be a shared location, and do this for both workspaces.<br />
* Be sure to avoid launching both Eclipse workspaces at the same time, as changes in one workspaces could overwrite the Task List in the other workspace.<br />
* If you upgrade Eclipse or move your workspace and don't see your tasks, check the ''Data Directory'' setting.<br />
<br />
== How do I export my task and repository data? ==<br />
<br />
Export via File > Export > Mylyn > Task Data<br />
<br />
== Why does Mylyn use the term "task"? ==<br />
<br />
There are many work items that make up the developer's workday. Many issue trackers and project management tools refer to these as: bugs, defects, actions, tickets, stories, enhancements, and the list goes on. We refer to all such work items as "tasks" because the word tasks is short and commonly used in time management tools. Task Repository connectors can customize the presentation of tasks, for example, indicating which is a defect and which is an action item.<br />
<br />
= Task Editor =<br />
<br />
== Why am I seeing strange boxes where I expect to see proper characters? ==<br />
<br />
If for example you aren't seeing the proper single quote chacters in the summary of [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=197644 bug#197644]], check that the encoding is set correctly for the repository in the asociated Task Repositories view (Properties > Additional Settings > Character Encoding). For bugs.eclipse.org/bugs set your charcter encoding to ''ISO-8859-1''.<br />
<br />
= Task Repositories =<br />
<br />
== What if Mylyn doesn't support my task/bug/issue/ticket repository? ==<br />
<br />
To see support for your repository faster, do a search of the open repository connector requests and [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Bconnector%5D&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=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= vote for the corresponding bug] if your tracker is there, or [http://www.eclipse.org/mylar/bugs.php create a new bug]. <br />
<br />
[[Mylyn_User_Guide#Generic_Web_Repository_Connector|Generic Repository Connector]], allows creating Queries to the web-based issue tracking repositories and get list of issues from the web UI into the Task List.<br />
<br />
It is also possible to link a ''local task'' with the web page in web-based repository via the Mylyn Web integration.<br />
<br />
'''To create a task from any web-based repository:'''<br />
<br />
* Drag the URL from the address bar of the browser, or from a hyperlink in a bug listing to the ''Mylyn Tasks'' view. This will create a task for the bug, link it to the page, and populate the description with the title of the corresponding page. '''In Mozilla:''' simply drag the URL. '''In Internet Explorer:''' you must have <code>Ctrl</code> pressed in order for Eclipse to recognize the drop.<br />
* '''Alternatively,''' you can copy the URL, press the ''New Task'' button on the ''Mylyn Tasks'' view. This has the same effect as above but you can edit the description after retrieving it.<br />
* Opening the task will now open the corresponding issue. You can also <code>right+click</code> the task and select ''Open in External Browser''.<br />
<br />
[[Image:mylar-tasklist-weblink-editor.gif]]<br />
<br />
== Why were my repository credentials reset? ==<br />
<br />
If you upgrade Eclipse or your Java VM, you will need to reset your credentials in the ''Task Repositories'' view because these are stored in the secure Eclipse workbench keyring. Also see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=149607 bug 149607]. If you are migrating '''from Eclipse 3.2 to 3.3''' note that you will need to use a different update site, which is listed here: http://eclipse.org/mylyn/dl.php<br />
<br />
== Why are my updated repository attributes not showing up? ==<br />
<br />
Your server's repository attributes can change frequently, for example, there can be a new "milestone" or "version" added to the Bugzilla repository with each release. When the ''Preferences -> Mylyn -> Task List -> Synchronization'' setting is enabled, every 10th synchronization will update the attributes from the repository. If you do not have this setting enabled, your can force the update via the ''Update Attributes'' action on the task repositories' context menu in the ''Task Repositories'' view. Note that you will need to reopen a task editor to see the updated attributes. If you instead update via the button on the ''Attributes'' section of the ''Task Editor'' the attribute settings will be reloaded without needing to reopen.<br />
<br />
== Authentication Troubleshooting ==<br />
<br />
You must ensure repository credentials are filled out correctly. Refer to the diagram below:<br />
<br />
[[image: AuthenticationTroubleshooting2.png|right]]<br />
<br />
# Enter the repository URL (i.e. https://bugs.eclipse.org/bugs) and an optional label<br />
# Credentials<br />
#* Usually email address and password <br />
#* Some sites, such as <code>dev.eclipse.org</code>, use anonymous logon with password left blank.<br />
#Http Authentication (optional)<br />
#* Some sites are protected by either BASIC or DIGEST http authentication. If this is the case, enter appropriate credentials here.<br />
#* One way to test if the site requires http authentication is to point your browser at the repository. If you are presented with an authentication dialog popup, the site is likely protected by http authentication.<br />
#Proxy Server Configuration (optional)<br />
#* By default Mylyn uses the Platform's Install/Update proxy settings. Uncheck this box if you wish to use an alternative proxy.<br />
#* If the proxy requires authentication, this is where you enable and enter your proxy credentials.<br />
#* If you are experiencing connection problems, ensure your Install/Update proxy settings are valid or the repository specific settings are correct<br />
#* Mylyn has been tested with HTTP proxy servers. Currently SOCKS is not supported.<br />
#Validate Settings <br />
#*Press the ''validate'' button to test the settings<br />
#*If you are seeing errors like "HTTP Response Code 407" or "Proxy Authentication Error" it is likely that you need to configure proxy settas as described above.<br />
#*If your sever uses a certificate and fails to connect, e.g. you see exceptions <tt>sun.security.validator.ValidatorException: PKIX path building failed</tt> then you need to point Eclipse at your certificate, see the [http://ahtik.com/blog/2006/05/11/fixing-eclipse-mylar-jira-integration/ instructions on this blog].<br />
<br clear="all" /><br />
<br />
* If your repository uses MS NTLM authentication and only standard http authentication is being passed to the repository this can result when the local hostname cannot be resolved. Ensure your machine's hostname is set correctly and resolves to a valid address.<br />
<br />
== Why are task hyperlinks not working? ==<br />
<br />
For task hyperlinks in textual editors (e.g. Java editor) and other text viewers (e.g. History view comments) you must associate the project that contains the resource to the task repository. <br />
<br />
:''Project association can also come from 3rd party metadata trough the contrubuted [[Mylar_Integrator_Reference#Mapping_from_projects_to_Task_Repositories|extension point]]. [http://subclipse.tigris.org/ Subclipse] and [http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Mylyn Maven integration for Eclipse] plugins contributing it. See few more details [http://jroller.com/page/eu?entry=linking_projects_from_the_eclipse here].''<br />
<br />
Note that to view a hyperlink you must hold down the <code>Ctrl</code> key when hovering over the reference to the task. References to tasks are connector specific and the common reference is found on the top left of the task editor and other conventions tend to follow those used in the web UI (e.g. "bug 123" for Bugzilla, "ABC-123" for JIRA).<br />
<br />
[[Image:mylyn-project-repository-association.gif]]<br />
<br />
= Bugzilla Connector =<br />
<br />
== What versions are supported? ==<br />
<br />
We recommend using the latest [http://www.bugzilla.org/download/ release] of Bugzilla.<br />
<br />
* '''Bugzilla 2.18.6 is the lowest version of Bugzilla supported'''. If you are getting errors that indicate failure to update attributes this may be an indication that the Bugzilla server is not supported (< 2.18.6).<br />
<br />
*If you are using '''Bugzilla 2.18''' and are getting '''mid-air collisions''' this is likely due to incorrectly formatted timestamp field in the underlying bugs database table ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149513 bug 149513]). This can be resolved by upgrading to Bugzilla 2.20 or later.<br />
<br />
== Why are queries failing? ==<br />
<br />
*If '''queries are not working''' correctly ensure that you have the right Bugzilla server version selected for the corresponding repository: ''Task Repositories (View) ->'' right+click the repository ''-> Properties''. For supported versions see the [http://www.eclipse.org/mylar/dl.php download page]. If the repository is still not functioning it may be due to authentication or connectivity problems. If that does not resolve the problem please post a message to the newsgroup or [http://www.eclipse.org/mylar/bugs.php submit a bug].<br />
<br />
== Why do tasks fail to open? ==<br />
<br />
*If upon opening a bug, the Bugzilla tab only displays a warning "'''Could not download task data, possibly due to timeout or connectivity problem. Please check connection and try again.'''", ensure that your repository is returning XML data by pointing your browser to <code><your-repository-url>/show_bug.cgi?id=1&ctype=xml</code> to show the contents of bug 1 in XML form. The Bugzilla client requires that bugs be accessible in XML form. If the repository doesn't support xml then it is likely that the repository is too old (Mylyn currently supports Bugzilla 2.18 and later).<br />
<br />
* If '''reports fail to load''' or '''reports fail to synchronize''' (task description remains ''italic''), check the error log for a "'''File not found'''" error pointing to <code>bugzilla.dtd</code> or a "'''Failed to retrieve products from server'''" error message - these result when the <code>urlbase</code> parameter is not set on the bugzilla server, or your bugzilla installation is missing the <code>bugzilla.dtd</code> file. See: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=161759 bug#161759]<br />
<br />
* If '''attributes are missing options''' in the bug editor (ie. missing a recently added milestone, [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155431 bug# 155431]):<br />
** Update attributes by choosing ''Update Attributes'' from the context menu in the ''Task Repositories'' view<br />
** Synchronize the task in the Task List<br />
** Reopen the task - new options should be available.<br />
<br />
== Why do tasks fail to submit? ==<br />
<br />
* '''Error upon submit: unable to make any match for name/email entered.''' If your bugzilla is configured for user names rather than full email address the QA Contact field will cause the submit to fail ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=166555 bug# 166555]). To resolve, select 'Local users enabled' option on the Repository Configuration page. <br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your account's username and password and are not using the HTTP authentication fields instead.<br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your bugzilla instance's cookie domain under the required settings. The cookie domain must lead with a dot.<br />
<br />
* If '''attachments are failing to submit''' and you see that after processing the attachment, the bugzilla bug shows a size of "bytes" (no numbers), your database may be dropping the packet sending the file. '''On MySQL''', check the [http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html max_allowed_packet directive]. You may see errors like: <code>DBD::mysql::st execute</code> failed: Got a packet bigger than 'max_allowed_packet' bytes [for Statement "INSERT INTO attach_data (id, thedata) VALUES (38, ?)"] at <code>/path/to/bugzilla/attachment.cgi</code> line 993. Also, '''check the maximum attachment size''' in ''Bugzilla Parameters -> Attachments''.<br />
<br />
* If a submit fails with an '''Invalid Username or Password''' error even though repository settings do validate, make sure that cookies could be set. See also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175502 bug 175502]<br />
<br />
== What time zone is used in the task editor? ==<br />
<br />
*The '''times''' that appear in the Bugzilla bug editor (ie. created, modified) '''are local to the server hosting the Bugzilla repository''', not your local machine's time zone. <br />
<br />
== Known limitations ==<br />
<br />
* The <code>usermatchmode</code> is not currently supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168204 bug 168204]) and as such full email addresses need to be used.<br />
<br />
* The <code>usevisibilitygroups</code> parameter is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=180876 bug#180876]). Group assignment will currently be lost if updated using the Bugzilla rich task editor.<br />
<br />
* Version 1.0 of Mylyn presents an error message upon new comment submission to RedHat's public Bugzilla repository. The comment is in fact posted. This issue is resolved in Mylyn 2.0M2 and higher. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=183251 bug#183251])<br />
<br />
= JIRA Connector =<br />
<br />
If you see errors like the following, work around this by opening repository ''Properties Page'' and clicking OK (bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169102 169102]).<br />
<br />
org.tigris.jira.core.service.exceptions.AuthenticationException<br />
at org.tigris.jira.internal.core.service.soap.SoapJiraService.getProjectsNoSchemes(SoapJiraService.java:204)<br />
<br />
== What are the server requirements? ==<br />
<br />
The '''JIRA SOAP/RPC services have to be running on the JIRA server''':<br />
<br />
* Jira 3.3.3 or higher (3.7 or higher for attachment retrieval)<br />
* Jira RPC plugin 1.4.3 or higher<br />
<br />
Latest information also available on the [http://www.eclipse.org/mylar/dl.php download page].<br />
<br />
Related Resources:<br />
<br />
* [http://confluence.atlassian.com/display/JIRA/JIRA+Development+Hub Jira Development Wiki]<br />
* [http://confluence.atlassian.com/pages/viewpage.action?pageId=1035 Jira RPC Plugin Overview]<br />
<br />
== Why can't I connect? ==<br />
<br />
* If you get a <code>org.tigris.jira.core.service.exceptions.ServiceUnavailableException</code> you need to turn on the JIRA SOAP/RPC services on the server.<br />
* Similarly, if you get a "Processing instructions are not allowed within SOAP messages" message, ensure that SOAP/RPC services are on.<br />
* If you get a '''503''' error code verify that the SOAP/RPC interface is enabled.<br />
* If you get a '''403''' error code verify that the SOAP/RPC interface is enabled, and also check your authentication mechanism. If the server is using NTLM authentication, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156397 bug 156937] for diagnosis steps.<br />
* If you see an '''"unrecognized priority" message''' in the ''Error Log'', the problem is that the JIRA Connector does not support customized priorities so the priority value specified in that message will not correspond to the priority icons visible in the Task List.<br />
* If you are being '''prompted for your log-in credentials''' by the Browser tab of the task editor or the new task editor, this is because without rich editor support the connector is using the web-based UI instead of logging in on your behalf as is done with a rich task editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142869 bug 142869]).<br />
* If you get a <CODE>AuthenticationException</code> and a query won't synchronize, use Task Repositories (view) -> Properties (on the repository) -> Validate Settings. This will clear the connection if it died.<br />
<br />
<!-- HEAVILY OUTDATED. PLUGIN NOW USES COMMON PROXY INFRASTRUCTURE<br />
== Why can't I synchronize when using a proxy server? ==<br />
<br />
* Proxy configuration is '''based on the normal Java HTTP system properties''', which can be configured either by launching Eclipse with <code>-vmargs</code> and using the following settings, or by putting these settings into the or by putting the following into the <code>eclipse/eclipse.ini</code> file (after -vmags):<br />
-Dhttp.proxyHost=<host> <br />
-Dhttp.proxyPort=<port><br />
* Make sure that when using these settings you do not enable the proxy settings on the ''Install/Update'' preference page, since they may override these settings.<br />
* If you are using '''SSL''', you will also need to set the <code>https.proxyHost</code> and <code>https.proxyPort</code>. <br />
* Authentication is configured with the <code>http.proxyUser</code> and <code>http.proxyPassword</code> system properties (also for SSL)<br />
* You can also use <code>http.nonProxyHosts</code> system property to enumerate hosts that should not be proxied. Note that matching is implemented on the exact host name used for JIRA server and patterns are not supported. --><br />
<br />
== Known limitations ==<br />
* Attachment retrieval (including retrieval of the task context and attachment list in the task editor) require JIRA 3.7 or above ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=169757 bug 169757])<br />
<!-- * NTLM authentication is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172395 bug 172395]) --><br />
* Customized priorities are not currently supported, so all issues with a customized priority will have the default priority level ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=165518 bug 165518]).<br />
* blank but editable custom fields doesn't appear in the RSS data, and as result we can't show them for editing<br />
* because of JIRA api limitations, we can support custom fields in the task editor, but not in the new custom task editor<br />
<!-- * On JIRA 3.6.x private filters saved on the server can fail to retrieve results ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=174328 bug 174328]). The work-around is to create a custom query in Mylyn using the form-based query designer or to share the filter in JIRA. --><br />
<br />
== How can I enable compression for SOAP messages? ==<br />
<br />
If your repository has lots of projects and components you can speed up the download of the repository configuration by enabling compression. <br />
<br />
* Add a filter-mapping to your JIRA server configuration: [http://jira.atlassian.com/browse/JRA-10353].<br />
* Enable compression in your global JIRA configuration.<br />
* Check the compression setting for your task repository in Mylyn versions 2.0M2 and later.<br />
<br />
== Reporting issues ==<br />
<br />
Since JIRA can be heavily customized there is a chance that some particular customizations may not work, so if you can't connect to your proprietary repository it is a good idea to try the following public repositories to make sure you have working configuration:<br />
<br />
* http://jira.codehaus.org<br />
* http://issues.apache.org/jira/<br />
* http://opensource.atlassian.com/projects/spring <br />
<br />
If you can't get query results, you could try to call "Open with Browser" on query node in the Task List view and then save link "Current view: XML" and attach it to the bug report.<br />
<br />
Even if query don't work you could try "Open Repository Task" from your JIRA repository node on the Task Repositories view and check if you can open JIRA task editor for that issue. Same for the Task search (Ctrl-H, Task Search)<br />
<br />
To investigate various error you may need to enable debug tracing. To do that you need to create the <code>.options</code> file with the following content:<br />
<br />
<pre><br />
org.eclipse.mylyn.jira.ui/connector=true<br />
org.eclipse.mylyn.jira.ui/dataHandler=true<br />
</pre><br />
<br />
and then add the following options to the Eclipse command line (or eclipse.ini file):<br />
<br />
<pre><br />
-debug <path to the .options file>/.options<br />
</pre><br />
<br />
The additional logging will go into the regular Eclipse log and the Error Log view<br />
<br />
= Trac Connector =<br />
<br />
== What are the server requirements? ==<br />
<br />
The Trac connector offers two access methods:<br />
<br />
'''XML-RPC''' (recommended)<br />
<br />
Requirements:<br />
* Trac 0.10<br />
* [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] rev. 1950<br />
<br />
This access method offers editing of tasks in a rich editor, attachment support and offline editing. It requires the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] for Trac to be enabled for the accessed repository. The XmlRpcPlugin provides a remote interface to the Trac repository and is distributed separately from Trac (see [http://trac.edgewall.org/ticket/217 #217]). See these [http://trac-hacks.org/wiki/XmlRpcPlugin#Installation install instructions] for requirements and documentation.<br />
<br />
'''Web''' <br />
<br />
Requirements:<br />
* Trac 0.9 or later<br />
<br />
In this mode the standard Trac web interface is used for repository access. Tickets may be created and edited through a web browser. Offline editing and attachments are not supported.<br />
<br />
== Recommended Trac version ==<br />
<br />
Mylyn should work with any stable release Trac release that is version 0.9.x or 0.10.x (see below for known limitations). Mylyn works best when used with Trac's XML-RPC Plugin (see above) but we do not recommend a particular Trac version. <br />
<br />
The Trac connector tests are run against these Trac versions:<br />
<br />
* Trac 0.10.4, XML-RPC Plugin rev. 1950<br />
* Trac 0.9.6<br />
<br />
See {{bug|175211}} for details about Trac 0.11 support.<br />
<br />
== Why do I get an HTTP Error 500 Internal server error when creating a ticket that contains non-ASCII characters? ==<br />
<br />
Problems related to character encodings have been reported when Trac is run with Python 2.3. Upgrading to Python 2.4 may help to resolve this. Please comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=188363 bug #188363] if you encounter an internal server error when creating a ticket that contains non-ASCII characters.<br />
<br />
== Known limitations ==<br />
<br />
* Trac 0.10.1 <br />
** Known incompatibility with Trac XML-RPC Plugin. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164272 bug 164272] for details.<br />
* Trac 0.10.3 <br />
** Known incompatibility with old versions of the Trac HttpAuthPlugin (fixed in revision 1890 or later). The plug-in enables basic auth for XML-RPC when Trac AccountManagerPlugin for form based authentication is used. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168413 bug 168413] for details.<br />
* Trac 0.11<br />
** Currently untested.<br />
** Known incompatibility with Trac XML-RPC Plugin See [http://trac-hacks.org/wiki/XmlRpcPlugin] for details.<br />
<br />
== Why are tasks opened in a web browser and not in the rich editor? ==<br />
<br />
Please make sure that the access type in the repository properties is set to XML-RPC. This requires Trac 0.10 and XML-RPC (see above).<br />
<br />
== Which URLs does Mylyn access in a Trac repository? ==<br />
<br />
XML-RPC:<br />
<br />
* The expected URL is either /xmlrpc or /login/xmlrpc (if login credentials are provided)<br />
<br />
Web:<br />
<br />
* Authentication: /login <br />
* Querying: /query?format=tab...<br />
* Synchronizing ticket details: /ticket/...<br />
* Getting repository configuration to populate query dialog: /query or /newticket<br />
<br />
The web mode relies on screen scraping and is likely to fail if the design<br />
(i.e. HTML output) of the Trac repository is heavily customized.<br />
<br />
= Generic Web Repository Connector =<br />
<br />
== Where can I find the web repository connector ==<br />
<br />
It is available from the extensions update page. Please see http://www.eclipse.org/mylyn/downloads/<br />
<br />
== Why can't I connect using one of the existing templates? ==<br />
<br />
<br />
The Web Repository Connector have a Preview option in Advanced Configuration section on the Query preferences. If you get an error or preview table does not show expected list of tasks you can use Query Pattern like (.+?)(\n) to see content of the retrieved page and compare it with the source of the web page for the same url loaded into the web browser.<br />
<br />
If that does not help then you could use the wget tool (on Windows it available as a standalone command line tool and also included with Cygwin).<br />
<br />
Run the following command:<br />
<br />
<pre>wget -v -d -o query.log -O query.html "http://your.query.url"</pre><br />
<br />
If repository require basic http auth, you'll need to use ''--http-user=USER'' and ''--http-password=PASS'' options.<br />
<br />
Then open file ''query.html'' in the web browser and check if it show list of issues you need to fetch from the web server. If it does have correct list, then there could be a problem with query pattern used for parsing. <br />
<br />
A popular mistake is an unmasked '?' that separates request parameters in the url). For example:<br />
<br />
<pre><a href="show_bug.cgi\?id\=(.+?)">.+?<span class="summary">(.+?)</span></pre><br />
<br />
If ''query.html'' does not show expected list of issues you can check ''query.log'' for server responses and try to identify if server require authentication, redirecting your requests somewhere or issue any other errors.<br />
<br />
== Known limitations ==<br />
<br />
* In Mylyn 1.0: if a web server responds by requesting a redirect to an absolute URL while fetching a resource, the connector falsely prepends "/" to the URL and the request will fail. The workaround is to use final url where redirect is pointing to (you can find it as describe above). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=167282 bug 167282] for details.<br />
<br />
= Task-Focused UI =<br />
<br />
== What is the Task-Focused UI? ==<br />
<br />
When you activate a task, Mylyn automatically maintains a task context by monitoring your interaction. The task context provides a predictable degree-of-interest weighting of the relevance of the elements and relations that you work with to the task-at-hand (as described in the [http://kerstens.org/mik/publications/2006-11-mylar-fse.pdf Foundations of Software Engineering conference paper]). The Task-Focuse UI is the mechanism by which Mylyn presents Mylyn the task-context model in order to reduce information overload and to automate the manaul management of UI elements like editors and change sets. Examples:<br />
* Filtering, decoration and expansion management in views<br />
* Automatic folding in editors<br />
* Ranking in content assist<br />
* Editor management<br />
* Perspective management<br />
* Change set management<br />
<br />
== Why do files disappear from Focused views when I close them? ==<br />
<br />
By default Mylyn automatically manages the set of open files to match the task context, so that you don't have to. This ensures that the editor list (viewable via mechanisms like Ctrl+E) corresponds to what you in views like the ''Package Explorer'' when they are in Focused mode. When you close a file manually, you express that it is uninteresting, and as such it will be removed from the task context. It will also disappear from the corresponding automatically managed change sets for the same reason. This behavior can be turned off via ''Preferences -> Mylyn -> Context -> Manage open editors to match task context''. However, it is highly recommended since Mylyn will prevent the number of editors from bloating by automatically closing editors for elements that have decayed in interest, and always keep the editors for interesting elements open.<br />
<br />
<br />
== Why did all my editor tabs disappear? ==<br />
<br />
When you deactivate a task, all editors will be closed, and then when you reactivate the task all the windows will be open again. Try it, it's fun. <br />
<br />
Mylyn actively manages your open editors with task context. It takes some getting used to, but enables switching between tasks when you are multitasking without cluttering your editor tabs. This editor management can be disabled via ''Window -> Preferences -> Mylyn -> Context''. However, before disabling it consider reading the ''"Managing open editors..."'' section of [http://www-128.ibm.com/developerworks/java/library/j-mylar2/index.html#N10116 Task-focused programming with Mylar].<br />
<br />
== How do I get rid of an element if it is not interesting? ==<br />
<br />
When a view is focused elements will disappear on their own if they are not repeatedly selected via a mechanism called interest decay. Note that decay does not use the wall clock, but instead relies on the number of selections that you have made when working on that task to determine which elements disappear. This helps make it feel very predictable.<br />
<br />
If you want want to force one or more elements to disappear from the context use the '''Remove from Focus''' action on the context menu. Note that the element will still be part of the task context since it was previously part of the interaction. <br />
<br />
If you want to permanently delete the element from the interaction history use the '''Remove from Context''' action on the '''Context''' tab of the '''Task Editor'''. For example, if a company private element was part of a task context that is to be shared with a public repository, this action can be used to clean it up before sharing. Note that elements will be removed from the task context recursively.<br />
<br />
== Which Focused UI features can I turn off? ==<br />
<br />
'''All of them.''' When no task is active neither are any of Mylyn's features. When working with task contexts Mylyn's Focused UI features are all optional and in general configurable. While many find it the key benefit of Mylyn, the entire Focused UI is optional and can be uninstalled via ''Help -> Software Updates -> Manage Configuration''.<br />
<br />
The following table summarizes how the key features can be toggled:<br />
<br />
<table><br />
<tr><br />
<td>'''UI Mechanism'''</td><br />
<td>'''Example/description'''</td><br />
<td>'''Toggle using'''</td><br />
</tr><br />
<tr><br />
<td>Interest filtering</td><br />
<td>Package Explorer</td><br />
<td>''Apply Mylyn'' button on view toolbar</td><br />
</tr><br />
<tr><br />
<td>Automatic toggling of filtering</td><br />
<td>Package Explorer</td><br />
<td>''Preferences -> Mylar -> Context -> Toggle focused mode..</td><br />
</tr><br />
<tr><br />
<td>Interest decoration</td><br />
<td>Bolding of landmark elements</td><br />
<td>''Preferences -&gt; General -&gt; Appearance -&gt; Label Decoration''</td><br />
</tr><br />
<tr><br />
<td>Content assist</td><br />
<td>Ranking of interesting elements</td><br />
<td>Eclipse 3.2: ''Java -&gt; Editor -&gt; Content Assist -&gt; Work in Progress -&gt;'' turn off Mylyn, turn on Java</td><br />
</tr><br />
<tr><br />
<td>Active change sets</td><br />
<td>Grouping of changes by tasks</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Team''</td><br />
</tr><br />
<tr><br />
<td>Editor management</td><br />
<td>Auto opening/closing of editors</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Editor Management''</td><br />
</tr><br />
<tr><br />
<td>Active views</td><br />
<td>Active Search and Hierarchy</td><br />
<td>Only on if view is active</td><br />
</tr><br />
</table><br />
<br />
For additional configuration options see the ''Mylyn'' and ''General -> Appearance'' preference pages.<br />
<br />
== What is the performance profile of the Focused UI? ==<br />
<br />
The goal is for Mylyn to have '''no noticeable effect''' on Eclipse's speed or memory usage.<br />
You do not need to increase the amount of memory Eclipse runs with to use Mylyn. <br />
Any performance issue should be [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Mylyn reported as a bug]. <br />
<br />
The current '''Performance Profile''' is:<br />
<br />
# Mylyn only runs if a task is active, and has no impact on Eclipse if no task is active.<br />
# Task context models have negligible memory overhead. <br />
# When a task is active, additional view refresh is required to update the views based on interest model changes. This should not be noticeable on Windows where refresh is very quick, but could be more noticeable on other platforms.<br />
# The time to activate a task context is dominated by the time it takes Eclipse to open the editors in the context. You can set the preference for how many editors to open in the Mylyn preference page (e.g. setting to 1 will dramatically reduce activation time, but also remove the benefit of having open editors correspond to the task context). You can also turn off editor management entirely in the Mylyn Tasks view pull-down.<br />
# Eclipse startup is slowed down by (4) if a task is active when Eclipse is shut down.<br />
# The low priority background searches that the Active Search view runs can be noticeable on slower machines.<br />
<br />
== What happened to the Active Search and Active Hierarchy views? ==<br />
<br />
These views were not included in the Mylyn 1.0 release because they never made it beyond the experimental phase. <br />
* The ''Active Search'' view has not been sufficiently tuned to adapt to the lifecycle of a task context, and as a result requires manual manipulation of the degree-of-separation scope as you work on long-running tasks. Otherwise it becomes overloaded with elements. In addition, it is not yet clear whether an additional view is the right UI for this facility, and it is hard to find room for an additional view of this size on screen resolutions of 1600x1200 and smaller.<br />
* The ''Active Hierarchy'' view is also hard to allocate space for, especially when using the in-place hierarchy (Ctrl+T) on a landmark can be a quick way to see the relevant part of the task context's hierarchy.<br />
<br />
These features still show promise in displaying task context and saving repetitive searches, so we have not removed them. They have instead moved to the Mylyn Sandbox, and can be used and experimented with by following the [http://wiki.eclipse.org/index.php/Mylyn_Contributor_Reference#Sandbox instructions on the Contributors page]. For feedback on these views please use the corresponding bug reports or newsgroup.<br />
<br />
= Java Development =<br />
<br />
== Content assist troubleshooting ==<br />
<br />
Mylyn uses custom Content Assist processors in order to rank and separate the elements in the current task context. To see proposals ranked according to interest you must have only the ''Type Proposals (Mylyn)'' kinds checkbox enabled in the list below, otherwise you will see duplicates. '''If you do not see any proposals, check this list''' to ensure that either the Mylyn or the plain proposals are enabled. '''To do this automatically''', run ''New -> Mylyn -> Recommended Preferences''. Or you can select them manually as in the preference page below. <br />
<br />
[[Image:mylar-content-assist-prefs.gif]]<br />
<br />
'''Why do I see duplicate proposals?'''<br />
<br />
Ensure that you have only the ''(Mylyn)'' proposals kinds enabled in ''Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced'', otherwise you will see duplicates.<br />
<br />
If you use proposals via Ctrl+Shift+Space instead of the typical Ctrl+Space you will see duplicates. Vote for JDT/Text [https://bugs.eclipse.org/bugs/show_bug.cgi?id=147781 bug 147781] if you use this mechanism. Also see: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=129080 bug 129080]<br />
<br />
'''Why do I get an error message when using content assist?'''<br />
<br />
If after invoking Content Assist you see an error message dialog that states:<br />
The extension took too long to return from the 'computeCompletionProposals()' operation<br />
this is most likely due to something interrupting the proposal operation (e.g. garbage collection). Ignore it if it does not recur, increase Eclipse's memory if it does (e.g via <code>-Xmx384M</code> command line argument). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=141457 bug 141457] for more details.<br />
<br />
== Why do interesting elements not show in the Project Explorer? ==<br />
<br />
The ''Package Presentation -> Hierarchical'' mode is not supported on the ''Project Explorer'' view in Eclipse 3.2 through 3.3M3 and possibly later versions (https://bugs.eclipse.org/bugs/show_bug.cgi?id=161362 bug 161362). Use the view menu to set ''Package Presentation -> Flat'' as a work-around.<br />
<br />
== How do I stop declarations from showing in the Package Explorer? ==<br />
<br />
If you don't like Mylyn's constant showing of Java members in the ''Package Explorer'', select the drop-down menu, then ''Filters...'' and enable the ''Mylyn Java Declarations Filter''. It will then stick in the menu in case you want to toggle between modes. Note that this will hide interest information about members that aren't in your current file (e.g. showing you which methods are landmarks) so this mode is not recommended, but can be useful for <code>1024x768</code> screen resolutions.<br />
<br />
[[Image:mylar-java-filtering-declarations.gif]]<br />
<br />
== Why does nothing show up in the Active Search or Active Hierarchy? ==<br />
<br />
As you work, elements become Landmarks (bold decoration), and these elements populate the ''Active Search'' and ''Active Hierarchy'' views. To force an element to populate the views manually, make it a Landmark by <code>right+clicking</code> or hitting <code>Ctrl+Alt+Shift+UpArrow</code>.<br />
<br />
== Known limitations ==<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=106678 Bug 106678]: The Project Explorer's Hierarchical Java package presentation layout is not supported on Eclipse 3.3Mx, and interesting elements will be hidden if enabled. Work-around is to use the default Flat package presentation.<br />
<br />
= Team Support =<br />
<br />
== Why does task change set not appear when I modify files? ==<br />
<br />
A task change set should appear if you activate a task and modify a file connected to a compatible source repository (e.g. CVS, SVN). If it does not try the following:<br />
<br />
* Ensure you have installed the [http://www.eclipse.org/mylyn/downloads/ ''Mylyn Bridge: Eclipse SDK'' feature]. Note that this feature is not currently distributed with the Java-only Eclipse download ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191793 bug 191793] ).<br />
<br />
* Verify that the [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuring_the_Synchronize_view_for_change_sets configured ''Synchronize View'' is configured for change sets].<br />
<br />
If the above are working but the change set appears to be missing relevant files:<br />
<br />
* You may be seeing the ''Synchronize'' view's refresh problem ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142395 bug 142395]). Toggle from ''Incoming/Ougtoing'' to ''Incoming'' mode and back again to refresh the view.<br />
<br />
* If the files or change set are still missing deactivate and reactivate the task to force a full refresh.<br />
<br />
== Why do files disappear from the change set when I close them? ==<br />
<br />
If you have the ''Preferences -> Mylyn -> Context -> Manage open editors to match task context'' option enabled, Mylyn will perform editor management so that you don't have to. Closing a file makes it less interesting, and causes it to disappear from the active task context, and hence from the change set. This option prevents you from having to manage the set of open files, will automatically close editors for files that become uninteresting, and will ensure that the open editors match the task context.<br />
<br />
== Why is interest lost when I retrieve someone else's context? ==<br />
<br />
To identify elements within a project, Mylyn relies on the name of the project being consistent across workspaces. If the project name in the workspace that the context was created with is different than its name in your workspace, the task context will not show elements within that project ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164058 bug 164058]). The work-around is to use the same project names across your team's workspaces.<br />
<br />
The other case where context can be lost is if the elements change names outside of the workspace ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164243 bug 164243]).<br />
<br />
= Misc =<br />
<br />
<br />
<br />
== How does Mylyn relate to IBM's Jazz? ==<br />
<br />
At the EclipseCon and JavaONE 2006 conferences IBM demonstrated previews of Jazz, a collaborative team server and Eclipse-based client. Articles have remarked on the similarities between Mylyn and Jazz because both integrate tasks into Eclipse (Jazz's "work items" and Mylyn's "tasks"), and both provide change sets grouped by task. But there are both significant differences and complementary aspects to the two approaches. A key goal of Mylyn is to provide an open source framework to support integration of task management with ''existing issue trackers and source repositories''. According to the presentations, components that come with Jazz include include a ''next-generation issue tracker and source repository'' and related lifecycle management tools such as project health. In addition, a driving and unique goal of Mylyn is to focus the UI around a usage-based and degree-of-interested weighted task context, which is complementary to the Jazz platform. Just as it integrates with Mylyn's Task List, Mylyn's Task Focused UI and task context model components are possible to integrate with other kinds of task management systems, such as the one provided by Jazz.<br />
<br />
Update: at EclipseCon 2007 the IBM Jazz team showed a Mylyn connector for Jazz.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/FAQ&diff=49783Mylyn/FAQ2007-09-10T03:52:31Z<p>Steffen.pingel.eclipse.org: /* Recommended Trac version */</p>
<hr />
<div>[[Category:Mylyn]] <br />
<br />
[[Mylyn User Guide]], <br />
[http://eclipse.org/mylyn Mylyn Home],<br />
[http://wiki.eclipse.org/index.php?title=Special:Userlogin&returnto=Special:Userlogout Log in to edit]<br />
<br />
For instructions on [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Download_Mylar downloading] [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installation installing] and [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuration configuring] <br />
Mylyn, see the [[Mylyn User Guide]]. For instructions on developing and contributing to Mylyn, see the [[Mylyn Contributor Reference]].<br />
<br />
= Installation =<br />
<br />
== What versions of Eclipse are supported? ==<br />
<br />
See the [http://eclipse.org/mylyn/dl.php download page].<br />
<br />
Mylyn also relies on a web browser that works with the Standard Widget Toolkit; Windows and MacOS users are fine, but Linux users might have to download another browser. See [http://www.eclipse.org/swt/faq.php#browserlinux the SWT Browser guide] for which browsers will work. See [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux installing browser on Linux] for installation instructions.<br />
<br />
== What version of Java is required? ==<br />
<br />
Mylyn needs the '''Java 5''' virtual machine.<br />
<br />
To check the version of the Java virtual machine that Eclipse was launched with to to ''Help -> About Eclipse SDK -> Configuration Details'' and verify that the java.vm.version is 1.5. <br />
<br />
Mac users should refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
* If you do not have Java 5, you can download it from [http://72.5.124.55/javase/downloads/index.jsp Sun's web site]. <br />
* If you have more than one VM, you need to specify that Eclipse should use the JDK1.5 VM. <br />
<br />
In Unix, set the environment variable <code>JAVA_HOME</code> to the root of the JDK1.5 installation and/or set the <code>PATH</code> variable to put the JDK1.5 executable directory before any other VM executable directories. For example, under <code>bash</code> in Unix:<br />
export JAVA_HOME="''(location of JDK1.5 root)''"<br />
export PATH=$JAVA_HOME/bin:$PATH<br />
<br />
<b>We do [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140955 not recommend] using JDK 1.6 on Eclipse 3.1.</b> (It works fine with Eclipse 3.2 or 3.3.) To use JDK 1.6 on Eclipse 3.1, you must add the following line to your <code>config.ini</code>file:<br />
<code><br />
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,<br />
J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6<br />
</code><br />
<br />
== What version of Mylyn is distributed with the Eclipse downloads? ==<br />
<br />
The [http://www.eclipse.org/downloads/ default Eclipse downloads] contain the following Mylyn redistributions. Since the redistributed versions can be missing important bug fixes or feature additions, we recommend using the [http://www.eclipse.org/mylyn/downloads latest version of Mylyn].<br />
<br />
* Eclipse IDE for Java Developers: all of Mylyn except Team integration (e.g. automatic change sets) integration. Install the Eclipse CVS integration and then install the latest Mylyn build to get this component.<br />
<br />
* Eclipse IDE for Java EE Developers: all of Mylyn redistribution, install manually<br />
<br />
* Eclipse IDE for C/C++ Developers: no Mylyn redistribution, install manually<br />
<br />
* Eclipse for RCP/Plug-in Developers: all of Mylyn redistributed<br />
<br />
* Eclipse Classic: no Mylyn redistribution, install manually<br />
<br />
== My tasks or queries disappeared, what do I do? ==<br />
<br />
This happens if Mylyn failed to install. First ensure that you have a correct install by following the instructions in the next section. After that, if you still do not see your tasks use the ''Task List'' view menu -> ''Restore Tasks From History...'' command (also available via ''File -> Import -> Task List''.<br />
<br />
== Installation Troubleshooting ==<br />
<br />
''' Java Persistence API Tools error when updating the JEE Eclipse Package '''<br />
<br />
If you are trying to install additional features and get this error you have hit [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194959 bug 194959] which should be resolved soon. The work-around is to check off the ''Europa Discovery Site'' and install the first two components of the ''Data Tools Platform''.<br />
<br />
''' Update failures '''<br />
<br />
On Eclipse versions earlier than 3.3 (final) use '''only the "Search for new features.."''' option when updating Mylyn. If you use "Search for updates..." the Update Manager will allow a partial install that can cause Mylyn to fail to start, and you will need to run update again. See the ''feature configuration problem'' section below for details. If you encounter this problemm consider voting for Platform [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132450 bug 132450].<br />
<br />
''' Startup exceptions '''<br />
<br />
If you see startup errors or warnings such as <code>BundleException</code> or timeout messages restart Eclipse with the <code>-clean</code> flag either on the command line, in your shortcut link, or by temporarily it into the <code>eclipse/eclipse.ini</code> file. If that does not resolve the problem please [http://www.eclipse.org/mylar/bugs.php file a bug].<br />
<br />
''' Incompatible VM (e.g. JDK 1.4) '''<br />
<br />
If you are using the wrong VM, you'll see errors like the following in your log file. <br />
<code><br />
Root exception: java.lang.UnsupportedClassVersionError:<br />
org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)<br />
</code><br />
<br />
See [[#Download_and_configure_Java_5_or_6|Configure Java]] to fix this problem.<br />
<br />
''' Incompatible version of Eclipse '''<br />
<br />
Separate versions and update sites exist [http://eclipse.org/mylyn/dl.php for Eclipse 3.1 and 3.2]), in which case you may see errors like the following in your <code><workspace>/.metadata/.log </code>file or in a Mylyn view:<br />
<code><br />
java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()<br />
The activator org.eclipse.mylar.java.MylarJavaPlugin for bundle org.eclipse.mylar.java is invalid<br />
</code><br />
<br />
''' Mylyn feature configuration problem '''<br />
<br />
If the above do not address the issue, the easiest thing to do is uninstall any old versions and update to the latest Mylyn. Your tasks won't be lost, because by default they are stored in the <code><workspace>/.metadata/.mylyn</code> folder which will be read next time Mylyn starts correctly. <br />
* First, uninstall the old version of Mylyn using ''Help -> Software Updates -> Manage Configuration''. <br />
* You need to Disable all Mylyn features by right-clicking them.<br />
* Allow Eclipse to restart after the last is disabled.<br />
* After restart, ensure that the 3rd toolbar button is pressed (figure below) so that you see the disabled features to uninstall.<br />
* Uninstall all the disabled features using the popup menu. <br />
<br />
If you don't uninstall, the the Update Manager will think that you have the latest and tell you that there are no updates. <br />
<br />
<b>Note: manually removing the plug-ins and features can lead to configuration errors.</b> <br />
<br />
After uninstalling, update Eclipse by adding the correct update site specified at on the [http://eclipse.org/mylar/dl.php download page], and after that automatically or manually updating will install the correct version.<br />
<br />
[[Image:mylar-eclipse-manage-configuration.gif]]<br />
<br />
'''What do I need to do in installation to be able to use Mylyn task management features with bug/task/issue trackers?'''<br />
<br />
When you install, make sure that you select a connector for your bug/task/issue tracking software. For example, to use Bugzilla, you have to install the Bugzilla connector component.<br />
<br />
'''I've installed Mylyn ; why can't I see anything different?'''<br />
<br />
The two most likely possibilities are:<br />
# You don't have any Mylyn views open. Select ''Window -> Show View -> Other'', then select ''Mylyn'' and you should see the available Mylyn Views. <br />
# If you still don't see anything, then perhaps you aren't using the JDK1.5 VM (or later). See [[Mylyn_Installation_Guide#Download_and_configure_Java|configuring Java]].<br />
<br />
<br />
'''What does the error "Network connection problems encountered during search" mean?'''<br />
<br />
If you get that message while trying to download Mylyn, it means that Eclipse couldn't find the location you entered. This might be because you copied something incorrectly (watch for extra characters -- even extra spaces can cause errors), or because the site went down. You may be able to see if the site is up or down by copying the URL into your Web browser.<br />
<br />
'''What does the "Update manager failure" message mean? '''<br />
<br />
It means that Eclipse could not access the update site, or that it got confused about the configuration state of your Eclipse. First try updating again to see if the update site is accessible. <br />
<br />
If you are trying to update the JIRA connector you can also try de-selecting that feature in case the <code>Tigris.org</code> update site is not accessible. Using ''Search for new features to install..'' when installing can help to avoid this problem. If that does not work see the feature configuration troubleshooting below. <br />
<br />
'''What does "Could not create Browser page: No more handles (<code>java.lang.UnsatisfiedLinkError: ...</code>)" mean?'''<br />
<br />
It probably means that you are running Linux and don't have Eclipse and a Web browser configured to work together. See [[http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Installing_Browser_on_Linux| installing a browser on Linux]].<br />
<br />
'''When downloading, why do I get a warning that the feature was unsigned?'''<br />
<br />
Signing plugins requires extra administrative details with <code>eclipse.org</code> which most plug-ins seek to avoid. <br />
<br />
'''N.B.''': Security issues with features should not be underestimated. Eclipse allows users to download new functionality from remote servers. A rogue plug-in can act as a perfect Trojan horse. It can look innocent enough and provide useful function while spawning threads in the background with full access to the local file system and the Internet (if connected). Beware of installing features from update sites you do not trust.<br />
<br />
'''What does "<code>Root exception: java.lang.UnsupportedClassVersionError: org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)</code>" mean?'''<br />
<br />
It probably means that the virtual machine is JDK1.4 or lower. See [[Mylyn_Installation_Guide#Download_and_configure_Java| download and configure Java]].<br />
<br />
'''Why am I getting messages in my <code><workspace>/.metadata/.log</code> or my Mylyn view that say things like <code>"java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()"</code> and "The activator <code>org.eclipse.mylar.java.MylarJavaPlugin</code> for bundle <code>org.eclipse.mylar.java</code> is invalid"?'''<br />
<br />
This probably means that your Mylyn download version didn't match your Eclipse download version. Note that [http://eclipse.org/mylar/dl.php the download site] has different downloads for Eclipse 3.1 and Eclipse 3.2.<br />
<br />
To fix this problem, see the [[Mylyn_Uninstallation_Guide| uninstallation guide]], then re-install from [http://eclipse.org/mylar/dl.php the correct download site].<br />
<br />
'''What does "Could not create Bugzilla editor input" and "<code>java.io.IOException</code>: SAX2 driver class <code>org.apache.xerces.parsers.SAXParser</code> not found" mean?'''<br />
<br />
It probably means that you are on MacOS, and for some reason are missing Xerces from the Mac JDK1.5. You will probably need to add it to your default classpath. Please refer to and comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=144287 bug 144287] if you see this problem.<br />
<br />
To ensure that you are using the 1.5 VM refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
'''I've just updated to Mylyn 2.0 and I don't see any tasks in my Task List'''<br />
<br />
As part of the update to Mylyn 2.0 the old data folder has been migrated to <workspace folder>/.metadata/.mylyn from the old location <workspace folder>/.mylar. IF for some reason migration failed (.mylar folder still exists), simply shut down Eclipse and manually move your old <workspace folder>/.mylar folder to <workspace folder>/.metadata/.mylyn (note the name change to .mylyn)<br />
<br />
== Configuration Troubleshooting == <br />
<br />
'''How can I change the number of editors left open before Mylyn starts closing editors?'''<br />
<br />
Turn off or increase the number of editors to leave open using ''Preferences -> General -> Editors -> Number of opened editors before closing''. Since Mylyn will manage the open editors with task activation, this number can be set higher or you can disable automatic closing entirely.<br />
<br />
'''Do I need the Outline View when running Mylyn?'''<br />
<br />
No, not really. The Package Explorer and folded signatures should provide enough context for you. If, at some point, you really need to see an Outline View, you can always enter (Ctrl+O) to show the in-place Outline View.<br />
<br />
'''What does the message "content assist proposals no longer appear" mean?'''<br />
<br />
This usually happens when uninstalling when using Eclipse 3.2. Make sure that the "Java Completions" and "Java Types" proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
'''Why do I get errors like "HTTP Response Code 407" or "Proxy Authentication Error" when accessing repositories through a proxy server?'''<br />
<br />
It is likely that you need to configure these proxy server settings. Select ''Window -> Preferences -> Install/Update'', and update the section in the "Proxy settings" section of the form.<br />
<br />
'''I can't use <code>Ctrl+Alt+Shift+Arrow Up</code> for'' Mark as Landmark''. What do I do?<br />
<br />
This is usually a Linux/GNOME problem, where the Gnome keyboard shortcuts are interfering with the Eclipse shortcuts. Go to the Keyboard shortcuts (which might be something like ''Desktop -> Control Centre -> Keyboard Shortcuts'' or ''System -> Preferences -> Keyboard Shortcuts'') and disable both of these shortcuts:<br />
* Move one workspace up<br />
* Move one workspace down<br />
<br />
See also: [[Mylyn_User_Guide#Keyboard_mappings_on_Linux| keyboard mappings on Linux]].<br />
<br />
'''How do I turn on spell checking?'''<br />
<br />
See [[Mylyn_User_Guide#Spell_Checking| spell checking]].<br />
<br />
== Uninstall troubleshooting ==<br />
<br />
When '''uninstalling in Eclipse''' Mylyn via the ''Help -> Software Updates -> Manage Configuration'' dialog you will need to uninstall dependencies first (e.g. Bugzilla Connector, Subclipse integration) and then uninstall the core Mylyn features.<br />
<br />
When '''uninstalling manually''' by deleting all of the Mylyn plug-ins and features from the <code>eclipse/plugins</code> and <code>eclipse/features</code> directory make sure to delete all of the plug-ins and then restart Eclipse with the -clean option (e.g. by inserting it into a shortcut or the <code>eclipse.ini</code> file.<br />
<br />
On '''Eclipse 3.1:''' you may need to reset the Java editor to be default for <code>.java</code> again via: ''Preferences -> General -> Editors -> File Associations''<br />
<br />
On '''Eclipse 3.2:''' if after uninstalling '''content assist proposals no longer appear''' you need to ensure that the ''Java Completions'' and ''Java Types'' proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylyn FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
== I am seeing <code>java.lang.OutOfMemoryError: PermGen space </code>errors, what's wrong? ==<br />
<br />
If your Eclipse crashes, or you see the above error after installing Mylyn or other plug-ins, you have most likely hit the infamous MaxPermSize bug. This is not a Mylyn specific problem, but a general Eclipse problem that is often triggered on Eclipse 3.2 and later, if you have many plug-ins installed and are using a Sun JVM. <br />
<br />
To fix it simply add the following to your launch arguments. This is usually to your shortcut, or to the <tt>eclipse/configuration/config.ini</tt> file:<br />
<br />
-XX:MaxPermSize=128M<br />
<br />
If you are using a large number of plug-ins (e.g. WTP) you may need to increase the number to more than 128M. <br />
<br />
Details of the problem are on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250 Platform bug 92250].<br />
<br />
= Task List =<br />
<br />
== Why won't the Archive category disappear? ==<br />
<br />
The ''Archive'' category will automatically appear if a task needs to be shown, but is not in any query or category. <br />
In order to ensure that you do not miss reminders or notifications the following tasks will always be shown in the Task List, even if they have been removed from a category or a query:<br />
* Tasks scheduled for this week or overdue. Remove these by using the ''Schedule'' pop-up menu option to defer them to a future week or to clear the schedule.<br />
* Repository tasks that have incoming changes, such as comments. Remove these by reading them or marking them as "read" via the ''Mark -> Read'' pop-up menu.<br />
<br />
== The Archive category contains many irrelevant tasks, how do I clean it up? ==<br />
<br />
If you created very broad queries you could end up with thousands of tasks in the Archive category. Other than clearing the <tt>workspace/.metadata/.mylyn/tasklist.xml.zip</tt> and <code>workspace/.metadata/.mylyn/offline</code> folder (note that this will entirely reset your Task List) the easiest option is to:<br />
* Clean up your queries to include only tasks of interest (note that including completed/resolved tasks is recommended).<br />
* Turn off ''Focus on Workweek'' in the ''Task List''.<br />
* Turn off the ''Filter Archive Category'' option in the ''Task List'' view menu.<br />
* Delete all of the unneeded tasks from within the Archive category. Note that if the tasks are not matched by queries they will be deleted permanently and any local notes or scheduling information that you have added to them will be lost.<br />
<br />
== How does Mylyn count the active time for a task? ==<br />
<br />
Whenever you work on a task, Mylyn accumulates the time you spend actively working on a task. This time can be viewed in the ''Personal Planning'' section of the ''Task Editor''. When you are not interacting with Eclipse, the timing automatically times out after 3 minutes by default. This means that activity outside of Eclipse will not be captured when you work on the task and that the timings in Mylyn are a lower bound of the total time spent on the task (capturing timings for work done outside of Eclipse involves OS specific extensions).<br />
<br />
== How do I prevent long-running tasks from adding to the progress bar? ==<br />
<br />
If you have many long-running or recurring tasks scheduled for this week, they can affect the ''Task List'' weekly progress bar. This can be misleading as they may never be completed. The current work-around to prevent long-running tasks from being included in the weekly progress bar is to schedule their estimated time to be 0 (zero). Alternatively, you can schedule only the amount of time you plan on spending on that task this week.<br />
<br />
== Does the Task List replace the Eclipse Tasks view? ==<br />
<br />
The SDK's ''Tasks'' view is used for showing markers such as 'todo' tags which indicate a local problem with a resource, similar to a compiler warning. As such, these 'tasks' are at a much lower level of granularity than Mylyn's tasks, and one task could involve cleaning up multiple todos. In order to make working with only the markers in a particular task context, e.g. for clean-up before committing, the ''Apply Mylyn'' filter is available for both the ''Problems'' and the ''Tasks'' views.<br />
<br />
== What if I use multiple workspaces? ==<br />
<br />
Mylyn's support for multiple workspaces is currently limited (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130658 bug 130658] for a discussion) because the Task List is considered to be specific to the person, and not to the workspace. We recommend configuring your Eclipse workspace to use working sets instead of relying on multiple workspaces. <br />
* John O'Shea's blog: [http://www.xlml.com/aehso/2007/02/02/eclipse-workspaces-containing-projects-with-overlapping-locations-and-mylar/ Eclipse workspaces containing projects with overlapping locations, and Mylar]<br />
<br />
If using a single workspace is not possible you can do the following:<br />
* In ''Preferences -> Mylyn -> Task List'' set the ''Data Directory'' to be a shared location, and do this for both workspaces.<br />
* Be sure to avoid launching both Eclipse workspaces at the same time, as changes in one workspaces could overwrite the Task List in the other workspace.<br />
* If you upgrade Eclipse or move your workspace and don't see your tasks, check the ''Data Directory'' setting.<br />
<br />
== How do I export my task and repository data? ==<br />
<br />
Export via File > Export > Mylyn > Task Data<br />
<br />
== Why does Mylyn use the term "task"? ==<br />
<br />
There are many work items that make up the developer's workday. Many issue trackers and project management tools refer to these as: bugs, defects, actions, tickets, stories, enhancements, and the list goes on. We refer to all such work items as "tasks" because the word tasks is short and commonly used in time management tools. Task Repository connectors can customize the presentation of tasks, for example, indicating which is a defect and which is an action item.<br />
<br />
= Task Editor =<br />
<br />
== Why am I seeing strange boxes where I expect to see proper characters? ==<br />
<br />
If for example you aren't seeing the proper single quote chacters in the summary of [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=197644 bug#197644]], check that the encoding is set correctly for the repository in the asociated Task Repositories view (Properties > Additional Settings > Character Encoding). For bugs.eclipse.org/bugs set your charcter encoding to ''ISO-8859-1''.<br />
<br />
= Task Repositories =<br />
<br />
== What if Mylyn doesn't support my task/bug/issue/ticket repository? ==<br />
<br />
To see support for your repository faster, do a search of the open repository connector requests and [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Bconnector%5D&product=Mylyn&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=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= vote for the corresponding bug] if your tracker is there, or [http://www.eclipse.org/mylar/bugs.php create a new bug]. <br />
<br />
[[Mylyn_User_Guide#Generic_Web_Repository_Connector|Generic Repository Connector]], allows creating Queries to the web-based issue tracking repositories and get list of issues from the web UI into the Task List.<br />
<br />
It is also possible to link a ''local task'' with the web page in web-based repository via the Mylyn Web integration.<br />
<br />
'''To create a task from any web-based repository:'''<br />
<br />
* Drag the URL from the address bar of the browser, or from a hyperlink in a bug listing to the ''Mylyn Tasks'' view. This will create a task for the bug, link it to the page, and populate the description with the title of the corresponding page. '''In Mozilla:''' simply drag the URL. '''In Internet Explorer:''' you must have <code>Ctrl</code> pressed in order for Eclipse to recognize the drop.<br />
* '''Alternatively,''' you can copy the URL, press the ''New Task'' button on the ''Mylyn Tasks'' view. This has the same effect as above but you can edit the description after retrieving it.<br />
* Opening the task will now open the corresponding issue. You can also <code>right+click</code> the task and select ''Open in External Browser''.<br />
<br />
[[Image:mylar-tasklist-weblink-editor.gif]]<br />
<br />
== Why were my repository credentials reset? ==<br />
<br />
If you upgrade Eclipse or your Java VM, you will need to reset your credentials in the ''Task Repositories'' view because these are stored in the secure Eclipse workbench keyring. Also see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=149607 bug 149607]. If you are migrating '''from Eclipse 3.2 to 3.3''' note that you will need to use a different update site, which is listed here: http://eclipse.org/mylyn/dl.php<br />
<br />
== Why are my updated repository attributes not showing up? ==<br />
<br />
Your server's repository attributes can change frequently, for example, there can be a new "milestone" or "version" added to the Bugzilla repository with each release. When the ''Preferences -> Mylyn -> Task List -> Synchronization'' setting is enabled, every 10th synchronization will update the attributes from the repository. If you do not have this setting enabled, your can force the update via the ''Update Attributes'' action on the task repositories' context menu in the ''Task Repositories'' view. Note that you will need to reopen a task editor to see the updated attributes. If you instead update via the button on the ''Attributes'' section of the ''Task Editor'' the attribute settings will be reloaded without needing to reopen.<br />
<br />
== Authentication Troubleshooting ==<br />
<br />
You must ensure repository credentials are filled out correctly. Refer to the diagram below:<br />
<br />
[[image: AuthenticationTroubleshooting2.png|right]]<br />
<br />
# Enter the repository URL (i.e. https://bugs.eclipse.org/bugs) and an optional label<br />
# Credentials<br />
#* Usually email address and password <br />
#* Some sites, such as <code>dev.eclipse.org</code>, use anonymous logon with password left blank.<br />
#Http Authentication (optional)<br />
#* Some sites are protected by either BASIC or DIGEST http authentication. If this is the case, enter appropriate credentials here.<br />
#* One way to test if the site requires http authentication is to point your browser at the repository. If you are presented with an authentication dialog popup, the site is likely protected by http authentication.<br />
#Proxy Server Configuration (optional)<br />
#* By default Mylyn uses the Platform's Install/Update proxy settings. Uncheck this box if you wish to use an alternative proxy.<br />
#* If the proxy requires authentication, this is where you enable and enter your proxy credentials.<br />
#* If you are experiencing connection problems, ensure your Install/Update proxy settings are valid or the repository specific settings are correct<br />
#* Mylyn has been tested with HTTP proxy servers. Currently SOCKS is not supported.<br />
#Validate Settings <br />
#*Press the ''validate'' button to test the settings<br />
#*If you are seeing errors like "HTTP Response Code 407" or "Proxy Authentication Error" it is likely that you need to configure proxy settas as described above.<br />
#*If your sever uses a certificate and fails to connect, e.g. you see exceptions <tt>sun.security.validator.ValidatorException: PKIX path building failed</tt> then you need to point Eclipse at your certificate, see the [http://ahtik.com/blog/2006/05/11/fixing-eclipse-mylar-jira-integration/ instructions on this blog].<br />
<br clear="all" /><br />
<br />
* If your repository uses MS NTLM authentication and only standard http authentication is being passed to the repository this can result when the local hostname cannot be resolved. Ensure your machine's hostname is set correctly and resolves to a valid address.<br />
<br />
== Why are task hyperlinks not working? ==<br />
<br />
For task hyperlinks in textual editors (e.g. Java editor) and other text viewers (e.g. History view comments) you must associate the project that contains the resource to the task repository. <br />
<br />
:''Project association can also come from 3rd party metadata trough the contrubuted [[Mylar_Integrator_Reference#Mapping_from_projects_to_Task_Repositories|extension point]]. [http://subclipse.tigris.org/ Subclipse] and [http://docs.codehaus.org/display/M2ECLIPSE/Integration+with+Mylyn Maven integration for Eclipse] plugins contributing it. See few more details [http://jroller.com/page/eu?entry=linking_projects_from_the_eclipse here].''<br />
<br />
Note that to view a hyperlink you must hold down the <code>Ctrl</code> key when hovering over the reference to the task. References to tasks are connector specific and the common reference is found on the top left of the task editor and other conventions tend to follow those used in the web UI (e.g. "bug 123" for Bugzilla, "ABC-123" for JIRA).<br />
<br />
[[Image:mylyn-project-repository-association.gif]]<br />
<br />
= Bugzilla Connector =<br />
<br />
== What versions are supported? ==<br />
<br />
We recommend using the latest [http://www.bugzilla.org/download/ release] of Bugzilla.<br />
<br />
* '''Bugzilla 2.18.6 is the lowest version of Bugzilla supported'''. If you are getting errors that indicate failure to update attributes this may be an indication that the Bugzilla server is not supported (< 2.18.6).<br />
<br />
*If you are using '''Bugzilla 2.18''' and are getting '''mid-air collisions''' this is likely due to incorrectly formatted timestamp field in the underlying bugs database table ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149513 bug 149513]). This can be resolved by upgrading to Bugzilla 2.20 or later.<br />
<br />
== Why are queries failing? ==<br />
<br />
*If '''queries are not working''' correctly ensure that you have the right Bugzilla server version selected for the corresponding repository: ''Task Repositories (View) ->'' right+click the repository ''-> Properties''. For supported versions see the [http://www.eclipse.org/mylar/dl.php download page]. If the repository is still not functioning it may be due to authentication or connectivity problems. If that does not resolve the problem please post a message to the newsgroup or [http://www.eclipse.org/mylar/bugs.php submit a bug].<br />
<br />
== Why do tasks fail to open? ==<br />
<br />
*If upon opening a bug, the Bugzilla tab only displays a warning "'''Could not download task data, possibly due to timeout or connectivity problem. Please check connection and try again.'''", ensure that your repository is returning XML data by pointing your browser to <code><your-repository-url>/show_bug.cgi?id=1&ctype=xml</code> to show the contents of bug 1 in XML form. The Bugzilla client requires that bugs be accessible in XML form. If the repository doesn't support xml then it is likely that the repository is too old (Mylyn currently supports Bugzilla 2.18 and later).<br />
<br />
* If '''reports fail to load''' or '''reports fail to synchronize''' (task description remains ''italic''), check the error log for a "'''File not found'''" error pointing to <code>bugzilla.dtd</code> or a "'''Failed to retrieve products from server'''" error message - these result when the <code>urlbase</code> parameter is not set on the bugzilla server, or your bugzilla installation is missing the <code>bugzilla.dtd</code> file. See: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=161759 bug#161759]<br />
<br />
* If '''attributes are missing options''' in the bug editor (ie. missing a recently added milestone, [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155431 bug# 155431]):<br />
** Update attributes by choosing ''Update Attributes'' from the context menu in the ''Task Repositories'' view<br />
** Synchronize the task in the Task List<br />
** Reopen the task - new options should be available.<br />
<br />
== Why do tasks fail to submit? ==<br />
<br />
* '''Error upon submit: unable to make any match for name/email entered.''' If your bugzilla is configured for user names rather than full email address the QA Contact field will cause the submit to fail ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=166555 bug# 166555]). To resolve, select 'Local users enabled' option on the Repository Configuration page. <br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your account's username and password and are not using the HTTP authentication fields instead.<br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your bugzilla instance's cookie domain under the required settings. The cookie domain must lead with a dot.<br />
<br />
* If '''attachments are failing to submit''' and you see that after processing the attachment, the bugzilla bug shows a size of "bytes" (no numbers), your database may be dropping the packet sending the file. '''On MySQL''', check the [http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html max_allowed_packet directive]. You may see errors like: <code>DBD::mysql::st execute</code> failed: Got a packet bigger than 'max_allowed_packet' bytes [for Statement "INSERT INTO attach_data (id, thedata) VALUES (38, ?)"] at <code>/path/to/bugzilla/attachment.cgi</code> line 993. Also, '''check the maximum attachment size''' in ''Bugzilla Parameters -> Attachments''.<br />
<br />
* If a submit fails with an '''Invalid Username or Password''' error even though repository settings do validate, make sure that cookies could be set. See also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175502 bug 175502]<br />
<br />
== What time zone is used in the task editor? ==<br />
<br />
*The '''times''' that appear in the Bugzilla bug editor (ie. created, modified) '''are local to the server hosting the Bugzilla repository''', not your local machine's time zone. <br />
<br />
== Known limitations ==<br />
<br />
* The <code>usermatchmode</code> is not currently supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168204 bug 168204]) and as such full email addresses need to be used.<br />
<br />
* The <code>usevisibilitygroups</code> parameter is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=180876 bug#180876]). Group assignment will currently be lost if updated using the Bugzilla rich task editor.<br />
<br />
* Version 1.0 of Mylyn presents an error message upon new comment submission to RedHat's public Bugzilla repository. The comment is in fact posted. This issue is resolved in Mylyn 2.0M2 and higher. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=183251 bug#183251])<br />
<br />
= JIRA Connector =<br />
<br />
If you see errors like the following, work around this by opening repository ''Properties Page'' and clicking OK (bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169102 169102]).<br />
<br />
org.tigris.jira.core.service.exceptions.AuthenticationException<br />
at org.tigris.jira.internal.core.service.soap.SoapJiraService.getProjectsNoSchemes(SoapJiraService.java:204)<br />
<br />
== What are the server requirements? ==<br />
<br />
The '''JIRA SOAP/RPC services have to be running on the JIRA server''':<br />
<br />
* Jira 3.3.3 or higher (3.7 or higher for attachment retrieval)<br />
* Jira RPC plugin 1.4.3 or higher<br />
<br />
Latest information also available on the [http://www.eclipse.org/mylar/dl.php download page].<br />
<br />
Related Resources:<br />
<br />
* [http://confluence.atlassian.com/display/JIRA/JIRA+Development+Hub Jira Development Wiki]<br />
* [http://confluence.atlassian.com/pages/viewpage.action?pageId=1035 Jira RPC Plugin Overview]<br />
<br />
== Why can't I connect? ==<br />
<br />
* If you get a <code>org.tigris.jira.core.service.exceptions.ServiceUnavailableException</code> you need to turn on the JIRA SOAP/RPC services on the server.<br />
* Similarly, if you get a "Processing instructions are not allowed within SOAP messages" message, ensure that SOAP/RPC services are on.<br />
* If you get a '''503''' error code verify that the SOAP/RPC interface is enabled.<br />
* If you get a '''403''' error code verify that the SOAP/RPC interface is enabled, and also check your authentication mechanism. If the server is using NTLM authentication, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156397 bug 156937] for diagnosis steps.<br />
* If you see an '''"unrecognized priority" message''' in the ''Error Log'', the problem is that the JIRA Connector does not support customized priorities so the priority value specified in that message will not correspond to the priority icons visible in the Task List.<br />
* If you are being '''prompted for your log-in credentials''' by the Browser tab of the task editor or the new task editor, this is because without rich editor support the connector is using the web-based UI instead of logging in on your behalf as is done with a rich task editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142869 bug 142869]).<br />
* If you get a <CODE>AuthenticationException</code> and a query won't synchronize, use Task Repositories (view) -> Properties (on the repository) -> Validate Settings. This will clear the connection if it died.<br />
<br />
<!-- HEAVILY OUTDATED. PLUGIN NOW USES COMMON PROXY INFRASTRUCTURE<br />
== Why can't I synchronize when using a proxy server? ==<br />
<br />
* Proxy configuration is '''based on the normal Java HTTP system properties''', which can be configured either by launching Eclipse with <code>-vmargs</code> and using the following settings, or by putting these settings into the or by putting the following into the <code>eclipse/eclipse.ini</code> file (after -vmags):<br />
-Dhttp.proxyHost=<host> <br />
-Dhttp.proxyPort=<port><br />
* Make sure that when using these settings you do not enable the proxy settings on the ''Install/Update'' preference page, since they may override these settings.<br />
* If you are using '''SSL''', you will also need to set the <code>https.proxyHost</code> and <code>https.proxyPort</code>. <br />
* Authentication is configured with the <code>http.proxyUser</code> and <code>http.proxyPassword</code> system properties (also for SSL)<br />
* You can also use <code>http.nonProxyHosts</code> system property to enumerate hosts that should not be proxied. Note that matching is implemented on the exact host name used for JIRA server and patterns are not supported. --><br />
<br />
== Known limitations ==<br />
* Attachment retrieval (including retrieval of the task context and attachment list in the task editor) require JIRA 3.7 or above ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=169757 bug 169757])<br />
<!-- * NTLM authentication is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172395 bug 172395]) --><br />
* Customized priorities are not currently supported, so all issues with a customized priority will have the default priority level ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=165518 bug 165518]).<br />
* blank but editable custom fields doesn't appear in the RSS data, and as result we can't show them for editing<br />
* because of JIRA api limitations, we can support custom fields in the task editor, but not in the new custom task editor<br />
<!-- * On JIRA 3.6.x private filters saved on the server can fail to retrieve results ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=174328 bug 174328]). The work-around is to create a custom query in Mylyn using the form-based query designer or to share the filter in JIRA. --><br />
<br />
== How can I enable compression for SOAP messages? ==<br />
<br />
If your repository has lots of projects and components you can speed up the download of the repository configuration by enabling compression. <br />
<br />
* Add a filter-mapping to your JIRA server configuration: [http://jira.atlassian.com/browse/JRA-10353].<br />
* Enable compression in your global JIRA configuration.<br />
* Check the compression setting for your task repository in Mylyn versions 2.0M2 and later.<br />
<br />
== Reporting issues ==<br />
<br />
Since JIRA can be heavily customized there is a chance that some particular customizations may not work, so if you can't connect to your proprietary repository it is a good idea to try the following public repositories to make sure you have working configuration:<br />
<br />
* http://jira.codehaus.org<br />
* http://issues.apache.org/jira/<br />
* http://opensource.atlassian.com/projects/spring <br />
<br />
If you can't get query results, you could try to call "Open with Browser" on query node in the Task List view and then save link "Current view: XML" and attach it to the bug report.<br />
<br />
Even if query don't work you could try "Open Repository Task" from your JIRA repository node on the Task Repositories view and check if you can open JIRA task editor for that issue. Same for the Task search (Ctrl-H, Task Search)<br />
<br />
To investigate various error you may need to enable debug tracing. To do that you need to create the <code>.options</code> file with the following content:<br />
<br />
<pre><br />
org.eclipse.mylyn.jira.ui/connector=true<br />
org.eclipse.mylyn.jira.ui/dataHandler=true<br />
</pre><br />
<br />
and then add the following options to the Eclipse command line (or eclipse.ini file):<br />
<br />
<pre><br />
-debug <path to the .options file>/.options<br />
</pre><br />
<br />
The additional logging will go into the regular Eclipse log and the Error Log view<br />
<br />
= Trac Connector =<br />
<br />
== What are the server requirements? ==<br />
<br />
The Trac connector offers two access methods:<br />
<br />
'''XML-RPC''' (recommended)<br />
<br />
Requirements:<br />
* Trac 0.10<br />
* [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] rev. 1950<br />
<br />
This access method offers editing of tasks in a rich editor, attachment support and offline editing. It requires the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] for Trac to be enabled for the accessed repository. The XmlRpcPlugin provides a remote interface to the Trac repository and is distributed separately from Trac (see [http://trac.edgewall.org/ticket/217 #217]). See these [http://trac-hacks.org/wiki/XmlRpcPlugin#Installation install instructions] for requirements and documentation.<br />
<br />
'''Web''' <br />
<br />
Requirements:<br />
* Trac 0.9 or later<br />
<br />
In this mode the standard Trac web interface is used for repository access. Tickets may be created and edited through a web browser. Offline editing and attachments are not supported.<br />
<br />
== Recommended Trac version ==<br />
<br />
Mylyn should work with any stable release Trac release that is version 0.9.x or 0.10.x (see below for known limitations). Mylyn works best when used with Trac's XML-RPC Plugin (see above) but we do not recommend a particular Trac version. <br />
<br />
The Trac connector tests are run against these Trac versions:<br />
<br />
* Trac 0.10.4, XML-RPC Plugin rev. 1950<br />
* Trac 0.9.6<br />
<br />
See {{bug|175211}} for details about Trac 0.11 support.<br />
<br />
== Why do I get an HTTP Error 500 Internal server error when creating a ticket that contains non-ASCII characters? ==<br />
<br />
Problems related to character encodings have been reported when Trac is run with Python 2.3. Upgrading to Python 2.4 may help to resolve this. Please comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=188363 bug #188363] if you encounter an internal server error when creating a ticket that contains non-ASCII characters.<br />
<br />
== Known limitations ==<br />
<br />
* Trac 0.10.1 <br />
** Known incompatibility with Trac XML-RPC Plugin. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164272 bug 164272] for details.<br />
* Trac 0.10.3 <br />
** Known incompatibility with old versions of the Trac HttpAuthPlugin (fixed in revision 1890 or later). The plug-in enables basic auth for XML-RPC when Trac AccountManagerPlugin for form based authentication is used. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168413 bug 168413] for details.<br />
* Trac 0.11<br />
** Currently untested.<br />
** Known incompatibility with Trac XML-RPC Plugin See [http://trac-hacks.org/wiki/XmlRpcPlugin] for details.<br />
<br />
== Why are tasks opened in a web browser and not in the rich editor? ==<br />
<br />
Please make sure that the access type in the repository properties is set to XML-RPC. This requires Trac 0.10 and XML-RPC (see above).<br />
<br />
= Generic Web Repository Connector =<br />
<br />
== Where can I find the web repository connector ==<br />
<br />
It is available from the extensions update page. Please see http://www.eclipse.org/mylyn/downloads/<br />
<br />
== Why can't I connect using one of the existing templates? ==<br />
<br />
<br />
The Web Repository Connector have a Preview option in Advanced Configuration section on the Query preferences. If you get an error or preview table does not show expected list of tasks you can use Query Pattern like (.+?)(\n) to see content of the retrieved page and compare it with the source of the web page for the same url loaded into the web browser.<br />
<br />
If that does not help then you could use the wget tool (on Windows it available as a standalone command line tool and also included with Cygwin).<br />
<br />
Run the following command:<br />
<br />
<pre>wget -v -d -o query.log -O query.html "http://your.query.url"</pre><br />
<br />
If repository require basic http auth, you'll need to use ''--http-user=USER'' and ''--http-password=PASS'' options.<br />
<br />
Then open file ''query.html'' in the web browser and check if it show list of issues you need to fetch from the web server. If it does have correct list, then there could be a problem with query pattern used for parsing. <br />
<br />
A popular mistake is an unmasked '?' that separates request parameters in the url). For example:<br />
<br />
<pre><a href="show_bug.cgi\?id\=(.+?)">.+?<span class="summary">(.+?)</span></pre><br />
<br />
If ''query.html'' does not show expected list of issues you can check ''query.log'' for server responses and try to identify if server require authentication, redirecting your requests somewhere or issue any other errors.<br />
<br />
== Known limitations ==<br />
<br />
* In Mylyn 1.0: if a web server responds by requesting a redirect to an absolute URL while fetching a resource, the connector falsely prepends "/" to the URL and the request will fail. The workaround is to use final url where redirect is pointing to (you can find it as describe above). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=167282 bug 167282] for details.<br />
<br />
= Task-Focused UI =<br />
<br />
== What is the Task-Focused UI? ==<br />
<br />
When you activate a task, Mylyn automatically maintains a task context by monitoring your interaction. The task context provides a predictable degree-of-interest weighting of the relevance of the elements and relations that you work with to the task-at-hand (as described in the [http://kerstens.org/mik/publications/2006-11-mylar-fse.pdf Foundations of Software Engineering conference paper]). The Task-Focuse UI is the mechanism by which Mylyn presents Mylyn the task-context model in order to reduce information overload and to automate the manaul management of UI elements like editors and change sets. Examples:<br />
* Filtering, decoration and expansion management in views<br />
* Automatic folding in editors<br />
* Ranking in content assist<br />
* Editor management<br />
* Perspective management<br />
* Change set management<br />
<br />
== Why do files disappear from Focused views when I close them? ==<br />
<br />
By default Mylyn automatically manages the set of open files to match the task context, so that you don't have to. This ensures that the editor list (viewable via mechanisms like Ctrl+E) corresponds to what you in views like the ''Package Explorer'' when they are in Focused mode. When you close a file manually, you express that it is uninteresting, and as such it will be removed from the task context. It will also disappear from the corresponding automatically managed change sets for the same reason. This behavior can be turned off via ''Preferences -> Mylyn -> Context -> Manage open editors to match task context''. However, it is highly recommended since Mylyn will prevent the number of editors from bloating by automatically closing editors for elements that have decayed in interest, and always keep the editors for interesting elements open.<br />
<br />
<br />
== Why did all my editor tabs disappear? ==<br />
<br />
When you deactivate a task, all editors will be closed, and then when you reactivate the task all the windows will be open again. Try it, it's fun. <br />
<br />
Mylyn actively manages your open editors with task context. It takes some getting used to, but enables switching between tasks when you are multitasking without cluttering your editor tabs. This editor management can be disabled via ''Window -> Preferences -> Mylyn -> Context''. However, before disabling it consider reading the ''"Managing open editors..."'' section of [http://www-128.ibm.com/developerworks/java/library/j-mylar2/index.html#N10116 Task-focused programming with Mylar].<br />
<br />
== How do I get rid of an element if it is not interesting? ==<br />
<br />
When a view is focused elements will disappear on their own if they are not repeatedly selected via a mechanism called interest decay. Note that decay does not use the wall clock, but instead relies on the number of selections that you have made when working on that task to determine which elements disappear. This helps make it feel very predictable.<br />
<br />
If you want want to force one or more elements to disappear from the context use the '''Remove from Focus''' action on the context menu. Note that the element will still be part of the task context since it was previously part of the interaction. <br />
<br />
If you want to permanently delete the element from the interaction history use the '''Remove from Context''' action on the '''Context''' tab of the '''Task Editor'''. For example, if a company private element was part of a task context that is to be shared with a public repository, this action can be used to clean it up before sharing. Note that elements will be removed from the task context recursively.<br />
<br />
== Which Focused UI features can I turn off? ==<br />
<br />
'''All of them.''' When no task is active neither are any of Mylyn's features. When working with task contexts Mylyn's Focused UI features are all optional and in general configurable. While many find it the key benefit of Mylyn, the entire Focused UI is optional and can be uninstalled via ''Help -> Software Updates -> Manage Configuration''.<br />
<br />
The following table summarizes how the key features can be toggled:<br />
<br />
<table><br />
<tr><br />
<td>'''UI Mechanism'''</td><br />
<td>'''Example/description'''</td><br />
<td>'''Toggle using'''</td><br />
</tr><br />
<tr><br />
<td>Interest filtering</td><br />
<td>Package Explorer</td><br />
<td>''Apply Mylyn'' button on view toolbar</td><br />
</tr><br />
<tr><br />
<td>Automatic toggling of filtering</td><br />
<td>Package Explorer</td><br />
<td>''Preferences -> Mylar -> Context -> Toggle focused mode..</td><br />
</tr><br />
<tr><br />
<td>Interest decoration</td><br />
<td>Bolding of landmark elements</td><br />
<td>''Preferences -&gt; General -&gt; Appearance -&gt; Label Decoration''</td><br />
</tr><br />
<tr><br />
<td>Content assist</td><br />
<td>Ranking of interesting elements</td><br />
<td>Eclipse 3.2: ''Java -&gt; Editor -&gt; Content Assist -&gt; Work in Progress -&gt;'' turn off Mylyn, turn on Java</td><br />
</tr><br />
<tr><br />
<td>Active change sets</td><br />
<td>Grouping of changes by tasks</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Team''</td><br />
</tr><br />
<tr><br />
<td>Editor management</td><br />
<td>Auto opening/closing of editors</td><br />
<td>''Preferences -&gt; Mylyn -&gt; Editor Management''</td><br />
</tr><br />
<tr><br />
<td>Active views</td><br />
<td>Active Search and Hierarchy</td><br />
<td>Only on if view is active</td><br />
</tr><br />
</table><br />
<br />
For additional configuration options see the ''Mylyn'' and ''General -> Appearance'' preference pages.<br />
<br />
== What is the performance profile of the Focused UI? ==<br />
<br />
The goal is for Mylyn to have '''no noticeable effect''' on Eclipse's speed or memory usage.<br />
You do not need to increase the amount of memory Eclipse runs with to use Mylyn. <br />
Any performance issue should be [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Mylyn reported as a bug]. <br />
<br />
The current '''Performance Profile''' is:<br />
<br />
# Mylyn only runs if a task is active, and has no impact on Eclipse if no task is active.<br />
# Task context models have negligible memory overhead. <br />
# When a task is active, additional view refresh is required to update the views based on interest model changes. This should not be noticeable on Windows where refresh is very quick, but could be more noticeable on other platforms.<br />
# The time to activate a task context is dominated by the time it takes Eclipse to open the editors in the context. You can set the preference for how many editors to open in the Mylyn preference page (e.g. setting to 1 will dramatically reduce activation time, but also remove the benefit of having open editors correspond to the task context). You can also turn off editor management entirely in the Mylyn Tasks view pull-down.<br />
# Eclipse startup is slowed down by (4) if a task is active when Eclipse is shut down.<br />
# The low priority background searches that the Active Search view runs can be noticeable on slower machines.<br />
<br />
== What happened to the Active Search and Active Hierarchy views? ==<br />
<br />
These views were not included in the Mylyn 1.0 release because they never made it beyond the experimental phase. <br />
* The ''Active Search'' view has not been sufficiently tuned to adapt to the lifecycle of a task context, and as a result requires manual manipulation of the degree-of-separation scope as you work on long-running tasks. Otherwise it becomes overloaded with elements. In addition, it is not yet clear whether an additional view is the right UI for this facility, and it is hard to find room for an additional view of this size on screen resolutions of 1600x1200 and smaller.<br />
* The ''Active Hierarchy'' view is also hard to allocate space for, especially when using the in-place hierarchy (Ctrl+T) on a landmark can be a quick way to see the relevant part of the task context's hierarchy.<br />
<br />
These features still show promise in displaying task context and saving repetitive searches, so we have not removed them. They have instead moved to the Mylyn Sandbox, and can be used and experimented with by following the [http://wiki.eclipse.org/index.php/Mylyn_Contributor_Reference#Sandbox instructions on the Contributors page]. For feedback on these views please use the corresponding bug reports or newsgroup.<br />
<br />
= Java Development =<br />
<br />
== Content assist troubleshooting ==<br />
<br />
Mylyn uses custom Content Assist processors in order to rank and separate the elements in the current task context. To see proposals ranked according to interest you must have only the ''Type Proposals (Mylyn)'' kinds checkbox enabled in the list below, otherwise you will see duplicates. '''If you do not see any proposals, check this list''' to ensure that either the Mylyn or the plain proposals are enabled. '''To do this automatically''', run ''New -> Mylyn -> Recommended Preferences''. Or you can select them manually as in the preference page below. <br />
<br />
[[Image:mylar-content-assist-prefs.gif]]<br />
<br />
'''Why do I see duplicate proposals?'''<br />
<br />
Ensure that you have only the ''(Mylyn)'' proposals kinds enabled in ''Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced'', otherwise you will see duplicates.<br />
<br />
If you use proposals via Ctrl+Shift+Space instead of the typical Ctrl+Space you will see duplicates. Vote for JDT/Text [https://bugs.eclipse.org/bugs/show_bug.cgi?id=147781 bug 147781] if you use this mechanism. Also see: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=129080 bug 129080]<br />
<br />
'''Why do I get an error message when using content assist?'''<br />
<br />
If after invoking Content Assist you see an error message dialog that states:<br />
The extension took too long to return from the 'computeCompletionProposals()' operation<br />
this is most likely due to something interrupting the proposal operation (e.g. garbage collection). Ignore it if it does not recur, increase Eclipse's memory if it does (e.g via <code>-Xmx384M</code> command line argument). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=141457 bug 141457] for more details.<br />
<br />
== Why do interesting elements not show in the Project Explorer? ==<br />
<br />
The ''Package Presentation -> Hierarchical'' mode is not supported on the ''Project Explorer'' view in Eclipse 3.2 through 3.3M3 and possibly later versions (https://bugs.eclipse.org/bugs/show_bug.cgi?id=161362 bug 161362). Use the view menu to set ''Package Presentation -> Flat'' as a work-around.<br />
<br />
== How do I stop declarations from showing in the Package Explorer? ==<br />
<br />
If you don't like Mylyn's constant showing of Java members in the ''Package Explorer'', select the drop-down menu, then ''Filters...'' and enable the ''Mylyn Java Declarations Filter''. It will then stick in the menu in case you want to toggle between modes. Note that this will hide interest information about members that aren't in your current file (e.g. showing you which methods are landmarks) so this mode is not recommended, but can be useful for <code>1024x768</code> screen resolutions.<br />
<br />
[[Image:mylar-java-filtering-declarations.gif]]<br />
<br />
== Why does nothing show up in the Active Search or Active Hierarchy? ==<br />
<br />
As you work, elements become Landmarks (bold decoration), and these elements populate the ''Active Search'' and ''Active Hierarchy'' views. To force an element to populate the views manually, make it a Landmark by <code>right+clicking</code> or hitting <code>Ctrl+Alt+Shift+UpArrow</code>.<br />
<br />
== Known limitations ==<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=106678 Bug 106678]: The Project Explorer's Hierarchical Java package presentation layout is not supported on Eclipse 3.3Mx, and interesting elements will be hidden if enabled. Work-around is to use the default Flat package presentation.<br />
<br />
= Team Support =<br />
<br />
== Why does task change set not appear when I modify files? ==<br />
<br />
A task change set should appear if you activate a task and modify a file connected to a compatible source repository (e.g. CVS, SVN). If it does not try the following:<br />
<br />
* Ensure you have installed the [http://www.eclipse.org/mylyn/downloads/ ''Mylyn Bridge: Eclipse SDK'' feature]. Note that this feature is not currently distributed with the Java-only Eclipse download ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191793 bug 191793] ).<br />
<br />
* Verify that the [http://wiki.eclipse.org/index.php/Mylyn_User_Guide#Configuring_the_Synchronize_view_for_change_sets configured ''Synchronize View'' is configured for change sets].<br />
<br />
If the above are working but the change set appears to be missing relevant files:<br />
<br />
* You may be seeing the ''Synchronize'' view's refresh problem ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142395 bug 142395]). Toggle from ''Incoming/Ougtoing'' to ''Incoming'' mode and back again to refresh the view.<br />
<br />
* If the files or change set are still missing deactivate and reactivate the task to force a full refresh.<br />
<br />
== Why do files disappear from the change set when I close them? ==<br />
<br />
If you have the ''Preferences -> Mylyn -> Context -> Manage open editors to match task context'' option enabled, Mylyn will perform editor management so that you don't have to. Closing a file makes it less interesting, and causes it to disappear from the active task context, and hence from the change set. This option prevents you from having to manage the set of open files, will automatically close editors for files that become uninteresting, and will ensure that the open editors match the task context.<br />
<br />
== Why is interest lost when I retrieve someone else's context? ==<br />
<br />
To identify elements within a project, Mylyn relies on the name of the project being consistent across workspaces. If the project name in the workspace that the context was created with is different than its name in your workspace, the task context will not show elements within that project ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164058 bug 164058]). The work-around is to use the same project names across your team's workspaces.<br />
<br />
The other case where context can be lost is if the elements change names outside of the workspace ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164243 bug 164243]).<br />
<br />
= Misc =<br />
<br />
<br />
<br />
== How does Mylyn relate to IBM's Jazz? ==<br />
<br />
At the EclipseCon and JavaONE 2006 conferences IBM demonstrated previews of Jazz, a collaborative team server and Eclipse-based client. Articles have remarked on the similarities between Mylyn and Jazz because both integrate tasks into Eclipse (Jazz's "work items" and Mylyn's "tasks"), and both provide change sets grouped by task. But there are both significant differences and complementary aspects to the two approaches. A key goal of Mylyn is to provide an open source framework to support integration of task management with ''existing issue trackers and source repositories''. According to the presentations, components that come with Jazz include include a ''next-generation issue tracker and source repository'' and related lifecycle management tools such as project health. In addition, a driving and unique goal of Mylyn is to focus the UI around a usage-based and degree-of-interested weighted task context, which is complementary to the Jazz platform. Just as it integrates with Mylyn's Task List, Mylyn's Task Focused UI and task context model components are possible to integrate with other kinds of task management systems, such as the one provided by Jazz.<br />
<br />
Update: at EclipseCon 2007 the IBM Jazz team showed a Mylyn connector for Jazz.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Plan/3.0&diff=48436Mylyn/Plan/3.02007-08-28T19:47:46Z<p>Steffen.pingel.eclipse.org: /* Theme Brainstorming */</p>
<hr />
<div>[[Category:Mylyn]] <br />
Please note that this is '''VERY ROUGH DRAFT''' and changes are still in progress. To propose items or discussion the [http://eclipse.org/mylyn/communiation mylyn-integrators] mailing list. Also see the [[Mylyn 2.0 Plan]].<br />
<br />
= Milestones =<br />
Mylar milestones are released 1 week after [http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_3.html Eclipse milestones]. Click to view open bugs. Dates will be listed in the Mylyn Calendar (view as [http://www.google.com/calendar/ical/kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com/public/basic.ics iCal] or [http://www.google.com/calendar/embed?src=kq3ed9c0latktst29lrl8nffu0%40group.calendar.google.com html]).<br />
* 2.1M1: August 27, 2007<br />
* 2.1: October 6, 2007<br />
* 2.2M1: November 17, 2007<br />
* 2.2: January 12, 2008<br />
* 2.3M1: February 23, 2008<br />
* 2.3: March 5, 2008<br />
* 3.0RC: May 17, 2008 (API Freeze)<br />
* 3.0: Jun 28, 2008 (view [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&target_milestone=3.0&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= all open 3.0 bugs])<br />
<br />
= Scope =<br />
<br />
The first goal of Mylyn is to make task and context management seamlessly integrated with the Eclipse Platform by providing rich and extensible frameworks for task repository connectors, structure bridges and team support. The second goal is to provide a reference implementation of the Task-Focused UI for the Eclipse SDK. This includes structure bridges for the artifacts supported by the SDK which include Java, PDE, Ant and generic files. It also includes the Bugzilla Connector as the reference task repository implementation, and CVS integration as the reference team support. Additional features can be considered based on the availability community contributions and resources.<br />
<br />
= Priorities =<br />
<br />
In addition to using the planned themes listed below, we need to continue prioritizing the ongoing input of our growing user community. Committers should prioritize bugs in the following order. This order need not be used if a bug contains a community contribution of a patch, in which case the [http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference#Contributing_patches quality of the patch] determines the priority.<br />
# Frameworks & APIs: Tasks, Context, Team, Monitor, headless use<br />
# UI: Tasks List, Task Editor, Task-focused UI<br />
# Connectors: Bugzilla (reference implementation), Trac (committer supported), JIRA (community supported)<br />
<br />
= Platforms =<br />
* Eclipse: 3.3 and 3.4 Milestones (only latest milestone supported at time of release)<br />
* Java: JRE 5.0 or later required<br />
* Operating Systems: all supported by Eclipse<br />
<br />
= Theme Brainstorming =<br />
<br />
Legend: in progress, <font color=green>completed</font>, <font color=gray>optional</font> <br />
<br />
''Theme dump from the 2007-07-24 conference call''<br />
<br />
Supporting Integrators<br />
* Headless use<br />
* Tasks framework: the usual<br />
* Team framework: making it more generic, Platform/Team contributions<br />
* Context framework: ohter langauges WTP, DLTK<br />
<br />
: EK: componentize task editors<br />
<br />
Task List usability<br />
* Archive category<br />
* Uncategorized category<br />
* Subtasks<br />
* Notifications<br />
* Improve presentation of incoming changes ({{bug|177208}})<br />
* Task editor workflow<br />
* Streamline task creation<br />
<br />
: EK: multiple instances of Task List view to facilitate drag and drop and different presentations; more flexible ways to group tasks without creating many queries (to make it easier to deal with and observe many issues; it is also one of the most voted requests); improve task editor usability (i.e. scroll to recent changes, sync editor with outline and other views); tagging tasks and creating custom task hierarchies; improving task list storage for incremental updates and allow full text search (perhaps using lucene)<br />
<br />
Task Activity<br />
* Lots of fixes needed<br />
<br />
: EK: clean up bugs related to context interaction with the IDE. In some cases Java code completion is less relevant with context activated; Package Explorer show random elements (like class patch containers), or don't clean the parent nodes after temporary/transient child got removed from context; inconsistency between "remove from context" menu and keyboard shortcuts (the latter work on stuff that don't have menu)<br />
<br />
Task List models<br />
* Content providers vs. filters and groupings (e.g. subtasks)<br />
* Better support for presentations<br />
* Generic schema vs. connector-specific schema<br />
<br />
Synchronization<br />
* Synch priority<br />
* Network I/O responsiveness, cancellability<br />
* Incremental synch architecture<br />
<br />
Task schema<br />
* common schema<br />
* generic XML format for repository task data and repo configuration<br />
<br />
: EK: the above is either the same or need to be clarified. Is these formats intended for import/export or for working with 3rd party repositories. The former probably better to address with public API instead of relying on the schema.<br />
<br />
Task context (degree-of-interest model)<br />
* Surfacing relationships<br />
* Improving bookkeeping<br />
* Preserving element identity: refactoring, migrating handles<br />
* Composite contexts for subtasks and working sets<br />
<br />
: EK: previewing context without activation; preserve user identity within context to see context evolution when multiple people working on the task; context comparison; recovering the task context from global history and generally improve "clean task" story.<br />
<br />
Internal process<br />
* Explicitly tag bug reports needed by advanced use cases or committers?</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=47527Mylyn/Porting Guide2007-08-22T22:51:57Z<p>Steffen.pingel.eclipse.org: /* Tasks API */</p>
<hr />
<div>[[Category:Mylyn]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from 1.0 to 2.0 =<br />
<br />
See the <b>[[Mylyn Porting Guide 2.0]]</b><br />
<br />
= Porting from 2.0 to 3.0 =<br />
<br />
There is currently no need to port Mylyn from the 2.0 APIs since current Mylyn releases are backwards compatible. Throughout the 2.x release cycle we will be using this wiki to gather changes and suggestions for improving the APIs for 3.0.<br />
<br />
== Tasks API == <br />
<br />
* <code>AbstractRepositoryConnector</code><br />
** <code>isRepositoryConfigurationStale(TaskRepository)</code> has been added<br />
<br />
* <code>AbstractRenderingEngine</code> has been added for converting Wiki syntax to HTML<br />
<br />
* <code>AbstractRepositoryTaskEditor</code> has been extended to provide HTML preview capabilities for repositories that support Wiki syntax in ticket descriptions and comments<br />
** <code>addSelectableControl()</code>: added<br />
** <code>createReplyHyperlink()</code> is now protected (was private)<br />
** <code>DescriptionListener</code> is now protected (was private)<br />
** <code>getParentEditor()</code>: added<br />
** <code>getRenderingEngine()</code>: added<br />
** <code>removeSelectableControl()</code>: added<br />
** <code>fillToolBar(..)</code>: added<br />
<br />
* <code>TaskEditor</code><br />
** class no longer final (experimental extensibility)<br />
<br />
* <code>TaskListManager</code><br />
** resolveIdentifiersConflict() has been added<br />
<br />
* <code>TaskTextViewerConfiguration</code> has been added (former name was RepositoryViewerConfig)<br />
<br />
== Pending Changes for Mylyn 3.0 == <br />
<br />
* Rename <code>IMylarMonitorLifecycleListener</code> to <code>IMonitorLifecycleListener</code><br />
* Rename <code>MockRepositoryTask</code> to <code>MockTask</code></div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=47301Mylyn/Meetings2007-08-21T15:44:14Z<p>Steffen.pingel.eclipse.org: /* Tuesday, August 21, 10-11am PT */</p>
<hr />
<div>[[Category:Mylyn]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
=== Pending Discussion Items ===<br />
<br />
* UI design of merging open task dialog ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=193423 bug 193423])<br />
* UI and content provider discussion design of improving the Archive category ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=181388 bug 181388])<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, August 21, 10-11am PT ====<br />
<br />
Agenda: <br />
* Summer of Code student status reports (Balazs, Jevgeni, Xiaoyang)<br />
** Figure out how to distribute Trac wiki editor {{bug|200114}} (Steffen)<br />
* Timezone datestamp issue {{bug|198714}} (Rob)<br />
* API to store arbitrary attributes in the AbstractTask: patch on bug {{bug|199818}}, {{bug|199817}} (Eugene)<br />
* grouping of query elements, 2nd patch on {{bug|175318}} (Eugene)<br />
* Policy: resoving bug reports (Rob)<br />
* 2.1M1 release planning (Mik)<br />
<br />
Minutes:<br />
...<br />
----<br />
<br />
=== Past Meetings ===<br />
<br />
==== Tuesday, August 14, 10-11am PT ====<br />
<br />
Agenda: <br />
* Summer of Code student status reports (Balazs, Jevgeni, Xiaoyang)<br />
* API to store arbitrary attributes in the AbstractTask: {{bug|199818}}, {{bug|199817}} (Eugene)<br />
* Vacation catchup (Mik & Rob)<br />
* 2.1M1 release planning (Mik)<br />
<br />
Minutes:<br />
...<br />
<br />
==== Tuesday, July 31, 10-11am PT ====<br />
<br />
Agenda: <br />
* Summer of Code student status reports (Balazs, Jevgeni, Xiaoyang)<br />
* August 7 meeting CANCELLED (most committers offline)<br />
<br />
==== Tuesday, July 24, 10-11am PT ====<br />
<br />
Agenda: <br />
* Summer of Code student status reports (Balazs, Jevgeni, Xiaoyang)<br />
* 3.0 planning (Mik)<br />
<br />
Minutes:<br />
* Explore participation in Eclips.org Bug Day<br />
* Add 'helpwanted' query to community page<br />
* Mik offline: July 30 - August 10<br />
* Rob offline: August 3 - 8<br />
* Steffen offline: August 7 - 14<br />
----<br />
<br />
==== Tuesday, July 17, 10-11am PT ====<br />
<br />
Agenda: <br />
* Summer of Code student status reports (Balazs, Jevgeni, Xiaoyang)<br />
* XPlanner status (Helen)<br />
* vserver admin status report (Rob)<br />
* dev builds are behind bug reports (Eugene)<br />
* grouping in the task list [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175318 bug 175318] (Eugene)<br />
* refactor abstract task editor to not use ScrolledForm [https://bugs.eclipse.org/bugs/show_bug.cgi?id=195326 bug 195326] (Eugene)<br />
* <s>Duplicate detector for jira [https://bugs.eclipse.org/bugs/show_bug.cgi?id=195079 bug 195079]</s>(Rob)<br />
* Bug triage and clean-up (Mik)<br />
* 3.0 planning (Mik)<br />
<br />
Minutes:<br />
* ...<br />
<br />
<br />
==== Tuesday, July 10, 10-11am PT ====<br />
<br />
Agenda:<br />
* 3.0 Objectives (Mik)<br />
* <s>"Additional Settings" section in Repository settings [https://bugs.eclipse.org/bugs/show_bug.cgi?id=195058 195058] (Eugene)</s><br />
* Pending Patches (Steffen)<br />
<br />
Minutes:<br />
* Steffen to create new bug to address revealing bugs with pending patches in the Task List UI<br />
<br />
==== Tuesday, July 4, 10-11am PT ====<br />
<br />
Agenda:<br />
* Summer of code update (students)<br />
* 2.0 decompression (Mik)<br />
* Update site split (Mik)<br />
<br />
Minutes:<br />
* Tools for checking for binary and source compatibility with older releases: [http://clirr.sourceforge.net/ Clirr], [http://javadiff.sourceforge.net/ JDiff]<br />
* Automatic adding "extras" update site entry and follow up on "sites to visit" bug in PDE<br />
<br />
==== Tuesday, June 26, 10-11am PT ====<br />
<br />
* Summer of code update (students)<br />
* 2.0 endgame (Mik)<br />
* Feature and update site changes, EPP packaging (Mik)<br />
* Continuous build (Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194258 194258] [api] Stream multi task data retrieval straight to storage bypassing in memory cache (Eugene)<br />
* Contribution for committers (Eugene)<br />
<br />
Minutes:<br />
<br />
==== Tuesday, June 19, 10-11am PT ====<br />
<br />
* Summer of code update (students)<br />
* Continuous build (Steffen)<br />
<br />
Future:<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* vserver admin status report<br />
----<br />
<br />
==== Tuesday, June 12, 10-11am PT ====<br />
<br />
* Project Rename Status (Mik)<br />
* Summer of code update (students)<br />
* 2.0 RC1 release status (Mik)<br />
** Release of JIRA connector?<br />
* Error handling design (Mik, Rob, Steffen)<br />
* Fixes for the synchronization API ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=191575 #191575])<br />
* Notification of API changes (Steffen)<br />
<br />
Actions:<br />
* Mik to investigate options for disabling old mylar plugins (required for tonight's dev build)<br />
* Eugene to take quick pass at synchronization api changes tonight [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=191575 bug#191575]]<br />
----<br />
<br />
<br />
<br />
==== Tuesday, June 5, 10-11am PT ====<br />
<br />
* Google Summer of Code kick-off (Balazs, Jevgeni, Xiaoyang)<br />
* vserver admin practices (Rob, Steffen)<br />
* 2.0 end game planning<br />
** Committers 2.0 plan update<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
<i>Stale items</i><br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Actions:<br />
* Rob to administer vserver (corrdinate with Steffen)<br />
** Contact Denis regarding updates<br />
** Investigate backup options<br />
<br />
==== Tuesday, May 29, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Task vs. TaskData; properties vs. class hierarchy (Eugene)<br />
** Full vs. light synchronization (Eugene)<br />
<i>Stale items</i><br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* (Eugene) Proposed eliminating Task hierarchy and replace with property based access<br />
** Suggests merging Task and AbstractRepositoryTask<br />
** Willing to add property support to ITask for 2.1 if requested by integrators.<br />
* (Steffen) The property-based vs. sub-classing discussing is important and we need to consider this for 3.0 again. <br />
* (Rob) raised TaskData migration and committers agree that migraion of existing offline data not practical<br />
<br />
Actions:<br />
* (Mik) introduce class factories and remove custom task externalizers<br />
* replace AbstractQueryHit by Tasks<br />
* allow connectors to submit Task or TaskData objects as hits<br />
* convert offline storage from Java Serialization to XML<br />
* construct attribute editors through factory, do not store repository configuration in offline storage<br />
* apply pending rename changes from porting guide<br />
* refactor attachment API <br />
<br />
<br />
<br />
==== Tuesday, May 22, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* Top voted bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169123 169123]: Updated bug does not preserve values of custom fields in Jira (Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Minutes:<br />
* Task workflow and special query support likely getting bumped<br />
* Rob: related bug#185805 (timestamp bug) and bug#186939 (blocked jobs)<br />
* Steffen: httpclient message.shutdown() can be used to force shutdown of network IO<br />
<br />
Actions:<br />
* Rob and Steffen:<br />
**to start offline refactoring.<br />
**included refactoring of local tasks to AbstractRepositoryTask (P1)<br />
**For RC0, add progress monitor to all api methods that involve IO to easy future implementation.<br />
* Steffen to open new bug for alternate containment representations (outline, task editor can be used to reveal) duplicates for bugzilla could use this<br />
* Mik to make new bug for Open Resource bug related to Task Working sets (defer Eugen's multiple tasklist views patch since will require additional view memento facility?) <br />
* Rob: Will investigate breaking out past activity from scheduled mode (after higher priority api changes).<br />
* For next call: Committers should review their P1 and P2 tasks and form a realistic list for 2.0<br />
<br />
==== Tuesday, May 15, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Decisions made regarding offline TaskData handling and presentation merged with wiki ([[Mylar Offline Refactoring]]).<br />
<br />
==== Tuesday, May 8, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
** Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Additive improvements deferred in favor of API changes.<br />
Main API changes (P2):<br />
* Local task become repository tasks<br />
* Hits become Tasks (but retain UI representation)<br />
* Offline storage improvements ([[Mylar Offline Refactoring]])<br />
* Tasklist externalization<br />
* AbstractRepositoryTaskEditor (make protected methods private)<br />
* Multiple Task Downloads (synch api changes)<br />
* Context listeners api (Mik)<br />
* Extract repository configuration<br />
<br />
<br />
==== Tuesday, May 1, 10-11am PT ====<br />
<br />
* Eclipse Forum Europe report (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Monitor update (Meghan)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
* Post action items/summary/minutes after each meeting (Mik?)<br />
<br />
Actions:<br />
* Eugene<br />
** send screenshot example of strikethrough looking like row lines<br />
* Mik<br />
** consider moving activation to task icon<br />
** working sets in tasklist needs priority since we need to put miles on it before release<br />
* Rob<br />
** persistence api should be finalized so that we can drop in alternate back ends<br />
<br />
==== Tuesday, April 24, 10-11am PT ====<br />
<br />
* Post action items/summary/minutes after each meeting<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* Greg Wilson gave brief overview of planned work for SoC project<br />
* Discussed options for implementing offline storage for task data<br />
* Discussed use cases for RSS support in the Task List<br />
* Discussed tagging and working sets support in the Task List<br />
<br />
Actions:<br />
<br />
* Does it make sense to keep task data separate from the task list?<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165880 165880: Listeners API should allow to pass multiple events in one call] Potential source of refresh issues (Eugene)<br />
<br />
==== Tuesday, April 17, 10-11am PT ====<br />
<br />
* Google Summer of Code planning (Mik)<br />
* ROME depency accepted (Eugene, Mik)<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
** Contributing custom models to task list and task repositories views. per-milestone/version grouping, or grouping query results by certain attributes (Eugene)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API updates (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* Post action items/summary after each meeting<br />
<br />
==== Tuesday, April 10, 10-11am PT ====<br />
<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API changes (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=179873 179873: Completed status not correct for JIRA tasks]<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
==== Tuesday, April 3, 10-11am PT ====<br />
<br />
* Mylar 2.0M2 release wrap-up, 2.0M3 planning (Mik)<br />
* Offline storage strategy design discussion(Rob, Steffen)<br />
<br />
==== Tuesday, March 27, 10-11am PT ====<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
<br />
* Mylar 2.0M2 status<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176513 176513] [api] Multiple task data request (Rob)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 160389] [api] Serialization / loss of data etc (Rob)<br />
* JIRA statuses: resolved vs. closed<br />
<br />
==== Tuesday, March 20, 10-11am PT ====<br />
<br />
* [http://wiki.eclipse.org/index.php/Mylar_GSoC_2007 Goolge Summer of Code ideas] (Mik)<br />
* Eclipse 3.3M6 status (Mik)<br />
* JIRA network utilization ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=175407 175407])<br />
* JIRA test server<br />
* usage reporting (Meghan)<br />
<br />
==== Tuesday, March 13, 10-11am PT ====<br />
<br />
Agenda:<br />
* EclipseCon decompression (Mik)<br />
* JIRA test server (Steffen)<br />
* 2.0M2 planning<br />
* AttributeFactoryUI/RepositoryConfiguration (Rob, Steffen)<br />
<br />
==== Tuesday, February 27, 10-11am PT ====<br />
<br />
Agenda:<br />
* '-' issue - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=166174 bug 166174]<br />
* EclipseCon planning (Mik)<br />
** 3.2 dev build<br />
** Stickers/Buttons/T-shirts<br />
** Poster<br />
* In-place context view (Mik, Eugene)<br />
* GSoC 2007 project (Steffen)<br />
<br />
Actions:<br />
* Find Mylar film glasses (Steffen)<br />
* Find out if there is any space left for poster presentations (Rob)<br />
* At EclipseCon ask EMF folks about using EMF for repository mappings (Mik & Rob)<br />
<br />
==== Tuesday, February 20, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* 2.0M1 release review (Mik)<br />
* Id vs handle vs key (Mik)<br />
* How to make Query creation more obvious for new users (Eugene)<br />
* Showing Task ID/Keys in UI (task list and task dialogs, editor tabs and headers, task history dropdown, change sets) (Eugene)<br />
* JIRA issues (Eugene, Steffen)<br />
<br />
Actions:<br />
* File form header bug<br />
* Create method: TaskList.getTask(String connectorKind, String taskUrl)<br />
* Create AbstractRepositoryTask.getKey()<br />
<br />
==== Tuesday, February 13, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* IP submission follow-ups for Lucene 2.0, Axis2 (Mik)<br />
* Major connector externalizer and task handle usage refactoring (Mik)<br />
* JIRA issues<br />
* Make Steffen JIRA committer<br />
* Discuss refactoring of RepositoryTaskAttributes (bug 150680?) (Steffen)<br />
** Separate UI representation from attribute?<br />
** How to link attributes to repository configuration?<br />
<br />
==== Tuesday, February 6, 10-11am PT ====<br />
<br />
Agenda<br />
* Finalizing of Mylar 2.0 plan (Mik)<br />
* Status of IP submissions (Mik)<br />
* Orbit dependencies<br />
* Status of JIRA<br />
* Issues with handles (Eugene)<br />
* Issues with event notification api (Rob)<br />
<br />
==== Tuesday, January 30, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Moving to Eclipse 3.3M5 builds (Mik)<br />
* Final IP and contribution submissions for Europa (Mik)<br />
* Status Jira Core Services and library dependencies (Steffen)<br />
<br />
==== Tuesday, January 23, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Implementation strategy for<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=171081 171081]: Autodetect JIRA repository for Open Corresponding Task (Eugene)<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=159135 159135]: Automatic resolution of links between projects and issue repositories (Eugene)<br />
* Additional contributions to be made by the Jan. 31st Europa cutoff (Mik)<br />
Actions<br />
* Consider Lucene 2.0 IPZilla submission (Mik)<br />
<br />
==== Tuesday, January 16, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning<br />
* Tomcat and server setup for mylar.eclipse.org<br />
* TaskId vs TaskHandle (numerous issues with JIRA connector) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170587 bug 170587]<br />
* Models and their application to the tasklist (Rob, Eugene) ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147084 147084: merge Task List and Task Activity views])<br />
** "[use] models and provide model that would show unread/changed/conflicting tasks" ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=170606 170606: Add action to Task List to filter out read requests])<br />
** 153573: add support for nesting top level task list elements, e.g. via incorporating working sets<br />
* Task web browser<br />
Actions:<br />
* Add milestone buckets 2.0M1 through M3 (Mik)<br />
* Gets JIRA enterprise license key for test server (Mik)<br />
* Ask about server backup policy (2.6 Gigs used), disk space for usage data (Mik)<br />
* Consider downgrading Tomcat to 5.5 (Meghan)<br />
* Write up Mylar monitor data collection project (Meghan)<br />
* Plans hyperlink detection improvements and bugs (Rob)<br />
**170679: [api] improve hyperlink detection api<br />
**170681: [api] allow connectors to contribute alternate content providers (models) to tasklist<br />
**170685: [api] allow connectors to contribute filters to tasklist<br />
<br />
==== Tuesday, Januray 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylar 2.0 milestone and Europa planning.<br />
* Synchronization, progress indication, and cancellation of repository task operations ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168257 168257], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=150682 150682], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154258 154258], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 143011])<br />
* Mylar error handling ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168049 168049], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168672 168672], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165383 165383])<br />
* Task activity timing improvement ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147537 147537])<br />
* JIRA issues (auth problem and integrating JIRA client)<br />
Actions:<br />
* Write up error policy (Steffen)<br />
* Plan synchronization related bugs (Rob)<br />
* Find platform release dates (Mik)<br />
* Define scope of project on planning page (Mik)<br />
* Add dummy query on codehouse project (Mik)<br />
<br />
==== Tuesday, December 19, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* 1.0.1 priorities (Mik) <br />
* Slap Eugene for discrediting Mylar in blogs and Mik for not blogging<br />
* Layout of search/query page<br />
<br />
==== Tuesday, December 12, 10-10:30am PT ====<br />
* Mylar 1.0 celebration and retrospective.<br />
* Brock Janiczak's JIRA core services contribution (Eugene, Mik?).<br />
* Discovery update sites (Eugene, Mik).<br />
* Version numbers (Mik).<br />
<br />
==== Tuesday, December 5, 10-10:30am PT ====<br />
* Remaining priorities for 1.0 (Mik)<br />
* API status (Mik)<br />
** Externalizers ITaskListExternalize<br />
** Listeners API, primarily ITaskListChangeListener<br />
** Adapting to ITask and broken selection of the task respositories<br />
* Proxy settings status (Rob)<br />
* Subclipse integration and Team API (Eugene)<br />
<br />
<br />
==== Tuesday, November 21, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Remaining 1.0RC1 items (Mik)<br />
** Issues with tack context (multiple folders, unfiltering issues, etc)<br />
** Issues with new local task UI (focus, inline vs. editor)<br />
** Moving task drop down and pause button out of Task List UI?<br />
* Bugzilla and repository infrastructure status (Rob)<br />
* Trac status (Steffen)<br />
* Web connector status (Mik)<br />
* JIRA connnector status (Mik & Eugene)<br />
Actions<br />
* Mik emails newsgroup/mylar-dev about task list toolbar changes<br />
* Mik fixes classpath of context.core xmlrpc-use<br />
* Visible editor always unfiltered<br />
* Eugene files bug on editor color problem<br />
* Steffen files bug People section with JIRA<br />
<br />
==== Tuesday, November 14, 10-11am PT ====<br />
<br />
Agenda<br />
* Mylar 1.0 priorities.<br />
* Pause button UI (Mik?)<br />
Actions<br />
* Need people section for Trac<br />
* Discuss removing commit context button on newsgroup<br />
* Allow proxy settings to be specified per-repository<br />
<br />
==== Tuesday, October 31, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Authentication infrastructure and connectors (Rob)<br />
* Offline support for JIRA (Mik)<br />
* Pause button UI (Mik)<br />
<br />
<br />
==== Tuesday, October 24, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda<br />
* 0.8 post-mortem (Mik)<br />
* Storage of offline task data (See [[Mylar Task List]]) (Rob)<br />
* JIRA priorities (Mik)<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* [http://dev.eclipse.org/mhonarc/lists/mylar-dev/msg00706.html Alternative integration] with remote repositories (Eugene)<br />
<br />
Actions<br />
* Investigate Lucene as store for offline task data (Rob)<br />
* Investigate showing working sets as top-level nodes in Task List (Mik)<br />
<br />
==== Tuesday, October 17, 10-11am PT ====<br />
<br />
Agenda<br />
* 0.8 release planning<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Rich editor for Trac (Steffen?)<br />
* Repository task data (Rob)<br />
** Offline persistence: object serialization (current), xml, database [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 bug 160389]<br />
** Lazy loading [https://bugs.eclipse.org/bugs/show_bug.cgi?id=157257 bug 157257]<br />
* Issues with Task monitoring and filtering for projects with more then one source folder<br />
* Jira integration planning<br />
* User guide and improving the docs<br />
<br />
Actions<br />
* Need "Add to Task List" action on query hits<br />
* Consider merging the above action with dialog for "Add Existing Task..."<br />
* Need to consider pre-fetching task data for query hits<br />
<br />
==== Tuesday, September 26 2006, 10-11am PT ====<br />
* 0.7 release planning<br />
* Project and repository association (Rob)<br />
* 1.0 planning (Mik)<br />
<br />
==== Wednesday, August 23 2006, 10-11am PT ====<br />
* Planning for 0.6.2<br />
* Generic web Repository Connector integration (Eugene)<br />
* Trac Connector rich editor (Steffen)<br />
* AbstractRepositoryConnector split into core and UI<br />
* Planning for 0.7 and 1.0<br />
* Zest website integration and release cycles<br />
<br />
==== Wednesday, August 2 2006, 10-11am PT ====<br />
Agenda<br />
* 0.6.1 post-mortem<br />
* 0.6.2 and 1.0 planning<br />
* Summer of Code status<br />
** Trac Connector (Steffen)<br />
** Bugzilla enhancements (Jeff)<br />
** JIRA<br />
* Design discussion on splitting AbstractRepositoryConnector into core/ui<br />
* Sandbox release for web connector (Eugene)<br />
Vacations<br />
* Rob: 3rd - 8th<br />
* Mik: 8th - 17th<br />
Actions<br />
* Consumers of APIs update Javadocs as they use them, a la wiki <br />
* Decide on conference call time and interval next meeting<br />
* Investigate Rome dependency for Sandbox (Mik)<br />
<br />
==== Thursday, July 6 2006, 10am PT ====<br />
* wrap up discussion of 0.6 release<br />
* Trac integration status (Steffen)<br />
* enhancing Bugzilla connector status (Jeff)<br />
* Connector naming conventions<br />
* tasks API discussion. String-based task id, separate task id, url and repository url, (issues 146396, 149624, 149509), other refactoring of tasks, hits, query and repository classes<br />
* UI for repository settings<br />
* prioritizing for 0.7 and beyond<br />
* planning and use of Bugzilla priorities<br />
<br />
==== Tuesday, June 13 2006, 10am PT ====<br />
* Schedule a regular meeting time and interval<br />
* Google SoC: Trac integration (Steffen)<br />
* Google Soc: enhancing Bugzilla connector (Jeff)<br />
* Repository connector API discussion (Mik)<br />
* Prioritize tasks for 0.6 (Mik)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=43084Mylyn/Porting Guide2007-07-18T03:04:16Z<p>Steffen.pingel.eclipse.org: /* Pending Changes for Mylyn 3.0 */</p>
<hr />
<div>[[Category:Mylyn]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from 1.0 to 2.0 =<br />
<br />
See the <b>[[Mylyn Porting Guide 2.0]]</b><br />
<br />
= Porting from 2.0 to 3.0 =<br />
<br />
There is currently no need to port Mylyn from the 2.0 APIs since current Mylyn releases are backwards compatible. Throughout the 2.x release cycle we will be using this wiki to gather changes and suggestions for improving the APIs for 3.0.<br />
<br />
== Tasks API == <br />
<br />
* <code>AbstractRepositoryConnector</code><br />
** <code>isRepositoryConfigurationStale(TaskRepository)</code> has been added<br />
<br />
* <code>AbstractRenderingEngine</code> has been added for converting Wiki syntax to HTML<br />
<br />
* <code>AbstractRepositoryTaskEditor</code> has been extended to provide HTML preview capabilities for repositories that support Wiki syntax in ticket descriptions and comments<br />
** <code>addSelectableControl()</code> has been added<br />
** <code>createReplyHyperlink()</code> is now protected (was private)<br />
** <code>DescriptionListener</code> is now protected (was private)<br />
** <code>getParentEditor()</code> has been added<br />
** <code>getRenderingEngine()</code> has been added<br />
** <code>removeSelectableControl()</code> has been added<br />
<br />
== Pending Changes for Mylyn 3.0 == <br />
<br />
* Rename <code>IMylarMonitorLifecycleListener</code> to <code>IMonitorLifecycleListener</code><br />
* Rename <code>MockRepositoryTask</code> to <code>MockTask</code></div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=42405Mylyn/Meetings2007-07-10T15:48:36Z<p>Steffen.pingel.eclipse.org: /* Tuesday, July 10, 10-11am PT */</p>
<hr />
<div>[[Category:Mylyn]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, July 10, 10-11am PT ====<br />
<br />
Agenda:<br />
* 3.0 Objectives (Mik)<br />
* vserver admin status report (Rob)<br />
* "Additional Settings" section in Repository settings [https://bugs.eclipse.org/bugs/show_bug.cgi?id=195058 195058] (Eugene)<br />
* Pending Patches (Steffen)<br />
<br />
Minutes:<br />
* ...<br />
<br />
----<br />
<br />
=== Past Meetings ===<br />
<br />
==== Tuesday, July 4, 10-11am PT ====<br />
<br />
Agenda:<br />
* Summer of code update (students)<br />
* 2.0 decompression (Mik)<br />
* Update site split (Mik)<br />
<br />
Minutes:<br />
* Tools for checking for binary and source compatibility with older releases: [http://clirr.sourceforge.net/ Clirr], [http://javadiff.sourceforge.net/ JDiff]<br />
* Automatic adding "extras" update site entry and follow up on "sites to visit" bug in PDE<br />
<br />
==== Tuesday, June 26, 10-11am PT ====<br />
<br />
* Summer of code update (students)<br />
* 2.0 endgame (Mik)<br />
* Feature and update site changes, EPP packaging (Mik)<br />
* Continuous build (Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194258 194258] [api] Stream multi task data retrieval straight to storage bypassing in memory cache (Eugene)<br />
* Contribution for committers (Eugene)<br />
<br />
Minutes:<br />
<br />
==== Tuesday, June 19, 10-11am PT ====<br />
<br />
* Summer of code update (students)<br />
* Continuous build (Steffen)<br />
<br />
Future:<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* vserver admin status report<br />
----<br />
<br />
==== Tuesday, June 12, 10-11am PT ====<br />
<br />
* Project Rename Status (Mik)<br />
* Summer of code update (students)<br />
* 2.0 RC1 release status (Mik)<br />
** Release of JIRA connector?<br />
* Error handling design (Mik, Rob, Steffen)<br />
* Fixes for the synchronization API ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=191575 #191575])<br />
* Notification of API changes (Steffen)<br />
<br />
Actions:<br />
* Mik to investigate options for disabling old mylar plugins (required for tonight's dev build)<br />
* Eugene to take quick pass at synchronization api changes tonight [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=191575 bug#191575]]<br />
----<br />
<br />
<br />
<br />
==== Tuesday, June 5, 10-11am PT ====<br />
<br />
* Google Summer of Code kick-off (Balazs, Jevgeni, Xiaoyang)<br />
* vserver admin practices (Rob, Steffen)<br />
* 2.0 end game planning<br />
** Committers 2.0 plan update<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
<i>Stale items</i><br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Actions:<br />
* Rob to administer vserver (corrdinate with Steffen)<br />
** Contact Denis regarding updates<br />
** Investigate backup options<br />
<br />
==== Tuesday, May 29, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Task vs. TaskData; properties vs. class hierarchy (Eugene)<br />
** Full vs. light synchronization (Eugene)<br />
<i>Stale items</i><br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* (Eugene) Proposed eliminating Task hierarchy and replace with property based access<br />
** Suggests merging Task and AbstractRepositoryTask<br />
** Willing to add property support to ITask for 2.1 if requested by integrators.<br />
* (Steffen) The property-based vs. sub-classing discussing is important and we need to consider this for 3.0 again. <br />
* (Rob) raised TaskData migration and committers agree that migraion of existing offline data not practical<br />
<br />
Actions:<br />
* (Mik) introduce class factories and remove custom task externalizers<br />
* replace AbstractQueryHit by Tasks<br />
* allow connectors to submit Task or TaskData objects as hits<br />
* convert offline storage from Java Serialization to XML<br />
* construct attribute editors through factory, do not store repository configuration in offline storage<br />
* apply pending rename changes from porting guide<br />
* refactor attachment API <br />
<br />
<br />
<br />
==== Tuesday, May 22, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* Top voted bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169123 169123]: Updated bug does not preserve values of custom fields in Jira (Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Minutes:<br />
* Task workflow and special query support likely getting bumped<br />
* Rob: related bug#185805 (timestamp bug) and bug#186939 (blocked jobs)<br />
* Steffen: httpclient message.shutdown() can be used to force shutdown of network IO<br />
<br />
Actions:<br />
* Rob and Steffen:<br />
**to start offline refactoring.<br />
**included refactoring of local tasks to AbstractRepositoryTask (P1)<br />
**For RC0, add progress monitor to all api methods that involve IO to easy future implementation.<br />
* Steffen to open new bug for alternate containment representations (outline, task editor can be used to reveal) duplicates for bugzilla could use this<br />
* Mik to make new bug for Open Resource bug related to Task Working sets (defer Eugen's multiple tasklist views patch since will require additional view memento facility?) <br />
* Rob: Will investigate breaking out past activity from scheduled mode (after higher priority api changes).<br />
* For next call: Committers should review their P1 and P2 tasks and form a realistic list for 2.0<br />
<br />
==== Tuesday, May 15, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Decisions made regarding offline TaskData handling and presentation merged with wiki ([[Mylar Offline Refactoring]]).<br />
<br />
==== Tuesday, May 8, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
** Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Additive improvements deferred in favor of API changes.<br />
Main API changes (P2):<br />
* Local task become repository tasks<br />
* Hits become Tasks (but retain UI representation)<br />
* Offline storage improvements ([[Mylar Offline Refactoring]])<br />
* Tasklist externalization<br />
* AbstractRepositoryTaskEditor (make protected methods private)<br />
* Multiple Task Downloads (synch api changes)<br />
* Context listeners api (Mik)<br />
* Extract repository configuration<br />
<br />
<br />
==== Tuesday, May 1, 10-11am PT ====<br />
<br />
* Eclipse Forum Europe report (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Monitor update (Meghan)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
* Post action items/summary/minutes after each meeting (Mik?)<br />
<br />
Actions:<br />
* Eugene<br />
** send screenshot example of strikethrough looking like row lines<br />
* Mik<br />
** consider moving activation to task icon<br />
** working sets in tasklist needs priority since we need to put miles on it before release<br />
* Rob<br />
** persistence api should be finalized so that we can drop in alternate back ends<br />
<br />
==== Tuesday, April 24, 10-11am PT ====<br />
<br />
* Post action items/summary/minutes after each meeting<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* Greg Wilson gave brief overview of planned work for SoC project<br />
* Discussed options for implementing offline storage for task data<br />
* Discussed use cases for RSS support in the Task List<br />
* Discussed tagging and working sets support in the Task List<br />
<br />
Actions:<br />
<br />
* Does it make sense to keep task data separate from the task list?<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165880 165880: Listeners API should allow to pass multiple events in one call] Potential source of refresh issues (Eugene)<br />
<br />
==== Tuesday, April 17, 10-11am PT ====<br />
<br />
* Google Summer of Code planning (Mik)<br />
* ROME depency accepted (Eugene, Mik)<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
** Contributing custom models to task list and task repositories views. per-milestone/version grouping, or grouping query results by certain attributes (Eugene)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API updates (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* Post action items/summary after each meeting<br />
<br />
==== Tuesday, April 10, 10-11am PT ====<br />
<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API changes (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=179873 179873: Completed status not correct for JIRA tasks]<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
==== Tuesday, April 3, 10-11am PT ====<br />
<br />
* Mylar 2.0M2 release wrap-up, 2.0M3 planning (Mik)<br />
* Offline storage strategy design discussion(Rob, Steffen)<br />
<br />
==== Tuesday, March 27, 10-11am PT ====<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
<br />
* Mylar 2.0M2 status<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176513 176513] [api] Multiple task data request (Rob)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 160389] [api] Serialization / loss of data etc (Rob)<br />
* JIRA statuses: resolved vs. closed<br />
<br />
==== Tuesday, March 20, 10-11am PT ====<br />
<br />
* [http://wiki.eclipse.org/index.php/Mylar_GSoC_2007 Goolge Summer of Code ideas] (Mik)<br />
* Eclipse 3.3M6 status (Mik)<br />
* JIRA network utilization ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=175407 175407])<br />
* JIRA test server<br />
* usage reporting (Meghan)<br />
<br />
==== Tuesday, March 13, 10-11am PT ====<br />
<br />
Agenda:<br />
* EclipseCon decompression (Mik)<br />
* JIRA test server (Steffen)<br />
* 2.0M2 planning<br />
* AttributeFactoryUI/RepositoryConfiguration (Rob, Steffen)<br />
<br />
==== Tuesday, February 27, 10-11am PT ====<br />
<br />
Agenda:<br />
* '-' issue - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=166174 bug 166174]<br />
* EclipseCon planning (Mik)<br />
** 3.2 dev build<br />
** Stickers/Buttons/T-shirts<br />
** Poster<br />
* In-place context view (Mik, Eugene)<br />
* GSoC 2007 project (Steffen)<br />
<br />
Actions:<br />
* Find Mylar film glasses (Steffen)<br />
* Find out if there is any space left for poster presentations (Rob)<br />
* At EclipseCon ask EMF folks about using EMF for repository mappings (Mik & Rob)<br />
<br />
==== Tuesday, February 20, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* 2.0M1 release review (Mik)<br />
* Id vs handle vs key (Mik)<br />
* How to make Query creation more obvious for new users (Eugene)<br />
* Showing Task ID/Keys in UI (task list and task dialogs, editor tabs and headers, task history dropdown, change sets) (Eugene)<br />
* JIRA issues (Eugene, Steffen)<br />
<br />
Actions:<br />
* File form header bug<br />
* Create method: TaskList.getTask(String connectorKind, String taskUrl)<br />
* Create AbstractRepositoryTask.getKey()<br />
<br />
==== Tuesday, February 13, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* IP submission follow-ups for Lucene 2.0, Axis2 (Mik)<br />
* Major connector externalizer and task handle usage refactoring (Mik)<br />
* JIRA issues<br />
* Make Steffen JIRA committer<br />
* Discuss refactoring of RepositoryTaskAttributes (bug 150680?) (Steffen)<br />
** Separate UI representation from attribute?<br />
** How to link attributes to repository configuration?<br />
<br />
==== Tuesday, February 6, 10-11am PT ====<br />
<br />
Agenda<br />
* Finalizing of Mylar 2.0 plan (Mik)<br />
* Status of IP submissions (Mik)<br />
* Orbit dependencies<br />
* Status of JIRA<br />
* Issues with handles (Eugene)<br />
* Issues with event notification api (Rob)<br />
<br />
==== Tuesday, January 30, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Moving to Eclipse 3.3M5 builds (Mik)<br />
* Final IP and contribution submissions for Europa (Mik)<br />
* Status Jira Core Services and library dependencies (Steffen)<br />
<br />
==== Tuesday, January 23, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Implementation strategy for<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=171081 171081]: Autodetect JIRA repository for Open Corresponding Task (Eugene)<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=159135 159135]: Automatic resolution of links between projects and issue repositories (Eugene)<br />
* Additional contributions to be made by the Jan. 31st Europa cutoff (Mik)<br />
Actions<br />
* Consider Lucene 2.0 IPZilla submission (Mik)<br />
<br />
==== Tuesday, January 16, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning<br />
* Tomcat and server setup for mylar.eclipse.org<br />
* TaskId vs TaskHandle (numerous issues with JIRA connector) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170587 bug 170587]<br />
* Models and their application to the tasklist (Rob, Eugene) ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147084 147084: merge Task List and Task Activity views])<br />
** "[use] models and provide model that would show unread/changed/conflicting tasks" ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=170606 170606: Add action to Task List to filter out read requests])<br />
** 153573: add support for nesting top level task list elements, e.g. via incorporating working sets<br />
* Task web browser<br />
Actions:<br />
* Add milestone buckets 2.0M1 through M3 (Mik)<br />
* Gets JIRA enterprise license key for test server (Mik)<br />
* Ask about server backup policy (2.6 Gigs used), disk space for usage data (Mik)<br />
* Consider downgrading Tomcat to 5.5 (Meghan)<br />
* Write up Mylar monitor data collection project (Meghan)<br />
* Plans hyperlink detection improvements and bugs (Rob)<br />
**170679: [api] improve hyperlink detection api<br />
**170681: [api] allow connectors to contribute alternate content providers (models) to tasklist<br />
**170685: [api] allow connectors to contribute filters to tasklist<br />
<br />
==== Tuesday, Januray 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylar 2.0 milestone and Europa planning.<br />
* Synchronization, progress indication, and cancellation of repository task operations ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168257 168257], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=150682 150682], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154258 154258], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 143011])<br />
* Mylar error handling ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168049 168049], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168672 168672], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165383 165383])<br />
* Task activity timing improvement ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147537 147537])<br />
* JIRA issues (auth problem and integrating JIRA client)<br />
Actions:<br />
* Write up error policy (Steffen)<br />
* Plan synchronization related bugs (Rob)<br />
* Find platform release dates (Mik)<br />
* Define scope of project on planning page (Mik)<br />
* Add dummy query on codehouse project (Mik)<br />
<br />
==== Tuesday, December 19, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* 1.0.1 priorities (Mik) <br />
* Slap Eugene for discrediting Mylar in blogs and Mik for not blogging<br />
* Layout of search/query page<br />
<br />
==== Tuesday, December 12, 10-10:30am PT ====<br />
* Mylar 1.0 celebration and retrospective.<br />
* Brock Janiczak's JIRA core services contribution (Eugene, Mik?).<br />
* Discovery update sites (Eugene, Mik).<br />
* Version numbers (Mik).<br />
<br />
==== Tuesday, December 5, 10-10:30am PT ====<br />
* Remaining priorities for 1.0 (Mik)<br />
* API status (Mik)<br />
** Externalizers ITaskListExternalize<br />
** Listeners API, primarily ITaskListChangeListener<br />
** Adapting to ITask and broken selection of the task respositories<br />
* Proxy settings status (Rob)<br />
* Subclipse integration and Team API (Eugene)<br />
<br />
<br />
==== Tuesday, November 21, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Remaining 1.0RC1 items (Mik)<br />
** Issues with tack context (multiple folders, unfiltering issues, etc)<br />
** Issues with new local task UI (focus, inline vs. editor)<br />
** Moving task drop down and pause button out of Task List UI?<br />
* Bugzilla and repository infrastructure status (Rob)<br />
* Trac status (Steffen)<br />
* Web connector status (Mik)<br />
* JIRA connnector status (Mik & Eugene)<br />
Actions<br />
* Mik emails newsgroup/mylar-dev about task list toolbar changes<br />
* Mik fixes classpath of context.core xmlrpc-use<br />
* Visible editor always unfiltered<br />
* Eugene files bug on editor color problem<br />
* Steffen files bug People section with JIRA<br />
<br />
==== Tuesday, November 14, 10-11am PT ====<br />
<br />
Agenda<br />
* Mylar 1.0 priorities.<br />
* Pause button UI (Mik?)<br />
Actions<br />
* Need people section for Trac<br />
* Discuss removing commit context button on newsgroup<br />
* Allow proxy settings to be specified per-repository<br />
<br />
==== Tuesday, October 31, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Authentication infrastructure and connectors (Rob)<br />
* Offline support for JIRA (Mik)<br />
* Pause button UI (Mik)<br />
<br />
<br />
==== Tuesday, October 24, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda<br />
* 0.8 post-mortem (Mik)<br />
* Storage of offline task data (See [[Mylar Task List]]) (Rob)<br />
* JIRA priorities (Mik)<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* [http://dev.eclipse.org/mhonarc/lists/mylar-dev/msg00706.html Alternative integration] with remote repositories (Eugene)<br />
<br />
Actions<br />
* Investigate Lucene as store for offline task data (Rob)<br />
* Investigate showing working sets as top-level nodes in Task List (Mik)<br />
<br />
==== Tuesday, October 17, 10-11am PT ====<br />
<br />
Agenda<br />
* 0.8 release planning<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Rich editor for Trac (Steffen?)<br />
* Repository task data (Rob)<br />
** Offline persistence: object serialization (current), xml, database [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 bug 160389]<br />
** Lazy loading [https://bugs.eclipse.org/bugs/show_bug.cgi?id=157257 bug 157257]<br />
* Issues with Task monitoring and filtering for projects with more then one source folder<br />
* Jira integration planning<br />
* User guide and improving the docs<br />
<br />
Actions<br />
* Need "Add to Task List" action on query hits<br />
* Consider merging the above action with dialog for "Add Existing Task..."<br />
* Need to consider pre-fetching task data for query hits<br />
<br />
==== Tuesday, September 26 2006, 10-11am PT ====<br />
* 0.7 release planning<br />
* Project and repository association (Rob)<br />
* 1.0 planning (Mik)<br />
<br />
==== Wednesday, August 23 2006, 10-11am PT ====<br />
* Planning for 0.6.2<br />
* Generic web Repository Connector integration (Eugene)<br />
* Trac Connector rich editor (Steffen)<br />
* AbstractRepositoryConnector split into core and UI<br />
* Planning for 0.7 and 1.0<br />
* Zest website integration and release cycles<br />
<br />
==== Wednesday, August 2 2006, 10-11am PT ====<br />
Agenda<br />
* 0.6.1 post-mortem<br />
* 0.6.2 and 1.0 planning<br />
* Summer of Code status<br />
** Trac Connector (Steffen)<br />
** Bugzilla enhancements (Jeff)<br />
** JIRA<br />
* Design discussion on splitting AbstractRepositoryConnector into core/ui<br />
* Sandbox release for web connector (Eugene)<br />
Vacations<br />
* Rob: 3rd - 8th<br />
* Mik: 8th - 17th<br />
Actions<br />
* Consumers of APIs update Javadocs as they use them, a la wiki <br />
* Decide on conference call time and interval next meeting<br />
* Investigate Rome dependency for Sandbox (Mik)<br />
<br />
==== Thursday, July 6 2006, 10am PT ====<br />
* wrap up discussion of 0.6 release<br />
* Trac integration status (Steffen)<br />
* enhancing Bugzilla connector status (Jeff)<br />
* Connector naming conventions<br />
* tasks API discussion. String-based task id, separate task id, url and repository url, (issues 146396, 149624, 149509), other refactoring of tasks, hits, query and repository classes<br />
* UI for repository settings<br />
* prioritizing for 0.7 and beyond<br />
* planning and use of Bugzilla priorities<br />
<br />
==== Tuesday, June 13 2006, 10am PT ====<br />
* Schedule a regular meeting time and interval<br />
* Google SoC: Trac integration (Steffen)<br />
* Google Soc: enhancing Bugzilla connector (Jeff)<br />
* Repository connector API discussion (Mik)<br />
* Prioritize tasks for 0.6 (Mik)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=42347Mylyn/Meetings2007-07-10T04:05:48Z<p>Steffen.pingel.eclipse.org: </p>
<hr />
<div>[[Category:Mylyn]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, July 10, 10-11am PT ====<br />
<br />
Agenda:<br />
* 3.0 Objectives (Mik)<br />
* vserver admin status report (Rob)<br />
* "Additional Settings" section in Repository settings [https://bugs.eclipse.org/bugs/show_bug.cgi?id=195058 195058] (Eugene)<br />
* Pending Patches:<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=191114 #191114] provide HTML-based widget for rendering formatted wiki text in ticket description<br />
<br />
Minutes:<br />
* ...<br />
<br />
----<br />
<br />
=== Past Meetings ===<br />
<br />
==== Tuesday, July 4, 10-11am PT ====<br />
<br />
Agenda:<br />
* Summer of code update (students)<br />
* 2.0 decompression (Mik)<br />
* Update site split (Mik)<br />
<br />
Minutes:<br />
* Tools for checking for binary and source compatibility with older releases: [http://clirr.sourceforge.net/ Clirr], [http://javadiff.sourceforge.net/ JDiff]<br />
* Automatic adding "extras" update site entry and follow up on "sites to visit" bug in PDE<br />
<br />
==== Tuesday, June 26, 10-11am PT ====<br />
<br />
* Summer of code update (students)<br />
* 2.0 endgame (Mik)<br />
* Feature and update site changes, EPP packaging (Mik)<br />
* Continuous build (Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=194258 194258] [api] Stream multi task data retrieval straight to storage bypassing in memory cache (Eugene)<br />
* Contribution for committers (Eugene)<br />
<br />
Minutes:<br />
<br />
==== Tuesday, June 19, 10-11am PT ====<br />
<br />
* Summer of code update (students)<br />
* Continuous build (Steffen)<br />
<br />
Future:<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* vserver admin status report<br />
----<br />
<br />
==== Tuesday, June 12, 10-11am PT ====<br />
<br />
* Project Rename Status (Mik)<br />
* Summer of code update (students)<br />
* 2.0 RC1 release status (Mik)<br />
** Release of JIRA connector?<br />
* Error handling design (Mik, Rob, Steffen)<br />
* Fixes for the synchronization API ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=191575 #191575])<br />
* Notification of API changes (Steffen)<br />
<br />
Actions:<br />
* Mik to investigate options for disabling old mylar plugins (required for tonight's dev build)<br />
* Eugene to take quick pass at synchronization api changes tonight [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=191575 bug#191575]]<br />
----<br />
<br />
<br />
<br />
==== Tuesday, June 5, 10-11am PT ====<br />
<br />
* Google Summer of Code kick-off (Balazs, Jevgeni, Xiaoyang)<br />
* vserver admin practices (Rob, Steffen)<br />
* 2.0 end game planning<br />
** Committers 2.0 plan update<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
<i>Stale items</i><br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Actions:<br />
* Rob to administer vserver (corrdinate with Steffen)<br />
** Contact Denis regarding updates<br />
** Investigate backup options<br />
<br />
==== Tuesday, May 29, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Task vs. TaskData; properties vs. class hierarchy (Eugene)<br />
** Full vs. light synchronization (Eugene)<br />
<i>Stale items</i><br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* (Eugene) Proposed eliminating Task hierarchy and replace with property based access<br />
** Suggests merging Task and AbstractRepositoryTask<br />
** Willing to add property support to ITask for 2.1 if requested by integrators.<br />
* (Steffen) The property-based vs. sub-classing discussing is important and we need to consider this for 3.0 again. <br />
* (Rob) raised TaskData migration and committers agree that migraion of existing offline data not practical<br />
<br />
Actions:<br />
* (Mik) introduce class factories and remove custom task externalizers<br />
* replace AbstractQueryHit by Tasks<br />
* allow connectors to submit Task or TaskData objects as hits<br />
* convert offline storage from Java Serialization to XML<br />
* construct attribute editors through factory, do not store repository configuration in offline storage<br />
* apply pending rename changes from porting guide<br />
* refactor attachment API <br />
<br />
<br />
<br />
==== Tuesday, May 22, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* Top voted bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169123 169123]: Updated bug does not preserve values of custom fields in Jira (Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Minutes:<br />
* Task workflow and special query support likely getting bumped<br />
* Rob: related bug#185805 (timestamp bug) and bug#186939 (blocked jobs)<br />
* Steffen: httpclient message.shutdown() can be used to force shutdown of network IO<br />
<br />
Actions:<br />
* Rob and Steffen:<br />
**to start offline refactoring.<br />
**included refactoring of local tasks to AbstractRepositoryTask (P1)<br />
**For RC0, add progress monitor to all api methods that involve IO to easy future implementation.<br />
* Steffen to open new bug for alternate containment representations (outline, task editor can be used to reveal) duplicates for bugzilla could use this<br />
* Mik to make new bug for Open Resource bug related to Task Working sets (defer Eugen's multiple tasklist views patch since will require additional view memento facility?) <br />
* Rob: Will investigate breaking out past activity from scheduled mode (after higher priority api changes).<br />
* For next call: Committers should review their P1 and P2 tasks and form a realistic list for 2.0<br />
<br />
==== Tuesday, May 15, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Decisions made regarding offline TaskData handling and presentation merged with wiki ([[Mylar Offline Refactoring]]).<br />
<br />
==== Tuesday, May 8, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
** Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Additive improvements deferred in favor of API changes.<br />
Main API changes (P2):<br />
* Local task become repository tasks<br />
* Hits become Tasks (but retain UI representation)<br />
* Offline storage improvements ([[Mylar Offline Refactoring]])<br />
* Tasklist externalization<br />
* AbstractRepositoryTaskEditor (make protected methods private)<br />
* Multiple Task Downloads (synch api changes)<br />
* Context listeners api (Mik)<br />
* Extract repository configuration<br />
<br />
<br />
==== Tuesday, May 1, 10-11am PT ====<br />
<br />
* Eclipse Forum Europe report (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Monitor update (Meghan)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
* Post action items/summary/minutes after each meeting (Mik?)<br />
<br />
Actions:<br />
* Eugene<br />
** send screenshot example of strikethrough looking like row lines<br />
* Mik<br />
** consider moving activation to task icon<br />
** working sets in tasklist needs priority since we need to put miles on it before release<br />
* Rob<br />
** persistence api should be finalized so that we can drop in alternate back ends<br />
<br />
==== Tuesday, April 24, 10-11am PT ====<br />
<br />
* Post action items/summary/minutes after each meeting<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* Greg Wilson gave brief overview of planned work for SoC project<br />
* Discussed options for implementing offline storage for task data<br />
* Discussed use cases for RSS support in the Task List<br />
* Discussed tagging and working sets support in the Task List<br />
<br />
Actions:<br />
<br />
* Does it make sense to keep task data separate from the task list?<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165880 165880: Listeners API should allow to pass multiple events in one call] Potential source of refresh issues (Eugene)<br />
<br />
==== Tuesday, April 17, 10-11am PT ====<br />
<br />
* Google Summer of Code planning (Mik)<br />
* ROME depency accepted (Eugene, Mik)<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
** Contributing custom models to task list and task repositories views. per-milestone/version grouping, or grouping query results by certain attributes (Eugene)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API updates (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* Post action items/summary after each meeting<br />
<br />
==== Tuesday, April 10, 10-11am PT ====<br />
<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API changes (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=179873 179873: Completed status not correct for JIRA tasks]<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
==== Tuesday, April 3, 10-11am PT ====<br />
<br />
* Mylar 2.0M2 release wrap-up, 2.0M3 planning (Mik)<br />
* Offline storage strategy design discussion(Rob, Steffen)<br />
<br />
==== Tuesday, March 27, 10-11am PT ====<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
<br />
* Mylar 2.0M2 status<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176513 176513] [api] Multiple task data request (Rob)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 160389] [api] Serialization / loss of data etc (Rob)<br />
* JIRA statuses: resolved vs. closed<br />
<br />
==== Tuesday, March 20, 10-11am PT ====<br />
<br />
* [http://wiki.eclipse.org/index.php/Mylar_GSoC_2007 Goolge Summer of Code ideas] (Mik)<br />
* Eclipse 3.3M6 status (Mik)<br />
* JIRA network utilization ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=175407 175407])<br />
* JIRA test server<br />
* usage reporting (Meghan)<br />
<br />
==== Tuesday, March 13, 10-11am PT ====<br />
<br />
Agenda:<br />
* EclipseCon decompression (Mik)<br />
* JIRA test server (Steffen)<br />
* 2.0M2 planning<br />
* AttributeFactoryUI/RepositoryConfiguration (Rob, Steffen)<br />
<br />
==== Tuesday, February 27, 10-11am PT ====<br />
<br />
Agenda:<br />
* '-' issue - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=166174 bug 166174]<br />
* EclipseCon planning (Mik)<br />
** 3.2 dev build<br />
** Stickers/Buttons/T-shirts<br />
** Poster<br />
* In-place context view (Mik, Eugene)<br />
* GSoC 2007 project (Steffen)<br />
<br />
Actions:<br />
* Find Mylar film glasses (Steffen)<br />
* Find out if there is any space left for poster presentations (Rob)<br />
* At EclipseCon ask EMF folks about using EMF for repository mappings (Mik & Rob)<br />
<br />
==== Tuesday, February 20, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* 2.0M1 release review (Mik)<br />
* Id vs handle vs key (Mik)<br />
* How to make Query creation more obvious for new users (Eugene)<br />
* Showing Task ID/Keys in UI (task list and task dialogs, editor tabs and headers, task history dropdown, change sets) (Eugene)<br />
* JIRA issues (Eugene, Steffen)<br />
<br />
Actions:<br />
* File form header bug<br />
* Create method: TaskList.getTask(String connectorKind, String taskUrl)<br />
* Create AbstractRepositoryTask.getKey()<br />
<br />
==== Tuesday, February 13, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* IP submission follow-ups for Lucene 2.0, Axis2 (Mik)<br />
* Major connector externalizer and task handle usage refactoring (Mik)<br />
* JIRA issues<br />
* Make Steffen JIRA committer<br />
* Discuss refactoring of RepositoryTaskAttributes (bug 150680?) (Steffen)<br />
** Separate UI representation from attribute?<br />
** How to link attributes to repository configuration?<br />
<br />
==== Tuesday, February 6, 10-11am PT ====<br />
<br />
Agenda<br />
* Finalizing of Mylar 2.0 plan (Mik)<br />
* Status of IP submissions (Mik)<br />
* Orbit dependencies<br />
* Status of JIRA<br />
* Issues with handles (Eugene)<br />
* Issues with event notification api (Rob)<br />
<br />
==== Tuesday, January 30, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Moving to Eclipse 3.3M5 builds (Mik)<br />
* Final IP and contribution submissions for Europa (Mik)<br />
* Status Jira Core Services and library dependencies (Steffen)<br />
<br />
==== Tuesday, January 23, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Implementation strategy for<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=171081 171081]: Autodetect JIRA repository for Open Corresponding Task (Eugene)<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=159135 159135]: Automatic resolution of links between projects and issue repositories (Eugene)<br />
* Additional contributions to be made by the Jan. 31st Europa cutoff (Mik)<br />
Actions<br />
* Consider Lucene 2.0 IPZilla submission (Mik)<br />
<br />
==== Tuesday, January 16, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning<br />
* Tomcat and server setup for mylar.eclipse.org<br />
* TaskId vs TaskHandle (numerous issues with JIRA connector) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170587 bug 170587]<br />
* Models and their application to the tasklist (Rob, Eugene) ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147084 147084: merge Task List and Task Activity views])<br />
** "[use] models and provide model that would show unread/changed/conflicting tasks" ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=170606 170606: Add action to Task List to filter out read requests])<br />
** 153573: add support for nesting top level task list elements, e.g. via incorporating working sets<br />
* Task web browser<br />
Actions:<br />
* Add milestone buckets 2.0M1 through M3 (Mik)<br />
* Gets JIRA enterprise license key for test server (Mik)<br />
* Ask about server backup policy (2.6 Gigs used), disk space for usage data (Mik)<br />
* Consider downgrading Tomcat to 5.5 (Meghan)<br />
* Write up Mylar monitor data collection project (Meghan)<br />
* Plans hyperlink detection improvements and bugs (Rob)<br />
**170679: [api] improve hyperlink detection api<br />
**170681: [api] allow connectors to contribute alternate content providers (models) to tasklist<br />
**170685: [api] allow connectors to contribute filters to tasklist<br />
<br />
==== Tuesday, Januray 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylar 2.0 milestone and Europa planning.<br />
* Synchronization, progress indication, and cancellation of repository task operations ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168257 168257], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=150682 150682], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154258 154258], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 143011])<br />
* Mylar error handling ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168049 168049], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168672 168672], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165383 165383])<br />
* Task activity timing improvement ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147537 147537])<br />
* JIRA issues (auth problem and integrating JIRA client)<br />
Actions:<br />
* Write up error policy (Steffen)<br />
* Plan synchronization related bugs (Rob)<br />
* Find platform release dates (Mik)<br />
* Define scope of project on planning page (Mik)<br />
* Add dummy query on codehouse project (Mik)<br />
<br />
==== Tuesday, December 19, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* 1.0.1 priorities (Mik) <br />
* Slap Eugene for discrediting Mylar in blogs and Mik for not blogging<br />
* Layout of search/query page<br />
<br />
==== Tuesday, December 12, 10-10:30am PT ====<br />
* Mylar 1.0 celebration and retrospective.<br />
* Brock Janiczak's JIRA core services contribution (Eugene, Mik?).<br />
* Discovery update sites (Eugene, Mik).<br />
* Version numbers (Mik).<br />
<br />
==== Tuesday, December 5, 10-10:30am PT ====<br />
* Remaining priorities for 1.0 (Mik)<br />
* API status (Mik)<br />
** Externalizers ITaskListExternalize<br />
** Listeners API, primarily ITaskListChangeListener<br />
** Adapting to ITask and broken selection of the task respositories<br />
* Proxy settings status (Rob)<br />
* Subclipse integration and Team API (Eugene)<br />
<br />
<br />
==== Tuesday, November 21, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Remaining 1.0RC1 items (Mik)<br />
** Issues with tack context (multiple folders, unfiltering issues, etc)<br />
** Issues with new local task UI (focus, inline vs. editor)<br />
** Moving task drop down and pause button out of Task List UI?<br />
* Bugzilla and repository infrastructure status (Rob)<br />
* Trac status (Steffen)<br />
* Web connector status (Mik)<br />
* JIRA connnector status (Mik & Eugene)<br />
Actions<br />
* Mik emails newsgroup/mylar-dev about task list toolbar changes<br />
* Mik fixes classpath of context.core xmlrpc-use<br />
* Visible editor always unfiltered<br />
* Eugene files bug on editor color problem<br />
* Steffen files bug People section with JIRA<br />
<br />
==== Tuesday, November 14, 10-11am PT ====<br />
<br />
Agenda<br />
* Mylar 1.0 priorities.<br />
* Pause button UI (Mik?)<br />
Actions<br />
* Need people section for Trac<br />
* Discuss removing commit context button on newsgroup<br />
* Allow proxy settings to be specified per-repository<br />
<br />
==== Tuesday, October 31, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Authentication infrastructure and connectors (Rob)<br />
* Offline support for JIRA (Mik)<br />
* Pause button UI (Mik)<br />
<br />
<br />
==== Tuesday, October 24, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda<br />
* 0.8 post-mortem (Mik)<br />
* Storage of offline task data (See [[Mylar Task List]]) (Rob)<br />
* JIRA priorities (Mik)<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* [http://dev.eclipse.org/mhonarc/lists/mylar-dev/msg00706.html Alternative integration] with remote repositories (Eugene)<br />
<br />
Actions<br />
* Investigate Lucene as store for offline task data (Rob)<br />
* Investigate showing working sets as top-level nodes in Task List (Mik)<br />
<br />
==== Tuesday, October 17, 10-11am PT ====<br />
<br />
Agenda<br />
* 0.8 release planning<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Rich editor for Trac (Steffen?)<br />
* Repository task data (Rob)<br />
** Offline persistence: object serialization (current), xml, database [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 bug 160389]<br />
** Lazy loading [https://bugs.eclipse.org/bugs/show_bug.cgi?id=157257 bug 157257]<br />
* Issues with Task monitoring and filtering for projects with more then one source folder<br />
* Jira integration planning<br />
* User guide and improving the docs<br />
<br />
Actions<br />
* Need "Add to Task List" action on query hits<br />
* Consider merging the above action with dialog for "Add Existing Task..."<br />
* Need to consider pre-fetching task data for query hits<br />
<br />
==== Tuesday, September 26 2006, 10-11am PT ====<br />
* 0.7 release planning<br />
* Project and repository association (Rob)<br />
* 1.0 planning (Mik)<br />
<br />
==== Wednesday, August 23 2006, 10-11am PT ====<br />
* Planning for 0.6.2<br />
* Generic web Repository Connector integration (Eugene)<br />
* Trac Connector rich editor (Steffen)<br />
* AbstractRepositoryConnector split into core and UI<br />
* Planning for 0.7 and 1.0<br />
* Zest website integration and release cycles<br />
<br />
==== Wednesday, August 2 2006, 10-11am PT ====<br />
Agenda<br />
* 0.6.1 post-mortem<br />
* 0.6.2 and 1.0 planning<br />
* Summer of Code status<br />
** Trac Connector (Steffen)<br />
** Bugzilla enhancements (Jeff)<br />
** JIRA<br />
* Design discussion on splitting AbstractRepositoryConnector into core/ui<br />
* Sandbox release for web connector (Eugene)<br />
Vacations<br />
* Rob: 3rd - 8th<br />
* Mik: 8th - 17th<br />
Actions<br />
* Consumers of APIs update Javadocs as they use them, a la wiki <br />
* Decide on conference call time and interval next meeting<br />
* Investigate Rome dependency for Sandbox (Mik)<br />
<br />
==== Thursday, July 6 2006, 10am PT ====<br />
* wrap up discussion of 0.6 release<br />
* Trac integration status (Steffen)<br />
* enhancing Bugzilla connector status (Jeff)<br />
* Connector naming conventions<br />
* tasks API discussion. String-based task id, separate task id, url and repository url, (issues 146396, 149624, 149509), other refactoring of tasks, hits, query and repository classes<br />
* UI for repository settings<br />
* prioritizing for 0.7 and beyond<br />
* planning and use of Bugzilla priorities<br />
<br />
==== Tuesday, June 13 2006, 10am PT ====<br />
* Schedule a regular meeting time and interval<br />
* Google SoC: Trac integration (Steffen)<br />
* Google Soc: enhancing Bugzilla connector (Jeff)<br />
* Repository connector API discussion (Mik)<br />
* Prioritize tasks for 0.6 (Mik)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=42346Mylyn/Porting Guide2007-07-10T01:00:11Z<p>Steffen.pingel.eclipse.org: /* Porting from 2.0 to 3.0 */</p>
<hr />
<div>[[Category:Mylyn]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from 1.0 to 2.0 =<br />
<br />
See the <b>[[Mylyn Porting Guide 2.0]]</b><br />
<br />
= Porting from 2.0 to 3.0 =<br />
<br />
There is currently no need to port Mylyn from the 2.0 APIs since current Mylyn releases are backwards compatible. Throughout the 2.x release cycle we will be using this wiki to gather changes and suggestions for improving the APIs for 3.0.<br />
<br />
== Tasks API == <br />
<br />
* <code>AbstractRenderingEngine</code> has been added for converting Wiki syntax to HTML<br />
<br />
* <code>AbstractRepositoryTaskEditor</code> has been extended to provide HTML preview capabilities for repositories that support Wiki syntax in ticket descriptions and comments<br />
** <code>addSelectableControl()</code> has been added<br />
** <code>createReplyHyperlink()</code> is now protected (was private)<br />
** <code>DescriptionListener</code> is now protected (was private)<br />
** <code>getParentEditor()</code> has been added<br />
** <code>getRenderingEngine()</code> has been added<br />
** <code>removeSelectableControl()</code> has been added<br />
<br />
== Pending Changes for Mylyn 3.0 == <br />
<br />
* Rename <code>IMylarMonitorLifecycleListener</code> to <code>IMonitorLifecycleListener</code></div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/FAQ&diff=40871Mylyn/FAQ2007-06-27T03:30:02Z<p>Steffen.pingel.eclipse.org: /* Why do I get an HTTP Error 500 Internal server error when creating a Ticket that contains non-ASCII characters? */</p>
<hr />
<div>[[Category:Mylar]] <br />
<br />
[[Mylar User Guide]], <br />
[http://eclipse.org/mylar Mylar Home],<br />
[http://wiki.eclipse.org/index.php?title=Special:Userlogin&returnto=Special:Userlogout Log in to edit]<br />
<br />
For instructions on [http://wiki.eclipse.org/index.php/Mylar_User_Guide#Download_Mylar downloading] [http://wiki.eclipse.org/index.php/Mylar_User_Guide#Installation installing] and [http://wiki.eclipse.org/index.php/Mylar_User_Guide#Configuration configuring] <br />
Mylar, see the [[Mylar User Guide]]. For instructions on developing and contributing to Mylar, see the [[Mylar Contributor Reference]].<br />
<br />
= Installation =<br />
<br />
== What versions of Eclipse are supported? ==<br />
<br />
See the [http://eclipse.org/mylyn/dl.php download page].<br />
<br />
Mylyn also relies on a web browser that works with the Standard Widget Toolkit; Windows and MacOS users are fine, but Linux users might have to download another browser. See [http://www.eclipse.org/swt/faq.php#browserlinux the SWT Browser guide] for which browsers will work. See [http://wiki.eclipse.org/index.php/Mylar_User_Guide#Installing_Browser_on_Linux installing browser on Linux] for installation instructions.<br />
<br />
== What version of Java is required? ==<br />
<br />
Mylyn needs the '''Java 5''' virtual machine.<br />
<br />
To check the version of the Java virtual machine that Eclipse was launched with to to ''Help -> About Eclipse SDK -> Configuration Details'' and verify that the java.vm.version is 1.5. <br />
<br />
Mac users should refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
* If you do not have Java 5, you can download it from [http://72.5.124.55/javase/downloads/index.jsp Sun's web site]. <br />
* If you have more than one VM, you need to specify that Eclipse should use the JDK1.5 VM. <br />
<br />
In Unix, set the environment variable <code>JAVA_HOME</code> to the root of the JDK1.5 installation and/or set the <code>PATH</code> variable to put the JDK1.5 executable directory before any other VM executable directories. For example, under <code>bash</code> in Unix:<br />
export JAVA_HOME="''(location of JDK1.5 root)''"<br />
export PATH=$JAVA_HOME/bin:$PATH<br />
<br />
<b>We do [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140955 not recommend] using JDK 1.6 on Eclipse 3.1.</b> (It works fine with Eclipse 3.2 or 3.3.) To use JDK 1.6 on Eclipse 3.1, you must add the following line to your <code>config.ini</code>file:<br />
<code><br />
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,<br />
J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6<br />
</code><br />
<br />
== My tasks or queries disappeared, what do I do? ==<br />
<br />
This happens if Mylyn failed to install. First ensure that you have a correct install by following the instructions in the next section. After that, if you still do not see your tasks use the ''Task List'' view menu -> ''Restore Tasks From History...'' command (also available via ''File -> Import -> Task List''.<br />
<br />
== Installation Troubleshooting ==<br />
<br />
''' Update failures '''<br />
<br />
On Eclipse versions earlier than 3.3 (final) use '''only the "Search for new features.."''' option when updating Mylar. If you use "Search for updates..." the Update Manager will allow a partial install that can cause Mylar to fail to start, and you will need to run update again. See the ''feature configuration problem'' section below for details. If you encounter this problemm consider voting for Platform [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132450 bug 132450].<br />
<br />
''' Startup exceptions '''<br />
<br />
If you see startup errors or warnings such as <code>BundleException</code> or timeout messages restart Eclipse with the <code>-clean</code> flag either on the command line, in your shortcut link, or by temporarily it into the <code>eclipse/eclipse.ini</code> file. If that does not resolve the problem please [http://www.eclipse.org/mylar/bugs.php file a bug].<br />
<br />
''' Incompatible VM (e.g. JDK 1.4) '''<br />
<br />
If you are using the wrong VM, you'll see errors like the following in your log file. <br />
<code><br />
Root exception: java.lang.UnsupportedClassVersionError:<br />
org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)<br />
</code><br />
<br />
See [[#Download_and_configure_Java_5_or_6|Configure Java]] to fix this problem.<br />
<br />
''' Incompatible version of Eclipse '''<br />
<br />
Separate versions and update sites exist [http://eclipse.org/mylar/dl.php for Eclipse 3.1 and 3.2]), in which case you may see errors like the following in your <code><workspace>/.metadata/.log </code>file or in a Mylar view:<br />
<code><br />
java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()<br />
The activator org.eclipse.mylar.java.MylarJavaPlugin for bundle org.eclipse.mylar.java is invalid<br />
</code><br />
<br />
''' Mylar feature configuration problem '''<br />
<br />
If the above do not address the issue, the easiest thing to do is uninstall any old versions and update to the latest Mylar. Your tasks won't be lost, because by default they are stored in the <code><workspace>/.mylar/tasklist.xml</code> file which will be read next time Mylar starts correctly. <br />
* First, uninstall the old version of Mylar using ''Help -> Software Updates -> Manage Configuration''. <br />
* You need to Disable all Mylar features by right-clicking them.<br />
* Allow Eclipse to restart after the last is disabled.<br />
* After restart, ensure that the 3rd toolbar button is pressed (figure below) so that you see the disabled features to uninstall.<br />
* Uninstall all the disabled features using the popup menu. <br />
<br />
If you don't uninstall, the the Update Manager will think that you have the latest and tell you that there are no updates. <br />
<br />
<b>Note: manually removing the plug-ins and features can lead to configuration errors.</b> <br />
<br />
After uninstalling, update Eclipse by adding the correct update site specified at on the [http://eclipse.org/mylar/dl.php download page], and after that automatically or manually updating will install the correct version.<br />
<br />
[[Image:mylar-eclipse-manage-configuration.gif]]<br />
<br />
'''What do I need to do in installation to be able to use Mylar task management features with bug/task/issue trackers?'''<br />
<br />
When you install, make sure that you select a connector for your bug/task/issue tracking software. For example, to use Bugzilla, you have to install the Bugzilla connector component.<br />
<br />
'''I've installed Mylar; why can't I see anything different?'''<br />
<br />
The two most likely possibilities are:<br />
# You don't have any Mylar views open. Select ''Window -> Show View -> Other'', then select ''Mylar'' and you should see the available Mylar Views. <br />
# If you still don't see anything, then perhaps you aren't using the JDK1.5 VM (or later). See [[Mylar_Installation_Guide#Download_and_configure_Java|configuring Java]].<br />
<br />
<br />
'''What does the error "Network connection problems encountered during search" mean?'''<br />
<br />
If you get that message while trying to download Mylar, it means that Eclipse couldn't find the location you entered. This might be because you copied something incorrectly (watch for extra characters -- even extra spaces can cause errors), or because the site went down. You may be able to see if the site is up or down by copying the URL into your Web browser.<br />
<br />
'''What does the "Update manager failure" message mean? '''<br />
<br />
It means that Eclipse could not access the update site, or that it got confused about the configuration state of your Eclipse. First try updating again to see if the update site is accessible. <br />
<br />
If you are trying to update the JIRA connector you can also try de-selecting that feature in case the <code>Tigris.org</code> update site is not accessible. Using ''Search for new features to install..'' when installing can help to avoid this problem. If that does not work see the feature configuration troubleshooting below. <br />
<br />
'''What does "Could not create Browser page: No more handles (<code>java.lang.UnsatisfiedLinkError: ...</code>)" mean?'''<br />
<br />
It probably means that you are running Linux and don't have Eclipse and a Web browser configured to work together. See [[http://wiki.eclipse.org/index.php/Mylar_User_Guide#Installing_Browser_on_Linux| installing a browser on Linux]].<br />
<br />
'''When downloading, why do I get a warning that the feature was unsigned?'''<br />
<br />
Signing plugins requires extra administrative details with <code>eclipse.org</code> which most plug-ins seek to avoid. <br />
<br />
'''N.B.''': Security issues with features should not be underestimated. Eclipse allows users to download new functionality from remote servers. A rogue plug-in can act as a perfect Trojan horse. It can look innocent enough and provide useful function while spawning threads in the background with full access to the local file system and the Internet (if connected). Beware of installing features from update sites you do not trust.<br />
<br />
'''What does "<code>Root exception: java.lang.UnsupportedClassVersionError: org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)</code>" mean?'''<br />
<br />
It probably means that the virtual machine is JDK1.4 or lower. See [[Mylar_Installation_Guide#Download_and_configure_Java| download and configure Java]].<br />
<br />
'''Why am I getting messages in my <code><workspace>/.metadata/.log</code> or my Mylar view that say things like <code>"java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()"</code> and "The activator <code>org.eclipse.mylar.java.MylarJavaPlugin</code> for bundle <code>org.eclipse.mylar.java</code> is invalid"?'''<br />
<br />
This probably means that your Mylar download version didn't match your Eclipse download version. Note that [http://eclipse.org/mylar/dl.php the download site] has different downloads for Eclipse 3.1 and Eclipse 3.2.<br />
<br />
To fix this problem, see the [[Mylar_Uninstallation_Guide| uninstallation guide]], then re-install from [http://eclipse.org/mylar/dl.php the correct download site].<br />
<br />
'''What does "Could not create Bugzilla editor input" and "<code>java.io.IOException</code>: SAX2 driver class <code>org.apache.xerces.parsers.SAXParser</code> not found" mean?'''<br />
<br />
It probably means that you are on MacOS, and for some reason are missing Xerces from the Mac JDK1.5. You will probably need to add it to your default classpath. Please refer to and comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=144287 bug 144287] if you see this problem.<br />
<br />
To ensure that you are using the 1.5 VM refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
'''I've just updated to Mylyn 2.0 and I don't see any tasks in my Task List'''<br />
<br />
As part of the update to Mylyn 2.0 the old data folder has been migrated to <workspace folder>/.metadata/.mylyn from the old location <workspace folder>/.mylar. IF for some reason migration failed (.mylar folder still exists), simply shut down Eclipse and manually move your old <workspace folder>/.mylar folder to <workspace folder>/.metadata/.mylyn (note the name change to .mylyn)<br />
<br />
== Configuration Troubleshooting == <br />
<br />
'''How can I change the number of editors left open before Mylar starts closing editors?'''<br />
<br />
Turn off or increase the number of editors to leave open using ''Preferences -> General -> Editors -> Number of opened editors before closing''. Since Mylar will manage the open editors with task activation, this number can be set higher or you can disable automatic closing entirely.<br />
<br />
'''Do I need the Outline View when running Mylar?'''<br />
<br />
No, not really. The Package Explorer and folded signatures should provide enough context for you. If, at some point, you really need to see an Outline View, you can always enter (Ctrl+O) to show the in-place Outline View.<br />
<br />
'''What does the message "content assist proposals no longer appear" mean?'''<br />
<br />
This usually happens when uninstalling when using Eclipse 3.2. Make sure that the "Java Completions" and "Java Types" proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylar FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
'''Why do I get errors like "HTTP Response Code 407" or "Proxy Authentication Error" when accessing repositories through a proxy server?'''<br />
<br />
It is likely that you need to configure these proxy server settings. Select ''Window -> Preferences -> Install/Update'', and update the section in the "Proxy settings" section of the form.<br />
<br />
'''I can't use <code>Ctrl+Alt+Shift+Arrow Up</code> for'' Mark as Landmark''. What do I do?<br />
<br />
This is usually a Linux/GNOME problem, where the Gnome keyboard shortcuts are interfering with the Eclipse shortcuts. Go to the Keyboard shortcuts (which might be something like ''Desktop -> Control Centre -> Keyboard Shortcuts'' or ''System -> Preferences -> Keyboard Shortcuts'') and disable both of these shortcuts:<br />
* Move one workspace up<br />
* Move one workspace down<br />
<br />
See also: [[Mylar_User_Guide#Keyboard_mappings_on_Linux| keyboard mappings on Linux]].<br />
<br />
'''How do I turn on spell checking?'''<br />
<br />
See [[Mylar_User_Guide#Spell_Checking| spell checking]].<br />
<br />
== Uninstall troubleshooting ==<br />
<br />
When '''uninstalling in Eclipse''' Mylar via the ''Help -> Software Updates -> Manage Configuration'' dialog you will need to uninstall dependencies first (e.g. Bugzilla Connector, Subclipse integration) and then uninstall the core Mylar features.<br />
<br />
When '''uninstalling manually''' by deleting all of the Mylar plug-ins and features from the <code>eclipse/plugins</code> and <code>eclipse/features</code> directory make sure to delete all of the plug-ins and then restart Eclipse with the -clean option (e.g. by inserting it into a shortcut or the <code>eclipse.ini</code> file.<br />
<br />
On '''Eclipse 3.1:''' you may need to reset the Java editor to be default for <code>.java</code> again via: ''Preferences -> General -> Editors -> File Associations''<br />
<br />
On '''Eclipse 3.2:''' if after uninstalling '''content assist proposals no longer appear''' you need to ensure that the ''Java Completions'' and ''Java Types'' proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylar FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
== I am seeing <code>java.lang.OutOfMemoryError: PermGen space </code>errors, what's wrong? ==<br />
<br />
If your Eclipse crashes, or you see the above error after installing Mylar or other plug-ins, you have most likely hit the infamous MaxPermSize bug. This is not a Mylar specific problem, but a general Eclipse problem that is often triggered on Eclipse 3.2 and later, if you have many plug-ins installed and are using a Sun JVM. <br />
<br />
To fix it simply add the following to your launch arguments. This is usually to your shortcut, or to the <tt>eclipse/configuration/config.ini</tt> file:<br />
<br />
-XX:MaxPermSize=128M<br />
<br />
If you are using a large number of plug-ins (e.g. WTP) you may need to increase the number to more than 128M. <br />
<br />
Details of the problem are on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250 Platform bug 92250].<br />
<br />
= Task List =<br />
<br />
== Why won't the Archive category disappear? ==<br />
<br />
The ''Archive'' category will automatically appear if a task needs to be shown, but is not in any query or category. <br />
In order to ensure that you do not miss reminders or notifications the following tasks will always be shown in the Task List, even if they have been removed from a category or a query:<br />
* Tasks scheduled for this week or overdue. Remove these by using the ''Schedule'' pop-up menu option to defer them to a future week or to clear the schedule.<br />
* Repository tasks that have incoming changes, such as comments. Remove these by reading them or marking them as "read" via the ''Mark -> Read'' pop-up menu.<br />
<br />
== How do I prevent long-running tasks from adding to the progress bar? ==<br />
<br />
If you have many long-running or recurring tasks scheduled for this week, they can affect the ''Task List'' weekly progress bar. This can be misleading as they may never be completed. The current work-around to prevent long-running tasks from being included in the weekly progress bar is to schedule their estimated time to be 0 (zero). Alternatively, you can schedule only the amount of time you plan on spending on that task this week.<br />
<br />
== Does the Task List replace the Eclipse Tasks view? ==<br />
<br />
The SDK's ''Tasks'' view is used for showing markers such as 'todo' tags which indicate a local problem with a resource, similar to a compiler warning. As such, these 'tasks' are at a much lower level of granularity than Mylar's tasks, and one task could involve cleaning up multiple todos. In order to make working with only the markers in a particular task context, e.g. for clean-up before committing, the ''Apply Mylar'' filter is available for both the ''Problems'' and the ''Tasks'' views.<br />
<br />
== What if I use multiple workspaces? ==<br />
<br />
Mylar's support for multiple workspaces is currently limited (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130658 bug 130658] for a discussion) because the Task List is considered to be specific to the person, and not to the workspace. We recommend configuring your Eclipse workspace to use working sets instead of relying on multiple workspaces. <br />
* John O'Shea's blog: [http://www.xlml.com/aehso/2007/02/02/eclipse-workspaces-containing-projects-with-overlapping-locations-and-mylar/ Eclipse workspaces containing projects with overlapping locations, and Mylar]<br />
<br />
If using a single workspace is not possible you can do the following:<br />
* In ''Preferences -> Mylar -> Task List'' set the ''Data Directory'' to be a shared location, and do this for both workspaces.<br />
* Be sure to avoid launching both Eclipse workspaces at the same time, as changes in one workspaces could overwrite the Task List in the other workspace.<br />
* If you upgrade Eclipse or move your workspace and don't see your tasks, check the ''Data Directory'' setting.<br />
<br />
== How do I export my task and repository data? ==<br />
<br />
Export via File > Export > Mylar > Task Data<br />
<br />
== Why does Mylar use the term "task"? ==<br />
<br />
There are many work items that make up the developer's workday. Many issue trackers and project management tools refer to these as: bugs, defects, actions, tickets, stories, enhancements, and the list goes on. We refer to all such work items as "tasks" because the word tasks is short and commonly used in time management tools. Task Repository connectors can customize the presentation of tasks, for example, indicating which is a defect and which is an action item.<br />
<br />
= Task Repositories =<br />
<br />
== What if Mylar doesn't support my task/bug/issue/ticket repository? ==<br />
<br />
To see support for your repository faster, do a search of the open repository connector requests and [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Bconnector%5D&product=Mylar&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=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= vote for the corresponding bug] if your tracker is there, or [http://www.eclipse.org/mylar/bugs.php create a new bug]. <br />
<br />
[[Mylar_User_Guide#Generic_Web_Repository_Connector|Generic Repository Connector]], allows creating Queries to the web-based issue tracking repositories and get list of issues from the web UI into the Task List.<br />
<br />
It is also possible to link a ''local task'' with the web page in web-based repository via the Mylar Web integration.<br />
<br />
'''To create a task from any web-based repository:'''<br />
<br />
* Drag the URL from the address bar of the browser, or from a hyperlink in a bug listing to the ''Mylar Tasks'' view. This will create a task for the bug, link it to the page, and populate the description with the title of the corresponding page. '''In Mozilla:''' simply drag the URL. '''In Internet Explorer:''' you must have <code>Ctrl</code> pressed in order for Eclipse to recognize the drop.<br />
* '''Alternatively,''' you can copy the URL, press the ''New Task'' button on the ''Mylar Tasks'' view. This has the same effect as above but you can edit the description after retrieving it.<br />
* Opening the task will now open the corresponding issue. You can also <code>right+click</code> the task and select ''Open in External Browser''.<br />
<br />
[[Image:mylar-tasklist-weblink-editor.gif]]<br />
<br />
== Why were my repository credentials reset? ==<br />
<br />
If you upgrade Eclipse or your Java VM, you will need to reset your credentials in the ''Task Repositories'' view because these are stored in the secure Eclipse workbench keyring. Also see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=149607 bug 149607]. If you are migrating '''from Eclipse 3.2 to 3.3''' note that you will need to use a different update site: http://eclipse.org/mylar/dl.php<br />
<br />
== Why are my updated repository attributes not showing up? ==<br />
<br />
Your server's repository attributes can change frequently, for example, there can be a new "milestone" or "version" added to the Bugzilla repository with each release. When the ''Preferences -> Mylar -> Task List -> Synchronization'' setting is enabled, every 10th synchronization will update the attributes from the repository. If you do not have this setting enabled, your can force the update via the ''Update Attributes'' action on the task repositories' context menu in the ''Task Repositories'' view. Note that you will need to reopen a task editor to see the updated attributes.<br />
<br />
== Authentication Troubleshooting ==<br />
<br />
You must ensure repository credentials are filled out correctly. Refer to the diagram below:<br />
<br />
[[image: AuthenticationTroubleshooting2.png|right]]<br />
<br />
# Enter the repository URL (i.e. https://bugs.eclipse.org/bugs) and an optional label<br />
# Credentials<br />
#* Usually email address and password <br />
#* Some sites, such as <code>dev.eclipse.org</code>, use anonymous logon with password left blank.<br />
#Http Authentication (optional)<br />
#* Some sites are protected by either BASIC or DIGEST http authentication. If this is the case, enter appropriate credentials here.<br />
#* One way to test if the site requires http authentication is to point your browser at the repository. If you are presented with an authentication dialog popup, the site is likely protected by http authentication.<br />
#Proxy Server Configuration (optional)<br />
#* By default Mylar uses the Platform's Install/Update proxy settings. Uncheck this box if you wish to use an alternative proxy.<br />
#* If the proxy requires authentication, this is where you enable and enter your proxy credentials.<br />
#* If you are experiencing connection problems, ensure your Install/Update proxy settings are valid or the repository specific settings are correct<br />
#* Mylar has been tested with HTTP proxy servers. Currently SOCKS is not supported.<br />
#Validate Settings <br />
#*Press the ''validate'' button to test the settings<br />
#*If you are seeing errors like "HTTP Response Code 407" or "Proxy Authentication Error" it is likely that you need to configure proxy settas as described above.<br />
#*If your sever uses a certificate and fails to connect, e.g. you see exceptions <tt>sun.security.validator.ValidatorException: PKIX path building failed</tt> then you need to point Eclipse at your certificate, see the [http://ahtik.com/blog/2006/05/11/fixing-eclipse-mylar-jira-integration/ instructions on this blog].<br />
<br clear="all" /><br />
<br />
= Bugzilla Connector =<br />
<br />
== What versions are supported? ==<br />
<br />
We recommend using the latest [http://www.bugzilla.org/download/ release] of Bugzilla.<br />
<br />
* '''Bugzilla 2.18.6 is the lowest version of Bugzilla supported'''. If you are getting errors that indicate failure to update attributes this may be an indication that the Bugzilla server is not supported (< 2.18.6).<br />
<br />
*If you are using '''Bugzilla 2.18''' and are getting '''mid-air collisions''' this is likely due to incorrectly formatted timestamp field in the underlying bugs database table ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149513 bug 149513]). This can be resolved by upgrading to Bugzilla 2.20 or later.<br />
<br />
== Why are queries failing? ==<br />
<br />
*If '''queries are not working''' correctly ensure that you have the right Bugzilla server version selected for the corresponding repository: ''Task Repositories (View) ->'' right+click the repository ''-> Properties''. For supported versions see the [http://www.eclipse.org/mylar/dl.php download page]. If the repository is still not functioning it may be due to authentication or connectivity problems. If that does not resolve the problem please post a message to the newsgroup or [http://www.eclipse.org/mylar/bugs.php submit a bug].<br />
<br />
== Why do tasks fail to open? ==<br />
<br />
*If upon opening a bug, the Bugzilla tab only displays a warning "'''Could not download task data, possibly due to timeout or connectivity problem. Please check connection and try again.'''", ensure that your repository is returning XML data by pointing your browser to <code><your-repository-url>/show_bug.cgi?id=1&ctype=xml</code> to show the contents of bug 1 in XML form. The Bugzilla client requires that bugs be accessible in XML form. If the repository doesn't support xml then it is likely that the repository is too old (Mylar currently supports Bugzilla 2.18 and later).<br />
<br />
* If '''reports fail to load''' or '''reports fail to synchronize''' (task description remains ''italic''), check the error log for a "'''File not found'''" error pointing to <code>bugzilla.dtd</code> or a "'''Failed to retrieve products from server'''" error message - these result when the <code>urlbase</code> parameter is not set on the bugzilla server, or your bugzilla installation is missing the <code>bugzilla.dtd</code> file. See: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=161759 bug#161759]<br />
<br />
* If '''attributes are missing options''' in the bug editor (ie. missing a recently added milestone, [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155431 bug# 155431]):<br />
** Update attributes by choosing ''Update Attributes'' from the context menu in the ''Task Repositories'' view<br />
** Synchronize the task in the Task List<br />
** Reopen the task - new options should be available.<br />
<br />
== Why do tasks fail to submit? ==<br />
<br />
* '''Error upon submit: unable to make any match for name/email entered.''' If your bugzilla is configured for user names rather than full email address the QA Contact field will cause the submit to fail ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=166555 bug# 166555]). To resolve, select 'Local users enabled' option on the Repository Configuration page. <br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your account's username and password and are not using the HTTP authentication fields instead.<br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your bugzilla instance's cookie domain under the required settings. The cookie domain must lead with a dot.<br />
<br />
* If '''attachments are failing to submit''' and you see that after processing the attachment, the bugzilla bug shows a size of "bytes" (no numbers), your database may be dropping the packet sending the file. '''On MySQL''', check the [http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html max_allowed_packet directive]. You may see errors like: <code>DBD::mysql::st execute</code> failed: Got a packet bigger than 'max_allowed_packet' bytes [for Statement "INSERT INTO attach_data (id, thedata) VALUES (38, ?)"] at <code>/path/to/bugzilla/attachment.cgi</code> line 993. Also, '''check the maximum attachment size''' in ''Bugzilla Parameters -> Attachments''.<br />
<br />
* If a submit fails with an '''Invalid Username or Password''' error even though repository settings do validate, make sure that cookies could be set. See also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175502 bug 175502]<br />
<br />
== What time zone is used in the task editor? ==<br />
<br />
*The '''times''' that appear in the Bugzilla bug editor (ie. created, modified) '''are local to the server hosting the Bugzilla repository''', not your local machine's time zone. <br />
<br />
== Known limitations ==<br />
<br />
* The <code>usermatchmode</code> is not currently supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168204 bug 168204]) and as such full email addresses need to be used.<br />
<br />
* The <code>usevisibilitygroups</code> parameter is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=180876 bug#180876]). Group assignment will currently be lost if updated using the Bugzilla rich task editor.<br />
<br />
* Version 1.0 of Mylar presents an error message upon new comment submission to RedHat's public Bugzilla repository. The comment is in fact posted. This issue is resolved in Mylar 2.0M2 and higher. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=183251 bug#183251])<br />
<br />
= JIRA Connector =<br />
<br />
If you see errors like the following, work around this by opening repository ''Properties Page'' and clicking OK (bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169102 169102]).<br />
<br />
org.tigris.jira.core.service.exceptions.AuthenticationException<br />
at org.tigris.jira.internal.core.service.soap.SoapJiraService.getProjectsNoSchemes(SoapJiraService.java:204)<br />
<br />
== What are the server requirements? ==<br />
<br />
The '''JIRA SOAP/RPC services have to be running on the JIRA server''':<br />
<br />
* Jira 3.3.3 or higher (3.7 or higher for attachment retrieval)<br />
* Jira RPC plugin 1.4.3 or higher<br />
<br />
Latest information also available on the [http://www.eclipse.org/mylar/dl.php download page].<br />
<br />
Related Resources:<br />
<br />
* [http://confluence.atlassian.com/display/JIRA/JIRA+Development+Hub Jira Development Wiki]<br />
* [http://confluence.atlassian.com/pages/viewpage.action?pageId=1035 Jira RPC Plugin Overview]<br />
<br />
== Why can't I connect? ==<br />
<br />
* If you get a <code>org.tigris.jira.core.service.exceptions.ServiceUnavailableException</code> you need to turn on the JIRA SOAP/RPC services on the server.<br />
* If you get a '''503''' error code verify that the SOAP/RPC interface is enabled.<br />
* If you get a '''403''' error code verify that the SOAP/RPC interface is enabled, and also check your authentication mechanism. If the server is using NTLM authentication, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156397 bug 156937] for diagnosis steps.<br />
* If you see an '''"unrecognized priority" message''' in the ''Error Log'', the problem is that the JIRA Connector does not support customized priorities so the priority value specified in that message will not correspond to the priority icons visible in the Task List.<br />
* If you are being '''prompted for your log-in credentials''' by the Browser tab of the task editor or the new task editor, this is because without rich editor support the connector is using the web-based UI instead of logging in on your behalf as is done with a rich task editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142869 bug 142869]).<br />
* If you get a <CODE>AuthenticationException</code> and a query won't synchronize, use Task Repositories (view) -> Properties (on the repository) -> Validate Settings. This will clear the connection if it died.<br />
<br />
== Why can't I synchronize when using a proxy server? ==<br />
<br />
* Proxy configuration is be '''based on the normal Java HTTP system properties''', which can be configured either by launching Eclipse with <code>-vmargs</code> and using the following settings, or by putting these settings into the or by putting the following into the <code>eclipse/eclipse.ini</code> file (after -vmags):<br />
-Dhttp.proxyHost=<host> <br />
-Dhttp.proxyPort=<port><br />
* Make sure that when using these settings you do not enable the proxy settings on the ''Install/Update'' preference page, since they may override these settings.<br />
* If you are using '''SSL''', you will also need to set the <code>https.proxyHost</code> and <code>https.proxyPort</code>. <br />
* Authentication is configured with the <code>http.proxyUser</code> and <code>http.proxyPassword</code> system properties (also for SSL)<br />
* You can also use <code>http.nonProxyHosts</code> system property to enumerate hosts that should not be proxied. Note that matching is implemented on the exact host name used for JIRA server and patterns are not supported.<br />
<br />
== Known limitations ==<br />
* Attachments are not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=169757 bug 169757])<br />
* NTLM authentication is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172395 bug 172395])<br />
* Customized priorities are not currently supported, so all issues with a customized priority will have the default priority level ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=165518 bug 165518]).<br />
* On JIRA 3.6.x private filters saved on the server can fail to retrieve results ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=174328 bug 174328]). The work-around is to create a custom query in Mylar using the form-based query designer or to share the filter in JIRA.<br />
* Attachment retrieval (including retrieval of the task context and attachment list in the task editor) require JIRA 3.7 or above.<br />
<br />
== How can I enable compression for SOAP messages? ==<br />
<br />
If your repository has lots of projects and components you can speed up the download of the repository configuration by enabling compression. <br />
<br />
* Add a filter-mapping to your JIRA server configuration: [http://jira.atlassian.com/browse/JRA-10353].<br />
* Enable compression in your global JIRA configuration.<br />
* Check the compression setting for your task repository in Mylar versions 2.0M2 and later.<br />
<br />
= Trac Connector =<br />
<br />
== What are the server requirements? ==<br />
<br />
The Trac connector offers two access methods:<br />
<br />
'''XML-RPC''' (recommended)<br />
<br />
Requirements:<br />
* Trac 0.10<br />
* [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] rev. 1950<br />
<br />
This access method offers editing of tasks in a rich editor, attachment support and offline editing. It requires the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] for Trac to be enabled for the accessed repository. The XmlRpcPlugin provides a remote interface to the Trac repository and is distributed separately from Trac (see [http://trac.edgewall.org/ticket/217 #217]). See these [http://trac-hacks.org/wiki/XmlRpcPlugin#Installation install instructions] for requirements and documentation.<br />
<br />
'''Web''' <br />
<br />
Requirements:<br />
* Trac 0.9 or later<br />
<br />
In this mode the standard Trac web interface is used for repository access. Tickets may be created and edited through a web browser. Offline editing and attachments are not supported.<br />
<br />
== Recommended Trac version ==<br />
<br />
Mylar should work with any stable release Trac release that is version 0.9.x or 0.10.x (see below for known limitations). Mylar works best when used with Trac's XML-RPC Plugin (see above) but we do not recommend a particular Trac version. <br />
<br />
The Trac connector tests are run against these Trac versions:<br />
<br />
* Trac 0.10, XML-RPC Plugin rev. 1950<br />
* Trac 0.9.6<br />
<br />
== Why do I get an HTTP Error 500 Internal server error when creating a ticket that contains non-ASCII characters? ==<br />
<br />
Problems related to character encodings have been reported when Trac is run with Python 2.3. Upgrading to Python 2.4 may help to resolve this. Please comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=188363 bug #188363] if you encounter an internal server error when creating a ticket that contains non-ASCII characters.<br />
<br />
== Known limitations ==<br />
<br />
* Trac 0.10.1 <br />
** Known incompatibility with Trac XML-RPC Plugin. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164272 bug 164272] for details.<br />
* Trac 0.10.3 <br />
** Known incompatibility with old versions of the Trac HttpAuthPlugin (fixed in revision 1890 or later). The plug-in enables basic auth for XML-RPC when Trac AccountManagerPlugin for form based authentication is used. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168413 bug 168413] for details.<br />
* Trac 0.11<br />
** Currently untested.<br />
** Known incompatibility with Trac XML-RPC Plugin See [http://trac-hacks.org/wiki/XmlRpcPlugin] for details.<br />
<br />
== Why are tasks opened in a web browser and not in the rich editor? ==<br />
<br />
Please make sure that the access type in the repository properties is set to XML-RPC. This requires Trac 0.10 and XML-RPC (see above).<br />
<br />
= Generic Web Repository Connector =<br />
<br />
== Why can't I connect using one of the existing templates? ==<br />
<br />
<br />
The Web Repository Connector have a Preview option in Advanced Configuration section on the Query preferences. If you get an error or preview table does not show expected list of tasks you can use Query Pattern like (.+?)(\n) to see content of the retrieved page and compare it with the source of the web page for the same url loaded into the web browser.<br />
<br />
If that does not help then you could use the wget tool (on Windows it available as a standalone command line tool and also included with Cygwin).<br />
<br />
Run the following command:<br />
<br />
<pre>wget -v -d -o query.log -O query.html "http://your.query.url"</pre><br />
<br />
If repository require basic http auth, you'll need to use ''--http-user=USER'' and ''--http-password=PASS'' options.<br />
<br />
Then open file ''query.html'' in the web browser and check if it show list of issues you need to fetch from the web server. If it does have correct list, then there could be a problem with query pattern used for parsing. <br />
<br />
A popular mistake is an unmasked '?' that separates request parameters in the url). For example:<br />
<br />
<pre><a href="show_bug.cgi\?id\=(.+?)">.+?<span class="summary">(.+?)</span></pre><br />
<br />
If ''query.html'' does not show expected list of issues you can check ''query.log'' for server responses and try to identify if server require authentication, redirecting your requests somewhere or issue any other errors.<br />
<br />
== Known limitations ==<br />
<br />
* In Mylar 1.0: if a web server responds by requesting a redirect to an absolute URL while fetching a resource, the connector falsely prepends "/" to the URL and the request will fail. The workaround is to use final url where redirect is pointing to (you can find it as describe above). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=167282 bug 167282] for details.<br />
<br />
<br />
= Task-Focused UI =<br />
<br />
== What is the Task-Focused UI? ==<br />
<br />
When you activate a task, Mylar automatically maintains a task context by monitoring your interaction. The task context provides a predictable degree-of-interest weighting of the relevance of the elements and relations that you work with to the task-at-hand (as described in the [http://kerstens.org/mik/publications/2006-11-mylar-fse.pdf Foundations of Software Engineering conference paper]). The Task-Focuse UI is the mechanism by which Mylar presents Mylar the task-context model in order to reduce information overload and to automate the manaul management of UI elements like editors and change sets. Examples:<br />
* Filtering, decoration and expansion management in views<br />
* Automatic folding in editors<br />
* Ranking in content assist<br />
* Editor management<br />
* Perspective management<br />
* Change set management<br />
<br />
== Why do files disappear from Focused views when I close them? ==<br />
<br />
By default Mylar automatically manages the set of open files to match the task context, so that you don't have to. This ensures that the editor list (viewable via mechanisms like Ctrl+E) corresponds to what you in views like the ''Package Explorer'' when they are in Focused mode. When you close a file manually, you express that it is uninteresting, and as such it will be removed from the task context. It will also disappear from the corresponding automatically managed change sets for the same reason. This behavior can be turned off via ''Preferences -> Mylar -> Context -> Manage open editors to match task context''. However, it is highly recommended since Mylar will prevent the number of editors from bloating by automatically closing editors for elements that have decayed in interest, and always keep the editors for interesting elements open.<br />
<br />
<br />
== Why did all my editor tabs disappear? ==<br />
<br />
When you deactivate a task, all editors will be closed, and then when you reactivate the task all the windows will be open again. Try it, it's fun. <br />
<br />
Mylar actively manages your open editors with task context. It takes some getting used to, but enables switching between tasks when you are multitasking without cluttering your editor tabs. This editor management can be disabled via ''Window -> Preferences -> Mylar -> Context''. However, before disabling it consider reading the ''"Managing open editors..."'' section of [http://www-128.ibm.com/developerworks/java/library/j-mylar2/index.html#N10116 Task-focused programming with Mylar].<br />
<br />
== How do I get rid of an element if it is not interesting? ==<br />
<br />
When a view is focused elements will disappear on their own if they are not repeatedly selected via a mechanism called interest decay. Note that decay does not use the wall clock, but instead relies on the number of selections that you have made when working on that task to determine which elements disappear. This helps make it feel very predictable.<br />
<br />
If you want want to force one or more elements to disappear from the context use the '''Remove from Focus''' action on the context menu. Note that the element will still be part of the task context since it was previously part of the interaction. <br />
<br />
If you want to permanently delete the element from the interaction history use the '''Remove from Context''' action on the '''Context''' tab of the '''Task Editor'''. For example, if a company private element was part of a task context that is to be shared with a public repository, this action can be used to clean it up before sharing. Note that elements will be removed from the task context recursively.<br />
<br />
== Which Focused UI features can I turn off? ==<br />
<br />
'''All of them.''' When no task is active neither are any of Mylar's features. When working with task contexts Mylar's Focused UI features are all optional and in general configurable. While many find it the key benefit of Mylar, the entire Focused UI is optional and can be uninstalled via ''Help -> Software Updates -> Manage Configuration''.<br />
<br />
The following table summarizes how the key features can be toggled:<br />
<br />
<table><br />
<tr><br />
<td>'''UI Mechanism'''</td><br />
<td>'''Example/description'''</td><br />
<td>'''Toggle using'''</td><br />
</tr><br />
<tr><br />
<td>Interest filtering</td><br />
<td>Package Explorer</td><br />
<td>''Apply Mylar'' button on view toolbar</td><br />
</tr><br />
<tr><br />
<td>Automatic toggling of filtering</td><br />
<td>Package Explorer</td><br />
<td>''Preferences -> Mylar -> Context -> Toggle focused mode..</td><br />
</tr><br />
<tr><br />
<td>Interest decoration</td><br />
<td>Bolding of landmark elements</td><br />
<td>''Preferences -&gt; General -&gt; Appearance -&gt; Label Decoration''</td><br />
</tr><br />
<tr><br />
<td>Content assist</td><br />
<td>Ranking of interesting elements</td><br />
<td>Eclipse 3.2: ''Java -&gt; Editor -&gt; Content Assist -&gt; Work in Progress -&gt;'' turn off Mylar, turn on Java</td><br />
</tr><br />
<tr><br />
<td>Active change sets</td><br />
<td>Grouping of changes by tasks</td><br />
<td>''Preferences -&gt; Mylar -&gt; Team''</td><br />
</tr><br />
<tr><br />
<td>Editor management</td><br />
<td>Auto opening/closing of editors</td><br />
<td>''Preferences -&gt; Mylar -&gt; Editor Management''</td><br />
</tr><br />
<tr><br />
<td>Active views</td><br />
<td>Active Search and Hierarchy</td><br />
<td>Only on if view is active</td><br />
</tr><br />
</table><br />
<br />
For additional configuration options see the ''Mylar'' and ''General -> Appearance'' preference pages.<br />
<br />
== What is the performance profile of the Focused UI? ==<br />
<br />
The goal is for Mylar to have '''no noticeable effect''' on Eclipse's speed or memory usage.<br />
You do not need to increase the amount of memory Eclipse runs with to use Mylar. <br />
Any performance issue should be [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Mylar reported as a bug]. <br />
<br />
The current '''Performance Profile''' is:<br />
<br />
# Mylar only runs if a task is active, and has no impact on Eclipse if no task is active.<br />
# Task context models have negligible memory overhead. <br />
# When a task is active, additional view refresh is required to update the views based on interest model changes. This should not be noticeable on Windows where refresh is very quick, but could be more noticeable on other platforms.<br />
# The time to activate a task context is dominated by the time it takes Eclipse to open the editors in the context. You can set the preference for how many editors to open in the Mylar preference page (e.g. setting to 1 will dramatically reduce activation time, but also remove the benefit of having open editors correspond to the task context). You can also turn off editor management entirely in the Mylar Tasks view pull-down.<br />
# Eclipse startup is slowed down by (4) if a task is active when Eclipse is shut down.<br />
# The low priority background searches that the Active Search view runs can be noticeable on slower machines.<br />
<br />
== What happened to the Active Search and Active Hierarchy views? ==<br />
<br />
These views were not included in the Mylar 1.0 release because they never made it beyond the experimental phase. <br />
* The ''Active Search'' view has not been sufficiently tuned to adapt to the lifecycle of a task context, and as a result requires manual manipulation of the degree-of-separation scope as you work on long-running tasks. Otherwise it becomes overloaded with elements. In addition, it is not yet clear whether an additional view is the right UI for this facility, and it is hard to find room for an additional view of this size on screen resolutions of 1600x1200 and smaller.<br />
* The ''Active Hierarchy'' view is also hard to allocate space for, especially when using the in-place hierarchy (Ctrl+T) on a landmark can be a quick way to see the relevant part of the task context's hierarchy.<br />
<br />
These features still show promise in displaying task context and saving repetitive searches, so we have not removed them. They have instead moved to the Mylar Sandbox, and can be used and experimented with by following the [http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference#Sandbox instructions on the Contributors page]. For feedback on these views please use the corresponding bug reports or newsgroup.<br />
<br />
= Java Development =<br />
<br />
== Content assist troubleshooting ==<br />
<br />
Mylar uses custom Content Assist processors in order to rank and separate the elements in the current task context. To see proposals ranked according to interest you must have only the ''Type Proposals (Mylar)'' kinds checkbox enabled in the list below, otherwise you will see duplicates. '''If you do not see any proposals, check this list''' to ensure that either the Mylar or the plain proposals are enabled. '''To do this automatically''', run ''New -> Mylar -> Recommended Preferences''. Or you can select them manually as in the preference page below. <br />
<br />
[[Image:mylar-content-assist-prefs.gif]]<br />
<br />
'''Why do I see duplicate proposals?'''<br />
<br />
Ensure that you have only the ''(Mylar)'' proposals kinds enabled in ''Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced'', otherwise you will see duplicates.<br />
<br />
If you use proposals via Ctrl+Shift+Space instead of the typical Ctrl+Space you will see duplicates. Vote for JDT/Text [https://bugs.eclipse.org/bugs/show_bug.cgi?id=147781 bug 147781] if you use this mechanism. Also see: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=129080 bug 129080]<br />
<br />
'''Why do I get an error message when using content assist?'''<br />
<br />
If after invoking Content Assist you see an error message dialog that states:<br />
The extension took too long to return from the 'computeCompletionProposals()' operation<br />
this is most likely due to something interrupting the proposal operation (e.g. garbage collection). Ignore it if it does not recur, increase Eclipse's memory if it does (e.g via <code>-Xmx384M</code> command line argument). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=141457 bug 141457] for more details.<br />
<br />
== Why do interesting elements not show in the Project Explorer? ==<br />
<br />
The ''Package Presentation -> Hierarchical'' mode is not supported on the ''Project Explorer'' view in Eclipse 3.2 through 3.3M3 and possibly later versions (https://bugs.eclipse.org/bugs/show_bug.cgi?id=161362 bug 161362). Use the view menu to set ''Package Presentation -> Flat'' as a work-around.<br />
<br />
== How do I stop declarations from showing in the Package Explorer? ==<br />
<br />
If you don't like Mylar's constant showing of Java members in the ''Package Explorer'', select the drop-down menu, then ''Filters...'' and enable the ''Mylar Java Declarations Filter''. It will then stick in the menu in case you want to toggle between modes. Note that this will hide interest information about members that aren't in your current file (e.g. showing you which methods are landmarks) so this mode is not recommended, but can be useful for <code>1024x768</code> screen resolutions.<br />
<br />
[[Image:mylar-java-filtering-declarations.gif]]<br />
<br />
== Why does nothing show up in the Active Search or Active Hierarchy? ==<br />
<br />
As you work, elements become Landmarks (bold decoration), and these elements populate the ''Active Search'' and ''Active Hierarchy'' views. To force an element to populate the views manually, make it a Landmark by <code>right+clicking</code> or hitting <code>Ctrl+Alt+Shift+UpArrow</code>.<br />
<br />
== Known limitations ==<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=106678 Bug 106678]: The Project Explorer's Hierarchical Java package presentation layout is not supported on Eclipse 3.3Mx, and interesting elements will be hidden if enabled. Work-around is to use the default Flat package presentation.<br />
<br />
= Team Support =<br />
<br />
== Why are files missing from the task's change set? ==<br />
<br />
First, verify that you have [http://wiki.eclipse.org/index.php/Mylar_User_Guide#Configuring_the_Synchronize_view_for_change_sets configured the ''Synchronize View'' for change sets].<br />
<br />
The change set may have disappeared as a result of a commit. The work-around for this is to deactivate and reactivate the task.<br />
<br />
== Why do files disappear from the change set when I close them? ==<br />
<br />
If you have the ''Preferences -> Mylar -> Context -> Manage open editors to match task context'' option enabled, Mylar will perform editor management so that you don't have to. Closing a file makes it less interesting, and causes it to disappear from the active task context, and hence from the change set. This option prevents you from having to manage the set of open files, will automatically close editors for files that become uninteresting, and will ensure that the open editors match the task context.<br />
<br />
== Why is interest lost when I retrieve someone else's context? ==<br />
<br />
To identify elements within a project, Mylar relies on the name of the project being consistent across workspaces. If the project name in the workspace that the context was created with is different than its name in your workspace, the task context will not show elements within that project ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164058 bug 164058]). The work-around is to use the same project names across your team's workspaces.<br />
<br />
The other case where context can be lost is if the elements change names outside of the workspace ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164243 bug 164243]).<br />
<br />
= Misc =<br />
<br />
<br />
<br />
== How does Mylar relate to IBM's Jazz? ==<br />
<br />
At the EclipseCon and JavaONE 2006 conferences IBM demonstrated previews of Jazz, a collaborative team server and Eclipse-based client. Articles have remarked on the similarities between Mylar and Jazz because both integrate tasks into Eclipse (Jazz's "work items" and Mylar's "tasks"), and both provide change sets grouped by task. But there are both significant differences and complementary aspects to the two approaches. A key goal of Mylar is to provide an open source framework to support integration of task management with ''existing issue trackers and source repositories''. According to the presentations, components that come with Jazz include include a ''next-generation issue tracker and source repository'' and related lifecycle management tools such as project health. In addition, a driving and unique goal of Mylar is to focus the UI around a usage-based and degree-of-interested weighted task context, which is complementary to the Jazz platform. Just as it integrates with Mylar's Task List, Mylar's Task Focused UI and task context model components are possible to integrate with other kinds of task management systems, such as the one provided by Jazz.<br />
<br />
Update: at EclipseCon 2007 the IBM Jazz team showed a Mylar connector for Jazz.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/FAQ&diff=40870Mylyn/FAQ2007-06-27T03:29:15Z<p>Steffen.pingel.eclipse.org: /* Trac Connector */</p>
<hr />
<div>[[Category:Mylar]] <br />
<br />
[[Mylar User Guide]], <br />
[http://eclipse.org/mylar Mylar Home],<br />
[http://wiki.eclipse.org/index.php?title=Special:Userlogin&returnto=Special:Userlogout Log in to edit]<br />
<br />
For instructions on [http://wiki.eclipse.org/index.php/Mylar_User_Guide#Download_Mylar downloading] [http://wiki.eclipse.org/index.php/Mylar_User_Guide#Installation installing] and [http://wiki.eclipse.org/index.php/Mylar_User_Guide#Configuration configuring] <br />
Mylar, see the [[Mylar User Guide]]. For instructions on developing and contributing to Mylar, see the [[Mylar Contributor Reference]].<br />
<br />
= Installation =<br />
<br />
== What versions of Eclipse are supported? ==<br />
<br />
See the [http://eclipse.org/mylyn/dl.php download page].<br />
<br />
Mylyn also relies on a web browser that works with the Standard Widget Toolkit; Windows and MacOS users are fine, but Linux users might have to download another browser. See [http://www.eclipse.org/swt/faq.php#browserlinux the SWT Browser guide] for which browsers will work. See [http://wiki.eclipse.org/index.php/Mylar_User_Guide#Installing_Browser_on_Linux installing browser on Linux] for installation instructions.<br />
<br />
== What version of Java is required? ==<br />
<br />
Mylyn needs the '''Java 5''' virtual machine.<br />
<br />
To check the version of the Java virtual machine that Eclipse was launched with to to ''Help -> About Eclipse SDK -> Configuration Details'' and verify that the java.vm.version is 1.5. <br />
<br />
Mac users should refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
* If you do not have Java 5, you can download it from [http://72.5.124.55/javase/downloads/index.jsp Sun's web site]. <br />
* If you have more than one VM, you need to specify that Eclipse should use the JDK1.5 VM. <br />
<br />
In Unix, set the environment variable <code>JAVA_HOME</code> to the root of the JDK1.5 installation and/or set the <code>PATH</code> variable to put the JDK1.5 executable directory before any other VM executable directories. For example, under <code>bash</code> in Unix:<br />
export JAVA_HOME="''(location of JDK1.5 root)''"<br />
export PATH=$JAVA_HOME/bin:$PATH<br />
<br />
<b>We do [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140955 not recommend] using JDK 1.6 on Eclipse 3.1.</b> (It works fine with Eclipse 3.2 or 3.3.) To use JDK 1.6 on Eclipse 3.1, you must add the following line to your <code>config.ini</code>file:<br />
<code><br />
org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,<br />
J2SE-1.3,J2SE-1.4,J2SE-1.5,JavaSE-1.6<br />
</code><br />
<br />
== My tasks or queries disappeared, what do I do? ==<br />
<br />
This happens if Mylyn failed to install. First ensure that you have a correct install by following the instructions in the next section. After that, if you still do not see your tasks use the ''Task List'' view menu -> ''Restore Tasks From History...'' command (also available via ''File -> Import -> Task List''.<br />
<br />
== Installation Troubleshooting ==<br />
<br />
''' Update failures '''<br />
<br />
On Eclipse versions earlier than 3.3 (final) use '''only the "Search for new features.."''' option when updating Mylar. If you use "Search for updates..." the Update Manager will allow a partial install that can cause Mylar to fail to start, and you will need to run update again. See the ''feature configuration problem'' section below for details. If you encounter this problemm consider voting for Platform [https://bugs.eclipse.org/bugs/show_bug.cgi?id=132450 bug 132450].<br />
<br />
''' Startup exceptions '''<br />
<br />
If you see startup errors or warnings such as <code>BundleException</code> or timeout messages restart Eclipse with the <code>-clean</code> flag either on the command line, in your shortcut link, or by temporarily it into the <code>eclipse/eclipse.ini</code> file. If that does not resolve the problem please [http://www.eclipse.org/mylar/bugs.php file a bug].<br />
<br />
''' Incompatible VM (e.g. JDK 1.4) '''<br />
<br />
If you are using the wrong VM, you'll see errors like the following in your log file. <br />
<code><br />
Root exception: java.lang.UnsupportedClassVersionError:<br />
org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)<br />
</code><br />
<br />
See [[#Download_and_configure_Java_5_or_6|Configure Java]] to fix this problem.<br />
<br />
''' Incompatible version of Eclipse '''<br />
<br />
Separate versions and update sites exist [http://eclipse.org/mylar/dl.php for Eclipse 3.1 and 3.2]), in which case you may see errors like the following in your <code><workspace>/.metadata/.log </code>file or in a Mylar view:<br />
<code><br />
java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()<br />
The activator org.eclipse.mylar.java.MylarJavaPlugin for bundle org.eclipse.mylar.java is invalid<br />
</code><br />
<br />
''' Mylar feature configuration problem '''<br />
<br />
If the above do not address the issue, the easiest thing to do is uninstall any old versions and update to the latest Mylar. Your tasks won't be lost, because by default they are stored in the <code><workspace>/.mylar/tasklist.xml</code> file which will be read next time Mylar starts correctly. <br />
* First, uninstall the old version of Mylar using ''Help -> Software Updates -> Manage Configuration''. <br />
* You need to Disable all Mylar features by right-clicking them.<br />
* Allow Eclipse to restart after the last is disabled.<br />
* After restart, ensure that the 3rd toolbar button is pressed (figure below) so that you see the disabled features to uninstall.<br />
* Uninstall all the disabled features using the popup menu. <br />
<br />
If you don't uninstall, the the Update Manager will think that you have the latest and tell you that there are no updates. <br />
<br />
<b>Note: manually removing the plug-ins and features can lead to configuration errors.</b> <br />
<br />
After uninstalling, update Eclipse by adding the correct update site specified at on the [http://eclipse.org/mylar/dl.php download page], and after that automatically or manually updating will install the correct version.<br />
<br />
[[Image:mylar-eclipse-manage-configuration.gif]]<br />
<br />
'''What do I need to do in installation to be able to use Mylar task management features with bug/task/issue trackers?'''<br />
<br />
When you install, make sure that you select a connector for your bug/task/issue tracking software. For example, to use Bugzilla, you have to install the Bugzilla connector component.<br />
<br />
'''I've installed Mylar; why can't I see anything different?'''<br />
<br />
The two most likely possibilities are:<br />
# You don't have any Mylar views open. Select ''Window -> Show View -> Other'', then select ''Mylar'' and you should see the available Mylar Views. <br />
# If you still don't see anything, then perhaps you aren't using the JDK1.5 VM (or later). See [[Mylar_Installation_Guide#Download_and_configure_Java|configuring Java]].<br />
<br />
<br />
'''What does the error "Network connection problems encountered during search" mean?'''<br />
<br />
If you get that message while trying to download Mylar, it means that Eclipse couldn't find the location you entered. This might be because you copied something incorrectly (watch for extra characters -- even extra spaces can cause errors), or because the site went down. You may be able to see if the site is up or down by copying the URL into your Web browser.<br />
<br />
'''What does the "Update manager failure" message mean? '''<br />
<br />
It means that Eclipse could not access the update site, or that it got confused about the configuration state of your Eclipse. First try updating again to see if the update site is accessible. <br />
<br />
If you are trying to update the JIRA connector you can also try de-selecting that feature in case the <code>Tigris.org</code> update site is not accessible. Using ''Search for new features to install..'' when installing can help to avoid this problem. If that does not work see the feature configuration troubleshooting below. <br />
<br />
'''What does "Could not create Browser page: No more handles (<code>java.lang.UnsatisfiedLinkError: ...</code>)" mean?'''<br />
<br />
It probably means that you are running Linux and don't have Eclipse and a Web browser configured to work together. See [[http://wiki.eclipse.org/index.php/Mylar_User_Guide#Installing_Browser_on_Linux| installing a browser on Linux]].<br />
<br />
'''When downloading, why do I get a warning that the feature was unsigned?'''<br />
<br />
Signing plugins requires extra administrative details with <code>eclipse.org</code> which most plug-ins seek to avoid. <br />
<br />
'''N.B.''': Security issues with features should not be underestimated. Eclipse allows users to download new functionality from remote servers. A rogue plug-in can act as a perfect Trojan horse. It can look innocent enough and provide useful function while spawning threads in the background with full access to the local file system and the Internet (if connected). Beware of installing features from update sites you do not trust.<br />
<br />
'''What does "<code>Root exception: java.lang.UnsupportedClassVersionError: org/eclipse/mylar/tasklist/MylarTasklistPlugin (Unsupported major.minor version 49.0)</code>" mean?'''<br />
<br />
It probably means that the virtual machine is JDK1.4 or lower. See [[Mylar_Installation_Guide#Download_and_configure_Java| download and configure Java]].<br />
<br />
'''Why am I getting messages in my <code><workspace>/.metadata/.log</code> or my Mylar view that say things like <code>"java.lang.NoSuchMethodError: org.eclipse.ui.internal.dialogs.FilteredTree.getFilterControl()"</code> and "The activator <code>org.eclipse.mylar.java.MylarJavaPlugin</code> for bundle <code>org.eclipse.mylar.java</code> is invalid"?'''<br />
<br />
This probably means that your Mylar download version didn't match your Eclipse download version. Note that [http://eclipse.org/mylar/dl.php the download site] has different downloads for Eclipse 3.1 and Eclipse 3.2.<br />
<br />
To fix this problem, see the [[Mylar_Uninstallation_Guide| uninstallation guide]], then re-install from [http://eclipse.org/mylar/dl.php the correct download site].<br />
<br />
'''What does "Could not create Bugzilla editor input" and "<code>java.io.IOException</code>: SAX2 driver class <code>org.apache.xerces.parsers.SAXParser</code> not found" mean?'''<br />
<br />
It probably means that you are on MacOS, and for some reason are missing Xerces from the Mac JDK1.5. You will probably need to add it to your default classpath. Please refer to and comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=144287 bug 144287] if you see this problem.<br />
<br />
To ensure that you are using the 1.5 VM refer to the last comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=116347#c4 bug 1163477] for instructions on how to change the 1.4 default.<br />
<br />
'''I've just updated to Mylyn 2.0 and I don't see any tasks in my Task List'''<br />
<br />
As part of the update to Mylyn 2.0 the old data folder has been migrated to <workspace folder>/.metadata/.mylyn from the old location <workspace folder>/.mylar. IF for some reason migration failed (.mylar folder still exists), simply shut down Eclipse and manually move your old <workspace folder>/.mylar folder to <workspace folder>/.metadata/.mylyn (note the name change to .mylyn)<br />
<br />
== Configuration Troubleshooting == <br />
<br />
'''How can I change the number of editors left open before Mylar starts closing editors?'''<br />
<br />
Turn off or increase the number of editors to leave open using ''Preferences -> General -> Editors -> Number of opened editors before closing''. Since Mylar will manage the open editors with task activation, this number can be set higher or you can disable automatic closing entirely.<br />
<br />
'''Do I need the Outline View when running Mylar?'''<br />
<br />
No, not really. The Package Explorer and folded signatures should provide enough context for you. If, at some point, you really need to see an Outline View, you can always enter (Ctrl+O) to show the in-place Outline View.<br />
<br />
'''What does the message "content assist proposals no longer appear" mean?'''<br />
<br />
This usually happens when uninstalling when using Eclipse 3.2. Make sure that the "Java Completions" and "Java Types" proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylar FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
'''Why do I get errors like "HTTP Response Code 407" or "Proxy Authentication Error" when accessing repositories through a proxy server?'''<br />
<br />
It is likely that you need to configure these proxy server settings. Select ''Window -> Preferences -> Install/Update'', and update the section in the "Proxy settings" section of the form.<br />
<br />
'''I can't use <code>Ctrl+Alt+Shift+Arrow Up</code> for'' Mark as Landmark''. What do I do?<br />
<br />
This is usually a Linux/GNOME problem, where the Gnome keyboard shortcuts are interfering with the Eclipse shortcuts. Go to the Keyboard shortcuts (which might be something like ''Desktop -> Control Centre -> Keyboard Shortcuts'' or ''System -> Preferences -> Keyboard Shortcuts'') and disable both of these shortcuts:<br />
* Move one workspace up<br />
* Move one workspace down<br />
<br />
See also: [[Mylar_User_Guide#Keyboard_mappings_on_Linux| keyboard mappings on Linux]].<br />
<br />
'''How do I turn on spell checking?'''<br />
<br />
See [[Mylar_User_Guide#Spell_Checking| spell checking]].<br />
<br />
== Uninstall troubleshooting ==<br />
<br />
When '''uninstalling in Eclipse''' Mylar via the ''Help -> Software Updates -> Manage Configuration'' dialog you will need to uninstall dependencies first (e.g. Bugzilla Connector, Subclipse integration) and then uninstall the core Mylar features.<br />
<br />
When '''uninstalling manually''' by deleting all of the Mylar plug-ins and features from the <code>eclipse/plugins</code> and <code>eclipse/features</code> directory make sure to delete all of the plug-ins and then restart Eclipse with the -clean option (e.g. by inserting it into a shortcut or the <code>eclipse.ini</code> file.<br />
<br />
On '''Eclipse 3.1:''' you may need to reset the Java editor to be default for <code>.java</code> again via: ''Preferences -> General -> Editors -> File Associations''<br />
<br />
On '''Eclipse 3.2:''' if after uninstalling '''content assist proposals no longer appear''' you need to ensure that the ''Java Completions'' and ''Java Types'' proposal categories are included in the default proposals via: ''Preferences -> Java -> Editor -> Content Assist -> Advanced -> Restore Defaults''. Also see: [[Mylar FAQ#Content assist troubleshooting| content assist troubleshooting]]. This [https://bugs.eclipse.org/bugs/show_bug.cgi?id=140416 bug] has been fixed in Eclipse 3.2.1.<br />
<br />
== I am seeing <code>java.lang.OutOfMemoryError: PermGen space </code>errors, what's wrong? ==<br />
<br />
If your Eclipse crashes, or you see the above error after installing Mylar or other plug-ins, you have most likely hit the infamous MaxPermSize bug. This is not a Mylar specific problem, but a general Eclipse problem that is often triggered on Eclipse 3.2 and later, if you have many plug-ins installed and are using a Sun JVM. <br />
<br />
To fix it simply add the following to your launch arguments. This is usually to your shortcut, or to the <tt>eclipse/configuration/config.ini</tt> file:<br />
<br />
-XX:MaxPermSize=128M<br />
<br />
If you are using a large number of plug-ins (e.g. WTP) you may need to increase the number to more than 128M. <br />
<br />
Details of the problem are on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=92250 Platform bug 92250].<br />
<br />
= Task List =<br />
<br />
== Why won't the Archive category disappear? ==<br />
<br />
The ''Archive'' category will automatically appear if a task needs to be shown, but is not in any query or category. <br />
In order to ensure that you do not miss reminders or notifications the following tasks will always be shown in the Task List, even if they have been removed from a category or a query:<br />
* Tasks scheduled for this week or overdue. Remove these by using the ''Schedule'' pop-up menu option to defer them to a future week or to clear the schedule.<br />
* Repository tasks that have incoming changes, such as comments. Remove these by reading them or marking them as "read" via the ''Mark -> Read'' pop-up menu.<br />
<br />
== How do I prevent long-running tasks from adding to the progress bar? ==<br />
<br />
If you have many long-running or recurring tasks scheduled for this week, they can affect the ''Task List'' weekly progress bar. This can be misleading as they may never be completed. The current work-around to prevent long-running tasks from being included in the weekly progress bar is to schedule their estimated time to be 0 (zero). Alternatively, you can schedule only the amount of time you plan on spending on that task this week.<br />
<br />
== Does the Task List replace the Eclipse Tasks view? ==<br />
<br />
The SDK's ''Tasks'' view is used for showing markers such as 'todo' tags which indicate a local problem with a resource, similar to a compiler warning. As such, these 'tasks' are at a much lower level of granularity than Mylar's tasks, and one task could involve cleaning up multiple todos. In order to make working with only the markers in a particular task context, e.g. for clean-up before committing, the ''Apply Mylar'' filter is available for both the ''Problems'' and the ''Tasks'' views.<br />
<br />
== What if I use multiple workspaces? ==<br />
<br />
Mylar's support for multiple workspaces is currently limited (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=130658 bug 130658] for a discussion) because the Task List is considered to be specific to the person, and not to the workspace. We recommend configuring your Eclipse workspace to use working sets instead of relying on multiple workspaces. <br />
* John O'Shea's blog: [http://www.xlml.com/aehso/2007/02/02/eclipse-workspaces-containing-projects-with-overlapping-locations-and-mylar/ Eclipse workspaces containing projects with overlapping locations, and Mylar]<br />
<br />
If using a single workspace is not possible you can do the following:<br />
* In ''Preferences -> Mylar -> Task List'' set the ''Data Directory'' to be a shared location, and do this for both workspaces.<br />
* Be sure to avoid launching both Eclipse workspaces at the same time, as changes in one workspaces could overwrite the Task List in the other workspace.<br />
* If you upgrade Eclipse or move your workspace and don't see your tasks, check the ''Data Directory'' setting.<br />
<br />
== How do I export my task and repository data? ==<br />
<br />
Export via File > Export > Mylar > Task Data<br />
<br />
== Why does Mylar use the term "task"? ==<br />
<br />
There are many work items that make up the developer's workday. Many issue trackers and project management tools refer to these as: bugs, defects, actions, tickets, stories, enhancements, and the list goes on. We refer to all such work items as "tasks" because the word tasks is short and commonly used in time management tools. Task Repository connectors can customize the presentation of tasks, for example, indicating which is a defect and which is an action item.<br />
<br />
= Task Repositories =<br />
<br />
== What if Mylar doesn't support my task/bug/issue/ticket repository? ==<br />
<br />
To see support for your repository faster, do a search of the open repository connector requests and [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=anywordssubstr&short_desc=%5Bconnector%5D&product=Mylar&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=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= vote for the corresponding bug] if your tracker is there, or [http://www.eclipse.org/mylar/bugs.php create a new bug]. <br />
<br />
[[Mylar_User_Guide#Generic_Web_Repository_Connector|Generic Repository Connector]], allows creating Queries to the web-based issue tracking repositories and get list of issues from the web UI into the Task List.<br />
<br />
It is also possible to link a ''local task'' with the web page in web-based repository via the Mylar Web integration.<br />
<br />
'''To create a task from any web-based repository:'''<br />
<br />
* Drag the URL from the address bar of the browser, or from a hyperlink in a bug listing to the ''Mylar Tasks'' view. This will create a task for the bug, link it to the page, and populate the description with the title of the corresponding page. '''In Mozilla:''' simply drag the URL. '''In Internet Explorer:''' you must have <code>Ctrl</code> pressed in order for Eclipse to recognize the drop.<br />
* '''Alternatively,''' you can copy the URL, press the ''New Task'' button on the ''Mylar Tasks'' view. This has the same effect as above but you can edit the description after retrieving it.<br />
* Opening the task will now open the corresponding issue. You can also <code>right+click</code> the task and select ''Open in External Browser''.<br />
<br />
[[Image:mylar-tasklist-weblink-editor.gif]]<br />
<br />
== Why were my repository credentials reset? ==<br />
<br />
If you upgrade Eclipse or your Java VM, you will need to reset your credentials in the ''Task Repositories'' view because these are stored in the secure Eclipse workbench keyring. Also see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=149607 bug 149607]. If you are migrating '''from Eclipse 3.2 to 3.3''' note that you will need to use a different update site: http://eclipse.org/mylar/dl.php<br />
<br />
== Why are my updated repository attributes not showing up? ==<br />
<br />
Your server's repository attributes can change frequently, for example, there can be a new "milestone" or "version" added to the Bugzilla repository with each release. When the ''Preferences -> Mylar -> Task List -> Synchronization'' setting is enabled, every 10th synchronization will update the attributes from the repository. If you do not have this setting enabled, your can force the update via the ''Update Attributes'' action on the task repositories' context menu in the ''Task Repositories'' view. Note that you will need to reopen a task editor to see the updated attributes.<br />
<br />
== Authentication Troubleshooting ==<br />
<br />
You must ensure repository credentials are filled out correctly. Refer to the diagram below:<br />
<br />
[[image: AuthenticationTroubleshooting2.png|right]]<br />
<br />
# Enter the repository URL (i.e. https://bugs.eclipse.org/bugs) and an optional label<br />
# Credentials<br />
#* Usually email address and password <br />
#* Some sites, such as <code>dev.eclipse.org</code>, use anonymous logon with password left blank.<br />
#Http Authentication (optional)<br />
#* Some sites are protected by either BASIC or DIGEST http authentication. If this is the case, enter appropriate credentials here.<br />
#* One way to test if the site requires http authentication is to point your browser at the repository. If you are presented with an authentication dialog popup, the site is likely protected by http authentication.<br />
#Proxy Server Configuration (optional)<br />
#* By default Mylar uses the Platform's Install/Update proxy settings. Uncheck this box if you wish to use an alternative proxy.<br />
#* If the proxy requires authentication, this is where you enable and enter your proxy credentials.<br />
#* If you are experiencing connection problems, ensure your Install/Update proxy settings are valid or the repository specific settings are correct<br />
#* Mylar has been tested with HTTP proxy servers. Currently SOCKS is not supported.<br />
#Validate Settings <br />
#*Press the ''validate'' button to test the settings<br />
#*If you are seeing errors like "HTTP Response Code 407" or "Proxy Authentication Error" it is likely that you need to configure proxy settas as described above.<br />
#*If your sever uses a certificate and fails to connect, e.g. you see exceptions <tt>sun.security.validator.ValidatorException: PKIX path building failed</tt> then you need to point Eclipse at your certificate, see the [http://ahtik.com/blog/2006/05/11/fixing-eclipse-mylar-jira-integration/ instructions on this blog].<br />
<br clear="all" /><br />
<br />
= Bugzilla Connector =<br />
<br />
== What versions are supported? ==<br />
<br />
We recommend using the latest [http://www.bugzilla.org/download/ release] of Bugzilla.<br />
<br />
* '''Bugzilla 2.18.6 is the lowest version of Bugzilla supported'''. If you are getting errors that indicate failure to update attributes this may be an indication that the Bugzilla server is not supported (< 2.18.6).<br />
<br />
*If you are using '''Bugzilla 2.18''' and are getting '''mid-air collisions''' this is likely due to incorrectly formatted timestamp field in the underlying bugs database table ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=149513 bug 149513]). This can be resolved by upgrading to Bugzilla 2.20 or later.<br />
<br />
== Why are queries failing? ==<br />
<br />
*If '''queries are not working''' correctly ensure that you have the right Bugzilla server version selected for the corresponding repository: ''Task Repositories (View) ->'' right+click the repository ''-> Properties''. For supported versions see the [http://www.eclipse.org/mylar/dl.php download page]. If the repository is still not functioning it may be due to authentication or connectivity problems. If that does not resolve the problem please post a message to the newsgroup or [http://www.eclipse.org/mylar/bugs.php submit a bug].<br />
<br />
== Why do tasks fail to open? ==<br />
<br />
*If upon opening a bug, the Bugzilla tab only displays a warning "'''Could not download task data, possibly due to timeout or connectivity problem. Please check connection and try again.'''", ensure that your repository is returning XML data by pointing your browser to <code><your-repository-url>/show_bug.cgi?id=1&ctype=xml</code> to show the contents of bug 1 in XML form. The Bugzilla client requires that bugs be accessible in XML form. If the repository doesn't support xml then it is likely that the repository is too old (Mylar currently supports Bugzilla 2.18 and later).<br />
<br />
* If '''reports fail to load''' or '''reports fail to synchronize''' (task description remains ''italic''), check the error log for a "'''File not found'''" error pointing to <code>bugzilla.dtd</code> or a "'''Failed to retrieve products from server'''" error message - these result when the <code>urlbase</code> parameter is not set on the bugzilla server, or your bugzilla installation is missing the <code>bugzilla.dtd</code> file. See: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=161759 bug#161759]<br />
<br />
* If '''attributes are missing options''' in the bug editor (ie. missing a recently added milestone, [https://bugs.eclipse.org/bugs/show_bug.cgi?id=155431 bug# 155431]):<br />
** Update attributes by choosing ''Update Attributes'' from the context menu in the ''Task Repositories'' view<br />
** Synchronize the task in the Task List<br />
** Reopen the task - new options should be available.<br />
<br />
== Why do tasks fail to submit? ==<br />
<br />
* '''Error upon submit: unable to make any match for name/email entered.''' If your bugzilla is configured for user names rather than full email address the QA Contact field will cause the submit to fail ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=166555 bug# 166555]). To resolve, select 'Local users enabled' option on the Repository Configuration page. <br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your account's username and password and are not using the HTTP authentication fields instead.<br />
<br />
* If tasks '''fail to submit''' with credentials error, but the repository validates fine, make sure that you've correctly setup your bugzilla instance's cookie domain under the required settings. The cookie domain must lead with a dot.<br />
<br />
* If '''attachments are failing to submit''' and you see that after processing the attachment, the bugzilla bug shows a size of "bytes" (no numbers), your database may be dropping the packet sending the file. '''On MySQL''', check the [http://dev.mysql.com/doc/refman/5.0/en/packet-too-large.html max_allowed_packet directive]. You may see errors like: <code>DBD::mysql::st execute</code> failed: Got a packet bigger than 'max_allowed_packet' bytes [for Statement "INSERT INTO attach_data (id, thedata) VALUES (38, ?)"] at <code>/path/to/bugzilla/attachment.cgi</code> line 993. Also, '''check the maximum attachment size''' in ''Bugzilla Parameters -> Attachments''.<br />
<br />
* If a submit fails with an '''Invalid Username or Password''' error even though repository settings do validate, make sure that cookies could be set. See also [https://bugs.eclipse.org/bugs/show_bug.cgi?id=175502 bug 175502]<br />
<br />
== What time zone is used in the task editor? ==<br />
<br />
*The '''times''' that appear in the Bugzilla bug editor (ie. created, modified) '''are local to the server hosting the Bugzilla repository''', not your local machine's time zone. <br />
<br />
== Known limitations ==<br />
<br />
* The <code>usermatchmode</code> is not currently supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168204 bug 168204]) and as such full email addresses need to be used.<br />
<br />
* The <code>usevisibilitygroups</code> parameter is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=180876 bug#180876]). Group assignment will currently be lost if updated using the Bugzilla rich task editor.<br />
<br />
* Version 1.0 of Mylar presents an error message upon new comment submission to RedHat's public Bugzilla repository. The comment is in fact posted. This issue is resolved in Mylar 2.0M2 and higher. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=183251 bug#183251])<br />
<br />
= JIRA Connector =<br />
<br />
If you see errors like the following, work around this by opening repository ''Properties Page'' and clicking OK (bug [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169102 169102]).<br />
<br />
org.tigris.jira.core.service.exceptions.AuthenticationException<br />
at org.tigris.jira.internal.core.service.soap.SoapJiraService.getProjectsNoSchemes(SoapJiraService.java:204)<br />
<br />
== What are the server requirements? ==<br />
<br />
The '''JIRA SOAP/RPC services have to be running on the JIRA server''':<br />
<br />
* Jira 3.3.3 or higher (3.7 or higher for attachment retrieval)<br />
* Jira RPC plugin 1.4.3 or higher<br />
<br />
Latest information also available on the [http://www.eclipse.org/mylar/dl.php download page].<br />
<br />
Related Resources:<br />
<br />
* [http://confluence.atlassian.com/display/JIRA/JIRA+Development+Hub Jira Development Wiki]<br />
* [http://confluence.atlassian.com/pages/viewpage.action?pageId=1035 Jira RPC Plugin Overview]<br />
<br />
== Why can't I connect? ==<br />
<br />
* If you get a <code>org.tigris.jira.core.service.exceptions.ServiceUnavailableException</code> you need to turn on the JIRA SOAP/RPC services on the server.<br />
* If you get a '''503''' error code verify that the SOAP/RPC interface is enabled.<br />
* If you get a '''403''' error code verify that the SOAP/RPC interface is enabled, and also check your authentication mechanism. If the server is using NTLM authentication, see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=156397 bug 156937] for diagnosis steps.<br />
* If you see an '''"unrecognized priority" message''' in the ''Error Log'', the problem is that the JIRA Connector does not support customized priorities so the priority value specified in that message will not correspond to the priority icons visible in the Task List.<br />
* If you are being '''prompted for your log-in credentials''' by the Browser tab of the task editor or the new task editor, this is because without rich editor support the connector is using the web-based UI instead of logging in on your behalf as is done with a rich task editor ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=142869 bug 142869]).<br />
* If you get a <CODE>AuthenticationException</code> and a query won't synchronize, use Task Repositories (view) -> Properties (on the repository) -> Validate Settings. This will clear the connection if it died.<br />
<br />
== Why can't I synchronize when using a proxy server? ==<br />
<br />
* Proxy configuration is be '''based on the normal Java HTTP system properties''', which can be configured either by launching Eclipse with <code>-vmargs</code> and using the following settings, or by putting these settings into the or by putting the following into the <code>eclipse/eclipse.ini</code> file (after -vmags):<br />
-Dhttp.proxyHost=<host> <br />
-Dhttp.proxyPort=<port><br />
* Make sure that when using these settings you do not enable the proxy settings on the ''Install/Update'' preference page, since they may override these settings.<br />
* If you are using '''SSL''', you will also need to set the <code>https.proxyHost</code> and <code>https.proxyPort</code>. <br />
* Authentication is configured with the <code>http.proxyUser</code> and <code>http.proxyPassword</code> system properties (also for SSL)<br />
* You can also use <code>http.nonProxyHosts</code> system property to enumerate hosts that should not be proxied. Note that matching is implemented on the exact host name used for JIRA server and patterns are not supported.<br />
<br />
== Known limitations ==<br />
* Attachments are not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=169757 bug 169757])<br />
* NTLM authentication is not supported ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=172395 bug 172395])<br />
* Customized priorities are not currently supported, so all issues with a customized priority will have the default priority level ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=165518 bug 165518]).<br />
* On JIRA 3.6.x private filters saved on the server can fail to retrieve results ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=174328 bug 174328]). The work-around is to create a custom query in Mylar using the form-based query designer or to share the filter in JIRA.<br />
* Attachment retrieval (including retrieval of the task context and attachment list in the task editor) require JIRA 3.7 or above.<br />
<br />
== How can I enable compression for SOAP messages? ==<br />
<br />
If your repository has lots of projects and components you can speed up the download of the repository configuration by enabling compression. <br />
<br />
* Add a filter-mapping to your JIRA server configuration: [http://jira.atlassian.com/browse/JRA-10353].<br />
* Enable compression in your global JIRA configuration.<br />
* Check the compression setting for your task repository in Mylar versions 2.0M2 and later.<br />
<br />
= Trac Connector =<br />
<br />
== What are the server requirements? ==<br />
<br />
The Trac connector offers two access methods:<br />
<br />
'''XML-RPC''' (recommended)<br />
<br />
Requirements:<br />
* Trac 0.10<br />
* [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] rev. 1950<br />
<br />
This access method offers editing of tasks in a rich editor, attachment support and offline editing. It requires the [http://trac-hacks.org/wiki/XmlRpcPlugin XmlRpcPlugin] for Trac to be enabled for the accessed repository. The XmlRpcPlugin provides a remote interface to the Trac repository and is distributed separately from Trac (see [http://trac.edgewall.org/ticket/217 #217]). See these [http://trac-hacks.org/wiki/XmlRpcPlugin#Installation install instructions] for requirements and documentation.<br />
<br />
'''Web''' <br />
<br />
Requirements:<br />
* Trac 0.9 or later<br />
<br />
In this mode the standard Trac web interface is used for repository access. Tickets may be created and edited through a web browser. Offline editing and attachments are not supported.<br />
<br />
== Recommended Trac version ==<br />
<br />
Mylar should work with any stable release Trac release that is version 0.9.x or 0.10.x (see below for known limitations). Mylar works best when used with Trac's XML-RPC Plugin (see above) but we do not recommend a particular Trac version. <br />
<br />
The Trac connector tests are run against these Trac versions:<br />
<br />
* Trac 0.10, XML-RPC Plugin rev. 1950<br />
* Trac 0.9.6<br />
<br />
== Why do I get an HTTP Error 500 Internal server error when creating a Ticket that contains non-ASCII characters? ==<br />
<br />
Problems related to character encodings have been reported when Trac is run with Python 2.3. Upgrading to Python 2.4 may help to resolve this. Please comment on [https://bugs.eclipse.org/bugs/show_bug.cgi?id=188363 bug #1883639] if you encounter an internal server error when creating a Ticket that contains non-ASCII characters.<br />
<br />
== Known limitations ==<br />
<br />
* Trac 0.10.1 <br />
** Known incompatibility with Trac XML-RPC Plugin. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164272 bug 164272] for details.<br />
* Trac 0.10.3 <br />
** Known incompatibility with old versions of the Trac HttpAuthPlugin (fixed in revision 1890 or later). The plug-in enables basic auth for XML-RPC when Trac AccountManagerPlugin for form based authentication is used. See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168413 bug 168413] for details.<br />
* Trac 0.11<br />
** Currently untested.<br />
** Known incompatibility with Trac XML-RPC Plugin See [http://trac-hacks.org/wiki/XmlRpcPlugin] for details.<br />
<br />
== Why are tasks opened in a web browser and not in the rich editor? ==<br />
<br />
Please make sure that the access type in the repository properties is set to XML-RPC. This requires Trac 0.10 and XML-RPC (see above).<br />
<br />
= Generic Web Repository Connector =<br />
<br />
== Why can't I connect using one of the existing templates? ==<br />
<br />
<br />
The Web Repository Connector have a Preview option in Advanced Configuration section on the Query preferences. If you get an error or preview table does not show expected list of tasks you can use Query Pattern like (.+?)(\n) to see content of the retrieved page and compare it with the source of the web page for the same url loaded into the web browser.<br />
<br />
If that does not help then you could use the wget tool (on Windows it available as a standalone command line tool and also included with Cygwin).<br />
<br />
Run the following command:<br />
<br />
<pre>wget -v -d -o query.log -O query.html "http://your.query.url"</pre><br />
<br />
If repository require basic http auth, you'll need to use ''--http-user=USER'' and ''--http-password=PASS'' options.<br />
<br />
Then open file ''query.html'' in the web browser and check if it show list of issues you need to fetch from the web server. If it does have correct list, then there could be a problem with query pattern used for parsing. <br />
<br />
A popular mistake is an unmasked '?' that separates request parameters in the url). For example:<br />
<br />
<pre><a href="show_bug.cgi\?id\=(.+?)">.+?<span class="summary">(.+?)</span></pre><br />
<br />
If ''query.html'' does not show expected list of issues you can check ''query.log'' for server responses and try to identify if server require authentication, redirecting your requests somewhere or issue any other errors.<br />
<br />
== Known limitations ==<br />
<br />
* In Mylar 1.0: if a web server responds by requesting a redirect to an absolute URL while fetching a resource, the connector falsely prepends "/" to the URL and the request will fail. The workaround is to use final url where redirect is pointing to (you can find it as describe above). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=167282 bug 167282] for details.<br />
<br />
<br />
= Task-Focused UI =<br />
<br />
== What is the Task-Focused UI? ==<br />
<br />
When you activate a task, Mylar automatically maintains a task context by monitoring your interaction. The task context provides a predictable degree-of-interest weighting of the relevance of the elements and relations that you work with to the task-at-hand (as described in the [http://kerstens.org/mik/publications/2006-11-mylar-fse.pdf Foundations of Software Engineering conference paper]). The Task-Focuse UI is the mechanism by which Mylar presents Mylar the task-context model in order to reduce information overload and to automate the manaul management of UI elements like editors and change sets. Examples:<br />
* Filtering, decoration and expansion management in views<br />
* Automatic folding in editors<br />
* Ranking in content assist<br />
* Editor management<br />
* Perspective management<br />
* Change set management<br />
<br />
== Why do files disappear from Focused views when I close them? ==<br />
<br />
By default Mylar automatically manages the set of open files to match the task context, so that you don't have to. This ensures that the editor list (viewable via mechanisms like Ctrl+E) corresponds to what you in views like the ''Package Explorer'' when they are in Focused mode. When you close a file manually, you express that it is uninteresting, and as such it will be removed from the task context. It will also disappear from the corresponding automatically managed change sets for the same reason. This behavior can be turned off via ''Preferences -> Mylar -> Context -> Manage open editors to match task context''. However, it is highly recommended since Mylar will prevent the number of editors from bloating by automatically closing editors for elements that have decayed in interest, and always keep the editors for interesting elements open.<br />
<br />
<br />
== Why did all my editor tabs disappear? ==<br />
<br />
When you deactivate a task, all editors will be closed, and then when you reactivate the task all the windows will be open again. Try it, it's fun. <br />
<br />
Mylar actively manages your open editors with task context. It takes some getting used to, but enables switching between tasks when you are multitasking without cluttering your editor tabs. This editor management can be disabled via ''Window -> Preferences -> Mylar -> Context''. However, before disabling it consider reading the ''"Managing open editors..."'' section of [http://www-128.ibm.com/developerworks/java/library/j-mylar2/index.html#N10116 Task-focused programming with Mylar].<br />
<br />
== How do I get rid of an element if it is not interesting? ==<br />
<br />
When a view is focused elements will disappear on their own if they are not repeatedly selected via a mechanism called interest decay. Note that decay does not use the wall clock, but instead relies on the number of selections that you have made when working on that task to determine which elements disappear. This helps make it feel very predictable.<br />
<br />
If you want want to force one or more elements to disappear from the context use the '''Remove from Focus''' action on the context menu. Note that the element will still be part of the task context since it was previously part of the interaction. <br />
<br />
If you want to permanently delete the element from the interaction history use the '''Remove from Context''' action on the '''Context''' tab of the '''Task Editor'''. For example, if a company private element was part of a task context that is to be shared with a public repository, this action can be used to clean it up before sharing. Note that elements will be removed from the task context recursively.<br />
<br />
== Which Focused UI features can I turn off? ==<br />
<br />
'''All of them.''' When no task is active neither are any of Mylar's features. When working with task contexts Mylar's Focused UI features are all optional and in general configurable. While many find it the key benefit of Mylar, the entire Focused UI is optional and can be uninstalled via ''Help -> Software Updates -> Manage Configuration''.<br />
<br />
The following table summarizes how the key features can be toggled:<br />
<br />
<table><br />
<tr><br />
<td>'''UI Mechanism'''</td><br />
<td>'''Example/description'''</td><br />
<td>'''Toggle using'''</td><br />
</tr><br />
<tr><br />
<td>Interest filtering</td><br />
<td>Package Explorer</td><br />
<td>''Apply Mylar'' button on view toolbar</td><br />
</tr><br />
<tr><br />
<td>Automatic toggling of filtering</td><br />
<td>Package Explorer</td><br />
<td>''Preferences -> Mylar -> Context -> Toggle focused mode..</td><br />
</tr><br />
<tr><br />
<td>Interest decoration</td><br />
<td>Bolding of landmark elements</td><br />
<td>''Preferences -&gt; General -&gt; Appearance -&gt; Label Decoration''</td><br />
</tr><br />
<tr><br />
<td>Content assist</td><br />
<td>Ranking of interesting elements</td><br />
<td>Eclipse 3.2: ''Java -&gt; Editor -&gt; Content Assist -&gt; Work in Progress -&gt;'' turn off Mylar, turn on Java</td><br />
</tr><br />
<tr><br />
<td>Active change sets</td><br />
<td>Grouping of changes by tasks</td><br />
<td>''Preferences -&gt; Mylar -&gt; Team''</td><br />
</tr><br />
<tr><br />
<td>Editor management</td><br />
<td>Auto opening/closing of editors</td><br />
<td>''Preferences -&gt; Mylar -&gt; Editor Management''</td><br />
</tr><br />
<tr><br />
<td>Active views</td><br />
<td>Active Search and Hierarchy</td><br />
<td>Only on if view is active</td><br />
</tr><br />
</table><br />
<br />
For additional configuration options see the ''Mylar'' and ''General -> Appearance'' preference pages.<br />
<br />
== What is the performance profile of the Focused UI? ==<br />
<br />
The goal is for Mylar to have '''no noticeable effect''' on Eclipse's speed or memory usage.<br />
You do not need to increase the amount of memory Eclipse runs with to use Mylar. <br />
Any performance issue should be [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Mylar reported as a bug]. <br />
<br />
The current '''Performance Profile''' is:<br />
<br />
# Mylar only runs if a task is active, and has no impact on Eclipse if no task is active.<br />
# Task context models have negligible memory overhead. <br />
# When a task is active, additional view refresh is required to update the views based on interest model changes. This should not be noticeable on Windows where refresh is very quick, but could be more noticeable on other platforms.<br />
# The time to activate a task context is dominated by the time it takes Eclipse to open the editors in the context. You can set the preference for how many editors to open in the Mylar preference page (e.g. setting to 1 will dramatically reduce activation time, but also remove the benefit of having open editors correspond to the task context). You can also turn off editor management entirely in the Mylar Tasks view pull-down.<br />
# Eclipse startup is slowed down by (4) if a task is active when Eclipse is shut down.<br />
# The low priority background searches that the Active Search view runs can be noticeable on slower machines.<br />
<br />
== What happened to the Active Search and Active Hierarchy views? ==<br />
<br />
These views were not included in the Mylar 1.0 release because they never made it beyond the experimental phase. <br />
* The ''Active Search'' view has not been sufficiently tuned to adapt to the lifecycle of a task context, and as a result requires manual manipulation of the degree-of-separation scope as you work on long-running tasks. Otherwise it becomes overloaded with elements. In addition, it is not yet clear whether an additional view is the right UI for this facility, and it is hard to find room for an additional view of this size on screen resolutions of 1600x1200 and smaller.<br />
* The ''Active Hierarchy'' view is also hard to allocate space for, especially when using the in-place hierarchy (Ctrl+T) on a landmark can be a quick way to see the relevant part of the task context's hierarchy.<br />
<br />
These features still show promise in displaying task context and saving repetitive searches, so we have not removed them. They have instead moved to the Mylar Sandbox, and can be used and experimented with by following the [http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference#Sandbox instructions on the Contributors page]. For feedback on these views please use the corresponding bug reports or newsgroup.<br />
<br />
= Java Development =<br />
<br />
== Content assist troubleshooting ==<br />
<br />
Mylar uses custom Content Assist processors in order to rank and separate the elements in the current task context. To see proposals ranked according to interest you must have only the ''Type Proposals (Mylar)'' kinds checkbox enabled in the list below, otherwise you will see duplicates. '''If you do not see any proposals, check this list''' to ensure that either the Mylar or the plain proposals are enabled. '''To do this automatically''', run ''New -> Mylar -> Recommended Preferences''. Or you can select them manually as in the preference page below. <br />
<br />
[[Image:mylar-content-assist-prefs.gif]]<br />
<br />
'''Why do I see duplicate proposals?'''<br />
<br />
Ensure that you have only the ''(Mylar)'' proposals kinds enabled in ''Window -> Preferences -> Java -> Editor -> Content Assist -> Advanced'', otherwise you will see duplicates.<br />
<br />
If you use proposals via Ctrl+Shift+Space instead of the typical Ctrl+Space you will see duplicates. Vote for JDT/Text [https://bugs.eclipse.org/bugs/show_bug.cgi?id=147781 bug 147781] if you use this mechanism. Also see: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=129080 bug 129080]<br />
<br />
'''Why do I get an error message when using content assist?'''<br />
<br />
If after invoking Content Assist you see an error message dialog that states:<br />
The extension took too long to return from the 'computeCompletionProposals()' operation<br />
this is most likely due to something interrupting the proposal operation (e.g. garbage collection). Ignore it if it does not recur, increase Eclipse's memory if it does (e.g via <code>-Xmx384M</code> command line argument). See [https://bugs.eclipse.org/bugs/show_bug.cgi?id=141457 bug 141457] for more details.<br />
<br />
== Why do interesting elements not show in the Project Explorer? ==<br />
<br />
The ''Package Presentation -> Hierarchical'' mode is not supported on the ''Project Explorer'' view in Eclipse 3.2 through 3.3M3 and possibly later versions (https://bugs.eclipse.org/bugs/show_bug.cgi?id=161362 bug 161362). Use the view menu to set ''Package Presentation -> Flat'' as a work-around.<br />
<br />
== How do I stop declarations from showing in the Package Explorer? ==<br />
<br />
If you don't like Mylar's constant showing of Java members in the ''Package Explorer'', select the drop-down menu, then ''Filters...'' and enable the ''Mylar Java Declarations Filter''. It will then stick in the menu in case you want to toggle between modes. Note that this will hide interest information about members that aren't in your current file (e.g. showing you which methods are landmarks) so this mode is not recommended, but can be useful for <code>1024x768</code> screen resolutions.<br />
<br />
[[Image:mylar-java-filtering-declarations.gif]]<br />
<br />
== Why does nothing show up in the Active Search or Active Hierarchy? ==<br />
<br />
As you work, elements become Landmarks (bold decoration), and these elements populate the ''Active Search'' and ''Active Hierarchy'' views. To force an element to populate the views manually, make it a Landmark by <code>right+clicking</code> or hitting <code>Ctrl+Alt+Shift+UpArrow</code>.<br />
<br />
== Known limitations ==<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=106678 Bug 106678]: The Project Explorer's Hierarchical Java package presentation layout is not supported on Eclipse 3.3Mx, and interesting elements will be hidden if enabled. Work-around is to use the default Flat package presentation.<br />
<br />
= Team Support =<br />
<br />
== Why are files missing from the task's change set? ==<br />
<br />
First, verify that you have [http://wiki.eclipse.org/index.php/Mylar_User_Guide#Configuring_the_Synchronize_view_for_change_sets configured the ''Synchronize View'' for change sets].<br />
<br />
The change set may have disappeared as a result of a commit. The work-around for this is to deactivate and reactivate the task.<br />
<br />
== Why do files disappear from the change set when I close them? ==<br />
<br />
If you have the ''Preferences -> Mylar -> Context -> Manage open editors to match task context'' option enabled, Mylar will perform editor management so that you don't have to. Closing a file makes it less interesting, and causes it to disappear from the active task context, and hence from the change set. This option prevents you from having to manage the set of open files, will automatically close editors for files that become uninteresting, and will ensure that the open editors match the task context.<br />
<br />
== Why is interest lost when I retrieve someone else's context? ==<br />
<br />
To identify elements within a project, Mylar relies on the name of the project being consistent across workspaces. If the project name in the workspace that the context was created with is different than its name in your workspace, the task context will not show elements within that project ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=164058 bug 164058]). The work-around is to use the same project names across your team's workspaces.<br />
<br />
The other case where context can be lost is if the elements change names outside of the workspace ( [https://bugs.eclipse.org/bugs/show_bug.cgi?id=164243 bug 164243]).<br />
<br />
= Misc =<br />
<br />
<br />
<br />
== How does Mylar relate to IBM's Jazz? ==<br />
<br />
At the EclipseCon and JavaONE 2006 conferences IBM demonstrated previews of Jazz, a collaborative team server and Eclipse-based client. Articles have remarked on the similarities between Mylar and Jazz because both integrate tasks into Eclipse (Jazz's "work items" and Mylar's "tasks"), and both provide change sets grouped by task. But there are both significant differences and complementary aspects to the two approaches. A key goal of Mylar is to provide an open source framework to support integration of task management with ''existing issue trackers and source repositories''. According to the presentations, components that come with Jazz include include a ''next-generation issue tracker and source repository'' and related lifecycle management tools such as project health. In addition, a driving and unique goal of Mylar is to focus the UI around a usage-based and degree-of-interested weighted task context, which is complementary to the Jazz platform. Just as it integrates with Mylar's Task List, Mylar's Task Focused UI and task context model components are possible to integrate with other kinds of task management systems, such as the one provided by Jazz.<br />
<br />
Update: at EclipseCon 2007 the IBM Jazz team showed a Mylar connector for Jazz.</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Plan/2.0&diff=39999Mylyn/Plan/2.02007-06-21T17:23:39Z<p>Steffen.pingel.eclipse.org: /* Task Repositories */</p>
<hr />
<div>[[Category:Mylar]] <br />
Edit this document for corrections or clarifications. To discuss adding or removing items please use [https://bugs.eclipse.org/bugs/show_bug.cgi?id=173121 bug 173121].<br />
<br />
= Milestones =<br />
Mylar milestones are released 1 week after [http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_3.html Eclipse milestones]. Click to view open bugs. Each end-user release supports Eclipse 3.2 and 3.3.<br />
* 2.0M1: February 16, 2007<br />
* 2.0M2: March 30, 2007<br />
* 2.0M3: May 11, 2007 <br />
* <s>2.0RC0: June 8, 2007 (API freeze, no end-user release)</s><br />
* 2.0RC0: June 18, 2007 (RC scheduled changed due to project rename)<br />
* 2.0RC1: June 20, 2007<br />
* 2.0RC2: June 22, 2007<br />
* 2.0RC3: June 26, 2007<br />
* [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&target_milestone=2.0&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= 2.0: June 29, 2007]<br />
<br />
'''RC Ramp down plan for [[Europa_Simultaneous_Release | Europa]]''': after RC0 is produced RCs will be produced weekly until the 2.0 release. In the RC phase only bugs marked P2 or higher or severity major or higher will be fixed. APIs will not change except to address critical fixes. Any API additions or changes will be summarized in an email sent to mylar-dev.<br />
<br />
= Scope =<br />
<br />
The first goal of Mylar is to make task and context management seamlessly integrated with the Eclipse Platform by providing rich and extensible frameworks for task repository connectors, structure bridges and team support. The second goal is to provide a reference implementation of the Task-Focused UI for the Eclipse SDK. This includes structure bridges for the artifacts supported by the SDK which include Java, PDE, Ant and generic files. It also includes the Bugzilla Connector as the reference task repository implementation, and CVS integration as the reference team support. Additional features can be considered based on the availability community contributions and resources.<br />
<br />
= Priorities =<br />
<br />
In addition to using the planned themes listed below, we need to continue prioritizing the ongoing input of our growing user community. Committers should prioritize bugs in the following order. This order need not be used if a bug contains a community contribution of a patch, in which case the [http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference#Contributing_patches quality of the patch] determines the priority.<br />
# Frameworks & APIs: Tasks, Context, Team, Monitor, headless use<br />
# UI: Tasks List, Task Editor, Task-focused UI<br />
# Connectors: Bugzilla (reference implementation), Trac (committer supported), JIRA (community supported)<br />
<br />
= Platforms =<br />
* Eclipse 3.3: supported<br />
* Eclipse 3.2: supported, post 2.0 maintenance builds only<br />
* Java 5 or later required<br />
<br />
= Themes =<br />
<br />
Legend: in progress, <font color=green>completed</font>, <font color=gray>optional</font> <br />
<br />
== Task List ==<br />
<br />
* <font color="green">'''Support date view in Task List.''' A common way of organizing tasks to work on in the current week is by day. We should support this by integrating the Task Activity view's date range container presentation with the Task List. (bug 147084)</font><br />
<br />
* <font color=green>'''Support integration with planning and calendaring tools.''' Many task repositories have facilities for task planning in the form of milestones, due dates, and other organizations of tasks. The Task List and Task Editor should support such extensions, for example, allowing the Task List to be organized by milestone. (e.g. bug 152490).</font> [dates supported, alternate models post 2.0]<br />
<br />
* <font color=green>'''Support task dependencies.''' Many tasks are related to other tasks, whether it's because they should be worked on in sequence or are subtasks. We should make these dependencies explicit in the Task List and Task Editor. (bug 137543)</font><br />
<br />
* <font color="green">'''Support working set groupings.''' A Task List that includes projects from multiple "working spheres" (e.g. Project A, Project B, Personal) can become unwieldy and distracting. Integration of top-level working sets could address this. (bug 153573)</font> <br />
<br />
== Task Editing ==<br />
<br />
* <font color="green">'''Improve task activity timing.''' We currently have a task activity mechanism, but it is not explicit enough, and does not capture time spent outside of the workbench. It should also be extensible to OS-specific monitoring. (bug 135668).</font><br />
<br />
* <font color=green>'''Increase Task Editor information density'''. The task editor is a very frequent target of interaction, and we need to continue streamlining it. When opened it should show the user the most relevant information with minimal clicking and scrolling required. (bug 158921).</font><br />
<br />
* <font color=gray>'''Provide task workflow mechanism.''' There are many common workflows, such as commit/complete/deactivate. We should provide a mechanism for specifying and executing task-related workflows. This requires direct editing of task data (i.e., without editor submission). (bug 160780, bug 124224)</font><br />
<br />
* <font color=gray>'''Streamline task creation.''' Make it easier to create tasks, fork them, or promote local tasks to repository tasks. (bug 154896, bug 152211)</font><br />
<br />
== Task Repositories ==<br />
<br />
* <font color=green>'''Make offline cache faster and more robust.''' The offline cache is currently one large serialized file. We should make it more robust so that changes to connectors and the framework do not cause the offline data to be cleared. This should make it possible to put a repository into offline mode permanently, and never lose the task data. (bug 165809)</font><br />
<br />
* <font color=green>'''Improve connectivity problem and performance handling.''' Lack of or degraded connectivity should be transparent, and jobs should be cancellable. (bug 165833)</font><br />
<br />
* <font color=green>'''Improve synchronization control'''. Consider allowing synchronization to be controlled per repository (bug 165473), and allowing repositories to be put into offline mode (bug 165809).</font<br />
<br />
* <font color=green>'''Improve consistency between local and repository tasks.''' Need to consider how to promote task between local and repository, and whether local tasks should be a kind of repository. (bug 124321)</font><br />
<br />
* <font color=gray>'''Provide standard XML for tasks.''' To make creating connectors easier, we could provide a canonical and extensible XML for for tasks that we use for retrieving task data.</font><br />
<br />
* <s>'''Streamline task searching'''. It is currently impossible to search through local and cached task data. We could improve the search experience by providing Google-style syntax in the ''Task List'' find box, e.g. severity=critical. (bug 163341)</s> [deferred post 2.0, dependent on Platform, relying on Ctrl+H search instead]<br />
<br />
== Task-Focused UI ==<br />
<br />
* <font color="green">'''Provide preview and editing of task context.''' For submitting and retrieving contexts, or wanting to inspect a context for a non-active task, we should provide a preview pane. This should also support operations such as merge and element deletion. (bug 107259)</font><br />
<br />
* <font color=green>'''Support debugging views'''. This includes improved filtering of the thread tree, and automatic toggling/loading of breakpoints with task context.<font color=green> [thread tree supported, breakpoints post 2.0]<br />
<br />
* <font color=gray>'''Provide task context relation navigation.''' The ''Active Search'' that we deprecated provided relationship navigation. This facility could be re-introduced with an in-place view of relations between elements, e.g. calls, implements. (bug 104052)</font><br />
<br />
* <font color=gray>'''Preserve element identity through refactoring.''' Currently only the active context participates in refactoring. We either need to maintain a dependency map to update the element handles of inactive contexts, or migrate them when they are activated, via the refactoring history. (bug 164243)</font><br />
<br />
== General ==<br />
<br />
* <font color=green>'''Hyperlinking everywhere'''. Wherever structured elements show up, we should be hyperlinking them (e.g. bug 165827)</font><br />
<br />
* <font color=green>'''Improve error handling and resolution.''' When an error happens, we should do automatic duplicate detection, and if no duplicate is found prompt to submit a bug to the failing plug-in.</font> [submission and detection are still on-demand, not automatic]<br />
<br />
* '''Generalize task and context storage mechanisms.''' Our API currently specifies files and paths as the storage mechanism, but it should be general, to allow for alternate mechanisms such as server-based storage. (bug 171346)<br />
<br />
* <font color=green>'''Improve representation of people'''. Support real names, selecting CCs, content assist for fields with people. The user's identity should be represented in the UI (e.g. different icon when user appears in the CC list).</font><br />
<br />
* <font color=green>'''Personal monitoring and usage sharing'''. We require data from the Mylar monitor to inform our UI design. We should also make this data available to others, since it will include general Eclipse usage statistics. In order to provide users with an incentive to share their (anonymous) usage data we should include personal interaction monitoring facilities.</font></div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Plan/2.0&diff=39998Mylyn/Plan/2.02007-06-21T17:22:13Z<p>Steffen.pingel.eclipse.org: /* Task Repositories */</p>
<hr />
<div>[[Category:Mylar]] <br />
Edit this document for corrections or clarifications. To discuss adding or removing items please use [https://bugs.eclipse.org/bugs/show_bug.cgi?id=173121 bug 173121].<br />
<br />
= Milestones =<br />
Mylar milestones are released 1 week after [http://www.eclipse.org/eclipse/development/eclipse_project_plan_3_3.html Eclipse milestones]. Click to view open bugs. Each end-user release supports Eclipse 3.2 and 3.3.<br />
* 2.0M1: February 16, 2007<br />
* 2.0M2: March 30, 2007<br />
* 2.0M3: May 11, 2007 <br />
* <s>2.0RC0: June 8, 2007 (API freeze, no end-user release)</s><br />
* 2.0RC0: June 18, 2007 (RC scheduled changed due to project rename)<br />
* 2.0RC1: June 20, 2007<br />
* 2.0RC2: June 22, 2007<br />
* 2.0RC3: June 26, 2007<br />
* [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Mylyn&target_milestone=2.0&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= 2.0: June 29, 2007]<br />
<br />
'''RC Ramp down plan for [[Europa_Simultaneous_Release | Europa]]''': after RC0 is produced RCs will be produced weekly until the 2.0 release. In the RC phase only bugs marked P2 or higher or severity major or higher will be fixed. APIs will not change except to address critical fixes. Any API additions or changes will be summarized in an email sent to mylar-dev.<br />
<br />
= Scope =<br />
<br />
The first goal of Mylar is to make task and context management seamlessly integrated with the Eclipse Platform by providing rich and extensible frameworks for task repository connectors, structure bridges and team support. The second goal is to provide a reference implementation of the Task-Focused UI for the Eclipse SDK. This includes structure bridges for the artifacts supported by the SDK which include Java, PDE, Ant and generic files. It also includes the Bugzilla Connector as the reference task repository implementation, and CVS integration as the reference team support. Additional features can be considered based on the availability community contributions and resources.<br />
<br />
= Priorities =<br />
<br />
In addition to using the planned themes listed below, we need to continue prioritizing the ongoing input of our growing user community. Committers should prioritize bugs in the following order. This order need not be used if a bug contains a community contribution of a patch, in which case the [http://wiki.eclipse.org/index.php/Mylar_Contributor_Reference#Contributing_patches quality of the patch] determines the priority.<br />
# Frameworks & APIs: Tasks, Context, Team, Monitor, headless use<br />
# UI: Tasks List, Task Editor, Task-focused UI<br />
# Connectors: Bugzilla (reference implementation), Trac (committer supported), JIRA (community supported)<br />
<br />
= Platforms =<br />
* Eclipse 3.3: supported<br />
* Eclipse 3.2: supported, post 2.0 maintenance builds only<br />
* Java 5 or later required<br />
<br />
= Themes =<br />
<br />
Legend: in progress, <font color=green>completed</font>, <font color=gray>optional</font> <br />
<br />
== Task List ==<br />
<br />
* <font color="green">'''Support date view in Task List.''' A common way of organizing tasks to work on in the current week is by day. We should support this by integrating the Task Activity view's date range container presentation with the Task List. (bug 147084)</font><br />
<br />
* <font color=green>'''Support integration with planning and calendaring tools.''' Many task repositories have facilities for task planning in the form of milestones, due dates, and other organizations of tasks. The Task List and Task Editor should support such extensions, for example, allowing the Task List to be organized by milestone. (e.g. bug 152490).</font> [dates supported, alternate models post 2.0]<br />
<br />
* <font color=green>'''Support task dependencies.''' Many tasks are related to other tasks, whether it's because they should be worked on in sequence or are subtasks. We should make these dependencies explicit in the Task List and Task Editor. (bug 137543)</font><br />
<br />
* <font color="green">'''Support working set groupings.''' A Task List that includes projects from multiple "working spheres" (e.g. Project A, Project B, Personal) can become unwieldy and distracting. Integration of top-level working sets could address this. (bug 153573)</font> <br />
<br />
== Task Editing ==<br />
<br />
* <font color="green">'''Improve task activity timing.''' We currently have a task activity mechanism, but it is not explicit enough, and does not capture time spent outside of the workbench. It should also be extensible to OS-specific monitoring. (bug 135668).</font><br />
<br />
* <font color=green>'''Increase Task Editor information density'''. The task editor is a very frequent target of interaction, and we need to continue streamlining it. When opened it should show the user the most relevant information with minimal clicking and scrolling required. (bug 158921).</font><br />
<br />
* <font color=gray>'''Provide task workflow mechanism.''' There are many common workflows, such as commit/complete/deactivate. We should provide a mechanism for specifying and executing task-related workflows. This requires direct editing of task data (i.e., without editor submission). (bug 160780, bug 124224)</font><br />
<br />
* <font color=gray>'''Streamline task creation.''' Make it easier to create tasks, fork them, or promote local tasks to repository tasks. (bug 154896, bug 152211)</font><br />
<br />
== Task Repositories ==<br />
<br />
* <font color=green>'''Make offline cache faster and more robust.''' The offline cache is currently one large serialized file. We should make it more robust so that changes to connectors and the framework do not cause the offline data to be cleared. This should make it possible to put a repository into offline mode permanently, and never lose the task data. (bug 165809)</font><br />
<br />
* <font color=green>'''Improve connectivity problem and performance handling.''' Lack of or degraded connectivity should be transparent, and jobs should be cancellable. (bug 165833)</font><br />
<br />
* <font color=green>'''Improve synchronization control'''. Consider allowing synchronization to be controlled per repository (bug 165473), and allowing repositories to be put into offline mode (bug 165809).</font<br />
<br />
* <font color=gray>'''Improve consistency between local and repository tasks.''' Need to consider how to promote task between local and repository, and whether local tasks should be a kind of repository. (bug 12431)</font><br />
<br />
* <font color=gray>'''Provide standard XML for tasks.''' To make creating connectors easier, we could provide a canonical and extensible XML for for tasks that we use for retrieving task data.</font><br />
<br />
* <s>'''Streamline task searching'''. It is currently impossible to search through local and cached task data. We could improve the search experience by providing Google-style syntax in the ''Task List'' find box, e.g. severity=critical. (bug 163341)</s> [deferred post 2.0, dependent on Platform, relying on Ctrl+H search instead]<br />
<br />
== Task-Focused UI ==<br />
<br />
* <font color="green">'''Provide preview and editing of task context.''' For submitting and retrieving contexts, or wanting to inspect a context for a non-active task, we should provide a preview pane. This should also support operations such as merge and element deletion. (bug 107259)</font><br />
<br />
* <font color=green>'''Support debugging views'''. This includes improved filtering of the thread tree, and automatic toggling/loading of breakpoints with task context.<font color=green> [thread tree supported, breakpoints post 2.0]<br />
<br />
* <font color=gray>'''Provide task context relation navigation.''' The ''Active Search'' that we deprecated provided relationship navigation. This facility could be re-introduced with an in-place view of relations between elements, e.g. calls, implements. (bug 104052)</font><br />
<br />
* <font color=gray>'''Preserve element identity through refactoring.''' Currently only the active context participates in refactoring. We either need to maintain a dependency map to update the element handles of inactive contexts, or migrate them when they are activated, via the refactoring history. (bug 164243)</font><br />
<br />
== General ==<br />
<br />
* <font color=green>'''Hyperlinking everywhere'''. Wherever structured elements show up, we should be hyperlinking them (e.g. bug 165827)</font><br />
<br />
* <font color=green>'''Improve error handling and resolution.''' When an error happens, we should do automatic duplicate detection, and if no duplicate is found prompt to submit a bug to the failing plug-in.</font> [submission and detection are still on-demand, not automatic]<br />
<br />
* '''Generalize task and context storage mechanisms.''' Our API currently specifies files and paths as the storage mechanism, but it should be general, to allow for alternate mechanisms such as server-based storage. (bug 171346)<br />
<br />
* <font color=green>'''Improve representation of people'''. Support real names, selecting CCs, content assist for fields with people. The user's identity should be represented in the UI (e.g. different icon when user appears in the CC list).</font><br />
<br />
* <font color=green>'''Personal monitoring and usage sharing'''. We require data from the Mylar monitor to inform our UI design. We should also make this data available to others, since it will include general Eclipse usage statistics. In order to provide users with an incentive to share their (anonymous) usage data we should include personal interaction monitoring facilities.</font></div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=39682Mylyn/Meetings2007-06-19T15:08:25Z<p>Steffen.pingel.eclipse.org: /* Tuesday, June 19, 10-11am PT */</p>
<hr />
<div>[[Category:Mylar]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, June 19, 10-11am PT ====<br />
<br />
* Summer of code update (students)<br />
* Continuous build (Steffen)<br />
<br />
Future:<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* vserver admin status report<br />
<br />
----<br />
<br />
=== Past Meetings ===<br />
<br />
<br />
==== Tuesday, June 12, 10-11am PT ====<br />
<br />
* Project Rename Status (Mik)<br />
* Summer of code update (students)<br />
* 2.0 RC1 release status (Mik)<br />
** Release of JIRA connector?<br />
* Error handling design (Mik, Rob, Steffen)<br />
* Fixes for the synchronization API ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=191575 #191575])<br />
* Notification of API changes (Steffen)<br />
<br />
Actions:<br />
* Mik to investigate options for disabling old mylar plugins (required for tonight's dev build)<br />
* Eugene to take quick pass at synchronization api changes tonight [[https://bugs.eclipse.org/bugs/show_bug.cgi?id=191575 bug#191575]]<br />
----<br />
<br />
<br />
<br />
==== Tuesday, June 5, 10-11am PT ====<br />
<br />
* Google Summer of Code kick-off (Balazs, Jevgeni, Xiaoyang)<br />
* vserver admin practices (Rob, Steffen)<br />
* 2.0 end game planning<br />
** Committers 2.0 plan update<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
<i>Stale items</i><br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Actions:<br />
* Rob to administer vserver (corrdinate with Steffen)<br />
** Contact Denis regarding updates<br />
** Investigate backup options<br />
<br />
==== Tuesday, May 29, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Task vs. TaskData; properties vs. class hierarchy (Eugene)<br />
** Full vs. light synchronization (Eugene)<br />
<i>Stale items</i><br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* (Eugene) Proposed eliminating Task hierarchy and replace with property based access<br />
** Suggests merging Task and AbstractRepositoryTask<br />
** Willing to add property support to ITask for 2.1 if requested by integrators.<br />
* (Steffen) The property-based vs. sub-classing discussing is important and we need to consider this for 3.0 again. <br />
* (Rob) raised TaskData migration and committers agree that migraion of existing offline data not practical<br />
<br />
Actions:<br />
* (Mik) introduce class factories and remove custom task externalizers<br />
* replace AbstractQueryHit by Tasks<br />
* allow connectors to submit Task or TaskData objects as hits<br />
* convert offline storage from Java Serialization to XML<br />
* construct attribute editors through factory, do not store repository configuration in offline storage<br />
* apply pending rename changes from porting guide<br />
* refactor attachment API <br />
<br />
<br />
<br />
==== Tuesday, May 22, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* Top voted bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169123 169123]: Updated bug does not preserve values of custom fields in Jira (Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Minutes:<br />
* Task workflow and special query support likely getting bumped<br />
* Rob: related bug#185805 (timestamp bug) and bug#186939 (blocked jobs)<br />
* Steffen: httpclient message.shutdown() can be used to force shutdown of network IO<br />
<br />
Actions:<br />
* Rob and Steffen:<br />
**to start offline refactoring.<br />
**included refactoring of local tasks to AbstractRepositoryTask (P1)<br />
**For RC0, add progress monitor to all api methods that involve IO to easy future implementation.<br />
* Steffen to open new bug for alternate containment representations (outline, task editor can be used to reveal) duplicates for bugzilla could use this<br />
* Mik to make new bug for Open Resource bug related to Task Working sets (defer Eugen's multiple tasklist views patch since will require additional view memento facility?) <br />
* Rob: Will investigate breaking out past activity from scheduled mode (after higher priority api changes).<br />
* For next call: Committers should review their P1 and P2 tasks and form a realistic list for 2.0<br />
<br />
==== Tuesday, May 15, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Decisions made regarding offline TaskData handling and presentation merged with wiki ([[Mylar Offline Refactoring]]).<br />
<br />
==== Tuesday, May 8, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
** Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Additive improvements deferred in favor of API changes.<br />
Main API changes (P2):<br />
* Local task become repository tasks<br />
* Hits become Tasks (but retain UI representation)<br />
* Offline storage improvements ([[Mylar Offline Refactoring]])<br />
* Tasklist externalization<br />
* AbstractRepositoryTaskEditor (make protected methods private)<br />
* Multiple Task Downloads (synch api changes)<br />
* Context listeners api (Mik)<br />
* Extract repository configuration<br />
<br />
<br />
==== Tuesday, May 1, 10-11am PT ====<br />
<br />
* Eclipse Forum Europe report (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Monitor update (Meghan)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
* Post action items/summary/minutes after each meeting (Mik?)<br />
<br />
Actions:<br />
* Eugene<br />
** send screenshot example of strikethrough looking like row lines<br />
* Mik<br />
** consider moving activation to task icon<br />
** working sets in tasklist needs priority since we need to put miles on it before release<br />
* Rob<br />
** persistence api should be finalized so that we can drop in alternate back ends<br />
<br />
==== Tuesday, April 24, 10-11am PT ====<br />
<br />
* Post action items/summary/minutes after each meeting<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* Greg Wilson gave brief overview of planned work for SoC project<br />
* Discussed options for implementing offline storage for task data<br />
* Discussed use cases for RSS support in the Task List<br />
* Discussed tagging and working sets support in the Task List<br />
<br />
Actions:<br />
<br />
* Does it make sense to keep task data separate from the task list?<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165880 165880: Listeners API should allow to pass multiple events in one call] Potential source of refresh issues (Eugene)<br />
<br />
==== Tuesday, April 17, 10-11am PT ====<br />
<br />
* Google Summer of Code planning (Mik)<br />
* ROME depency accepted (Eugene, Mik)<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
** Contributing custom models to task list and task repositories views. per-milestone/version grouping, or grouping query results by certain attributes (Eugene)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API updates (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* Post action items/summary after each meeting<br />
<br />
==== Tuesday, April 10, 10-11am PT ====<br />
<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API changes (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=179873 179873: Completed status not correct for JIRA tasks]<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
==== Tuesday, April 3, 10-11am PT ====<br />
<br />
* Mylar 2.0M2 release wrap-up, 2.0M3 planning (Mik)<br />
* Offline storage strategy design discussion(Rob, Steffen)<br />
<br />
==== Tuesday, March 27, 10-11am PT ====<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
<br />
* Mylar 2.0M2 status<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176513 176513] [api] Multiple task data request (Rob)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 160389] [api] Serialization / loss of data etc (Rob)<br />
* JIRA statuses: resolved vs. closed<br />
<br />
==== Tuesday, March 20, 10-11am PT ====<br />
<br />
* [http://wiki.eclipse.org/index.php/Mylar_GSoC_2007 Goolge Summer of Code ideas] (Mik)<br />
* Eclipse 3.3M6 status (Mik)<br />
* JIRA network utilization ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=175407 175407])<br />
* JIRA test server<br />
* usage reporting (Meghan)<br />
<br />
==== Tuesday, March 13, 10-11am PT ====<br />
<br />
Agenda:<br />
* EclipseCon decompression (Mik)<br />
* JIRA test server (Steffen)<br />
* 2.0M2 planning<br />
* AttributeFactoryUI/RepositoryConfiguration (Rob, Steffen)<br />
<br />
==== Tuesday, February 27, 10-11am PT ====<br />
<br />
Agenda:<br />
* '-' issue - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=166174 bug 166174]<br />
* EclipseCon planning (Mik)<br />
** 3.2 dev build<br />
** Stickers/Buttons/T-shirts<br />
** Poster<br />
* In-place context view (Mik, Eugene)<br />
* GSoC 2007 project (Steffen)<br />
<br />
Actions:<br />
* Find Mylar film glasses (Steffen)<br />
* Find out if there is any space left for poster presentations (Rob)<br />
* At EclipseCon ask EMF folks about using EMF for repository mappings (Mik & Rob)<br />
<br />
==== Tuesday, February 20, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* 2.0M1 release review (Mik)<br />
* Id vs handle vs key (Mik)<br />
* How to make Query creation more obvious for new users (Eugene)<br />
* Showing Task ID/Keys in UI (task list and task dialogs, editor tabs and headers, task history dropdown, change sets) (Eugene)<br />
* JIRA issues (Eugene, Steffen)<br />
<br />
Actions:<br />
* File form header bug<br />
* Create method: TaskList.getTask(String connectorKind, String taskUrl)<br />
* Create AbstractRepositoryTask.getKey()<br />
<br />
==== Tuesday, February 13, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* IP submission follow-ups for Lucene 2.0, Axis2 (Mik)<br />
* Major connector externalizer and task handle usage refactoring (Mik)<br />
* JIRA issues<br />
* Make Steffen JIRA committer<br />
* Discuss refactoring of RepositoryTaskAttributes (bug 150680?) (Steffen)<br />
** Separate UI representation from attribute?<br />
** How to link attributes to repository configuration?<br />
<br />
==== Tuesday, February 6, 10-11am PT ====<br />
<br />
Agenda<br />
* Finalizing of Mylar 2.0 plan (Mik)<br />
* Status of IP submissions (Mik)<br />
* Orbit dependencies<br />
* Status of JIRA<br />
* Issues with handles (Eugene)<br />
* Issues with event notification api (Rob)<br />
<br />
==== Tuesday, January 30, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Moving to Eclipse 3.3M5 builds (Mik)<br />
* Final IP and contribution submissions for Europa (Mik)<br />
* Status Jira Core Services and library dependencies (Steffen)<br />
<br />
==== Tuesday, January 23, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Implementation strategy for<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=171081 171081]: Autodetect JIRA repository for Open Corresponding Task (Eugene)<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=159135 159135]: Automatic resolution of links between projects and issue repositories (Eugene)<br />
* Additional contributions to be made by the Jan. 31st Europa cutoff (Mik)<br />
Actions<br />
* Consider Lucene 2.0 IPZilla submission (Mik)<br />
<br />
==== Tuesday, January 16, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning<br />
* Tomcat and server setup for mylar.eclipse.org<br />
* TaskId vs TaskHandle (numerous issues with JIRA connector) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170587 bug 170587]<br />
* Models and their application to the tasklist (Rob, Eugene) ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147084 147084: merge Task List and Task Activity views])<br />
** "[use] models and provide model that would show unread/changed/conflicting tasks" ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=170606 170606: Add action to Task List to filter out read requests])<br />
** 153573: add support for nesting top level task list elements, e.g. via incorporating working sets<br />
* Task web browser<br />
Actions:<br />
* Add milestone buckets 2.0M1 through M3 (Mik)<br />
* Gets JIRA enterprise license key for test server (Mik)<br />
* Ask about server backup policy (2.6 Gigs used), disk space for usage data (Mik)<br />
* Consider downgrading Tomcat to 5.5 (Meghan)<br />
* Write up Mylar monitor data collection project (Meghan)<br />
* Plans hyperlink detection improvements and bugs (Rob)<br />
**170679: [api] improve hyperlink detection api<br />
**170681: [api] allow connectors to contribute alternate content providers (models) to tasklist<br />
**170685: [api] allow connectors to contribute filters to tasklist<br />
<br />
==== Tuesday, Januray 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylar 2.0 milestone and Europa planning.<br />
* Synchronization, progress indication, and cancellation of repository task operations ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168257 168257], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=150682 150682], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154258 154258], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 143011])<br />
* Mylar error handling ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168049 168049], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168672 168672], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165383 165383])<br />
* Task activity timing improvement ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147537 147537])<br />
* JIRA issues (auth problem and integrating JIRA client)<br />
Actions:<br />
* Write up error policy (Steffen)<br />
* Plan synchronization related bugs (Rob)<br />
* Find platform release dates (Mik)<br />
* Define scope of project on planning page (Mik)<br />
* Add dummy query on codehouse project (Mik)<br />
<br />
==== Tuesday, December 19, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* 1.0.1 priorities (Mik) <br />
* Slap Eugene for discrediting Mylar in blogs and Mik for not blogging<br />
* Layout of search/query page<br />
<br />
==== Tuesday, December 12, 10-10:30am PT ====<br />
* Mylar 1.0 celebration and retrospective.<br />
* Brock Janiczak's JIRA core services contribution (Eugene, Mik?).<br />
* Discovery update sites (Eugene, Mik).<br />
* Version numbers (Mik).<br />
<br />
==== Tuesday, December 5, 10-10:30am PT ====<br />
* Remaining priorities for 1.0 (Mik)<br />
* API status (Mik)<br />
** Externalizers ITaskListExternalize<br />
** Listeners API, primarily ITaskListChangeListener<br />
** Adapting to ITask and broken selection of the task respositories<br />
* Proxy settings status (Rob)<br />
* Subclipse integration and Team API (Eugene)<br />
<br />
<br />
==== Tuesday, November 21, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Remaining 1.0RC1 items (Mik)<br />
** Issues with tack context (multiple folders, unfiltering issues, etc)<br />
** Issues with new local task UI (focus, inline vs. editor)<br />
** Moving task drop down and pause button out of Task List UI?<br />
* Bugzilla and repository infrastructure status (Rob)<br />
* Trac status (Steffen)<br />
* Web connector status (Mik)<br />
* JIRA connnector status (Mik & Eugene)<br />
Actions<br />
* Mik emails newsgroup/mylar-dev about task list toolbar changes<br />
* Mik fixes classpath of context.core xmlrpc-use<br />
* Visible editor always unfiltered<br />
* Eugene files bug on editor color problem<br />
* Steffen files bug People section with JIRA<br />
<br />
==== Tuesday, November 14, 10-11am PT ====<br />
<br />
Agenda<br />
* Mylar 1.0 priorities.<br />
* Pause button UI (Mik?)<br />
Actions<br />
* Need people section for Trac<br />
* Discuss removing commit context button on newsgroup<br />
* Allow proxy settings to be specified per-repository<br />
<br />
==== Tuesday, October 31, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Authentication infrastructure and connectors (Rob)<br />
* Offline support for JIRA (Mik)<br />
* Pause button UI (Mik)<br />
<br />
<br />
==== Tuesday, October 24, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda<br />
* 0.8 post-mortem (Mik)<br />
* Storage of offline task data (See [[Mylar Task List]]) (Rob)<br />
* JIRA priorities (Mik)<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* [http://dev.eclipse.org/mhonarc/lists/mylar-dev/msg00706.html Alternative integration] with remote repositories (Eugene)<br />
<br />
Actions<br />
* Investigate Lucene as store for offline task data (Rob)<br />
* Investigate showing working sets as top-level nodes in Task List (Mik)<br />
<br />
==== Tuesday, October 17, 10-11am PT ====<br />
<br />
Agenda<br />
* 0.8 release planning<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Rich editor for Trac (Steffen?)<br />
* Repository task data (Rob)<br />
** Offline persistence: object serialization (current), xml, database [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 bug 160389]<br />
** Lazy loading [https://bugs.eclipse.org/bugs/show_bug.cgi?id=157257 bug 157257]<br />
* Issues with Task monitoring and filtering for projects with more then one source folder<br />
* Jira integration planning<br />
* User guide and improving the docs<br />
<br />
Actions<br />
* Need "Add to Task List" action on query hits<br />
* Consider merging the above action with dialog for "Add Existing Task..."<br />
* Need to consider pre-fetching task data for query hits<br />
<br />
==== Tuesday, September 26 2006, 10-11am PT ====<br />
* 0.7 release planning<br />
* Project and repository association (Rob)<br />
* 1.0 planning (Mik)<br />
<br />
==== Wednesday, August 23 2006, 10-11am PT ====<br />
* Planning for 0.6.2<br />
* Generic web Repository Connector integration (Eugene)<br />
* Trac Connector rich editor (Steffen)<br />
* AbstractRepositoryConnector split into core and UI<br />
* Planning for 0.7 and 1.0<br />
* Zest website integration and release cycles<br />
<br />
==== Wednesday, August 2 2006, 10-11am PT ====<br />
Agenda<br />
* 0.6.1 post-mortem<br />
* 0.6.2 and 1.0 planning<br />
* Summer of Code status<br />
** Trac Connector (Steffen)<br />
** Bugzilla enhancements (Jeff)<br />
** JIRA<br />
* Design discussion on splitting AbstractRepositoryConnector into core/ui<br />
* Sandbox release for web connector (Eugene)<br />
Vacations<br />
* Rob: 3rd - 8th<br />
* Mik: 8th - 17th<br />
Actions<br />
* Consumers of APIs update Javadocs as they use them, a la wiki <br />
* Decide on conference call time and interval next meeting<br />
* Investigate Rome dependency for Sandbox (Mik)<br />
<br />
==== Thursday, July 6 2006, 10am PT ====<br />
* wrap up discussion of 0.6 release<br />
* Trac integration status (Steffen)<br />
* enhancing Bugzilla connector status (Jeff)<br />
* Connector naming conventions<br />
* tasks API discussion. String-based task id, separate task id, url and repository url, (issues 146396, 149624, 149509), other refactoring of tasks, hits, query and repository classes<br />
* UI for repository settings<br />
* prioritizing for 0.7 and beyond<br />
* planning and use of Bugzilla priorities<br />
<br />
==== Tuesday, June 13 2006, 10am PT ====<br />
* Schedule a regular meeting time and interval<br />
* Google SoC: Trac integration (Steffen)<br />
* Google Soc: enhancing Bugzilla connector (Jeff)<br />
* Repository connector API discussion (Mik)<br />
* Prioritize tasks for 0.6 (Mik)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=38897Mylyn/Meetings2007-06-12T16:42:24Z<p>Steffen.pingel.eclipse.org: /* Tuesday, June 12, 10-11am PT */</p>
<hr />
<div>[[Category:Mylar]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, June 12, 10-11am PT ====<br />
<br />
* Project Rename Status (Mik)<br />
* Summer of code update (students)<br />
* 2.0 RC1 release status (Mik)<br />
** Release of JIRA connector?<br />
* Error handling design (Mik, Rob, Steffen)<br />
* Fixes for the synchronization API ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=191575 #191575])<br />
* Notification of API changes (Steffen)<br />
<br />
Future:<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* vserver admin status report<br />
<br />
----<br />
<br />
=== Past Meetings ===<br />
<br />
==== Tuesday, June 5, 10-11am PT ====<br />
<br />
* Google Summer of Code kick-off (Balazs, Jevgeni, Xiaoyang)<br />
* vserver admin practices (Rob, Steffen)<br />
* 2.0 end game planning<br />
** Committers 2.0 plan update<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
<i>Stale items</i><br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Actions:<br />
* Rob to administer vserver (corrdinate with Steffen)<br />
** Contact Denis regarding updates<br />
** Investigate backup options<br />
<br />
==== Tuesday, May 29, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Task vs. TaskData; properties vs. class hierarchy (Eugene)<br />
** Full vs. light synchronization (Eugene)<br />
<i>Stale items</i><br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* (Eugene) Proposed eliminating Task hierarchy and replace with property based access<br />
** Suggests merging Task and AbstractRepositoryTask<br />
** Willing to add property support to ITask for 2.1 if requested by integrators.<br />
* (Steffen) The property-based vs. sub-classing discussing is important and we need to consider this for 3.0 again. <br />
* (Rob) raised TaskData migration and committers agree that migraion of existing offline data not practical<br />
<br />
Actions:<br />
* (Mik) introduce class factories and remove custom task externalizers<br />
* replace AbstractQueryHit by Tasks<br />
* allow connectors to submit Task or TaskData objects as hits<br />
* convert offline storage from Java Serialization to XML<br />
* construct attribute editors through factory, do not store repository configuration in offline storage<br />
* apply pending rename changes from porting guide<br />
* refactor attachment API <br />
<br />
<br />
<br />
==== Tuesday, May 22, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* Top voted bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169123 169123]: Updated bug does not preserve values of custom fields in Jira (Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Minutes:<br />
* Task workflow and special query support likely getting bumped<br />
* Rob: related bug#185805 (timestamp bug) and bug#186939 (blocked jobs)<br />
* Steffen: httpclient message.shutdown() can be used to force shutdown of network IO<br />
<br />
Actions:<br />
* Rob and Steffen:<br />
**to start offline refactoring.<br />
**included refactoring of local tasks to AbstractRepositoryTask (P1)<br />
**For RC0, add progress monitor to all api methods that involve IO to easy future implementation.<br />
* Steffen to open new bug for alternate containment representations (outline, task editor can be used to reveal) duplicates for bugzilla could use this<br />
* Mik to make new bug for Open Resource bug related to Task Working sets (defer Eugen's multiple tasklist views patch since will require additional view memento facility?) <br />
* Rob: Will investigate breaking out past activity from scheduled mode (after higher priority api changes).<br />
* For next call: Committers should review their P1 and P2 tasks and form a realistic list for 2.0<br />
<br />
==== Tuesday, May 15, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Decisions made regarding offline TaskData handling and presentation merged with wiki ([[Mylar Offline Refactoring]]).<br />
<br />
==== Tuesday, May 8, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
** Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Additive improvements deferred in favor of API changes.<br />
Main API changes (P2):<br />
* Local task become repository tasks<br />
* Hits become Tasks (but retain UI representation)<br />
* Offline storage improvements ([[Mylar Offline Refactoring]])<br />
* Tasklist externalization<br />
* AbstractRepositoryTaskEditor (make protected methods private)<br />
* Multiple Task Downloads (synch api changes)<br />
* Context listeners api (Mik)<br />
* Extract repository configuration<br />
<br />
<br />
==== Tuesday, May 1, 10-11am PT ====<br />
<br />
* Eclipse Forum Europe report (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Monitor update (Meghan)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
* Post action items/summary/minutes after each meeting (Mik?)<br />
<br />
Actions:<br />
* Eugene<br />
** send screenshot example of strikethrough looking like row lines<br />
* Mik<br />
** consider moving activation to task icon<br />
** working sets in tasklist needs priority since we need to put miles on it before release<br />
* Rob<br />
** persistence api should be finalized so that we can drop in alternate back ends<br />
<br />
==== Tuesday, April 24, 10-11am PT ====<br />
<br />
* Post action items/summary/minutes after each meeting<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* Greg Wilson gave brief overview of planned work for SoC project<br />
* Discussed options for implementing offline storage for task data<br />
* Discussed use cases for RSS support in the Task List<br />
* Discussed tagging and working sets support in the Task List<br />
<br />
Actions:<br />
<br />
* Does it make sense to keep task data separate from the task list?<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165880 165880: Listeners API should allow to pass multiple events in one call] Potential source of refresh issues (Eugene)<br />
<br />
==== Tuesday, April 17, 10-11am PT ====<br />
<br />
* Google Summer of Code planning (Mik)<br />
* ROME depency accepted (Eugene, Mik)<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
** Contributing custom models to task list and task repositories views. per-milestone/version grouping, or grouping query results by certain attributes (Eugene)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API updates (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* Post action items/summary after each meeting<br />
<br />
==== Tuesday, April 10, 10-11am PT ====<br />
<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API changes (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=179873 179873: Completed status not correct for JIRA tasks]<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
==== Tuesday, April 3, 10-11am PT ====<br />
<br />
* Mylar 2.0M2 release wrap-up, 2.0M3 planning (Mik)<br />
* Offline storage strategy design discussion(Rob, Steffen)<br />
<br />
==== Tuesday, March 27, 10-11am PT ====<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
<br />
* Mylar 2.0M2 status<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176513 176513] [api] Multiple task data request (Rob)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 160389] [api] Serialization / loss of data etc (Rob)<br />
* JIRA statuses: resolved vs. closed<br />
<br />
==== Tuesday, March 20, 10-11am PT ====<br />
<br />
* [http://wiki.eclipse.org/index.php/Mylar_GSoC_2007 Goolge Summer of Code ideas] (Mik)<br />
* Eclipse 3.3M6 status (Mik)<br />
* JIRA network utilization ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=175407 175407])<br />
* JIRA test server<br />
* usage reporting (Meghan)<br />
<br />
==== Tuesday, March 13, 10-11am PT ====<br />
<br />
Agenda:<br />
* EclipseCon decompression (Mik)<br />
* JIRA test server (Steffen)<br />
* 2.0M2 planning<br />
* AttributeFactoryUI/RepositoryConfiguration (Rob, Steffen)<br />
<br />
==== Tuesday, February 27, 10-11am PT ====<br />
<br />
Agenda:<br />
* '-' issue - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=166174 bug 166174]<br />
* EclipseCon planning (Mik)<br />
** 3.2 dev build<br />
** Stickers/Buttons/T-shirts<br />
** Poster<br />
* In-place context view (Mik, Eugene)<br />
* GSoC 2007 project (Steffen)<br />
<br />
Actions:<br />
* Find Mylar film glasses (Steffen)<br />
* Find out if there is any space left for poster presentations (Rob)<br />
* At EclipseCon ask EMF folks about using EMF for repository mappings (Mik & Rob)<br />
<br />
==== Tuesday, February 20, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* 2.0M1 release review (Mik)<br />
* Id vs handle vs key (Mik)<br />
* How to make Query creation more obvious for new users (Eugene)<br />
* Showing Task ID/Keys in UI (task list and task dialogs, editor tabs and headers, task history dropdown, change sets) (Eugene)<br />
* JIRA issues (Eugene, Steffen)<br />
<br />
Actions:<br />
* File form header bug<br />
* Create method: TaskList.getTask(String connectorKind, String taskUrl)<br />
* Create AbstractRepositoryTask.getKey()<br />
<br />
==== Tuesday, February 13, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* IP submission follow-ups for Lucene 2.0, Axis2 (Mik)<br />
* Major connector externalizer and task handle usage refactoring (Mik)<br />
* JIRA issues<br />
* Make Steffen JIRA committer<br />
* Discuss refactoring of RepositoryTaskAttributes (bug 150680?) (Steffen)<br />
** Separate UI representation from attribute?<br />
** How to link attributes to repository configuration?<br />
<br />
==== Tuesday, February 6, 10-11am PT ====<br />
<br />
Agenda<br />
* Finalizing of Mylar 2.0 plan (Mik)<br />
* Status of IP submissions (Mik)<br />
* Orbit dependencies<br />
* Status of JIRA<br />
* Issues with handles (Eugene)<br />
* Issues with event notification api (Rob)<br />
<br />
==== Tuesday, January 30, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Moving to Eclipse 3.3M5 builds (Mik)<br />
* Final IP and contribution submissions for Europa (Mik)<br />
* Status Jira Core Services and library dependencies (Steffen)<br />
<br />
==== Tuesday, January 23, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Implementation strategy for<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=171081 171081]: Autodetect JIRA repository for Open Corresponding Task (Eugene)<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=159135 159135]: Automatic resolution of links between projects and issue repositories (Eugene)<br />
* Additional contributions to be made by the Jan. 31st Europa cutoff (Mik)<br />
Actions<br />
* Consider Lucene 2.0 IPZilla submission (Mik)<br />
<br />
==== Tuesday, January 16, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning<br />
* Tomcat and server setup for mylar.eclipse.org<br />
* TaskId vs TaskHandle (numerous issues with JIRA connector) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170587 bug 170587]<br />
* Models and their application to the tasklist (Rob, Eugene) ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147084 147084: merge Task List and Task Activity views])<br />
** "[use] models and provide model that would show unread/changed/conflicting tasks" ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=170606 170606: Add action to Task List to filter out read requests])<br />
** 153573: add support for nesting top level task list elements, e.g. via incorporating working sets<br />
* Task web browser<br />
Actions:<br />
* Add milestone buckets 2.0M1 through M3 (Mik)<br />
* Gets JIRA enterprise license key for test server (Mik)<br />
* Ask about server backup policy (2.6 Gigs used), disk space for usage data (Mik)<br />
* Consider downgrading Tomcat to 5.5 (Meghan)<br />
* Write up Mylar monitor data collection project (Meghan)<br />
* Plans hyperlink detection improvements and bugs (Rob)<br />
**170679: [api] improve hyperlink detection api<br />
**170681: [api] allow connectors to contribute alternate content providers (models) to tasklist<br />
**170685: [api] allow connectors to contribute filters to tasklist<br />
<br />
==== Tuesday, Januray 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylar 2.0 milestone and Europa planning.<br />
* Synchronization, progress indication, and cancellation of repository task operations ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168257 168257], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=150682 150682], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154258 154258], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 143011])<br />
* Mylar error handling ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168049 168049], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168672 168672], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165383 165383])<br />
* Task activity timing improvement ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147537 147537])<br />
* JIRA issues (auth problem and integrating JIRA client)<br />
Actions:<br />
* Write up error policy (Steffen)<br />
* Plan synchronization related bugs (Rob)<br />
* Find platform release dates (Mik)<br />
* Define scope of project on planning page (Mik)<br />
* Add dummy query on codehouse project (Mik)<br />
<br />
==== Tuesday, December 19, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* 1.0.1 priorities (Mik) <br />
* Slap Eugene for discrediting Mylar in blogs and Mik for not blogging<br />
* Layout of search/query page<br />
<br />
==== Tuesday, December 12, 10-10:30am PT ====<br />
* Mylar 1.0 celebration and retrospective.<br />
* Brock Janiczak's JIRA core services contribution (Eugene, Mik?).<br />
* Discovery update sites (Eugene, Mik).<br />
* Version numbers (Mik).<br />
<br />
==== Tuesday, December 5, 10-10:30am PT ====<br />
* Remaining priorities for 1.0 (Mik)<br />
* API status (Mik)<br />
** Externalizers ITaskListExternalize<br />
** Listeners API, primarily ITaskListChangeListener<br />
** Adapting to ITask and broken selection of the task respositories<br />
* Proxy settings status (Rob)<br />
* Subclipse integration and Team API (Eugene)<br />
<br />
<br />
==== Tuesday, November 21, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Remaining 1.0RC1 items (Mik)<br />
** Issues with tack context (multiple folders, unfiltering issues, etc)<br />
** Issues with new local task UI (focus, inline vs. editor)<br />
** Moving task drop down and pause button out of Task List UI?<br />
* Bugzilla and repository infrastructure status (Rob)<br />
* Trac status (Steffen)<br />
* Web connector status (Mik)<br />
* JIRA connnector status (Mik & Eugene)<br />
Actions<br />
* Mik emails newsgroup/mylar-dev about task list toolbar changes<br />
* Mik fixes classpath of context.core xmlrpc-use<br />
* Visible editor always unfiltered<br />
* Eugene files bug on editor color problem<br />
* Steffen files bug People section with JIRA<br />
<br />
==== Tuesday, November 14, 10-11am PT ====<br />
<br />
Agenda<br />
* Mylar 1.0 priorities.<br />
* Pause button UI (Mik?)<br />
Actions<br />
* Need people section for Trac<br />
* Discuss removing commit context button on newsgroup<br />
* Allow proxy settings to be specified per-repository<br />
<br />
==== Tuesday, October 31, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Authentication infrastructure and connectors (Rob)<br />
* Offline support for JIRA (Mik)<br />
* Pause button UI (Mik)<br />
<br />
<br />
==== Tuesday, October 24, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda<br />
* 0.8 post-mortem (Mik)<br />
* Storage of offline task data (See [[Mylar Task List]]) (Rob)<br />
* JIRA priorities (Mik)<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* [http://dev.eclipse.org/mhonarc/lists/mylar-dev/msg00706.html Alternative integration] with remote repositories (Eugene)<br />
<br />
Actions<br />
* Investigate Lucene as store for offline task data (Rob)<br />
* Investigate showing working sets as top-level nodes in Task List (Mik)<br />
<br />
==== Tuesday, October 17, 10-11am PT ====<br />
<br />
Agenda<br />
* 0.8 release planning<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Rich editor for Trac (Steffen?)<br />
* Repository task data (Rob)<br />
** Offline persistence: object serialization (current), xml, database [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 bug 160389]<br />
** Lazy loading [https://bugs.eclipse.org/bugs/show_bug.cgi?id=157257 bug 157257]<br />
* Issues with Task monitoring and filtering for projects with more then one source folder<br />
* Jira integration planning<br />
* User guide and improving the docs<br />
<br />
Actions<br />
* Need "Add to Task List" action on query hits<br />
* Consider merging the above action with dialog for "Add Existing Task..."<br />
* Need to consider pre-fetching task data for query hits<br />
<br />
==== Tuesday, September 26 2006, 10-11am PT ====<br />
* 0.7 release planning<br />
* Project and repository association (Rob)<br />
* 1.0 planning (Mik)<br />
<br />
==== Wednesday, August 23 2006, 10-11am PT ====<br />
* Planning for 0.6.2<br />
* Generic web Repository Connector integration (Eugene)<br />
* Trac Connector rich editor (Steffen)<br />
* AbstractRepositoryConnector split into core and UI<br />
* Planning for 0.7 and 1.0<br />
* Zest website integration and release cycles<br />
<br />
==== Wednesday, August 2 2006, 10-11am PT ====<br />
Agenda<br />
* 0.6.1 post-mortem<br />
* 0.6.2 and 1.0 planning<br />
* Summer of Code status<br />
** Trac Connector (Steffen)<br />
** Bugzilla enhancements (Jeff)<br />
** JIRA<br />
* Design discussion on splitting AbstractRepositoryConnector into core/ui<br />
* Sandbox release for web connector (Eugene)<br />
Vacations<br />
* Rob: 3rd - 8th<br />
* Mik: 8th - 17th<br />
Actions<br />
* Consumers of APIs update Javadocs as they use them, a la wiki <br />
* Decide on conference call time and interval next meeting<br />
* Investigate Rome dependency for Sandbox (Mik)<br />
<br />
==== Thursday, July 6 2006, 10am PT ====<br />
* wrap up discussion of 0.6 release<br />
* Trac integration status (Steffen)<br />
* enhancing Bugzilla connector status (Jeff)<br />
* Connector naming conventions<br />
* tasks API discussion. String-based task id, separate task id, url and repository url, (issues 146396, 149624, 149509), other refactoring of tasks, hits, query and repository classes<br />
* UI for repository settings<br />
* prioritizing for 0.7 and beyond<br />
* planning and use of Bugzilla priorities<br />
<br />
==== Tuesday, June 13 2006, 10am PT ====<br />
* Schedule a regular meeting time and interval<br />
* Google SoC: Trac integration (Steffen)<br />
* Google Soc: enhancing Bugzilla connector (Jeff)<br />
* Repository connector API discussion (Mik)<br />
* Prioritize tasks for 0.6 (Mik)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=38817Mylyn/Meetings2007-06-11T23:50:11Z<p>Steffen.pingel.eclipse.org: /* Tuesday, June 12, 10-11am PT */</p>
<hr />
<div>[[Category:Mylar]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, June 12, 10-11am PT ====<br />
<br />
* Renaming disaster status<br />
* 2.0 status<br />
* Notification of API changes (Steffen)<br />
<br />
Future:<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* vserver admin status report<br />
<br />
----<br />
<br />
=== Past Meetings ===<br />
<br />
==== Tuesday, June 5, 10-11am PT ====<br />
<br />
* Google Summer of Code kick-off (Balazs, Jevgeni, Xiaoyang)<br />
* vserver admin practices (Rob, Steffen)<br />
* 2.0 end game planning<br />
** Committers 2.0 plan update<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
<i>Stale items</i><br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Actions:<br />
* Rob to administer vserver (corrdinate with Steffen)<br />
** Contact Denis regarding updates<br />
** Investigate backup options<br />
<br />
==== Tuesday, May 29, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Task vs. TaskData; properties vs. class hierarchy (Eugene)<br />
** Full vs. light synchronization (Eugene)<br />
<i>Stale items</i><br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* (Eugene) Proposed eliminating Task hierarchy and replace with property based access<br />
** Suggests merging Task and AbstractRepositoryTask<br />
** Willing to add property support to ITask for 2.1 if requested by integrators.<br />
* (Steffen) The property-based vs. sub-classing discussing is important and we need to consider this for 3.0 again. <br />
* (Rob) raised TaskData migration and committers agree that migraion of existing offline data not practical<br />
<br />
Actions:<br />
* (Mik) introduce class factories and remove custom task externalizers<br />
* replace AbstractQueryHit by Tasks<br />
* allow connectors to submit Task or TaskData objects as hits<br />
* convert offline storage from Java Serialization to XML<br />
* construct attribute editors through factory, do not store repository configuration in offline storage<br />
* apply pending rename changes from porting guide<br />
* refactor attachment API <br />
<br />
<br />
<br />
==== Tuesday, May 22, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* Top voted bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169123 169123]: Updated bug does not preserve values of custom fields in Jira (Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Minutes:<br />
* Task workflow and special query support likely getting bumped<br />
* Rob: related bug#185805 (timestamp bug) and bug#186939 (blocked jobs)<br />
* Steffen: httpclient message.shutdown() can be used to force shutdown of network IO<br />
<br />
Actions:<br />
* Rob and Steffen:<br />
**to start offline refactoring.<br />
**included refactoring of local tasks to AbstractRepositoryTask (P1)<br />
**For RC0, add progress monitor to all api methods that involve IO to easy future implementation.<br />
* Steffen to open new bug for alternate containment representations (outline, task editor can be used to reveal) duplicates for bugzilla could use this<br />
* Mik to make new bug for Open Resource bug related to Task Working sets (defer Eugen's multiple tasklist views patch since will require additional view memento facility?) <br />
* Rob: Will investigate breaking out past activity from scheduled mode (after higher priority api changes).<br />
* For next call: Committers should review their P1 and P2 tasks and form a realistic list for 2.0<br />
<br />
==== Tuesday, May 15, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Decisions made regarding offline TaskData handling and presentation merged with wiki ([[Mylar Offline Refactoring]]).<br />
<br />
==== Tuesday, May 8, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
** Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Additive improvements deferred in favor of API changes.<br />
Main API changes (P2):<br />
* Local task become repository tasks<br />
* Hits become Tasks (but retain UI representation)<br />
* Offline storage improvements ([[Mylar Offline Refactoring]])<br />
* Tasklist externalization<br />
* AbstractRepositoryTaskEditor (make protected methods private)<br />
* Multiple Task Downloads (synch api changes)<br />
* Context listeners api (Mik)<br />
* Extract repository configuration<br />
<br />
<br />
==== Tuesday, May 1, 10-11am PT ====<br />
<br />
* Eclipse Forum Europe report (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Monitor update (Meghan)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
* Post action items/summary/minutes after each meeting (Mik?)<br />
<br />
Actions:<br />
* Eugene<br />
** send screenshot example of strikethrough looking like row lines<br />
* Mik<br />
** consider moving activation to task icon<br />
** working sets in tasklist needs priority since we need to put miles on it before release<br />
* Rob<br />
** persistence api should be finalized so that we can drop in alternate back ends<br />
<br />
==== Tuesday, April 24, 10-11am PT ====<br />
<br />
* Post action items/summary/minutes after each meeting<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* Greg Wilson gave brief overview of planned work for SoC project<br />
* Discussed options for implementing offline storage for task data<br />
* Discussed use cases for RSS support in the Task List<br />
* Discussed tagging and working sets support in the Task List<br />
<br />
Actions:<br />
<br />
* Does it make sense to keep task data separate from the task list?<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165880 165880: Listeners API should allow to pass multiple events in one call] Potential source of refresh issues (Eugene)<br />
<br />
==== Tuesday, April 17, 10-11am PT ====<br />
<br />
* Google Summer of Code planning (Mik)<br />
* ROME depency accepted (Eugene, Mik)<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
** Contributing custom models to task list and task repositories views. per-milestone/version grouping, or grouping query results by certain attributes (Eugene)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API updates (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* Post action items/summary after each meeting<br />
<br />
==== Tuesday, April 10, 10-11am PT ====<br />
<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API changes (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=179873 179873: Completed status not correct for JIRA tasks]<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
==== Tuesday, April 3, 10-11am PT ====<br />
<br />
* Mylar 2.0M2 release wrap-up, 2.0M3 planning (Mik)<br />
* Offline storage strategy design discussion(Rob, Steffen)<br />
<br />
==== Tuesday, March 27, 10-11am PT ====<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
<br />
* Mylar 2.0M2 status<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176513 176513] [api] Multiple task data request (Rob)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 160389] [api] Serialization / loss of data etc (Rob)<br />
* JIRA statuses: resolved vs. closed<br />
<br />
==== Tuesday, March 20, 10-11am PT ====<br />
<br />
* [http://wiki.eclipse.org/index.php/Mylar_GSoC_2007 Goolge Summer of Code ideas] (Mik)<br />
* Eclipse 3.3M6 status (Mik)<br />
* JIRA network utilization ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=175407 175407])<br />
* JIRA test server<br />
* usage reporting (Meghan)<br />
<br />
==== Tuesday, March 13, 10-11am PT ====<br />
<br />
Agenda:<br />
* EclipseCon decompression (Mik)<br />
* JIRA test server (Steffen)<br />
* 2.0M2 planning<br />
* AttributeFactoryUI/RepositoryConfiguration (Rob, Steffen)<br />
<br />
==== Tuesday, February 27, 10-11am PT ====<br />
<br />
Agenda:<br />
* '-' issue - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=166174 bug 166174]<br />
* EclipseCon planning (Mik)<br />
** 3.2 dev build<br />
** Stickers/Buttons/T-shirts<br />
** Poster<br />
* In-place context view (Mik, Eugene)<br />
* GSoC 2007 project (Steffen)<br />
<br />
Actions:<br />
* Find Mylar film glasses (Steffen)<br />
* Find out if there is any space left for poster presentations (Rob)<br />
* At EclipseCon ask EMF folks about using EMF for repository mappings (Mik & Rob)<br />
<br />
==== Tuesday, February 20, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* 2.0M1 release review (Mik)<br />
* Id vs handle vs key (Mik)<br />
* How to make Query creation more obvious for new users (Eugene)<br />
* Showing Task ID/Keys in UI (task list and task dialogs, editor tabs and headers, task history dropdown, change sets) (Eugene)<br />
* JIRA issues (Eugene, Steffen)<br />
<br />
Actions:<br />
* File form header bug<br />
* Create method: TaskList.getTask(String connectorKind, String taskUrl)<br />
* Create AbstractRepositoryTask.getKey()<br />
<br />
==== Tuesday, February 13, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* IP submission follow-ups for Lucene 2.0, Axis2 (Mik)<br />
* Major connector externalizer and task handle usage refactoring (Mik)<br />
* JIRA issues<br />
* Make Steffen JIRA committer<br />
* Discuss refactoring of RepositoryTaskAttributes (bug 150680?) (Steffen)<br />
** Separate UI representation from attribute?<br />
** How to link attributes to repository configuration?<br />
<br />
==== Tuesday, February 6, 10-11am PT ====<br />
<br />
Agenda<br />
* Finalizing of Mylar 2.0 plan (Mik)<br />
* Status of IP submissions (Mik)<br />
* Orbit dependencies<br />
* Status of JIRA<br />
* Issues with handles (Eugene)<br />
* Issues with event notification api (Rob)<br />
<br />
==== Tuesday, January 30, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Moving to Eclipse 3.3M5 builds (Mik)<br />
* Final IP and contribution submissions for Europa (Mik)<br />
* Status Jira Core Services and library dependencies (Steffen)<br />
<br />
==== Tuesday, January 23, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Implementation strategy for<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=171081 171081]: Autodetect JIRA repository for Open Corresponding Task (Eugene)<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=159135 159135]: Automatic resolution of links between projects and issue repositories (Eugene)<br />
* Additional contributions to be made by the Jan. 31st Europa cutoff (Mik)<br />
Actions<br />
* Consider Lucene 2.0 IPZilla submission (Mik)<br />
<br />
==== Tuesday, January 16, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning<br />
* Tomcat and server setup for mylar.eclipse.org<br />
* TaskId vs TaskHandle (numerous issues with JIRA connector) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170587 bug 170587]<br />
* Models and their application to the tasklist (Rob, Eugene) ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147084 147084: merge Task List and Task Activity views])<br />
** "[use] models and provide model that would show unread/changed/conflicting tasks" ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=170606 170606: Add action to Task List to filter out read requests])<br />
** 153573: add support for nesting top level task list elements, e.g. via incorporating working sets<br />
* Task web browser<br />
Actions:<br />
* Add milestone buckets 2.0M1 through M3 (Mik)<br />
* Gets JIRA enterprise license key for test server (Mik)<br />
* Ask about server backup policy (2.6 Gigs used), disk space for usage data (Mik)<br />
* Consider downgrading Tomcat to 5.5 (Meghan)<br />
* Write up Mylar monitor data collection project (Meghan)<br />
* Plans hyperlink detection improvements and bugs (Rob)<br />
**170679: [api] improve hyperlink detection api<br />
**170681: [api] allow connectors to contribute alternate content providers (models) to tasklist<br />
**170685: [api] allow connectors to contribute filters to tasklist<br />
<br />
==== Tuesday, Januray 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylar 2.0 milestone and Europa planning.<br />
* Synchronization, progress indication, and cancellation of repository task operations ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168257 168257], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=150682 150682], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154258 154258], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 143011])<br />
* Mylar error handling ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168049 168049], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168672 168672], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165383 165383])<br />
* Task activity timing improvement ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147537 147537])<br />
* JIRA issues (auth problem and integrating JIRA client)<br />
Actions:<br />
* Write up error policy (Steffen)<br />
* Plan synchronization related bugs (Rob)<br />
* Find platform release dates (Mik)<br />
* Define scope of project on planning page (Mik)<br />
* Add dummy query on codehouse project (Mik)<br />
<br />
==== Tuesday, December 19, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* 1.0.1 priorities (Mik) <br />
* Slap Eugene for discrediting Mylar in blogs and Mik for not blogging<br />
* Layout of search/query page<br />
<br />
==== Tuesday, December 12, 10-10:30am PT ====<br />
* Mylar 1.0 celebration and retrospective.<br />
* Brock Janiczak's JIRA core services contribution (Eugene, Mik?).<br />
* Discovery update sites (Eugene, Mik).<br />
* Version numbers (Mik).<br />
<br />
==== Tuesday, December 5, 10-10:30am PT ====<br />
* Remaining priorities for 1.0 (Mik)<br />
* API status (Mik)<br />
** Externalizers ITaskListExternalize<br />
** Listeners API, primarily ITaskListChangeListener<br />
** Adapting to ITask and broken selection of the task respositories<br />
* Proxy settings status (Rob)<br />
* Subclipse integration and Team API (Eugene)<br />
<br />
<br />
==== Tuesday, November 21, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Remaining 1.0RC1 items (Mik)<br />
** Issues with tack context (multiple folders, unfiltering issues, etc)<br />
** Issues with new local task UI (focus, inline vs. editor)<br />
** Moving task drop down and pause button out of Task List UI?<br />
* Bugzilla and repository infrastructure status (Rob)<br />
* Trac status (Steffen)<br />
* Web connector status (Mik)<br />
* JIRA connnector status (Mik & Eugene)<br />
Actions<br />
* Mik emails newsgroup/mylar-dev about task list toolbar changes<br />
* Mik fixes classpath of context.core xmlrpc-use<br />
* Visible editor always unfiltered<br />
* Eugene files bug on editor color problem<br />
* Steffen files bug People section with JIRA<br />
<br />
==== Tuesday, November 14, 10-11am PT ====<br />
<br />
Agenda<br />
* Mylar 1.0 priorities.<br />
* Pause button UI (Mik?)<br />
Actions<br />
* Need people section for Trac<br />
* Discuss removing commit context button on newsgroup<br />
* Allow proxy settings to be specified per-repository<br />
<br />
==== Tuesday, October 31, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Authentication infrastructure and connectors (Rob)<br />
* Offline support for JIRA (Mik)<br />
* Pause button UI (Mik)<br />
<br />
<br />
==== Tuesday, October 24, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda<br />
* 0.8 post-mortem (Mik)<br />
* Storage of offline task data (See [[Mylar Task List]]) (Rob)<br />
* JIRA priorities (Mik)<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* [http://dev.eclipse.org/mhonarc/lists/mylar-dev/msg00706.html Alternative integration] with remote repositories (Eugene)<br />
<br />
Actions<br />
* Investigate Lucene as store for offline task data (Rob)<br />
* Investigate showing working sets as top-level nodes in Task List (Mik)<br />
<br />
==== Tuesday, October 17, 10-11am PT ====<br />
<br />
Agenda<br />
* 0.8 release planning<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Rich editor for Trac (Steffen?)<br />
* Repository task data (Rob)<br />
** Offline persistence: object serialization (current), xml, database [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 bug 160389]<br />
** Lazy loading [https://bugs.eclipse.org/bugs/show_bug.cgi?id=157257 bug 157257]<br />
* Issues with Task monitoring and filtering for projects with more then one source folder<br />
* Jira integration planning<br />
* User guide and improving the docs<br />
<br />
Actions<br />
* Need "Add to Task List" action on query hits<br />
* Consider merging the above action with dialog for "Add Existing Task..."<br />
* Need to consider pre-fetching task data for query hits<br />
<br />
==== Tuesday, September 26 2006, 10-11am PT ====<br />
* 0.7 release planning<br />
* Project and repository association (Rob)<br />
* 1.0 planning (Mik)<br />
<br />
==== Wednesday, August 23 2006, 10-11am PT ====<br />
* Planning for 0.6.2<br />
* Generic web Repository Connector integration (Eugene)<br />
* Trac Connector rich editor (Steffen)<br />
* AbstractRepositoryConnector split into core and UI<br />
* Planning for 0.7 and 1.0<br />
* Zest website integration and release cycles<br />
<br />
==== Wednesday, August 2 2006, 10-11am PT ====<br />
Agenda<br />
* 0.6.1 post-mortem<br />
* 0.6.2 and 1.0 planning<br />
* Summer of Code status<br />
** Trac Connector (Steffen)<br />
** Bugzilla enhancements (Jeff)<br />
** JIRA<br />
* Design discussion on splitting AbstractRepositoryConnector into core/ui<br />
* Sandbox release for web connector (Eugene)<br />
Vacations<br />
* Rob: 3rd - 8th<br />
* Mik: 8th - 17th<br />
Actions<br />
* Consumers of APIs update Javadocs as they use them, a la wiki <br />
* Decide on conference call time and interval next meeting<br />
* Investigate Rome dependency for Sandbox (Mik)<br />
<br />
==== Thursday, July 6 2006, 10am PT ====<br />
* wrap up discussion of 0.6 release<br />
* Trac integration status (Steffen)<br />
* enhancing Bugzilla connector status (Jeff)<br />
* Connector naming conventions<br />
* tasks API discussion. String-based task id, separate task id, url and repository url, (issues 146396, 149624, 149509), other refactoring of tasks, hits, query and repository classes<br />
* UI for repository settings<br />
* prioritizing for 0.7 and beyond<br />
* planning and use of Bugzilla priorities<br />
<br />
==== Tuesday, June 13 2006, 10am PT ====<br />
* Schedule a regular meeting time and interval<br />
* Google SoC: Trac integration (Steffen)<br />
* Google Soc: enhancing Bugzilla connector (Jeff)<br />
* Repository connector API discussion (Mik)<br />
* Prioritize tasks for 0.6 (Mik)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=38107Mylyn/Porting Guide2007-06-05T04:13:56Z<p>Steffen.pingel.eclipse.org: /* Tasks API */</p>
<hr />
<div>[[Category:Mylar]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from Mylar 1.0 to 2.0 =<br />
<br />
== ''Pending Changes'' ==<br />
<br />
The following changes are planned but not yet implemented. Email mylar-dev if any of these pose a problem.<br />
<br />
* <code>AbstractRepositoryTaskEditor</code><br />
** creation of the <code>Composite</code> for "Attributes" section moved out of the <code>createAttributeLayout(..)</code> method into <code>createSections()</code>. So, method <code>createAttributeLayout(..)</code> is now takes that composite as parameter and returns <code>void</code>.<br />
<br />
* <code>AbstractRepositoryConnector</code>:<br />
** rename <code>createTaskFromExistingKey(..)</code> to <code>addExistingTask(..)</code><br />
** rename getRepositoryType() to getConnectorKind()<br />
<br />
* <code>AbstractRepositoryConnectorUi</code>:<br />
** remove hasRichEditor();<br />
<br />
* <code>AbstractRepositoryQuery</code><br />
** rename to <code>AbstractRepositoryTaskContainer</code> or merge with <code>AbstractTaskContainer</code><br />
<br />
* <code>AbstractRepositoryTask</code><br />
** rename getRepositoryKind() to getConnectorKind()<br />
** rename setLastSyncDateStamp() to setLastReadTimeStamp()<br />
** rename getLastSyncDateStamp() to getLastReadTimeStamp()<br />
<br />
* <code>IRepositoryConstants</code><br />
**rename PROPERTY_KIND to PROPERTY_CONNECTOR_KIND<br />
<br />
* <code>Task</code><br />
** rename getRepositoryKind() to getConnectorKind()<br />
** rename getDescription() to getSummary()<br />
** rename setKind() to setTaskKind()<br />
<br />
* <code>TaskListManager</code><br />
** task activity methods might move to a new TaskActivityManager class<br />
<br />
* <code>TaskRepository</code>:<br />
** rename <code>getKind()</code> to <code>getConnectorKind()</code><br />
** Make class final<br />
<br />
* Bridges:<br />
** Dtructure bridge: consider changing contentType -> structureKind<br />
<br />
== General ==<br />
<br />
* Library dependencies have moved to <code>org.eclipse.mylar</code><br />
<br />
* <code>MylarStatusHandler</code> and <code>IStatusHandler</code><br />
** moved from <code>org.eclipse.mylar.context.core</code> to <code>org.eclipse.mylar.core</code><br />
<br />
* <code>MylarStatus</code> (place holder, will improve as we solidify this)<br />
** <code>MylarStatusHandler.displayStatus(dialog title, IStatus status)</code> - call to display error and information dialogs<br />
** When returning <code>CoreException</code> pass in a <code>MylarStatus</code> with appropriate code (see <code>IMylarStatusConstants</code>).<br />
** If <code>IMylarStatusConstants.INTERNAL_ERROR</code> is sent to <code>MylarStatusHandler.displayStatus</code> an error dialog will appear and the error will be logged.<br />
** <code>IMylarStatusConstants.REPOSITORY_COLLISION</code> used for mid-air collision. Pass repository url and appropriate dialog will be displayed.<br />
<br />
* <code>WebClientUtil</code><br />
** moved from <code>..mylar.tasks.core</code> to <code>..mylar.core.net</code><br />
<br />
* Methods that do I/O operations now take an <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
<br />
== Tasks API == <br />
<br />
Sorting is alphabetical. <br />
<br />
* <code>AbstractQueryHit</code><br />
** <code>setDescription(..)</code> renamed to <code>setSummary(..)</code><br />
<br />
* <code>AbstractRepositoryConnector</code><br />
** <code>getLastSyncTimestamp(TaskRepository repository, Set<AbstractRepositoryTask> changedTasks)</code>: added (may change as part of [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176934 bug#176934])<br />
** <code>getSupportedVersions()</code> has been removed ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=176815 #1768159])<br />
** <code>createTaskFromExistingId()</code> is no longer abstract and takes care of task creation<br />
** <code>updateTaskFromTaskData(TaskRepository, AbstractRepositoryTask, RepositoryTaskData, boolean retrieveSubTasks)</code> added. Must be implemented to handle updating information on the <code>AbstractRepositoryTask</code> with data from the <code>RepositoryTaskData</code><br />
** renamed <code>updateTask</code> to <code>updateTaskFromRepository</code><br />
** <code>createTaskFromExistingKey()</code> renamed to createTaskFromExistingId() and is final<br />
** <code>makeTask()</code> added. Connector specific repository task construction<br />
** <code>setTaskDataManager()</code> added. Manager set upon connector construction in TasksUiPlugin. If being used headless, will need to manually set for offline support.<br />
<br />
* <code>AbstractRepositoryConnectorUi</code><br />
** <code>openRemoteTask(String repositoryUrl, String id)</code>: removed, this method no longer needs to be implemented by the connector. Instead classes can rely on the new <code>openRepositoryTask(..)</code> method, and override it if necessary.<br />
** getRepositoryUrl and all ID/URL methods: now final, change via setters<br />
** + findHyperlinks(...) override to detect hyperlinks in editors<br />
** handlesDueDates() added. Override and return true if connector capable of handling due dates.<br />
** getTaskKindLabel(RepositoryTaskData) returns suitable label for task kind (default is 'Task') override to suit<br />
<br />
* <code>AbstractRepositoryQuery</code><br />
** <code>setMaxHits()</code> removed and constrctor no longer takes number of hits. Connectors can use QueryHitCollector.MAX_HITS (currently 5000) when setting max number of hits to return.<br />
<br />
*<code>AbstractRepositorySettingsPage</code> validation changes.<br />
**<code>setNeedsValidation(boolean needsValidation)</code> if true validate button will be visible<br />
**<code>getValidator(TaskRepository repository)</code> return an instance of <code>Validator</code>. <br />
<br />
* <code>AbstractRepositoryTask</code><br />
** constructor now requires taskId (now immutable)<br />
** getIdentifyingLabel() -> getTaskKey()<br />
** getLastRefreshTimeInMinutes(Date) removed<br />
** no more static methods (use RepositoryTaskHandleUtil)<br />
** Replace this idiom:<br />
String handleIdentifier = AbstractRepositoryTask.getHandle(repository.getUrl(), taskId);<br />
ITask task = TasksUiPlugin.getTaskListManager().getTaskList().getTask(handle);<br />
** with:<br />
ITask task = TasksUiPlugin.getTaskListManager().getTaskList().getTask(repository.getUrl(), taskId);<br />
** isDirty() and setDirty() removed<br />
** isDownloaded() removed<br />
** getTaskData(), setTaskData() removed<br />
** isSubmitting(), setSubmitting() added<br />
<br />
* <code>AbstractRepositoryTaskEditor</code><br />
** <code>attachContext()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
**<code>attributeChanged()</code> Anything that needs to be saved must be in attribute form and passed to this method. Most if this is all done for you but if you override AbstractRepositoryTaskEditor.createCustomAttributeLayout() then you will want to ensure that attributeChanged is called upon editing. Utility method createTextField() handles this call. <br />
** <code>createLabel()</code> Utility method added. It will put an '*' at the front of the label if the attribute has been modified. Eventually this will be applied upon editing but currently only happens after re-freshing or re-opening the editor.<br />
** <code>createTaskFromExistingId()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
** <code>handleNewBugPost()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
** <code>SECTION_NAME</code> is an enum that holds default titles for the default sections. To override these default titles, set the appropriate (SECTION_NAME, new name) in <code>alternateSectionLabels</code> on <code>AbstractRepositoryTaskEditor</code>.<br />
** <code>updateEditor()</code> refreshes editor with new input in-place.<br />
** <code>uploadTaskFromRepository()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
<br />
<br />
*<code> AttributeContainer</code><br />
**<code>getAttributeFactory()</code> new method<br />
<br />
* <code>DateRangeContainer</code><br />
** getChildren() now returns set of underlying task objects (not DateRangeActivityDelegates which will be deprecated)<br />
** getDateRangeDelegates() returns the delegate formerly returned by getChildren()<br />
<br />
* <code>DelegatingTaskExternalizer</code><br />
** <code>readTaskInfo(..)</code> and <code>readQueryHitInfo(..)</code> are now called automatically and are private. Use your <code>createTask(..)</code> or <code>createQueryHit(..)</code> methods to customize reading additional attributes.<br />
<br />
* <code>DelegatingTaskExternalizer</code> <br />
** init() removed<br />
** readTaskData() removed<br />
<br />
* <code>IAttachmentHandler</code><br />
** <code>downloadAttachment()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011]). The data is now written to an <code>OutputStream</code> instead of a <code>File</code> ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=186070 #]186070). A default implementation for this method which uses <code>getAttachmentAsStream()</code> for retrieving the attachment is provided in <code>AbstractAttachmentHandler</code>.<br />
** <code>getAttachmentData()</code> has been replaced by <code>getAttachmentAsStream()</code> which now returns an InputStream for reading the attachment data ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=186070 #]186070).<br />
** <code>uploadAttachment()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011]). Attachment properties are now passed as an object of type <code>ITaskAttachment</code>. This interface provides a <code>createInputStream()</code> method to create a stream for reading the data source ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=186070 #]186070).<br />
<br />
* ITask<br />
** <code>setDescription(...)</code> renamed to <code>setSummary</code><br />
<br />
* <code>ITaskDataHandler</code><br />
** <code>getChangedSinceLastSync()</code> method moved to <code>AbstractRepositoryConnector</code><br />
** New comment now held in an attribute: <code>RepositoryTaskAttribute.COMMENT_NEW</code> will need to update handler and factory to produce connector specific attribute<br />
** <code>getTaskData()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
** <code>initializeTaskData(TaskRepository repository, RepositoryTaskData data, IProgressMonitor monitor)</code> called by NewTaskWizard to initialize new taskData objects (currently only in use by Trac but will adopt).<br />
** <code>getAttributeFactory(String repositoryUrl, String repositoryKind, String taskKind)</code> signature changed<br />
** <code>getDateForAttributeType(...)</code> moved to <code>AbstractAttributeFactory</code><br />
** <code>postTaskData()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
<br />
* <code>ITaskListElement</code>: now extends <code>java.lang.Comparable</code>, so Collections support of sorting can be used, since task list elements have a natural ordering. Default implementations are provided for tasks and containers. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=171590 bug 171590])<br />
<br />
* <code>ITaskListExternalizer</code><br />
** <code>readTask(..)</code> renamed to <code>createTask(..)</code>, no longer needs to set taskId, label, or repositoryUrl<br />
<br />
* <code>QueryHitCollector</code><br />
** MAX_HITS constant can be used as standard default number of hits handled per query. User notified when >= hits returned.<br />
<br />
* <code>RepositorySynchronizationManager</code><br />
** <code>updateOfflineState</code> is now <code>saveIncoming</code> and <code>saveOutgoing</code>. <br />
** <code>discardOutgoing</code> discards any pending outgoing changes<br />
<br />
* <code>RepositoryTaskAttribute</code><br />
** getID() -> getId()<br />
<br />
*<code>RepositoryTaskData</code><br />
**constructor now requires a task kind (string) (i.e. <code>Task.DEFAULT_TASK_KIND</code>)<br />
**<code>getTaskKind</code> return the task kind<br />
**<code>setNew(boolean)</code> signifies that this is unsubmitted task data. Used by editor factory to determine if existing or new editor to be opened.<br />
<br />
* <code>SynchronizeQueryJob</code><br />
** renamed setSynchTasks() to setSynchChangedTasks()<br />
<br />
* <code>Task</code><br />
** <code>dropSubTasks</code>: added, removes all subtasks<br />
** <code>getTooltipText()</code>: deleted, not used<br />
** Due dates are now supported <code>getDueDate(), setDueDate()</code><br />
** handleIdentifier: now private<br />
** get/setUrl are now get/setTaskUrl (to disambiguate with get/setRepositoryUrl())<br />
** <code>getElapsedTime()</code>: removed, not used previously, use <code>TaskListManager.getElapsedTime(ITask)</code> instead (note this method might move)<br />
** <code>setElapsedTime()</code>: removed, not used<br />
<br />
* <code>TaskEditor</code><br />
** <code>protected void pageChange(intNewPageIndex)</code> method removed (only called super)<br />
<br />
* <code>TaskList</code><br />
** <code>getChangeListeners()</code>: returns a <code>Set</code> instead of <code>List</code><br />
** <code>getRootCategory</code> renamed to <code>getUncategorizedCategory</code><br />
<br />
<br />
* <code>TaskListImages</code><br />
** renamed to <code>TasksUiImages</code> (still an internal class, should move to API)<br />
<br />
* <code>TaskListManager</code><br />
** <code>setDueDate()</code> used to set due date on a task and cause notification of local info changed.<br />
** <code>isDue(ITask)</code> true if task's due date isn't null and date has past<br />
<br />
* <code>TaskListWriter</code><br />
** <code>setTaskDataManager()</code> removed<br />
<br />
* <code>TaskRepository</code><br />
**TaskRepository.isAnonymous()<br />
**TaskRepository.setAnonymous(boolean)<br />
** (-) TaskRepository.getDefaultProxy() (Renamed and moved to WebClientUtil.getPlatformProxy())<br />
<br />
* <code>TasksUiUtil</code><br />
** <code>openUrl(String url)</code>: moved to <code>openUrl(String url, boolean useRichEditor)</code><br />
** <code>getImageDescriptorForPriority(..)</code> moved to TasksUiImages<br />
** <code>getImageForPriority(..)</code>moved to TasksUiImages<br />
<br />
== Context API ==<br />
* <code>AbstractContextUiBridge<code><br />
** removed: <code>restoreEditor(IMylarElement)</code> use <code>open(IMylarElement)</code> instead<br />
* <code>AbstractContextStore</code><br />
** <code>notifyContextStoreMoved()</code>: change to <code>contextStoreMoved()</code><br />
* <code>AbstractContextStructureBridge</code><br />
** <code>getDegreesOfSeparation()</code>: moved to <code>AbstractRelationProvider</code><br />
** <code>getRelationshipProviders()</code>: moved to extensions point, e.g.:<br />
<br />
<extension point="org.eclipse.mylar.context.core.bridges"><br />
<relationProvider<br />
class="org.eclipse.mylar.internal.java.search.JavaImplementorsProvider"<br />
contentType="java"/><br />
</extension><br />
<br />
* <code>IMylarContextListener</code>: renamed to <code>IInteractionContextListener</code><br />
** <code>contextCleared(..)</code>: added<br />
** <code>presentationSettingsChanging(..)</code>: removed, not used<br />
** <code>presentationSettingsChanged(..)</code>: removed, not used<br />
** <code>UpdateKind</code>: removed, not used<br />
<br />
* <code>IMylarContext</code>: renamed to <code>IInteranctionContext</code><br />
** <code>getHandleIdentifier()</code>: added to facilitate mapping<br />
<br />
* <code>IMylarElement</code>: renamed to <code>IInteractionElement</code><br />
* <code>IMylarObject</code>: renamed to <code>IInteractionObject</code><br />
* <code>IMylarRelation</code>: renamed to <code>IInteractionRelation</code><br />
* <code>IContextWriter</code>: renamed to <code>IInteractionContextWriter</code><br />
* <code>IContextReader</code>: renamed to <code>IInteractionContextReader</code><br />
* <code>IMylarContextListener</code>: renamed to <code>IInteractionContextListener</code><br />
* <code>MylarContextManager</code>: renamed to <code>InteractionContextManager</code><br />
<br />
== Monitor API ==<br />
<br />
*<code>MylarMonitorUiPlugin</code>: renamed to <code>MonitorUiPlugin</code><br />
** (-) setInactivityTimeout(...)<br />
<br />
* <code>org.eclipse.mylar.monitor</code>: split into <code>monitor.core</code> and <code>monitor.ui</code>, organize imports and update extension point IDs<br />
* <code>HandleObfuscator</code><br />
** moved to <code>InteractionEventObfuscator</code><br />
<br />
* <code>org.eclipse.mylar.monitor.usage.core</code> and <code>org.eclipse.mylar.monitor.usage.ui</code><br />
** moved to <code>..mylar.monitor.core</code>, <code>..mylar.monitor.usage</code> and <code>..mylar.monitor.usage.internal</code></div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=37971Mylyn/Porting Guide2007-06-03T04:40:35Z<p>Steffen.pingel.eclipse.org: /* Tasks API */</p>
<hr />
<div>[[Category:Mylar]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from Mylar 1.0 to 2.0 =<br />
<br />
== ''Pending Changes'' ==<br />
<br />
The following changes are planned but not yet implemented. Email mylar-dev if any of these pose a problem.<br />
<br />
* <code>AbstractRepositoryTaskEditor</code><br />
** creation of the <code>Composite</code> for "Attributes" section moved out of the <code>createAttributeLayout(..)</code> method into <code>createSections()</code>. So, method <code>createAttributeLayout(..)</code> is now takes that composite as parameter and returns <code>void</code>.<br />
<br />
* <code>AbstractRepositoryConnector</code>:<br />
** rename <code>createTaskFromExistingKey(..)</code> to <code>addExistingTask(..)</code><br />
** rename getRepositoryType() to getConnectorKind()<br />
<br />
* <code>AbstractRepositoryConnectorUi</code>:<br />
** remove hasRichEditor();<br />
<br />
* <code>AbstractRepositoryQuery</code><br />
** rename to <code>AbstractRepositoryTaskContainer</code> or merge with <code>AbstractTaskContainer</code><br />
<br />
* <code>AbstractRepositoryTask</code><br />
** rename getRepositoryKind() to getConnectorKind()<br />
** rename setLastSyncDateStamp() to setLastReadTimeStamp()<br />
** rename getLastSyncDateStamp() to getLastReadTimeStamp()<br />
<br />
* <code>IRepositoryConstants</code><br />
**rename PROPERTY_KIND to PROPERTY_CONNECTOR_KIND<br />
<br />
* <code>Task</code><br />
** rename getRepositoryKind() to getConnectorKind()<br />
** rename getDescription() to getSummary()<br />
** rename setKind() to setTaskKind()<br />
<br />
* <code>TaskListManager</code><br />
** task activity methods might move to a new TaskActivityManager class<br />
<br />
* <code>TaskRepository</code>:<br />
** rename <code>getKind()</code> to <code>getConnectorKind()</code><br />
** Make class final<br />
<br />
* Bridges:<br />
** Dtructure bridge: consider changing contentType -> structureKind<br />
<br />
== General ==<br />
<br />
* Library dependencies have moved to <code>org.eclipse.mylar</code><br />
<br />
* <code>MylarStatusHandler</code> and <code>IStatusHandler</code><br />
** moved from <code>org.eclipse.mylar.context.core</code> to <code>org.eclipse.mylar.core</code><br />
<br />
* <code>MylarStatus</code> (place holder, will improve as we solidify this)<br />
** <code>MylarStatusHandler.displayStatus(dialog title, IStatus status)</code> - call to display error and information dialogs<br />
** When returning <code>CoreException</code> pass in a <code>MylarStatus</code> with appropriate code (see <code>IMylarStatusConstants</code>).<br />
** If <code>IMylarStatusConstants.INTERNAL_ERROR</code> is sent to <code>MylarStatusHandler.displayStatus</code> an error dialog will appear and the error will be logged.<br />
** <code>IMylarStatusConstants.REPOSITORY_COLLISION</code> used for mid-air collision. Pass repository url and appropriate dialog will be displayed.<br />
<br />
* <code>WebClientUtil</code><br />
** moved from <code>..mylar.tasks.core</code> to <code>..mylar.core.net</code><br />
<br />
* Methods that do I/O operations now take an <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
<br />
== Tasks API == <br />
<br />
Sorting is alphabetical. <br />
<br />
* <code>AbstractQueryHit</code><br />
** <code>setDescription(..)</code> renamed to <code>setSummary(..)</code><br />
<br />
* <code>AbstractRepositoryConnector</code><br />
** <code>getLastSyncTimestamp(TaskRepository repository, Set<AbstractRepositoryTask> changedTasks)</code>: added (may change as part of [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176934 bug#176934])<br />
** <code>getSupportedVersions()</code> has been removed ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=176815 #1768159])<br />
** <code>createTaskFromExistingId()</code> is no longer abstract and takes care of task creation<br />
** <code>updateTaskFromTaskData(TaskRepository, AbstractRepositoryTask, RepositoryTaskData, boolean retrieveSubTasks)</code> added. Must be implemented to handle updating information on the <code>AbstractRepositoryTask</code> with data from the <code>RepositoryTaskData</code><br />
** renamed <code>updateTask</code> to <code>updateTaskFromRepository</code><br />
** <code>createTaskFromExistingKey()</code> renamed to createTaskFromExistingId() and is final<br />
** <code>makeTask()</code> added. Connector specific repository task construction<br />
** <code>setTaskDataManager()</code> added. Manager set upon connector construction in TasksUiPlugin. If being used headless, will need to manually set for offline support.<br />
<br />
* <code>AbstractRepositoryConnectorUi</code><br />
** <code>openRemoteTask(String repositoryUrl, String id)</code>: removed, this method no longer needs to be implemented by the connector. Instead classes can rely on the new <code>openRepositoryTask(..)</code> method, and override it if necessary.<br />
** getRepositoryUrl and all ID/URL methods: now final, change via setters<br />
** + findHyperlinks(...) override to detect hyperlinks in editors<br />
** handlesDueDates() added. Override and return true if connector capable of handling due dates.<br />
** getTaskKindLabel(RepositoryTaskData) returns suitable label for task kind (default is 'Task') override to suit<br />
<br />
* <code>AbstractRepositoryQuery</code><br />
** <code>setMaxHits()</code> removed and constrctor no longer takes number of hits. Connectors can use QueryHitCollector.MAX_HITS (currently 5000) when setting max number of hits to return.<br />
<br />
*<code>AbstractRepositorySettingsPage</code> validation changes.<br />
**<code>setNeedsValidation(boolean needsValidation)</code> if true validate button will be visible<br />
**<code>getValidator(TaskRepository repository)</code> return an instance of <code>Validator</code>. <br />
<br />
* <code>AbstractRepositoryTask</code><br />
** constructor now requires taskId (now immutable)<br />
** getIdentifyingLabel() -> getTaskKey()<br />
** getLastRefreshTimeInMinutes(Date) removed<br />
** no more static methods (use RepositoryTaskHandleUtil)<br />
** Replace this idiom:<br />
String handleIdentifier = AbstractRepositoryTask.getHandle(repository.getUrl(), taskId);<br />
ITask task = TasksUiPlugin.getTaskListManager().getTaskList().getTask(handle);<br />
** with:<br />
ITask task = TasksUiPlugin.getTaskListManager().getTaskList().getTask(repository.getUrl(), taskId);<br />
** isDirty() and setDirty() removed<br />
** isDownloaded() removed<br />
** getTaskData(), setTaskData() removed<br />
** isSubmitting(), setSubmitting() added<br />
<br />
* <code>AbstractRepositoryTaskEditor</code><br />
** <code>attachContext()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
**<code>attributeChanged()</code> Anything that needs to be saved must be in attribute form and passed to this method. Most if this is all done for you but if you override AbstractRepositoryTaskEditor.createCustomAttributeLayout() then you will want to ensure that attributeChanged is called upon editing. Utility method createTextField() handles this call. <br />
** <code>createLabel()</code> Utility method added. It will put an '*' at the front of the label if the attribute has been modified. Eventually this will be applied upon editing but currently only happens after re-freshing or re-opening the editor.<br />
** <code>createTaskFromExistingId()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
** <code>handleNewBugPost()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
** <code>SECTION_NAME</code> is an enum that holds default titles for the default sections. To override these default titles, set the appropriate (SECTION_NAME, new name) in <code>alternateSectionLabels</code> on <code>AbstractRepositoryTaskEditor</code>.<br />
** <code>updateEditor()</code> refreshes editor with new input in-place.<br />
** <code>uploadTaskFromRepository()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
<br />
<br />
*<code> AttributeContainer</code><br />
**<code>getAttributeFactory()</code> new method<br />
<br />
* <code>DateRangeContainer</code><br />
** getChildren() now returns set of underlying task objects (not DateRangeActivityDelegates which will be deprecated)<br />
** getDateRangeDelegates() returns the delegate formerly returned by getChildren()<br />
<br />
* <code>DelegatingTaskExternalizer</code><br />
** <code>readTaskInfo(..)</code> and <code>readQueryHitInfo(..)</code> are now called automatically and are private. Use your <code>createTask(..)</code> or <code>createQueryHit(..)</code> methods to customize reading additional attributes.<br />
<br />
* <code>DelegatingTaskExternalizer</code> <br />
** init() removed<br />
** readTaskData() removed<br />
<br />
* <code>IAttachmentHandler</code><br />
** <code>downloadAttachment()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
** <code>getAttachmentData()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
** <code>uploadAttachment()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
<br />
* ITask<br />
** <code>setDescription(...)</code> renamed to <code>setSummary</code><br />
<br />
* <code>ITaskDataHandler</code><br />
** <code>getChangedSinceLastSync()</code> method moved to <code>AbstractRepositoryConnector</code><br />
** New comment now held in an attribute: <code>RepositoryTaskAttribute.COMMENT_NEW</code> will need to update handler and factory to produce connector specific attribute<br />
** <code>getTaskData()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
** <code>initializeTaskData(TaskRepository repository, RepositoryTaskData data, IProgressMonitor monitor)</code> called by NewTaskWizard to initialize new taskData objects (currently only in use by Trac but will adopt).<br />
** <code>getAttributeFactory(String repositoryUrl, String repositoryKind, String taskKind)</code> signature changed<br />
** <code>getDateForAttributeType(...)</code> moved to <code>AbstractAttributeFactory</code><br />
** <code>postTaskData()</code> Added <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
<br />
* <code>ITaskListElement</code>: now extends <code>java.lang.Comparable</code>, so Collections support of sorting can be used, since task list elements have a natural ordering. Default implementations are provided for tasks and containers. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=171590 bug 171590])<br />
<br />
* <code>ITaskListExternalizer</code><br />
** <code>readTask(..)</code> renamed to <code>createTask(..)</code>, no longer needs to set taskId, label, or repositoryUrl<br />
<br />
* <code>QueryHitCollector</code><br />
** MAX_HITS constant can be used as standard default number of hits handled per query. User notified when >= hits returned.<br />
<br />
* <code>RepositorySynchronizationManager</code><br />
** <code>updateOfflineState</code> is now <code>saveIncoming</code> and <code>saveOutgoing</code>. <br />
** <code>discardOutgoing</code> discards any pending outgoing changes<br />
<br />
* <code>RepositoryTaskAttribute</code><br />
** getID() -> getId()<br />
<br />
*<code>RepositoryTaskData</code><br />
**constructor now requires a task kind (string) (i.e. <code>Task.DEFAULT_TASK_KIND</code>)<br />
**<code>getTaskKind</code> return the task kind<br />
**<code>setNew(boolean)</code> signifies that this is unsubmitted task data. Used by editor factory to determine if existing or new editor to be opened.<br />
<br />
* <code>SynchronizeQueryJob</code><br />
** renamed setSynchTasks() to setSynchChangedTasks()<br />
<br />
* <code>Task</code><br />
** <code>dropSubTasks</code>: added, removes all subtasks<br />
** <code>getTooltipText()</code>: deleted, not used<br />
** Due dates are now supported <code>getDueDate(), setDueDate()</code><br />
** handleIdentifier: now private<br />
** get/setUrl are now get/setTaskUrl (to disambiguate with get/setRepositoryUrl())<br />
** <code>getElapsedTime()</code>: removed, not used previously, use <code>TaskListManager.getElapsedTime(ITask)</code> instead (note this method might move)<br />
** <code>setElapsedTime()</code>: removed, not used<br />
<br />
* <code>TaskEditor</code><br />
** <code>protected void pageChange(intNewPageIndex)</code> method removed (only called super)<br />
<br />
* <code>TaskList</code><br />
** <code>getChangeListeners()</code>: returns a <code>Set</code> instead of <code>List</code><br />
** <code>getRootCategory</code> renamed to <code>getUncategorizedCategory</code><br />
<br />
<br />
* <code>TaskListImages</code><br />
** renamed to <code>TasksUiImages</code> (still an internal class, should move to API)<br />
<br />
* <code>TaskListManager</code><br />
** <code>setDueDate()</code> used to set due date on a task and cause notification of local info changed.<br />
** <code>isDue(ITask)</code> true if task's due date isn't null and date has past<br />
<br />
* <code>TaskListWriter</code><br />
** <code>setTaskDataManager()</code> removed<br />
<br />
* <code>TaskRepository</code><br />
**TaskRepository.isAnonymous()<br />
**TaskRepository.setAnonymous(boolean)<br />
** (-) TaskRepository.getDefaultProxy() (Renamed and moved to WebClientUtil.getPlatformProxy())<br />
<br />
* <code>TasksUiUtil</code><br />
** <code>openUrl(String url)</code>: moved to <code>openUrl(String url, boolean useRichEditor)</code><br />
** <code>getImageDescriptorForPriority(..)</code> moved to TasksUiImages<br />
** <code>getImageForPriority(..)</code>moved to TasksUiImages<br />
<br />
== Context API ==<br />
* <code>AbstractContextUiBridge<code><br />
** removed: <code>restoreEditor(IMylarElement)</code> use <code>open(IMylarElement)</code> instead<br />
* <code>AbstractContextStore</code><br />
** <code>notifyContextStoreMoved()</code>: change to <code>contextStoreMoved()</code><br />
* <code>AbstractContextStructureBridge</code><br />
** <code>getDegreesOfSeparation()</code>: moved to <code>AbstractRelationProvider</code><br />
** <code>getRelationshipProviders()</code>: moved to extensions point, e.g.:<br />
<br />
<extension point="org.eclipse.mylar.context.core.bridges"><br />
<relationProvider<br />
class="org.eclipse.mylar.internal.java.search.JavaImplementorsProvider"<br />
contentType="java"/><br />
</extension><br />
<br />
* <code>IMylarContextListener</code>: renamed to <code>IInteractionContextListener</code><br />
** <code>contextCleared(..)</code>: added<br />
** <code>presentationSettingsChanging(..)</code>: removed, not used<br />
** <code>presentationSettingsChanged(..)</code>: removed, not used<br />
** <code>UpdateKind</code>: removed, not used<br />
<br />
* <code>IMylarContext</code>: renamed to <code>IInteranctionContext</code><br />
** <code>getHandleIdentifier()</code>: added to facilitate mapping<br />
<br />
* <code>IMylarElement</code>: renamed to <code>IInteractionElement</code><br />
* <code>IMylarObject</code>: renamed to <code>IInteractionObject</code><br />
* <code>IMylarRelation</code>: renamed to <code>IInteractionRelation</code><br />
* <code>IContextWriter</code>: renamed to <code>IInteractionContextWriter</code><br />
* <code>IContextReader</code>: renamed to <code>IInteractionContextReader</code><br />
* <code>IMylarContextListener</code>: renamed to <code>IInteractionContextListener</code><br />
* <code>MylarContextManager</code>: renamed to <code>InteractionContextManager</code><br />
<br />
== Monitor API ==<br />
<br />
*<code>MylarMonitorUiPlugin</code>: renamed to <code>MonitorUiPlugin</code><br />
** (-) setInactivityTimeout(...)<br />
<br />
* <code>org.eclipse.mylar.monitor</code>: split into <code>monitor.core</code> and <code>monitor.ui</code>, organize imports and update extension point IDs<br />
* <code>HandleObfuscator</code><br />
** moved to <code>InteractionEventObfuscator</code><br />
<br />
* <code>org.eclipse.mylar.monitor.usage.core</code> and <code>org.eclipse.mylar.monitor.usage.ui</code><br />
** moved to <code>..mylar.monitor.core</code>, <code>..mylar.monitor.usage</code> and <code>..mylar.monitor.usage.internal</code></div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=37648Mylyn/Porting Guide2007-05-29T15:21:03Z<p>Steffen.pingel.eclipse.org: /* General */</p>
<hr />
<div>[[Category:Mylar]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from Mylar 1.0 to 2.0 =<br />
<br />
== ''Pending Changes'' ==<br />
<br />
The following changes are planned but not yet implemented. Email mylar-dev if any of these pose a problem.<br />
<br />
* <code>AbstractRepositoryTaskEditor</code><br />
** creation of the <code>Composite</code> for "Attributes" section moved out of the <code>createAttributeLayout(..)</code> method into <code>createSections()</code>. So, method <code>createAttributeLayout(..)</code> is now takes that composite as parameter and returns <code>void</code>.<br />
<br />
* <code>AbstractRepositoryConnector</code>:<br />
** rename <code>createTaskFromExistingKey(..)</code> to <code>addExistingTask(..)</code><br />
** rename getRepositoryType() to getConnectorKind()<br />
<br />
* <code>AbstractRepositoryConnectorUi</code>:<br />
** remove hasRichEditor();<br />
<br />
* <code>AbstractRepositoryQuery</code><br />
** rename to <code>AbstractRepositoryTaskContainer</code> or merge with <code>AbstractTaskContainer</code><br />
<br />
* <code>AbstractRepositoryTask</code><br />
** rename getRepositoryKind() to getConnectorKind()<br />
** rename setLastSyncDateStamp() to setLastReadTimeStamp()<br />
** rename getLastSyncDateStamp() to getLastReadTimeStamp()<br />
<br />
* <code>IRepositoryConstants</code><br />
**rename PROPERTY_KIND to PROPERTY_CONNECTOR_KIND<br />
<br />
* <code>Task</code><br />
** rename getRepositoryKind() to getConnectorKind()<br />
** rename getDescription() to getSummary()<br />
** rename setKind() to setTaskKind()<br />
<br />
* <code>TaskListManager</code><br />
** task activity methods might move to a new TaskActivityManager class<br />
<br />
* <code>TaskRepository</code>:<br />
** rename <code>getKind()</code> to <code>getConnectorKind()</code><br />
** Make class final<br />
<br />
* Bridges:<br />
** Dtructure bridge: consider changing contentType -> structureKind<br />
<br />
== General ==<br />
<br />
* Library dependencies have moved to <code>org.eclipse.mylar</code><br />
<br />
* <code>MylarStatusHandler</code> and <code>IStatusHandler</code><br />
** moved from <code>org.eclipse.mylar.context.core</code> to <code>org.eclipse.mylar.core</code><br />
<br />
* <code>MylarStatus</code> (place holder, will improve as we solidify this)<br />
** <code>MylarStatusHandler.displayStatus(dialog title, IStatus status)</code> - call to display error and information dialogs<br />
** When returning <code>CoreException</code> pass in a <code>MylarStatus</code> with appropriate code (see <code>IMylarStatusConstants</code>).<br />
** If <code>IMylarStatusConstants.INTERNAL_ERROR</code> is sent to <code>MylarStatusHandler.displayStatus</code> an error dialog will appear and the error will be logged.<br />
** <code>IMylarStatusConstants.REPOSITORY_COLLISION</code> used for mid-air collision. Pass repository url and appropriate dialog will be displayed.<br />
<br />
* <code>WebClientUtil</code><br />
** moved from <code>..mylar.tasks.core</code> to <code>..mylar.core.net</code><br />
<br />
* Methods that do I/O operations now take an <code>IProgressMonitor</code> parameter ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 #143011])<br />
<br />
== Tasks API == <br />
<br />
Sorting is alphabetical. <br />
<br />
* <code>AbstractQueryHit</code><br />
** <code>setDescription(..)</code> renamed to <code>setSummary(..)</code><br />
<br />
* <code>AbstractRepositoryConnector</code><br />
** <code>getLastSyncTimestamp(TaskRepository repository, Set<AbstractRepositoryTask> changedTasks)</code>: added (may change as part of [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176934 bug#176934])<br />
** <code>getSupportedVersions()</code> has been removed ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=176815 #1768159])<br />
** <code>createTaskFromExistingId()</code> is no longer abstract and takes care of task creation<br />
** <code>updateTaskFromTaskData(TaskRepository, AbstractRepositoryTask, RepositoryTaskData, boolean retrieveSubTasks)</code> added. Must be implemented to handle updating information on the <code>AbstractRepositoryTask</code> with data from the <code>RepositoryTaskData</code><br />
** renamed <code>updateTask</code> to <code>updateTaskFromRepository</code><br />
** <code>createTaskFromExistingKey()</code> renamed to createTaskFromExistingId() and is final<br />
** <code>makeTask()</code> added. Connector specific repository task construction<br />
** <code>setTaskDataManager()</code> added. Manager set upon connector construction in TasksUiPlugin. If being used headless, will need to manually set for offline support.<br />
<br />
* <code>AbstractRepositoryConnectorUi</code><br />
** <code>openRemoteTask(String repositoryUrl, String id)</code>: removed, this method no longer needs to be implemented by the connector. Instead classes can rely on the new <code>openRepositoryTask(..)</code> method, and override it if necessary.<br />
** getRepositoryUrl and all ID/URL methods: now final, change via setters<br />
** + findHyperlinks(...) override to detect hyperlinks in editors<br />
** handlesDueDates() added. Override and return true if connector capable of handling due dates.<br />
** getTaskKindLabel(RepositoryTaskData) returns suitable label for task kind (default is 'Task') override to suit<br />
<br />
* <code>AbstractRepositoryQuery</code><br />
** <code>setMaxHits()</code> removed and constrctor no longer takes number of hits. Connectors can use QueryHitCollector.MAX_HITS (currently 5000) when setting max number of hits to return.<br />
<br />
*<code>AbstractRepositorySettingsPage</code> validation changes.<br />
**<code>setNeedsValidation(boolean needsValidation)</code> if true validate button will be visible<br />
**<code>getValidator(TaskRepository repository)</code> return an instance of <code>Validator</code>. <br />
<br />
* <code>AbstractRepositoryTask</code><br />
** constructor now requires taskId (now immutable)<br />
** getIdentifyingLabel() -> getTaskKey()<br />
** getLastRefreshTimeInMinutes(Date) removed<br />
** no more static methods (use RepositoryTaskHandleUtil)<br />
** Replace this idiom:<br />
String handleIdentifier = AbstractRepositoryTask.getHandle(repository.getUrl(), taskId);<br />
ITask task = TasksUiPlugin.getTaskListManager().getTaskList().getTask(handle);<br />
** with:<br />
ITask task = TasksUiPlugin.getTaskListManager().getTaskList().getTask(repository.getUrl(), taskId);<br />
** isDirty() and setDirty() removed<br />
** isDownloaded() removed<br />
** getTaskData(), setTaskData() removed<br />
** isSubmitting(), setSubmitting() added<br />
<br />
* <code>AbstractRepositoryTaskEditor</code><br />
**<code>attributeChanged()</code> Anything that needs to be saved must be in attribute form and passed to this method. Most if this is all done for you but if you override AbstractRepositoryTaskEditor.createCustomAttributeLayout() then you will want to ensure that attributeChanged is called upon editing. Utility method createTextField() handles this call. <br />
** <code>createLabel()</code> Utility method added. It will put an '*' at the front of the label if the attribute has been modified. Eventually this will be applied upon editing but currently only happens after re-freshing or re-opening the editor.<br />
** <code>SECTION_NAME</code> is an enum that holds default titles for the default sections. To override these default titles, set the appropriate (SECTION_NAME, new name) in <code>alternateSectionLabels</code> on <code>AbstractRepositoryTaskEditor</code>.<br />
** <code>updateEditor()</code> refreshes editor with new input in-place.<br />
<br />
*<code> AttributeContainer</code><br />
**<code>getAttributeFactory()</code> new method<br />
<br />
* <code>DateRangeContainer</code><br />
** getChildren() now returns set of underlying task objects (not DateRangeActivityDelegates which will be deprecated)<br />
** getDateRangeDelegates() returns the delegate formerly returned by getChildren()<br />
<br />
* <code>DelegatingTaskExternalizer</code><br />
** <code>readTaskInfo(..)</code> and <code>readQueryHitInfo(..)</code> are now called automatically and are private. Use your <code>createTask(..)</code> or <code>createQueryHit(..)</code> methods to customize reading additional attributes.<br />
<br />
* <code>DelegatingTaskExternalizer</code> <br />
** init() removed<br />
** readTaskData() removed<br />
<br />
* ITask<br />
** <code>setDescription(...)</code> renamed to <code>setSummary</code><br />
<br />
* <code>ITaskDataHandler</code><br />
** <code>getChangedSinceLastSync()</code> method moved to <code>AbstractRepositoryConnector</code><br />
** New comment now held in an attribute: <code>RepositoryTaskAttribute.COMMENT_NEW</code> will need to update handler and factory to produce connector specific attribute<br />
** <code>initializeTaskData(TaskRepository repository, RepositoryTaskData data, IProgressMonitor monitor)</code> called by NewTaskWizard to initialize new taskData objects (currently only in use by Trac but will adopt).<br />
** <code>getAttributeFactory(String repositoryUrl, String repositoryKind, String taskKind)</code> signature changed<br />
** <code>getDateForAttributeType(...)</code> moved to <code>AbstractAttributeFactory</code><br />
<br />
* <code>ITaskListElement</code>: now extends <code>java.lang.Comparable</code>, so Collections support of sorting can be used, since task list elements have a natural ordering. Default implementations are provided for tasks and containers. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=171590 bug 171590])<br />
<br />
* <code>ITaskListExternalizer</code><br />
** <code>readTask(..)</code> renamed to <code>createTask(..)</code>, no longer needs to set taskId, label, or repositoryUrl<br />
<br />
* <code>QueryHitCollector</code><br />
** MAX_HITS constant can be used as standard default number of hits handled per query. User notified when >= hits returned.<br />
<br />
* <code>RepositorySynchronizationManager</code><br />
** <code>updateOfflineState</code> is now <code>saveIncoming</code> and <code>saveOutgoing</code>. <br />
** <code>discardOutgoing</code> discards any pending outgoing changes<br />
<br />
* <code>RepositoryTaskAttribute</code><br />
** getID() -> getId()<br />
<br />
*<code>RepositoryTaskData</code><br />
**constructor now requires a task kind (string) (i.e. <code>Task.DEFAULT_TASK_KIND</code>)<br />
**<code>getTaskKind</code> return the task kind<br />
**<code>setNew(boolean)</code> signifies that this is unsubmitted task data. Used by editor factory to determine if existing or new editor to be opened.<br />
<br />
* <code>SynchronizeQueryJob</code><br />
** renamed setSynchTasks() to setSynchChangedTasks()<br />
<br />
* <code>Task</code><br />
** <code>dropSubTasks</code>: added, removes all subtasks<br />
** <code>getTooltipText()</code>: deleted, not used<br />
** Due dates are now supported <code>getDueDate(), setDueDate()</code><br />
** handleIdentifier: now private<br />
** get/setUrl are now get/setTaskUrl (to disambiguate with get/setRepositoryUrl())<br />
** <code>getElapsedTime()</code>: removed, not used previously, use <code>TaskListManager.getElapsedTime(ITask)</code> instead (note this method might move)<br />
** <code>setElapsedTime()</code>: removed, not used<br />
<br />
* <code>TaskEditor</code><br />
** <code>protected void pageChange(intNewPageIndex)</code> method removed (only called super)<br />
<br />
* <code>TaskList</code><br />
** <code>getChangeListeners()</code>: returns a <code>Set</code> instead of <code>List</code><br />
** <code>getRootCategory</code> renamed to <code>getUncategorizedCategory</code><br />
<br />
<br />
* <code>TaskListImages</code><br />
** renamed to <code>TasksUiImages</code> (still an internal class, should move to API)<br />
<br />
* <code>TaskListManager</code><br />
** <code>setDueDate()</code> used to set due date on a task and cause notification of local info changed.<br />
** <code>isDue(ITask)</code> true if task's due date isn't null and date has past<br />
<br />
* <code>TaskListWriter</code><br />
** <code>setTaskDataManager()</code> removed<br />
<br />
* <code>TaskRepository</code><br />
**TaskRepository.isAnonymous()<br />
**TaskRepository.setAnonymous(boolean)<br />
** (-) TaskRepository.getDefaultProxy() (Renamed and moved to WebClientUtil.getPlatformProxy())<br />
<br />
* <code>TasksUiUtil</code><br />
** <code>openUrl(String url)</code>: moved to <code>openUrl(String url, boolean useRichEditor)</code><br />
** <code>getImageDescriptorForPriority(..)</code> moved to TasksUiImages<br />
** <code>getImageForPriority(..)</code>moved to TasksUiImages<br />
<br />
== Context API ==<br />
* <code>AbstractContextUiBridge<code><br />
** removed: <code>restoreEditor(IMylarElement)</code> use <code>open(IMylarElement)</code> instead<br />
* <code>AbstractContextStore</code><br />
** <code>notifyContextStoreMoved()</code>: change to <code>contextStoreMoved()</code><br />
* <code>AbstractContextStructureBridge</code><br />
** <code>getDegreesOfSeparation()</code>: moved to <code>AbstractRelationProvider</code><br />
** <code>getRelationshipProviders()</code>: moved to extensions point, e.g.:<br />
<br />
<extension point="org.eclipse.mylar.context.core.bridges"><br />
<relationProvider<br />
class="org.eclipse.mylar.internal.java.search.JavaImplementorsProvider"<br />
contentType="java"/><br />
</extension><br />
<br />
* <code>IMylarContextListener</code>: renamed to <code>IInteractionContextListener</code><br />
** <code>contextCleared(..)</code>: added<br />
** <code>presentationSettingsChanging(..)</code>: removed, not used<br />
** <code>presentationSettingsChanged(..)</code>: removed, not used<br />
** <code>UpdateKind</code>: removed, not used<br />
<br />
* <code>IMylarContext</code>: renamed to <code>IInteranctionContext</code><br />
** <code>getHandleIdentifier()</code>: added to facilitate mapping<br />
<br />
* <code>IMylarElement</code>: renamed to <code>IInteractionElement</code><br />
* <code>IMylarObject</code>: renamed to <code>IInteractionObject</code><br />
* <code>IMylarRelation</code>: renamed to <code>IInteractionRelation</code><br />
* <code>IContextWriter</code>: renamed to <code>IInteractionContextWriter</code><br />
* <code>IContextReader</code>: renamed to <code>IInteractionContextReader</code><br />
* <code>IMylarContextListener</code>: renamed to <code>IInteractionContextListener</code><br />
* <code>MylarContextManager</code>: renamed to <code>InteractionContextManager</code><br />
<br />
== Monitor API ==<br />
<br />
*<code>MylarMonitorUiPlugin</code>: renamed to <code>MonitorUiPlugin</code><br />
** (-) setInactivityTimeout(...)<br />
<br />
* <code>org.eclipse.mylar.monitor</code>: split into <code>monitor.core</code> and <code>monitor.ui</code>, organize imports and update extension point IDs<br />
* <code>HandleObfuscator</code><br />
** moved to <code>InteractionEventObfuscator</code><br />
<br />
* <code>org.eclipse.mylar.monitor.usage.core</code> and <code>org.eclipse.mylar.monitor.usage.ui</code><br />
** moved to <code>..mylar.monitor.core</code>, <code>..mylar.monitor.usage</code> and <code>..mylar.monitor.usage.internal</code></div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=37647Mylyn/Porting Guide2007-05-29T15:20:48Z<p>Steffen.pingel.eclipse.org: /* General */</p>
<hr />
<div>[[Category:Mylar]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from Mylar 1.0 to 2.0 =<br />
<br />
== ''Pending Changes'' ==<br />
<br />
The following changes are planned but not yet implemented. Email mylar-dev if any of these pose a problem.<br />
<br />
* <code>AbstractRepositoryTaskEditor</code><br />
** creation of the <code>Composite</code> for "Attributes" section moved out of the <code>createAttributeLayout(..)</code> method into <code>createSections()</code>. So, method <code>createAttributeLayout(..)</code> is now takes that composite as parameter and returns <code>void</code>.<br />
<br />
* <code>AbstractRepositoryConnector</code>:<br />
** rename <code>createTaskFromExistingKey(..)</code> to <code>addExistingTask(..)</code><br />
** rename getRepositoryType() to getConnectorKind()<br />
<br />
* <code>AbstractRepositoryConnectorUi</code>:<br />
** remove hasRichEditor();<br />
<br />
* <code>AbstractRepositoryQuery</code><br />
** rename to <code>AbstractRepositoryTaskContainer</code> or merge with <code>AbstractTaskContainer</code><br />
<br />
* <code>AbstractRepositoryTask</code><br />
** rename getRepositoryKind() to getConnectorKind()<br />
** rename setLastSyncDateStamp() to setLastReadTimeStamp()<br />
** rename getLastSyncDateStamp() to getLastReadTimeStamp()<br />
<br />
* <code>IRepositoryConstants</code><br />
**rename PROPERTY_KIND to PROPERTY_CONNECTOR_KIND<br />
<br />
* <code>Task</code><br />
** rename getRepositoryKind() to getConnectorKind()<br />
** rename getDescription() to getSummary()<br />
** rename setKind() to setTaskKind()<br />
<br />
* <code>TaskListManager</code><br />
** task activity methods might move to a new TaskActivityManager class<br />
<br />
* <code>TaskRepository</code>:<br />
** rename <code>getKind()</code> to <code>getConnectorKind()</code><br />
** Make class final<br />
<br />
* Bridges:<br />
** Dtructure bridge: consider changing contentType -> structureKind<br />
<br />
== General ==<br />
<br />
* Library dependencies have moved to <code>org.eclipse.mylar</code><br />
<br />
* <code>MylarStatusHandler</code> and <code>IStatusHandler</code><br />
** moved from <code>org.eclipse.mylar.context.core</code> to <code>org.eclipse.mylar.core</code><br />
<br />
* <code>MylarStatus</code> (place holder, will improve as we solidify this)<br />
** <code>MylarStatusHandler.displayStatus(dialog title, IStatus status)</code> - call to display error and information dialogs<br />
** When returning <code>CoreException</code> pass in a <code>MylarStatus</code> with appropriate code (see <code>IMylarStatusConstants</code>).<br />
** If <code>IMylarStatusConstants.INTERNAL_ERROR</code> is sent to <code>MylarStatusHandler.displayStatus</code> an error dialog will appear and the error will be logged.<br />
** <code>IMylarStatusConstants.REPOSITORY_COLLISION</code> used for mid-air collision. Pass repository url and appropriate dialog will be displayed.<br />
<br />
* <code>WebClientUtil</code><br />
** moved from <code>..mylar.tasks.core</code> to <code>..mylar.core.net</code><br />
<br />
* Methods that do I/O operations now take an <code>IProgressMonitor</code> parameter (#[https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 143011])<br />
<br />
== Tasks API == <br />
<br />
Sorting is alphabetical. <br />
<br />
* <code>AbstractQueryHit</code><br />
** <code>setDescription(..)</code> renamed to <code>setSummary(..)</code><br />
<br />
* <code>AbstractRepositoryConnector</code><br />
** <code>getLastSyncTimestamp(TaskRepository repository, Set<AbstractRepositoryTask> changedTasks)</code>: added (may change as part of [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176934 bug#176934])<br />
** <code>getSupportedVersions()</code> has been removed ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=176815 #1768159])<br />
** <code>createTaskFromExistingId()</code> is no longer abstract and takes care of task creation<br />
** <code>updateTaskFromTaskData(TaskRepository, AbstractRepositoryTask, RepositoryTaskData, boolean retrieveSubTasks)</code> added. Must be implemented to handle updating information on the <code>AbstractRepositoryTask</code> with data from the <code>RepositoryTaskData</code><br />
** renamed <code>updateTask</code> to <code>updateTaskFromRepository</code><br />
** <code>createTaskFromExistingKey()</code> renamed to createTaskFromExistingId() and is final<br />
** <code>makeTask()</code> added. Connector specific repository task construction<br />
** <code>setTaskDataManager()</code> added. Manager set upon connector construction in TasksUiPlugin. If being used headless, will need to manually set for offline support.<br />
<br />
* <code>AbstractRepositoryConnectorUi</code><br />
** <code>openRemoteTask(String repositoryUrl, String id)</code>: removed, this method no longer needs to be implemented by the connector. Instead classes can rely on the new <code>openRepositoryTask(..)</code> method, and override it if necessary.<br />
** getRepositoryUrl and all ID/URL methods: now final, change via setters<br />
** + findHyperlinks(...) override to detect hyperlinks in editors<br />
** handlesDueDates() added. Override and return true if connector capable of handling due dates.<br />
** getTaskKindLabel(RepositoryTaskData) returns suitable label for task kind (default is 'Task') override to suit<br />
<br />
* <code>AbstractRepositoryQuery</code><br />
** <code>setMaxHits()</code> removed and constrctor no longer takes number of hits. Connectors can use QueryHitCollector.MAX_HITS (currently 5000) when setting max number of hits to return.<br />
<br />
*<code>AbstractRepositorySettingsPage</code> validation changes.<br />
**<code>setNeedsValidation(boolean needsValidation)</code> if true validate button will be visible<br />
**<code>getValidator(TaskRepository repository)</code> return an instance of <code>Validator</code>. <br />
<br />
* <code>AbstractRepositoryTask</code><br />
** constructor now requires taskId (now immutable)<br />
** getIdentifyingLabel() -> getTaskKey()<br />
** getLastRefreshTimeInMinutes(Date) removed<br />
** no more static methods (use RepositoryTaskHandleUtil)<br />
** Replace this idiom:<br />
String handleIdentifier = AbstractRepositoryTask.getHandle(repository.getUrl(), taskId);<br />
ITask task = TasksUiPlugin.getTaskListManager().getTaskList().getTask(handle);<br />
** with:<br />
ITask task = TasksUiPlugin.getTaskListManager().getTaskList().getTask(repository.getUrl(), taskId);<br />
** isDirty() and setDirty() removed<br />
** isDownloaded() removed<br />
** getTaskData(), setTaskData() removed<br />
** isSubmitting(), setSubmitting() added<br />
<br />
* <code>AbstractRepositoryTaskEditor</code><br />
**<code>attributeChanged()</code> Anything that needs to be saved must be in attribute form and passed to this method. Most if this is all done for you but if you override AbstractRepositoryTaskEditor.createCustomAttributeLayout() then you will want to ensure that attributeChanged is called upon editing. Utility method createTextField() handles this call. <br />
** <code>createLabel()</code> Utility method added. It will put an '*' at the front of the label if the attribute has been modified. Eventually this will be applied upon editing but currently only happens after re-freshing or re-opening the editor.<br />
** <code>SECTION_NAME</code> is an enum that holds default titles for the default sections. To override these default titles, set the appropriate (SECTION_NAME, new name) in <code>alternateSectionLabels</code> on <code>AbstractRepositoryTaskEditor</code>.<br />
** <code>updateEditor()</code> refreshes editor with new input in-place.<br />
<br />
*<code> AttributeContainer</code><br />
**<code>getAttributeFactory()</code> new method<br />
<br />
* <code>DateRangeContainer</code><br />
** getChildren() now returns set of underlying task objects (not DateRangeActivityDelegates which will be deprecated)<br />
** getDateRangeDelegates() returns the delegate formerly returned by getChildren()<br />
<br />
* <code>DelegatingTaskExternalizer</code><br />
** <code>readTaskInfo(..)</code> and <code>readQueryHitInfo(..)</code> are now called automatically and are private. Use your <code>createTask(..)</code> or <code>createQueryHit(..)</code> methods to customize reading additional attributes.<br />
<br />
* <code>DelegatingTaskExternalizer</code> <br />
** init() removed<br />
** readTaskData() removed<br />
<br />
* ITask<br />
** <code>setDescription(...)</code> renamed to <code>setSummary</code><br />
<br />
* <code>ITaskDataHandler</code><br />
** <code>getChangedSinceLastSync()</code> method moved to <code>AbstractRepositoryConnector</code><br />
** New comment now held in an attribute: <code>RepositoryTaskAttribute.COMMENT_NEW</code> will need to update handler and factory to produce connector specific attribute<br />
** <code>initializeTaskData(TaskRepository repository, RepositoryTaskData data, IProgressMonitor monitor)</code> called by NewTaskWizard to initialize new taskData objects (currently only in use by Trac but will adopt).<br />
** <code>getAttributeFactory(String repositoryUrl, String repositoryKind, String taskKind)</code> signature changed<br />
** <code>getDateForAttributeType(...)</code> moved to <code>AbstractAttributeFactory</code><br />
<br />
* <code>ITaskListElement</code>: now extends <code>java.lang.Comparable</code>, so Collections support of sorting can be used, since task list elements have a natural ordering. Default implementations are provided for tasks and containers. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=171590 bug 171590])<br />
<br />
* <code>ITaskListExternalizer</code><br />
** <code>readTask(..)</code> renamed to <code>createTask(..)</code>, no longer needs to set taskId, label, or repositoryUrl<br />
<br />
* <code>QueryHitCollector</code><br />
** MAX_HITS constant can be used as standard default number of hits handled per query. User notified when >= hits returned.<br />
<br />
* <code>RepositorySynchronizationManager</code><br />
** <code>updateOfflineState</code> is now <code>saveIncoming</code> and <code>saveOutgoing</code>. <br />
** <code>discardOutgoing</code> discards any pending outgoing changes<br />
<br />
* <code>RepositoryTaskAttribute</code><br />
** getID() -> getId()<br />
<br />
*<code>RepositoryTaskData</code><br />
**constructor now requires a task kind (string) (i.e. <code>Task.DEFAULT_TASK_KIND</code>)<br />
**<code>getTaskKind</code> return the task kind<br />
**<code>setNew(boolean)</code> signifies that this is unsubmitted task data. Used by editor factory to determine if existing or new editor to be opened.<br />
<br />
* <code>SynchronizeQueryJob</code><br />
** renamed setSynchTasks() to setSynchChangedTasks()<br />
<br />
* <code>Task</code><br />
** <code>dropSubTasks</code>: added, removes all subtasks<br />
** <code>getTooltipText()</code>: deleted, not used<br />
** Due dates are now supported <code>getDueDate(), setDueDate()</code><br />
** handleIdentifier: now private<br />
** get/setUrl are now get/setTaskUrl (to disambiguate with get/setRepositoryUrl())<br />
** <code>getElapsedTime()</code>: removed, not used previously, use <code>TaskListManager.getElapsedTime(ITask)</code> instead (note this method might move)<br />
** <code>setElapsedTime()</code>: removed, not used<br />
<br />
* <code>TaskEditor</code><br />
** <code>protected void pageChange(intNewPageIndex)</code> method removed (only called super)<br />
<br />
* <code>TaskList</code><br />
** <code>getChangeListeners()</code>: returns a <code>Set</code> instead of <code>List</code><br />
** <code>getRootCategory</code> renamed to <code>getUncategorizedCategory</code><br />
<br />
<br />
* <code>TaskListImages</code><br />
** renamed to <code>TasksUiImages</code> (still an internal class, should move to API)<br />
<br />
* <code>TaskListManager</code><br />
** <code>setDueDate()</code> used to set due date on a task and cause notification of local info changed.<br />
** <code>isDue(ITask)</code> true if task's due date isn't null and date has past<br />
<br />
* <code>TaskListWriter</code><br />
** <code>setTaskDataManager()</code> removed<br />
<br />
* <code>TaskRepository</code><br />
**TaskRepository.isAnonymous()<br />
**TaskRepository.setAnonymous(boolean)<br />
** (-) TaskRepository.getDefaultProxy() (Renamed and moved to WebClientUtil.getPlatformProxy())<br />
<br />
* <code>TasksUiUtil</code><br />
** <code>openUrl(String url)</code>: moved to <code>openUrl(String url, boolean useRichEditor)</code><br />
** <code>getImageDescriptorForPriority(..)</code> moved to TasksUiImages<br />
** <code>getImageForPriority(..)</code>moved to TasksUiImages<br />
<br />
== Context API ==<br />
* <code>AbstractContextUiBridge<code><br />
** removed: <code>restoreEditor(IMylarElement)</code> use <code>open(IMylarElement)</code> instead<br />
* <code>AbstractContextStore</code><br />
** <code>notifyContextStoreMoved()</code>: change to <code>contextStoreMoved()</code><br />
* <code>AbstractContextStructureBridge</code><br />
** <code>getDegreesOfSeparation()</code>: moved to <code>AbstractRelationProvider</code><br />
** <code>getRelationshipProviders()</code>: moved to extensions point, e.g.:<br />
<br />
<extension point="org.eclipse.mylar.context.core.bridges"><br />
<relationProvider<br />
class="org.eclipse.mylar.internal.java.search.JavaImplementorsProvider"<br />
contentType="java"/><br />
</extension><br />
<br />
* <code>IMylarContextListener</code>: renamed to <code>IInteractionContextListener</code><br />
** <code>contextCleared(..)</code>: added<br />
** <code>presentationSettingsChanging(..)</code>: removed, not used<br />
** <code>presentationSettingsChanged(..)</code>: removed, not used<br />
** <code>UpdateKind</code>: removed, not used<br />
<br />
* <code>IMylarContext</code>: renamed to <code>IInteranctionContext</code><br />
** <code>getHandleIdentifier()</code>: added to facilitate mapping<br />
<br />
* <code>IMylarElement</code>: renamed to <code>IInteractionElement</code><br />
* <code>IMylarObject</code>: renamed to <code>IInteractionObject</code><br />
* <code>IMylarRelation</code>: renamed to <code>IInteractionRelation</code><br />
* <code>IContextWriter</code>: renamed to <code>IInteractionContextWriter</code><br />
* <code>IContextReader</code>: renamed to <code>IInteractionContextReader</code><br />
* <code>IMylarContextListener</code>: renamed to <code>IInteractionContextListener</code><br />
* <code>MylarContextManager</code>: renamed to <code>InteractionContextManager</code><br />
<br />
== Monitor API ==<br />
<br />
*<code>MylarMonitorUiPlugin</code>: renamed to <code>MonitorUiPlugin</code><br />
** (-) setInactivityTimeout(...)<br />
<br />
* <code>org.eclipse.mylar.monitor</code>: split into <code>monitor.core</code> and <code>monitor.ui</code>, organize imports and update extension point IDs<br />
* <code>HandleObfuscator</code><br />
** moved to <code>InteractionEventObfuscator</code><br />
<br />
* <code>org.eclipse.mylar.monitor.usage.core</code> and <code>org.eclipse.mylar.monitor.usage.ui</code><br />
** moved to <code>..mylar.monitor.core</code>, <code>..mylar.monitor.usage</code> and <code>..mylar.monitor.usage.internal</code></div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Porting_Guide&diff=37646Mylyn/Porting Guide2007-05-29T15:20:31Z<p>Steffen.pingel.eclipse.org: /* General */</p>
<hr />
<div>[[Category:Mylar]] <br />
This document will have Mylar 2.0 specific API changes added to it as we make them. If interested in keeping up with these changes we '''suggest setting a watch''' for this page. Note that changes involving classes moving packages are not listed, use ''Organize Imports'' to resolve.<br />
<br />
= Porting from Mylar 1.0 to 2.0 =<br />
<br />
== ''Pending Changes'' ==<br />
<br />
The following changes are planned but not yet implemented. Email mylar-dev if any of these pose a problem.<br />
<br />
* <code>AbstractRepositoryTaskEditor</code><br />
** creation of the <code>Composite</code> for "Attributes" section moved out of the <code>createAttributeLayout(..)</code> method into <code>createSections()</code>. So, method <code>createAttributeLayout(..)</code> is now takes that composite as parameter and returns <code>void</code>.<br />
<br />
* <code>AbstractRepositoryConnector</code>:<br />
** rename <code>createTaskFromExistingKey(..)</code> to <code>addExistingTask(..)</code><br />
** rename getRepositoryType() to getConnectorKind()<br />
<br />
* <code>AbstractRepositoryConnectorUi</code>:<br />
** remove hasRichEditor();<br />
<br />
* <code>AbstractRepositoryQuery</code><br />
** rename to <code>AbstractRepositoryTaskContainer</code> or merge with <code>AbstractTaskContainer</code><br />
<br />
* <code>AbstractRepositoryTask</code><br />
** rename getRepositoryKind() to getConnectorKind()<br />
** rename setLastSyncDateStamp() to setLastReadTimeStamp()<br />
** rename getLastSyncDateStamp() to getLastReadTimeStamp()<br />
<br />
* <code>IRepositoryConstants</code><br />
**rename PROPERTY_KIND to PROPERTY_CONNECTOR_KIND<br />
<br />
* <code>Task</code><br />
** rename getRepositoryKind() to getConnectorKind()<br />
** rename getDescription() to getSummary()<br />
** rename setKind() to setTaskKind()<br />
<br />
* <code>TaskListManager</code><br />
** task activity methods might move to a new TaskActivityManager class<br />
<br />
* <code>TaskRepository</code>:<br />
** rename <code>getKind()</code> to <code>getConnectorKind()</code><br />
** Make class final<br />
<br />
* Bridges:<br />
** Dtructure bridge: consider changing contentType -> structureKind<br />
<br />
== General ==<br />
<br />
* Library dependencies have moved to <code>org.eclipse.mylar</code><br />
<br />
* <code>MylarStatusHandler</code> and <code>IStatusHandler</code><br />
** moved from <code>org.eclipse.mylar.context.core</code> to <code>org.eclipse.mylar.core</code><br />
<br />
* <code>MylarStatus</code> (place holder, will improve as we solidify this)<br />
** <code>MylarStatusHandler.displayStatus(dialog title, IStatus status)</code> - call to display error and information dialogs<br />
** When returning <code>CoreException</code> pass in a <code>MylarStatus</code> with appropriate code (see <code>IMylarStatusConstants</code>).<br />
** If <code>IMylarStatusConstants.INTERNAL_ERROR</code> is sent to <code>MylarStatusHandler.displayStatus</code> an error dialog will appear and the error will be logged.<br />
** <code>IMylarStatusConstants.REPOSITORY_COLLISION</code> used for mid-air collision. Pass repository url and appropriate dialog will be displayed.<br />
<br />
* <code>WebClientUtil</code><br />
** moved from <code>..mylar.tasks.core</code> to <code>..mylar.core.net</code><br />
<br />
* Methods that do I/O operations now take an <code>IProgressMonitor</code> parameter [https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 143011]<br />
<br />
== Tasks API == <br />
<br />
Sorting is alphabetical. <br />
<br />
* <code>AbstractQueryHit</code><br />
** <code>setDescription(..)</code> renamed to <code>setSummary(..)</code><br />
<br />
* <code>AbstractRepositoryConnector</code><br />
** <code>getLastSyncTimestamp(TaskRepository repository, Set<AbstractRepositoryTask> changedTasks)</code>: added (may change as part of [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176934 bug#176934])<br />
** <code>getSupportedVersions()</code> has been removed ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=176815 #1768159])<br />
** <code>createTaskFromExistingId()</code> is no longer abstract and takes care of task creation<br />
** <code>updateTaskFromTaskData(TaskRepository, AbstractRepositoryTask, RepositoryTaskData, boolean retrieveSubTasks)</code> added. Must be implemented to handle updating information on the <code>AbstractRepositoryTask</code> with data from the <code>RepositoryTaskData</code><br />
** renamed <code>updateTask</code> to <code>updateTaskFromRepository</code><br />
** <code>createTaskFromExistingKey()</code> renamed to createTaskFromExistingId() and is final<br />
** <code>makeTask()</code> added. Connector specific repository task construction<br />
** <code>setTaskDataManager()</code> added. Manager set upon connector construction in TasksUiPlugin. If being used headless, will need to manually set for offline support.<br />
<br />
* <code>AbstractRepositoryConnectorUi</code><br />
** <code>openRemoteTask(String repositoryUrl, String id)</code>: removed, this method no longer needs to be implemented by the connector. Instead classes can rely on the new <code>openRepositoryTask(..)</code> method, and override it if necessary.<br />
** getRepositoryUrl and all ID/URL methods: now final, change via setters<br />
** + findHyperlinks(...) override to detect hyperlinks in editors<br />
** handlesDueDates() added. Override and return true if connector capable of handling due dates.<br />
** getTaskKindLabel(RepositoryTaskData) returns suitable label for task kind (default is 'Task') override to suit<br />
<br />
* <code>AbstractRepositoryQuery</code><br />
** <code>setMaxHits()</code> removed and constrctor no longer takes number of hits. Connectors can use QueryHitCollector.MAX_HITS (currently 5000) when setting max number of hits to return.<br />
<br />
*<code>AbstractRepositorySettingsPage</code> validation changes.<br />
**<code>setNeedsValidation(boolean needsValidation)</code> if true validate button will be visible<br />
**<code>getValidator(TaskRepository repository)</code> return an instance of <code>Validator</code>. <br />
<br />
* <code>AbstractRepositoryTask</code><br />
** constructor now requires taskId (now immutable)<br />
** getIdentifyingLabel() -> getTaskKey()<br />
** getLastRefreshTimeInMinutes(Date) removed<br />
** no more static methods (use RepositoryTaskHandleUtil)<br />
** Replace this idiom:<br />
String handleIdentifier = AbstractRepositoryTask.getHandle(repository.getUrl(), taskId);<br />
ITask task = TasksUiPlugin.getTaskListManager().getTaskList().getTask(handle);<br />
** with:<br />
ITask task = TasksUiPlugin.getTaskListManager().getTaskList().getTask(repository.getUrl(), taskId);<br />
** isDirty() and setDirty() removed<br />
** isDownloaded() removed<br />
** getTaskData(), setTaskData() removed<br />
** isSubmitting(), setSubmitting() added<br />
<br />
* <code>AbstractRepositoryTaskEditor</code><br />
**<code>attributeChanged()</code> Anything that needs to be saved must be in attribute form and passed to this method. Most if this is all done for you but if you override AbstractRepositoryTaskEditor.createCustomAttributeLayout() then you will want to ensure that attributeChanged is called upon editing. Utility method createTextField() handles this call. <br />
** <code>createLabel()</code> Utility method added. It will put an '*' at the front of the label if the attribute has been modified. Eventually this will be applied upon editing but currently only happens after re-freshing or re-opening the editor.<br />
** <code>SECTION_NAME</code> is an enum that holds default titles for the default sections. To override these default titles, set the appropriate (SECTION_NAME, new name) in <code>alternateSectionLabels</code> on <code>AbstractRepositoryTaskEditor</code>.<br />
** <code>updateEditor()</code> refreshes editor with new input in-place.<br />
<br />
*<code> AttributeContainer</code><br />
**<code>getAttributeFactory()</code> new method<br />
<br />
* <code>DateRangeContainer</code><br />
** getChildren() now returns set of underlying task objects (not DateRangeActivityDelegates which will be deprecated)<br />
** getDateRangeDelegates() returns the delegate formerly returned by getChildren()<br />
<br />
* <code>DelegatingTaskExternalizer</code><br />
** <code>readTaskInfo(..)</code> and <code>readQueryHitInfo(..)</code> are now called automatically and are private. Use your <code>createTask(..)</code> or <code>createQueryHit(..)</code> methods to customize reading additional attributes.<br />
<br />
* <code>DelegatingTaskExternalizer</code> <br />
** init() removed<br />
** readTaskData() removed<br />
<br />
* ITask<br />
** <code>setDescription(...)</code> renamed to <code>setSummary</code><br />
<br />
* <code>ITaskDataHandler</code><br />
** <code>getChangedSinceLastSync()</code> method moved to <code>AbstractRepositoryConnector</code><br />
** New comment now held in an attribute: <code>RepositoryTaskAttribute.COMMENT_NEW</code> will need to update handler and factory to produce connector specific attribute<br />
** <code>initializeTaskData(TaskRepository repository, RepositoryTaskData data, IProgressMonitor monitor)</code> called by NewTaskWizard to initialize new taskData objects (currently only in use by Trac but will adopt).<br />
** <code>getAttributeFactory(String repositoryUrl, String repositoryKind, String taskKind)</code> signature changed<br />
** <code>getDateForAttributeType(...)</code> moved to <code>AbstractAttributeFactory</code><br />
<br />
* <code>ITaskListElement</code>: now extends <code>java.lang.Comparable</code>, so Collections support of sorting can be used, since task list elements have a natural ordering. Default implementations are provided for tasks and containers. ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=171590 bug 171590])<br />
<br />
* <code>ITaskListExternalizer</code><br />
** <code>readTask(..)</code> renamed to <code>createTask(..)</code>, no longer needs to set taskId, label, or repositoryUrl<br />
<br />
* <code>QueryHitCollector</code><br />
** MAX_HITS constant can be used as standard default number of hits handled per query. User notified when >= hits returned.<br />
<br />
* <code>RepositorySynchronizationManager</code><br />
** <code>updateOfflineState</code> is now <code>saveIncoming</code> and <code>saveOutgoing</code>. <br />
** <code>discardOutgoing</code> discards any pending outgoing changes<br />
<br />
* <code>RepositoryTaskAttribute</code><br />
** getID() -> getId()<br />
<br />
*<code>RepositoryTaskData</code><br />
**constructor now requires a task kind (string) (i.e. <code>Task.DEFAULT_TASK_KIND</code>)<br />
**<code>getTaskKind</code> return the task kind<br />
**<code>setNew(boolean)</code> signifies that this is unsubmitted task data. Used by editor factory to determine if existing or new editor to be opened.<br />
<br />
* <code>SynchronizeQueryJob</code><br />
** renamed setSynchTasks() to setSynchChangedTasks()<br />
<br />
* <code>Task</code><br />
** <code>dropSubTasks</code>: added, removes all subtasks<br />
** <code>getTooltipText()</code>: deleted, not used<br />
** Due dates are now supported <code>getDueDate(), setDueDate()</code><br />
** handleIdentifier: now private<br />
** get/setUrl are now get/setTaskUrl (to disambiguate with get/setRepositoryUrl())<br />
** <code>getElapsedTime()</code>: removed, not used previously, use <code>TaskListManager.getElapsedTime(ITask)</code> instead (note this method might move)<br />
** <code>setElapsedTime()</code>: removed, not used<br />
<br />
* <code>TaskEditor</code><br />
** <code>protected void pageChange(intNewPageIndex)</code> method removed (only called super)<br />
<br />
* <code>TaskList</code><br />
** <code>getChangeListeners()</code>: returns a <code>Set</code> instead of <code>List</code><br />
** <code>getRootCategory</code> renamed to <code>getUncategorizedCategory</code><br />
<br />
<br />
* <code>TaskListImages</code><br />
** renamed to <code>TasksUiImages</code> (still an internal class, should move to API)<br />
<br />
* <code>TaskListManager</code><br />
** <code>setDueDate()</code> used to set due date on a task and cause notification of local info changed.<br />
** <code>isDue(ITask)</code> true if task's due date isn't null and date has past<br />
<br />
* <code>TaskListWriter</code><br />
** <code>setTaskDataManager()</code> removed<br />
<br />
* <code>TaskRepository</code><br />
**TaskRepository.isAnonymous()<br />
**TaskRepository.setAnonymous(boolean)<br />
** (-) TaskRepository.getDefaultProxy() (Renamed and moved to WebClientUtil.getPlatformProxy())<br />
<br />
* <code>TasksUiUtil</code><br />
** <code>openUrl(String url)</code>: moved to <code>openUrl(String url, boolean useRichEditor)</code><br />
** <code>getImageDescriptorForPriority(..)</code> moved to TasksUiImages<br />
** <code>getImageForPriority(..)</code>moved to TasksUiImages<br />
<br />
== Context API ==<br />
* <code>AbstractContextUiBridge<code><br />
** removed: <code>restoreEditor(IMylarElement)</code> use <code>open(IMylarElement)</code> instead<br />
* <code>AbstractContextStore</code><br />
** <code>notifyContextStoreMoved()</code>: change to <code>contextStoreMoved()</code><br />
* <code>AbstractContextStructureBridge</code><br />
** <code>getDegreesOfSeparation()</code>: moved to <code>AbstractRelationProvider</code><br />
** <code>getRelationshipProviders()</code>: moved to extensions point, e.g.:<br />
<br />
<extension point="org.eclipse.mylar.context.core.bridges"><br />
<relationProvider<br />
class="org.eclipse.mylar.internal.java.search.JavaImplementorsProvider"<br />
contentType="java"/><br />
</extension><br />
<br />
* <code>IMylarContextListener</code>: renamed to <code>IInteractionContextListener</code><br />
** <code>contextCleared(..)</code>: added<br />
** <code>presentationSettingsChanging(..)</code>: removed, not used<br />
** <code>presentationSettingsChanged(..)</code>: removed, not used<br />
** <code>UpdateKind</code>: removed, not used<br />
<br />
* <code>IMylarContext</code>: renamed to <code>IInteranctionContext</code><br />
** <code>getHandleIdentifier()</code>: added to facilitate mapping<br />
<br />
* <code>IMylarElement</code>: renamed to <code>IInteractionElement</code><br />
* <code>IMylarObject</code>: renamed to <code>IInteractionObject</code><br />
* <code>IMylarRelation</code>: renamed to <code>IInteractionRelation</code><br />
* <code>IContextWriter</code>: renamed to <code>IInteractionContextWriter</code><br />
* <code>IContextReader</code>: renamed to <code>IInteractionContextReader</code><br />
* <code>IMylarContextListener</code>: renamed to <code>IInteractionContextListener</code><br />
* <code>MylarContextManager</code>: renamed to <code>InteractionContextManager</code><br />
<br />
== Monitor API ==<br />
<br />
*<code>MylarMonitorUiPlugin</code>: renamed to <code>MonitorUiPlugin</code><br />
** (-) setInactivityTimeout(...)<br />
<br />
* <code>org.eclipse.mylar.monitor</code>: split into <code>monitor.core</code> and <code>monitor.ui</code>, organize imports and update extension point IDs<br />
* <code>HandleObfuscator</code><br />
** moved to <code>InteractionEventObfuscator</code><br />
<br />
* <code>org.eclipse.mylar.monitor.usage.core</code> and <code>org.eclipse.mylar.monitor.usage.ui</code><br />
** moved to <code>..mylar.monitor.core</code>, <code>..mylar.monitor.usage</code> and <code>..mylar.monitor.usage.internal</code></div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Meetings&diff=37641Mylyn/Meetings2007-05-29T14:58:23Z<p>Steffen.pingel.eclipse.org: /* Tuesday, May 29, 10-11am PT */</p>
<hr />
<div>[[Category:Mylar]]<br />
Tel: '''1-866-362-7064''' or 1-613-287-8000, Passcode: '''892048#'''<br />
<br />
=== Next Meeting ===<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
==== Tuesday, May 29, 10-11am PT ====<br />
<br />
* Google Summer of Code kick-off (Balazs, Jevgeni, Xiaoyang)<br />
* 2.0 end game planning<br />
** Committers to have thier 2.0 (P1,P2, P3) plans refined<br />
* Task Repository in offline mode (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage refactoring status update (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
----<br />
<br />
=== Past Meetings ===<br />
<br />
==== Tuesday, May 22, 10-11am PT ====<br />
<br />
* 2.0 end game planning<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* Top voted bug: [https://bugs.eclipse.org/bugs/show_bug.cgi?id=169123 169123]: Updated bug does not preserve values of custom fields in Jira (Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Minutes:<br />
* Task workflow and special query support likely getting bumped<br />
* Rob: related bug#185805 (timestamp bug) and bug#186939 (blocked jobs)<br />
* Steffen: httpclient message.shutdown() can be used to force shutdown of network IO<br />
<br />
Actions:<br />
* Rob and Steffen:<br />
**to start offline refactoring.<br />
**included refactoring of local tasks to AbstractRepositoryTask (P1)<br />
**For RC0, add progress monitor to all api methods that involve IO to easy future implementation.<br />
* Steffen to open new bug for alternate containment representations (outline, task editor can be used to reveal) duplicates for bugzilla could use this<br />
* Mik to make new bug for Open Resource bug related to Task Working sets (defer Eugen's multiple tasklist views patch since will require additional view memento facility?) <br />
* Rob: Will investigate breaking out past activity from scheduled mode (after higher priority api changes).<br />
* For next call: Committers should review their P1 and P2 tasks and form a realistic list for 2.0<br />
<br />
==== Tuesday, May 15, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
* Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen) ([[Mylar Offline Refactoring]])<br />
** Do we really need two separate APIs for task list and offline storage?<br />
** Class hierarchy vs. property-based API<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Decisions made regarding offline TaskData handling and presentation merged with wiki ([[Mylar Offline Refactoring]]).<br />
<br />
==== Tuesday, May 8, 10-11am PT ====<br />
<br />
* New Task List layout (Mik)<br />
* Monitor update (Meghan)<br />
** Server memory troubles (Steffen)<br />
* MylarStatus API and HTML errors [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170536 170536] (Steffen)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
<br />
Actions:<br />
* Additive improvements deferred in favor of API changes.<br />
Main API changes (P2):<br />
* Local task become repository tasks<br />
* Hits become Tasks (but retain UI representation)<br />
* Offline storage improvements ([[Mylar Offline Refactoring]])<br />
* Tasklist externalization<br />
* AbstractRepositoryTaskEditor (make protected methods private)<br />
* Multiple Task Downloads (synch api changes)<br />
* Context listeners api (Mik)<br />
* Extract repository configuration<br />
<br />
<br />
==== Tuesday, May 1, 10-11am PT ====<br />
<br />
* Eclipse Forum Europe report (Mik)<br />
* New Task List layout (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* Monitor update (Meghan)<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Mylar demo at JavaOne (Eugene, Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=153573 153573] add support for nesting top level task list elements, e.g. via incorporating working sets (Eugene)<br />
* Post action items/summary/minutes after each meeting (Mik?)<br />
<br />
Actions:<br />
* Eugene<br />
** send screenshot example of strikethrough looking like row lines<br />
* Mik<br />
** consider moving activation to task icon<br />
** working sets in tasklist needs priority since we need to put miles on it before release<br />
* Rob<br />
** persistence api should be finalized so that we can drop in alternate back ends<br />
<br />
==== Tuesday, April 24, 10-11am PT ====<br />
<br />
* Post action items/summary/minutes after each meeting<br />
* Streamline UI for basic RSS support (Eugene, Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
Minutes:<br />
* Greg Wilson gave brief overview of planned work for SoC project<br />
* Discussed options for implementing offline storage for task data<br />
* Discussed use cases for RSS support in the Task List<br />
* Discussed tagging and working sets support in the Task List<br />
<br />
Actions:<br />
<br />
* Does it make sense to keep task data separate from the task list?<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165880 165880: Listeners API should allow to pass multiple events in one call] Potential source of refresh issues (Eugene)<br />
<br />
==== Tuesday, April 17, 10-11am PT ====<br />
<br />
* Google Summer of Code planning (Mik)<br />
* ROME depency accepted (Eugene, Mik)<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
** Contributing custom models to task list and task repositories views. per-milestone/version grouping, or grouping query results by certain attributes (Eugene)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API updates (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
* Post action items/summary after each meeting<br />
<br />
==== Tuesday, April 10, 10-11am PT ====<br />
<br />
* Usage monitor status (Meghan)<br />
* Tagging and nesting task list elements UI discussion (Mik)<br />
* Offline storage strategy design discussion (Rob, Steffen)<br />
* 2.0M3 API changes (Mik)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=179873 179873: Completed status not correct for JIRA tasks]<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View (Eugene)<br />
<br />
==== Tuesday, April 3, 10-11am PT ====<br />
<br />
* Mylar 2.0M2 release wrap-up, 2.0M3 planning (Mik)<br />
* Offline storage strategy design discussion(Rob, Steffen)<br />
<br />
==== Tuesday, March 27, 10-11am PT ====<br />
<br />
Planning meetings are open to all interested. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
<br />
* Mylar 2.0M2 status<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=178933 178933] Show last recently used views in the Quick Context View<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176513 176513] [api] Multiple task data request (Rob)<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 160389] [api] Serialization / loss of data etc (Rob)<br />
* JIRA statuses: resolved vs. closed<br />
<br />
==== Tuesday, March 20, 10-11am PT ====<br />
<br />
* [http://wiki.eclipse.org/index.php/Mylar_GSoC_2007 Goolge Summer of Code ideas] (Mik)<br />
* Eclipse 3.3M6 status (Mik)<br />
* JIRA network utilization ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=175407 175407])<br />
* JIRA test server<br />
* usage reporting (Meghan)<br />
<br />
==== Tuesday, March 13, 10-11am PT ====<br />
<br />
Agenda:<br />
* EclipseCon decompression (Mik)<br />
* JIRA test server (Steffen)<br />
* 2.0M2 planning<br />
* AttributeFactoryUI/RepositoryConfiguration (Rob, Steffen)<br />
<br />
==== Tuesday, February 27, 10-11am PT ====<br />
<br />
Agenda:<br />
* '-' issue - [https://bugs.eclipse.org/bugs/show_bug.cgi?id=166174 bug 166174]<br />
* EclipseCon planning (Mik)<br />
** 3.2 dev build<br />
** Stickers/Buttons/T-shirts<br />
** Poster<br />
* In-place context view (Mik, Eugene)<br />
* GSoC 2007 project (Steffen)<br />
<br />
Actions:<br />
* Find Mylar film glasses (Steffen)<br />
* Find out if there is any space left for poster presentations (Rob)<br />
* At EclipseCon ask EMF folks about using EMF for repository mappings (Mik & Rob)<br />
<br />
==== Tuesday, February 20, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* 2.0M1 release review (Mik)<br />
* Id vs handle vs key (Mik)<br />
* How to make Query creation more obvious for new users (Eugene)<br />
* Showing Task ID/Keys in UI (task list and task dialogs, editor tabs and headers, task history dropdown, change sets) (Eugene)<br />
* JIRA issues (Eugene, Steffen)<br />
<br />
Actions:<br />
* File form header bug<br />
* Create method: TaskList.getTask(String connectorKind, String taskUrl)<br />
* Create AbstractRepositoryTask.getKey()<br />
<br />
==== Tuesday, February 13, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda:<br />
* IP submission follow-ups for Lucene 2.0, Axis2 (Mik)<br />
* Major connector externalizer and task handle usage refactoring (Mik)<br />
* JIRA issues<br />
* Make Steffen JIRA committer<br />
* Discuss refactoring of RepositoryTaskAttributes (bug 150680?) (Steffen)<br />
** Separate UI representation from attribute?<br />
** How to link attributes to repository configuration?<br />
<br />
==== Tuesday, February 6, 10-11am PT ====<br />
<br />
Agenda<br />
* Finalizing of Mylar 2.0 plan (Mik)<br />
* Status of IP submissions (Mik)<br />
* Orbit dependencies<br />
* Status of JIRA<br />
* Issues with handles (Eugene)<br />
* Issues with event notification api (Rob)<br />
<br />
==== Tuesday, January 30, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Moving to Eclipse 3.3M5 builds (Mik)<br />
* Final IP and contribution submissions for Europa (Mik)<br />
* Status Jira Core Services and library dependencies (Steffen)<br />
<br />
==== Tuesday, January 23, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning (Mik)<br />
* Implementation strategy for<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=171081 171081]: Autodetect JIRA repository for Open Corresponding Task (Eugene)<br />
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=159135 159135]: Automatic resolution of links between projects and issue repositories (Eugene)<br />
* Additional contributions to be made by the Jan. 31st Europa cutoff (Mik)<br />
Actions<br />
* Consider Lucene 2.0 IPZilla submission (Mik)<br />
<br />
==== Tuesday, January 16, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* Mylar 2.0 planning<br />
* Tomcat and server setup for mylar.eclipse.org<br />
* TaskId vs TaskHandle (numerous issues with JIRA connector) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=170587 bug 170587]<br />
* Models and their application to the tasklist (Rob, Eugene) ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147084 147084: merge Task List and Task Activity views])<br />
** "[use] models and provide model that would show unread/changed/conflicting tasks" ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=170606 170606: Add action to Task List to filter out read requests])<br />
** 153573: add support for nesting top level task list elements, e.g. via incorporating working sets<br />
* Task web browser<br />
Actions:<br />
* Add milestone buckets 2.0M1 through M3 (Mik)<br />
* Gets JIRA enterprise license key for test server (Mik)<br />
* Ask about server backup policy (2.6 Gigs used), disk space for usage data (Mik)<br />
* Consider downgrading Tomcat to 5.5 (Meghan)<br />
* Write up Mylar monitor data collection project (Meghan)<br />
* Plans hyperlink detection improvements and bugs (Rob)<br />
**170679: [api] improve hyperlink detection api<br />
**170681: [api] allow connectors to contribute alternate content providers (models) to tasklist<br />
**170685: [api] allow connectors to contribute filters to tasklist<br />
<br />
==== Tuesday, Januray 9, 10-11am PT ====<br />
<br />
Agenda:<br />
* Mylar 2.0 milestone and Europa planning.<br />
* Synchronization, progress indication, and cancellation of repository task operations ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168257 168257], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=150682 150682], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=154258 154258], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=143011 143011])<br />
* Mylar error handling ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=168049 168049], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165498 165498], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=168672 168672], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=165383 165383])<br />
* Task activity timing improvement ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=147537 147537])<br />
* JIRA issues (auth problem and integrating JIRA client)<br />
Actions:<br />
* Write up error policy (Steffen)<br />
* Plan synchronization related bugs (Rob)<br />
* Find platform release dates (Mik)<br />
* Define scope of project on planning page (Mik)<br />
* Add dummy query on codehouse project (Mik)<br />
<br />
==== Tuesday, December 19, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
* 1.0.1 priorities (Mik) <br />
* Slap Eugene for discrediting Mylar in blogs and Mik for not blogging<br />
* Layout of search/query page<br />
<br />
==== Tuesday, December 12, 10-10:30am PT ====<br />
* Mylar 1.0 celebration and retrospective.<br />
* Brock Janiczak's JIRA core services contribution (Eugene, Mik?).<br />
* Discovery update sites (Eugene, Mik).<br />
* Version numbers (Mik).<br />
<br />
==== Tuesday, December 5, 10-10:30am PT ====<br />
* Remaining priorities for 1.0 (Mik)<br />
* API status (Mik)<br />
** Externalizers ITaskListExternalize<br />
** Listeners API, primarily ITaskListChangeListener<br />
** Adapting to ITask and broken selection of the task respositories<br />
* Proxy settings status (Rob)<br />
* Subclipse integration and Team API (Eugene)<br />
<br />
<br />
==== Tuesday, November 21, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Remaining 1.0RC1 items (Mik)<br />
** Issues with tack context (multiple folders, unfiltering issues, etc)<br />
** Issues with new local task UI (focus, inline vs. editor)<br />
** Moving task drop down and pause button out of Task List UI?<br />
* Bugzilla and repository infrastructure status (Rob)<br />
* Trac status (Steffen)<br />
* Web connector status (Mik)<br />
* JIRA connnector status (Mik & Eugene)<br />
Actions<br />
* Mik emails newsgroup/mylar-dev about task list toolbar changes<br />
* Mik fixes classpath of context.core xmlrpc-use<br />
* Visible editor always unfiltered<br />
* Eugene files bug on editor color problem<br />
* Steffen files bug People section with JIRA<br />
<br />
==== Tuesday, November 14, 10-11am PT ====<br />
<br />
Agenda<br />
* Mylar 1.0 priorities.<br />
* Pause button UI (Mik?)<br />
Actions<br />
* Need people section for Trac<br />
* Discuss removing commit context button on newsgroup<br />
* Allow proxy settings to be specified per-repository<br />
<br />
==== Tuesday, October 31, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Authentication infrastructure and connectors (Rob)<br />
* Offline support for JIRA (Mik)<br />
* Pause button UI (Mik)<br />
<br />
<br />
==== Tuesday, October 24, 10-11am PT ====<br />
<br />
Planning meetings are open to all. When adding an item to the agenda please include your name.<br />
<br />
Agenda<br />
* 0.8 post-mortem (Mik)<br />
* Storage of offline task data (See [[Mylar Task List]]) (Rob)<br />
* JIRA priorities (Mik)<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* [http://dev.eclipse.org/mhonarc/lists/mylar-dev/msg00706.html Alternative integration] with remote repositories (Eugene)<br />
<br />
Actions<br />
* Investigate Lucene as store for offline task data (Rob)<br />
* Investigate showing working sets as top-level nodes in Task List (Mik)<br />
<br />
==== Tuesday, October 17, 10-11am PT ====<br />
<br />
Agenda<br />
* 0.8 release planning<br />
* Web repository connector UI , [https://bugs.eclipse.org/bugs/show_bug.cgi?id=158069 bug 158069] (Eugene)<br />
* Rich editor for Trac (Steffen?)<br />
* Repository task data (Rob)<br />
** Offline persistence: object serialization (current), xml, database [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 bug 160389]<br />
** Lazy loading [https://bugs.eclipse.org/bugs/show_bug.cgi?id=157257 bug 157257]<br />
* Issues with Task monitoring and filtering for projects with more then one source folder<br />
* Jira integration planning<br />
* User guide and improving the docs<br />
<br />
Actions<br />
* Need "Add to Task List" action on query hits<br />
* Consider merging the above action with dialog for "Add Existing Task..."<br />
* Need to consider pre-fetching task data for query hits<br />
<br />
==== Tuesday, September 26 2006, 10-11am PT ====<br />
* 0.7 release planning<br />
* Project and repository association (Rob)<br />
* 1.0 planning (Mik)<br />
<br />
==== Wednesday, August 23 2006, 10-11am PT ====<br />
* Planning for 0.6.2<br />
* Generic web Repository Connector integration (Eugene)<br />
* Trac Connector rich editor (Steffen)<br />
* AbstractRepositoryConnector split into core and UI<br />
* Planning for 0.7 and 1.0<br />
* Zest website integration and release cycles<br />
<br />
==== Wednesday, August 2 2006, 10-11am PT ====<br />
Agenda<br />
* 0.6.1 post-mortem<br />
* 0.6.2 and 1.0 planning<br />
* Summer of Code status<br />
** Trac Connector (Steffen)<br />
** Bugzilla enhancements (Jeff)<br />
** JIRA<br />
* Design discussion on splitting AbstractRepositoryConnector into core/ui<br />
* Sandbox release for web connector (Eugene)<br />
Vacations<br />
* Rob: 3rd - 8th<br />
* Mik: 8th - 17th<br />
Actions<br />
* Consumers of APIs update Javadocs as they use them, a la wiki <br />
* Decide on conference call time and interval next meeting<br />
* Investigate Rome dependency for Sandbox (Mik)<br />
<br />
==== Thursday, July 6 2006, 10am PT ====<br />
* wrap up discussion of 0.6 release<br />
* Trac integration status (Steffen)<br />
* enhancing Bugzilla connector status (Jeff)<br />
* Connector naming conventions<br />
* tasks API discussion. String-based task id, separate task id, url and repository url, (issues 146396, 149624, 149509), other refactoring of tasks, hits, query and repository classes<br />
* UI for repository settings<br />
* prioritizing for 0.7 and beyond<br />
* planning and use of Bugzilla priorities<br />
<br />
==== Tuesday, June 13 2006, 10am PT ====<br />
* Schedule a regular meeting time and interval<br />
* Google SoC: Trac integration (Steffen)<br />
* Google Soc: enhancing Bugzilla connector (Jeff)<br />
* Repository connector API discussion (Mik)<br />
* Prioritize tasks for 0.6 (Mik)</div>Steffen.pingel.eclipse.orghttps://wiki.eclipse.org/index.php?title=Mylyn/Refactoring&diff=37283Mylyn/Refactoring2007-05-24T05:57:07Z<p>Steffen.pingel.eclipse.org: /* For RC0 */</p>
<hr />
<div>== For RC0 ==<br />
* [Rob] Offline externalization in xml form<br />
** RepositoryTaskAttribute no longer holds options<br />
** Remove name and hidden property from RepositoryTaskAttribute <br />
** Remove all methods from AbstractAttributeFactory except for createAttribute() and getDateForAttributeType() [default implementation should return attribute.getDate()?]<br />
*** Attributes need to be created by connectors<br />
* [Rob] bug#176513<br />
* [Rob] bug#161734<br />
* [Steffen] AbstractRepositoryTaskEditor ui factory implementation<br />
* [Steffen] bug#173011 - specifically: add IProgressMonitor parameter to IO methods<br />
<br />
= Related Bug Reports =<br />
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=160389 160389] [api] change how offline task data is cached to disk and refactor attribute factory<br />
<br />
* 176513: [api] add support for requesting multiple task data in single request<br />
https://bugs.eclipse.org/bugs/show_bug.cgi?id=176513<br />
<br />
= Requirements =<br />
<br />
* Persistence<br />
** Provide a generic API for storing task attributes<br />
* Configuration extraction<br />
* Presenation api<br />
<br />
= API =<br />
<br />
Changes to current implementation:<br />
* RepositoryTaskData becomes a generic storage API<br />
* Excpected attributes and data types are specified through Java interfaces <br />
<br />
== Task Data ==<br />
<br />
ITaskDataManager {<br />
TaskDataState getTaskDataState(String repositoryUrl, String id);<br />
void saveTaskDataState(TaskDataState taskState);<br />
void refactorRepositoryUrl(String oldUrl, String newUrl);<br />
void removeTaskDataState(String repositoryUrl, String id);<br />
void saveNewTaskDataState(TaskDataState newTaskDataState); // (rfc) Sets unique new id<br />
Set<TaskDataState> getNewTaskDataState(String repositoryUrl); // (rfc)<br />
}<br />
<br />
<br />
*TaskDataState created via ITaskDataHandler.buildTaskDataState(RepositoryTaskData newData, RepositoryTaskData oldData, Set<RepositoryTaskAttribute> edits);<br />
*TaskDataState is an unmodifiable object but not final.<br />
<br />
TaskDataState {<br />
public TaskDataState(RepositoryTaskData newTaskData, RepositoryTaskData oldTaskData, Set<RepositoryTaskAttribute> edits); // Constructor sets values but does not do computation<br />
public init(); // Perform constructor specific initialization (i.e. calc changed attributes etc)<br />
RepositoryTaskData newTaskData;<br />
RepositoryTaskData oldTaskData;<br />
Set<RepositoryTaskAttribute> edits;<br />
isStateModified();<br />
hasIncomingChanges();<br />
hasChanged(RepositoryTaskAttribute attribute);<br />
Set<RepositoryTaskAttribute> getChanged();<br />
void discardEdits(String repositoryUrl, String id);<br />
}<br />
<br />
== Task Attributes ==<br />
<br />
Attributes are stored in RepositoryTaskData objects which manages all offline data for a task. For simplicity attributes can have properties (key/value pairs) but not have child attributes. To easily store and retrieve a list of related attributes such as attachments or comment attributes have a type (e.g. "attachment", "comment", "custom"). <br />
<br />
RepositoryTaskData {<br />
RepositoryTaskAttributeMapper mapper;<br />
RepositoryTaskAttribute createAttribute(String id, String type);<br />
RepositoryTaskAttribute getAttribute(String id);<br />
RepositoryTaskAttribute[] getAttributes(String type);<br />
}<br />
<br />
RepositoryTaskAttribute { // IMemento style<br />
String id; // unique ID<br />
void setDateValue(Date date);<br />
Date getDateValue();<br />
... // support for String, int, float, boolean<br />
}<br />
<br />
To map from predefined attribute keys that are used by the editor to access information about changed attributes each task data object holds on to a mapper (former AbstractAttributeFactory):<br />
<br />
RepositoryTaskAttributeMapper {<br />
String mapToAttributeID(String mylarID);<br />
}<br />
<br />
== Mylar Task Model ==<br />
<br />
Make this model explicit and define it in terms of Java interfaces. Only these interfaces are used by the editor to set/get values. Default implementation of proxy classes are provided for mapping to underlying task data objects. <br />
<br />
''Accessor methods should mirror fields available on AbstractRepositoryTask.'' (This could be separate from the offline storage so connectors without a TaskDataHandler could provide attachment support.)<br />
<br />
public interface IRepositoryTask {<br />
String getDescription();<br />
void setDescription(String description);<br />
...<br />
}<br />
<br />
public class RepositoryTaskProxy {<br />
RepositoryTaskProxy(RepositoryTaskData taskData);<br />
String getDescription() {<br />
taskData.getAttribute(RepositoryTaskData.DESCRIPTION).getStringValue();<br />
}<br />
void setDescription(String description) {<br />
taskData.getAttribute(RepositoryTaskData.DESCRIPTION).setStringValue(description);<br />
}<br />
void createAttributes() {<br />
taskData.createAttribute(RepositoryTaskData.DESCRIPTION);<br />
}<br />
...<br />
}<br />
<br />
IRepositoryTaskComment {<br />
String getId(); // allows to map to underlying attribute?<br />
String getAuthor();<br />
Date getCreated();<br />
...<br />
}<br />
<br />
IRepositoryTaskAttachment {<br />
String getFilename()<br />
String getDescription()<br />
...<br />
}<br />
<br />
IRepositoryTaskOperation {<br />
...<br />
}<br />
<br />
Instances of the interfaces are provided by ITaskDataHandler:<br />
<br />
ITaskDataHandler {<br />
IRepositoryTask getTask(RepositoryTaskData);<br />
IRepositoryTaskAttachment[] getAttachments(RepositoryTaskData);<br />
IRepositoryTaskComment[] getComments(RepositoryTaskData);<br />
}<br />
<br />
== Editor/UI ==<br />
<br />
The editor should only hold on to a RepositoryTaskData object. Connectors provide a factory for UI representation of attributes:<br />
<br />
AbstractConnectorUi {<br />
abstract ITaskUiFactory getTaskUiFactory()<br />
}<br />
<br />
ITaskUiFactory {<br />
String getLabel(RepositoryTaskAttribute attr)<br />
Control createEditor(RepositoryTaskAttribute attr, Composite parent)<br />
void addFieldEditors(Set<RepositoryTaskAttribute>, Composite parent); // reponsible for layout/order<br />
String getToolTip(RepositoryTaskAttribute attr)<br />
}<br />
<br />
Mylar provides default implementations to create an editor for an attribute:<br />
<br />
MylarEditorFactory {<br />
Control createComboEditor(RepositoryTaskAttribute attr, Composite parent, String[] options);<br />
}</div>Steffen.pingel.eclipse.org