mattcasters opened a new pull request, #7737:
URL: https://github.com/apache/hop/pull/7737

   ## Summary
   
   - **Same-id repo import merges plugin metadata** instead of replacing it. 
Multiple community plugins can publish their own `hop-marketplace-repo.yaml` 
with a shared repository id (e.g. `data-hopper-community`); later imports keep 
earlier plugins and append/update by G:A.
   - **Empty `plugins:` on re-import no longer wipes** existing metadata.
   - **`minHopVersion` / `maxHopVersion` treat `x.y.z-SNAPSHOT` as the `x.y.z` 
line** so a Hop SNAPSHOT build fulfills a requirement for the same release 
(e.g. `2.19.0-SNAPSHOT` satisfies `minHopVersion: 2.19.0`). Artifact version 
ordering still ranks SNAPSHOT below the release.
   
   Fixes #7736
   
   ## Test plan
   
   - [x] Unit tests: dual-import same id (datavault + pentaho), re-import 
updates G:A, empty plugins no-wipe, artifactId match when groupId missing
   - [x] Unit tests: SNAPSHOT Hop version vs min/max Hop bounds; SNAPSHOT still 
< release for artifact compare
   - [x] `./mvnw -pl plugins/misc/marketplace test` and `spotless:check`
   - [ ] Manual: import both community YAML URLs, confirm both plugins appear 
under one repo in hop-config / marketplace query


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to