|
1 | 1 | package tech.jhipster.lite.module.domain.resource;
|
2 | 2 |
|
| 3 | +/** |
| 4 | + * Represents the maturity and adoption level of JHipster modules. |
| 5 | + * Ranks range from experimental to community-validated, |
| 6 | + * helping users assess module stability and production readiness. |
| 7 | + */ |
3 | 8 | public enum JHipsterModuleRank {
|
4 | 9 | /**
|
5 |
| - * Not really usable as is, unless you have good expertise on the subject |
6 |
| - * (ex: custom-jhlite) |
| 10 | + * Experimental or advanced module requiring specific expertise |
7 | 11 | */
|
8 | 12 | RANK_D,
|
9 | 13 |
|
10 | 14 | /**
|
11 |
| - * No known usage on production product |
12 |
| - * (ex: vue-core, the current version) |
| 15 | + * Module without known production usage |
13 | 16 | */
|
14 | 17 | RANK_C,
|
15 | 18 |
|
16 | 19 | /**
|
17 |
| - * One declared usage on production product |
18 |
| - * (ex: kipe-authorization) |
| 20 | + * Module with at least one confirmed production usage |
19 | 21 | */
|
20 | 22 | RANK_B,
|
21 | 23 |
|
22 | 24 | /**
|
23 |
| - * Multiple declared usages on production product, by multiple person, on various projects |
24 |
| - * and demonstrated usage on a talk, book or blog post |
25 |
| - * (ex: java-base) |
| 25 | + * Module with multiple production usages across different projects |
| 26 | + * and documented through talks, books or blog posts |
26 | 27 | */
|
27 | 28 | RANK_A,
|
28 | 29 |
|
29 | 30 | /**
|
30 |
| - * A and recognized to add some features that are not available otherwise. |
31 |
| - * Features must be really unique and this must be recognized by at least 10 person |
32 |
| - * with a vote on any social network (GitHub being a social network). |
33 |
| - * With those criteria spring-boot-cucumber-mvc is a good candidate (missing votes). |
| 31 | + * Production-proven module providing unique features, |
| 32 | + * validated by community feedback (10+ endorsements) |
34 | 33 | */
|
35 | 34 | RANK_S,
|
36 | 35 | }
|
0 commit comments