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 "MoDisco/Wishlist"
< MoDisco
(→Infrastructure) |
(→Technologies) |
||
| Line 18: | Line 18: | ||
* a metamodel of an Eclipse project | * a metamodel of an Eclipse project | ||
* a discoverer to create a model out of an Eclipse project | * a discoverer to create a model out of an Eclipse project | ||
| + | ===A JSP component== | ||
| + | * a metamodel of a JSP | ||
| + | * a discoverer to create a model out of a JSP | ||
| + | |||
| + | <br> | ||
== Use cases == | == Use cases == | ||
Revision as of 11:30, 4 February 2010
This page lists things people would like to see addressed/fixed in MoDisco.
Contents
Infrastructure
- A MoDisco perspective
modisco.common.core and to modisco.discoverersmanager)
Model Browser
- Externalize the TreeView, the ContentProvider. This is necessary to be able to use the browser within CNF.
- Have an option on a link to dispaly the childs directly under the parent, without the node corresponding to the link. This is necessary to be able to use the browser within CNF.
Discoverers Manager
- A wizard to create "Discovery" project (plug-in project, with dependencies to
- A "global" discoverer which automatically detects from a project which ressources can be analyzed by available discovers. The result could be displayed in a wizard which allows selecting the discoverers to launch.
Technologies
A J2EE component
- metamodels and discoverer for web.xml
- metamodel and discoverers for configuration files for main frameworks(Struts, JSF, Hibernate, Spring, Maven, ...)
An Eclipse component
- a metamodel of an Eclipse project
- a discoverer to create a model out of an Eclipse project
=A JSP component
- a metamodel of a JSP
- a discoverer to create a model out of a JSP
Use cases
- M2M heuristics in existing Java->UML chain for filtering Java classes/interfaces and obtain lightweight UML models from huge Java legacy (criteria : util classes, ihm classes, low references/lines number, ... etc)
- JUnit 3 -> JUnit 4 automated refactoring