-
Task
-
Resolution: Unresolved
-
Minor
-
MTA 7.3.0
-
Quality / Stability / Reliability
-
5
-
False
-
-
False
-
-
-
None
Ruleset documentation focuses on JAVA ruleset
Can we include example rules for other languages
What is the main user goal aka job to be done?
Red Hat Migration Toolkit for Applications (MTA) and its upstream Konveyor project allow users to add custom rulesets for languages other than Java, enabling a broader scope for application modernization efforts. While some capabilities for non-Java languages are currently in Developer Preview or Technology Preview, the core functionality for custom rules exists.
The main user goals, or "jobs to be done," when adding custom rulesets for other languages can be articulated from different user personas:
- As an Administrator or Architect:
-
- I want to configure and extend MTA's analysis capabilities to include applications developed in diverse programming languages beyond standard Java support, such as .NET, Python, Node.js, or Go, even if they are currently in Developer or Technology Preview.
- So that I can enable comprehensive assessment and modernization planning for my entire application portfolio, identify issues, and estimate the effort required for modernization, especially for technologies where default rules may be limited or absent. This also helps in simplifying analysis configuration for non-admin users or third-party developers by providing "ready-made custom migration targets".
- As a Developer or Engineer:
-
- I want to create and apply specific rules to meticulously analyze custom code, identify proprietary libraries, or detect unique architectural patterns within applications written in non-Java languages. This is particularly necessary when a language discovered in the application does not have a supported provider.
- So that I can gain precise insights into migration issues and receive tailored guidance, messages, and tags for modernizing these applications, even if they use "custom libraries or other components that might not be covered by the provided standard migration rules". This granular control helps in addressing very specific or niche migration challenges.
- mentioned in
-
Page Loading...