|
361 | 361 | </excludeFilterFile> |
362 | 362 | <effort>Max</effort> |
363 | 363 | </configuration> |
| 364 | + </plugin> |
| 365 | + <plugin> |
| 366 | + <groupId>org.apache.maven.plugins</groupId> |
| 367 | + <artifactId>maven-checkstyle-plugin</artifactId> |
| 368 | + <configuration> |
| 369 | + <suppressionsLocation>src/config/checkstyle-suppressions.xml</suppressionsLocation> |
| 370 | + </configuration> |
364 | 371 | </plugin> |
365 | 372 | <plugin> |
366 | 373 | <groupId>org.apache.maven.plugins</groupId> |
|
413 | 420 | </plugins> |
414 | 421 | </build> |
415 | 422 |
|
| 423 | +<dependencyManagement> |
| 424 | + <dependencies> |
| 425 | + <dependency> |
| 426 | + <!-- |
| 427 | + We're using a specific Protobuf version to ensure compatibility with the |
| 428 | + Google Cloud Storage (GCS) client. The GCS client often relies on |
| 429 | + particular Long-Term Support (LTS) versions of Protobuf. When we upgrade |
| 430 | + the GCS client, we'll likely need to update Protobuf too. To prevent |
| 431 | + dependency conflicts, Protobuf will be shaded within the GCS connector's |
| 432 | + fat JAR. |
| 433 | + --> |
| 434 | + <groupId>com.google.protobuf</groupId> |
| 435 | + <artifactId>protobuf-java</artifactId> |
| 436 | + <version>3.25.5</version> |
| 437 | + </dependency> |
| 438 | + </dependencies> |
| 439 | + </dependencyManagement> |
| 440 | + |
416 | 441 | <dependencies> |
417 | 442 | <dependency> |
418 | 443 | <groupId>org.apache.hadoop</groupId> |
|
427 | 452 | <groupId>javax.enterprise</groupId> |
428 | 453 | <artifactId>cdi-api</artifactId> |
429 | 454 | </exclusion> |
| 455 | + <!-- Exclude protobuf-java 2.5.0 --> |
| 456 | + <exclusion> |
| 457 | + <groupId>com.google.protobuf</groupId> |
| 458 | + <artifactId>protobuf-java</artifactId> |
| 459 | + </exclusion> |
430 | 460 | </exclusions> |
431 | 461 | </dependency> |
432 | | - <dependency> |
433 | | - <groupId>org.apache.hadoop</groupId> |
434 | | - <artifactId>hadoop-common</artifactId> |
435 | | - <scope>test</scope> |
436 | | - <type>test-jar</type> |
437 | | - </dependency> |
438 | 462 | <dependency> |
439 | 463 | <groupId>org.assertj</groupId> |
440 | 464 | <artifactId>assertj-core</artifactId> |
|
458 | 482 | <dependency> |
459 | 483 | <groupId>com.google.cloud</groupId> |
460 | 484 | <artifactId>google-cloud-storage</artifactId> |
| 485 | + </dependency> |
| 486 | + <dependency> |
| 487 | + <groupId>org.junit.jupiter</groupId> |
| 488 | + <artifactId>junit-jupiter-api</artifactId> |
| 489 | + <scope>test</scope> |
461 | 490 | </dependency> |
462 | 491 | <dependency> |
463 | | - <groupId>com.google.protobuf</groupId> |
464 | | - <artifactId>protobuf-java</artifactId> |
465 | | - <!-- |
466 | | - We're using a specific Protobuf version to ensure compatibility with the |
467 | | - Google Cloud Storage (GCS) client. The GCS client often relies on |
468 | | - particular Long-Term Support (LTS) versions of Protobuf. When we upgrade |
469 | | - the GCS client, we'll likely need to update Protobuf too. To prevent |
470 | | - dependency conflicts, Protobuf will be shaded within the GCS connector's |
471 | | - fat JAR. |
472 | | - --> |
473 | | - <version>3.25.3</version> |
| 492 | + <groupId>org.junit.jupiter</groupId> |
| 493 | + <artifactId>junit-jupiter-engine</artifactId> |
| 494 | + <scope>test</scope> |
| 495 | + </dependency> |
| 496 | + <dependency> |
| 497 | + <groupId>org.junit.jupiter</groupId> |
| 498 | + <artifactId>junit-jupiter-params</artifactId> |
| 499 | + <scope>test</scope> |
474 | 500 | </dependency> |
475 | | - |
476 | 501 | </dependencies> |
477 | 502 | </project> |
478 | 503 |
|
0 commit comments