hansva opened a new issue, #9643:
URL: https://github.com/apache/hop/issues/9643

   ### What needs to happen?
   
   A plugin carries its own dependencies, and the ones several plugins share 
belong in
   `lib/core`, so there is one copy of each. Today:
   
   - the same jar often sits in the private `lib/` of several plugins;
   - some libraries exist in `lib/core` in two versions;
   - plugin poms pin versions that drift from what Hop ships.
   
   ### Proposal
   
   - **hop-libs manages whole library families.** It imports `jackson-bom` and 
aligns Avro,
     SLF4J and Hadoop modules, so `lib/core` holds one version of each.
   - **Shared libraries ship to `lib/core`** instead of several plugins' 
private `lib/`. Among
     them: JGit, sshd, Lettuce, commons-pool2, ANTLR, fastutil, moshi, 
Caffeine, Parquet,
     Guava, libphonenumber and netty-tcnative.
   - **Jackson modules ship to `lib/core`.** Several plugins only worked when 
Google, Beam or
     Spark happened to provide jsr310, dataformat-xml or dataformat-avro.
   - **Plugin poms take their versions from hop-libs** instead of pinning their 
own.
   - **AWS** no longer puts the Redshift and PostgreSQL plugin jars in 
`lib/core`.
   - **Spark** moves the 63 jars it shares with other plugins to `lib/core`. It 
also ships the
     Google Cloud Storage client for Iceberg tables, at the same versions as 
the Google plugin.
   - **Beam** ships the Confluent serializers to `lib/core`, like the Kafka 
plugin does.
   
   ### Result
   
   Checked on a client with all plugins installed:
   - no library is in `lib/core` at two versions;
   - no jar moved to `lib/core` needs a class that only a plugin's `lib/` has.
   
   The Spark-native, Iceberg, Lakehouse and Beam integration tests pass on 
minimal installs.
   
   Depends on #9639.
   
   ### Issue Priority
   
   Priority: 2
   
   ### Issue Component
   
   Component: Transforms


-- 
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