This page lists all the information, data, figures, visualisation retrieved by plugin EclipsePmi for project technology.ease.
From the plugin's documentation:
Eclipse PMI Retrieves meta data about the project from the Eclipse PMI infrastructure.
See the project's documentation for more information.
The plugin has generated
18 information items,
20 metrics,
8 recommendations,
1 visualisation,
3 downloads, and
0 figures. Last analysis was executed on 2022-01-23 00:25:14.
| Name | Value | |
|---|---|---|
| PMI_BUGZILLA_COMPONENT | ||
| PMI_BUGZILLA_CREATE_URL | https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EASE | |
| PMI_BUGZILLA_PRODUCT | EASE | |
| PMI_BUGZILLA_QUERY_URL | https://bugs.eclipse.org/bugs/buglist.cgi?product=EASE | |
| PMI_GETTINGSTARTED_URL | ||
| PMI_UPDATESITE_URL | ||
| PROJECT_CI_URL | https://ci.eclipse.org/ease/job/ease.build.nightly/ | |
| PROJECT_DESC | <p>Eclipse EASE™ allows the execution of script code (using scripting languages such as JS, Python, ...) within the context of the Eclipse Platform/RCP. As they are running in the same JRE as Eclipse itself, these scripts have direct access to any class of your application and may interact with your workbench.</p> <p>Through keywords within header data, scripts might be integrated seamlessly into the UI as toolbar and/or menu contributions. Thus the functionality could be extended by providing scripts only. No need to build, export and install a new feature, just provide a script and add it to your application at runtime.</p> <p>Scripting allows to easily extend an existing application, helps in automating everyday tasks and aids in rapid prototyping during application development. </p> <p>Following goals for the project have been defined:</p> <ol><li>Execute scripts within the running IDE.</li> <li>Support multiple script languages via a generic service that creates (multiple) script interpreters.</li> <li>Scripts are capable of interacting with the IDE, like accessing classes on the Eclipse/JRE classpath and calling methods upon them.</li> <li>Seamless integration of scripts into UI</li> <li>Scripts should be attachable to toolbars and menus</li> <li>Debuggers are aware of the script language/Java classes co-existence by providing variables access</li> <li>Provide means to sign scripts.</li> </ol> | |
| PROJECT_DOC_URL | ||
| PROJECT_DOWNLOAD_URL | https://www.eclipse.org/ease/download/ | |
| PROJECT_ID | technology.ease | |
| PROJECT_ITS_URL | ||
| PROJECT_MLS_DEV_URL | https://dev.eclipse.org/mailman/listinfo/ease-dev | |
| PROJECT_MLS_USR_URL | ||
| PROJECT_NAME | Eclipse Advanced Scripting Environment (Eclipse EASE ™) | |
| PROJECT_SCM_URL | https://git.eclipse.org/r/plugins/gitiles/ease/org.eclipse.ease.scripts | |
| PROJECT_URL | ||
| PROJECT_WIKI_URL | https://wiki.eclipse.org/EASE |
| Name | Mnemo | Description | Value | Indicator |
|---|---|---|---|---|
| Governance documentation | DOC_GOV | Is there a documentation explaining how decisions are made? | 1 | 5 |
| Board transparency | GOV_BOARD_PUBLIC | Are the minutes of the board publicly available? | 1 | 5 |
| Dependency check | OSS_DEP_CHECK | Analysis of dependencies to identify old, vulnerable dependencies, as provided by tools like dependency-check or JFrog/Nexus. | 1 | 5 |
| Escalation procedure | OSS_ESCALATE | Is there an easy and visible way for anybody to report toxic behaviour or unfair practices? | 1 | 5 |
| Inclusion initiative | OSS_INCLUSION | Is there a formal procedure to help people join and benefit from the community, whoever they are? | 1 | 5 |
| Access information | PROJECT_ACCESS_INFO | Is the access info (downloads, update sites..) correctly filled in the PMI records? | 1 | 3 |
| CI access | PROJECT_CI_ACCESS | Is the continuous integration info correctly filled in the PMI records? | 0 | 4 |
| CI information | PROJECT_CI_INFO | Is the continuous integration info correctly filled in the PMI records? | 1 | 5 |
| DL access | PROJECT_DL_ACCESS | Is the access info (downloads, update sites..) correctly filled in the PMI records? | 1 | 5 |
| DL information | PROJECT_DL_INFO | Is the access info (downloads, update sites..) correctly filled in the PMI records? | 1 | 5 |
| Doc access | PROJECT_DOC_ACCESS | Is the documentation info correctly filled in the PMI records? | 0 | 4 |
| Docs information | PROJECT_DOC_INFO | Is the documentation info correctly filled in the PMI records? | 4 | 5 |
| Getting started | PROJECT_GETTINGSTARTED_INFO | Is the documentation info correctly filled in the PMI records? | 0 | 4 |
| ITS access | PROJECT_ITS_ACCESS | Is the bugzilla info correctly filled in the PMI records? | 0 | 4 |
| ITS information | PROJECT_ITS_INFO | Is the bugzilla info correctly filled in the PMI records? | 5 | 5 |
| MLS access | PROJECT_MLS_ACCESS | Is the communication channel for the team info correctly filled in the PMI records? | 0 | 4 |
| MLS information | PROJECT_MLS_INFO | Is the communication channel for the team info correctly filled in the PMI records? | 0 | 3 |
| Number of releases | PROJECT_REL_VOL | The number of releases recorded in the PMI. | 8 | 4 |
| SCM access | PROJECT_SCM_ACCESS | Is the source_repo info correctly filled in the PMI records? | 1 | 5 |
| SCM information | PROJECT_SCM_INFO | Is the source_repo info correctly filled in the PMI records? | 1 | 4 |
| Type | Severity | Description |
|---|---|---|
| PMI_NOK_CI | High | The Hudson CI engine URL [https://ci.eclipse.org/ease/job/ease.build.nightly/] in the PMI is not detected as the root of a Hudson instance. |
| PMI_EMPTY_USER_ML | High | The user mailing list URL is empty in the PMI. It helps people know where to ask questions if they want to use the product and should be filled. |
| PMI_EMPTY_UPDATE | High | The update site URL is empty in the PMI. People need it if they want to use the product, and it should be filled. |
| PMI_EMPTY_TITLE | Medium | The title entry is empty in the PMI. |
| PMI_EMPTY_PROPOSAL | Low | The proposal document URL is empty in the PMI. It helps people understand the genesis of the project and should be filled. |
| PMI_EMPTY_PLAN | Low | The plan document URL is empty in the PMI. It helps people understand the roadmap of the project and should be filled. |
| PMI_EMPTY_GETTING_STARTED | Low | The getting started URL is empty in the PMI. It helps people use, and contribute to, the project and should be correctly filled. |
| PMI_EMPTY_DOC | Low | The documentation URL is empty in the PMI. It helps people use, and contribute to, the project and should be correctly filled. |
| Script | Name | URL |
|---|---|---|
| pmi_checks | Eclipse PMI Checks | /projects/technology.ease/EclipsePmi/pmi_checks |
| Plugin | Description | URL |
|---|---|---|
| pmi.json | pmi.json The PMI file as returned by the Eclipse repository (JSON). |
/projects/technology.ease/EclipsePmi/pmi.json |
| pmi_checks.csv | pmi_checks.csv The list of PMI checks and their results (CSV). |
/projects/technology.ease/EclipsePmi/pmi_checks.csv |
| pmi_checks.json | pmi_checks.json The list of PMI checks and their results (JSON). |
/projects/technology.ease/EclipsePmi/pmi_checks.json |
| Script | Description | URL |
|---|
Page generated by Alambic 3.3.3-dev on Mon Jan 24 00:03:53 2022.