Discouraged Access Warnings

Quote from http://wiki.eclipse.org/Dali_Discouraged_Access_Warnings :

Because test plug-ins are not loaded at run-time, there is no need to make them friends of the non-test plug-ins. To suppress the Discouraged Access warnings in a test plug-in, we add the appropriate build-time access rule exceptions to the project's Java build path (e.g. o.e.jpt.core.tests suppresses any access warnings caused by references to o.e.jpt.core). See the DTP description of this Eclipse feature.

Links

• Naming Conventions
• Version Numbering
• User Interface Guidelines

Target platforms

• e35 - Eclipse 3.5 / Galileo
• e36 - Eclipse 3.6 / Helios
• e37 - Eclipse 3.7 / Indigo

Mylyn Integration

Links :

• http://wiki.eclipse.org/Mylyn_Integrator_Reference
• http://wiki.eclipse.org/index.php/Mylyn_FAQ
• http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.mylyn.tasks/?root=Mylyn_Project
• http://trac.assembla.com/assemblamylyn
• https://bitbucket.org/atlassian/connector-eclipse/overview

Workflow for review as how it supposed to be in Sonar 2.9 :

Manual testing as it was done in Sonar Eclipse 2.1.0 :

1. Create repository => repository created and shown in category "Reviews" in views "Task/Team Repositories"
   • Validation of server URL (valid URL with protocol http or https)
   • Username required
2. Create query => reviews added to task list
3. Create new review thru Sonar UI, synchronize query => new review added to task list
4. Add new comment thru Sonar UI => notification and review marked as unread
5. Reassign review thru Sonar UI on another user, synchronize query => notification and review moved to category "Unmatched"
6. Reassign review thru Sonar UI on you => notification and review moved back to query
7. Remove repository => query and all reviews removed