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
(→Technologies) |
|||
| Line 7: | Line 7: | ||
== Technologies == | == 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 | ||
== Use cases == | == Use cases == | ||
Revision as of 11:18, 4 February 2010
This page lists things people would like to see addressed/fixed in MoDisco.
Infrastructure
- A MoDisco perspective
- A wizard to create "Discovery" project (plug-in project, with dependencies to modisco.common.core and to modisco.discoverersmanager)
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
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