Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "NoLongerUsed.ContentsmovedToAnotherPage"
m (sync'd up with Git version) |
m (sync'd up with Git version) |
||
| Line 52: | Line 52: | ||
<p>You can ask questions on cross-project list if the tests do not work as expected. Or, even better, you can make improvements/fixes directly on this wiki, if the instructions can be better. Feel free to supply patches on the cross-project component in bugzilla.</p> | <p>You can ask questions on cross-project list if the tests do not work as expected. Or, even better, you can make improvements/fixes directly on this wiki, if the instructions can be better. Feel free to supply patches on the cross-project component in bugzilla.</p> | ||
| − | <!-- | + | <!-- Following is commented out in Git repo version. --> |
[[Category:CBI| ]] [[Category:Oxygen| ]] [[Category:Neon| ]] [[Category:Mars| ]] [[Category:Luna| ]] | [[Category:CBI| ]] [[Category:Oxygen| ]] [[Category:Neon| ]] [[Category:Mars| ]] [[Category:Luna| ]] | ||
| − | |||
Revision as of 14:55, 16 October 2016
Contents
Running your own Repository Reports
Introduction
This document gives a brief outline of how to run the "repo reports" locally, against a repository on your local file system.
There are some tests, that look at jars specifically, that require the jars to be on local file system and essentially use plain 'ol Java file IO and regex-type checks on the contents.
Another class of tests, read the content.jar/xml meta-data and reports on the data or relationships in that meta data.
Yet another, small class of tests, verify the jars are signed. These tests are not really "Java" or "workspace" related, but use Java's "exec" method to invoke "jarsigner -verify" on multiple threads, on a directory of jars.
Running the repo tests
These instructions are focus for "running from your workspace", but could also easily be done "from the command line" if you know how to run Eclipse Applications from the command line.<p>
The Basics
<p>The Eclipse Application is named 'org.eclipse.cbi.p2repo.analyzers.repoReport'. It takes two "system properties"; one to specify
where you want the output to go, and another to specify where the repo is on the file system. For example:- -DreportOutputDir=/home/shared/eclipse/repoReport
- -DreportRepoDir=/home/www/html/downloads/eclipse/updates/4.2-I-builds/I20120531-1500/
The Details
The source project is named 'org.eclipse.cbi.p2repo.analyzers' and is currently in Git in repository named 'cbi/org.eclipse.cbi.p2repo.analyzers.git'. See org.eclipse.cbi.p2repo.analyzers.git (browse, stats, fork on OrionHub) .
Once you load that project into your workspace, it will include one "launch configuration" that can be used as a starting example, edited and used to launch the application from your workspace.
On a large repository, it take 5 or 10 minutes to complete, and then you just to look at the results (usually) with a web browser starting with the 'index.html' at the location you specified in 'reportOutputDir' property.
Getting help or making contributions
You can ask questions on cross-project list if the tests do not work as expected. Or, even better, you can make improvements/fixes directly on this wiki, if the instructions can be better. Feel free to supply patches on the cross-project component in bugzilla.