Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Virgo/Committers"
| Line 13: | Line 13: | ||
= Testing = | = Testing = | ||
| − | + | See {{VirgoLink|Test|Test|{{{tab}}}|testing}}. | |
= IP Due Diligence = | = IP Due Diligence = | ||
Revision as of 03:40, 22 June 2010
Version Control
Virgo uses git.
Coding
Virgo has a strong emphasis on maintainable, or "clean", code. If you need a really good introduction to coding, we recommend "Code Complete". If you are already a proficient programmer and want to write really clean code, read "Clean Code". If you are not an expert in writing Java, read "Effective Java".
Virgo code is thread safe unless specifically stated. Achieving thread safety in Java is not easy. We recommend "Java Concurrency in Practice" for a good grounding in Java concurrency.
Testing
See Test.
IP Due Diligence
Raising "works with" CQs
"works with" CQs are required for test dependencies which are not distributed with Virgo or checked in to Eclipse version control (git, svn, cvs).
The initial set of test dependencies was determined, for repositories which are built with ant, as follows:
1. In the build-xxx directory run ant report
2. Extract a raw list of the test dependency jars
find <report directory> -name "*-test.xml" -exec grep -E \/.+\.jar {} \; >test-jars.txt
3. Edit test-jars.txt using an editor with a regular expression global change facility and do the following global changes.
3.1 Replace regex .+\/(.+)\.jar\"> with $1.jar.
3.2 Replace regex .+\/(.+)\.jar\"\/> with $1.jar.
3.3 Replace -sources with the empty string
4. Sort test-jars.txt and remove duplicate lines.
5. Look through test-jars.txt and raise "works with" for any JARs which don't have a Virgo CQ for the correct version. Also, raise corresponding Virgo bugzillas and set the iplog flag to enter the bugzillas in the automated IP log.