huangping/starRiverProperty
1
0
Fork 0
mirror of https://github.com/hpd840321/starRiverProperty.git synced 2026-06-09 08:20:31 +08:00
Code Issues Packages Projects Releases Wiki Activity

Initial commit: reorganized source tree

Browse Source 
- backend/: 13 Maven modules (cw-elevator-application, cloudwalk-cloud, intelligent-cwoscomponent, ninca-crk, etc.)
- frontend/: 4 Vue projects (elevator-front, cwos-portal, alarm-front, front_acs) + decompiled + scripts
- scripts/: build, test-env, tools (Docker Compose, service templates, API parity)
- docs/: AGENTS.md, superpowers specs, architecture docs
- .gitignore: standard Java/Maven exclusions

Moved from legacy maven-*/ root layout to backend/ organized structure.
This commit is contained in:
hpd840321
2026-05-09 09:00:12 +08:00
commit 7b2bd307f1
7260 changed files with 612980 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.sisyphus/notepads/2026-05-01-ribbon-dubbo-restore/learnings.md
+6
View File
@@ -0,0 +1,6 @@
Plan: Manual QA for ribbon restore in cw-elevator-application 2.0.9
- Ribbon package inside JAR contains two classes: cn/cloudwalk/ribbon/NincaCrkStdRibbonConfiguration.class and cn/cloudwalk/elevator/debug/RibbonLoadBalancerProbeRunner.class. This means the requirement that only NincaCrkStdRibbonConfiguration.class remains in the ribbon directory is not satisfied.
- Deploy configuration files under deploy/v2-maven/ (application.properties, bootstrap.properties, run.sh) have changes compared to the baseline; diffs exist in all three files.
- JAR contains META-INF/MANIFEST.MF, so manifest presence is OK. JAR size ~110 MB indicates a large artifact but is expected for this build.
- Absence of OrgService.class and CommonService.class in the ribbon package is observed, which aligns with the intended cleanup, but overall JAR contents do not meet the single-class requirement.
- Verdict: REJECT for this task with evidence. Next steps: either revert ribbon packaging to include only NincaCrkStdRibbonConfiguration.class, or adjust QA acceptance criteria to account for additional helper classes like RibbonLoadBalancerProbeRunner.class; and update deploy configs to match baseline exactly.