Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: mhiew/PdfiumAndroid
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: BlueCodeSystems/PdfiumAndroid
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 6 commits
  • 11 files changed
  • 1 contributor

Commits on Sep 6, 2025

  1. build: migrate to Gradle 8/AGP 8, modernize SDK/NDK config, and add M…

    …aven Central publishing
    
    WHAT
    - Upgrade Gradle wrapper to 8.7 and Android Gradle Plugin to 8.6.0.
    - Migrate Android config: add namespace, set compileSdk/targetSdk 35, minSdk 28, enable BuildConfig, and Java 8 compatibility.
    - Switch to externalNativeBuild (ndkBuild) and adjust NDK settings; remove manifest package and prebuilt libc++_shared; add linker max page size flag.
    - Add publishing setup via maven-publish, signing, and Nexus staging; read coordinates from gradle.properties; enable sources/javadoc jars and release packaging task.
    - Configure JitPack to use JDK 17 and install required Android SDK/NDK components.
    
    WHY
    - AGP 8/Gradle 8 require Java 17 and current SDKs; updates keep the library compatible with modern Android toolchains.
    - Namespace migration and manifest cleanup align with AGP requirements and avoid duplicate package declarations.
    - NDK/ld flags ensure stable native builds and address large-page alignment issues.
    - Maven Central publishing simplifies releasing artifacts, with coordinates and metadata centralized in gradle.properties.
    - JitPack config ensures CI builds succeed under the newer toolchain.
    AndreLesa committed Sep 6, 2025
    Configuration menu
    Copy the full SHA
    cf6bd79 View commit details
    Browse the repository at this point in the history
  2. build(publish): add central-bundle.sh and document manual Maven Centr…

    …al bundle
    
    WHAT
    - Add scripts/central-bundle.sh to build, sign, checksum, and zip a Central-ready bundle using Gradle (no remote publish).
    - Update README with usage instructions, requirements, and output location.
    
    WHY
    - Provides a consistent, repeatable way to prepare artifacts for manual upload to Sonatype Central Portal when not using automated publishing.
    - Clarifies project release workflow and reduces human error during releases.
    AndreLesa committed Sep 6, 2025
    Configuration menu
    Copy the full SHA
    8115769 View commit details
    Browse the repository at this point in the history
  3. ci: JitPack publish to Maven Local, set GROUP, skip signing

    - Publish to Maven Local in JitPack so POM/artifacts are discoverable
    - Derive GROUP from repo owner in jitpack.yml; default GROUP set to com.github.BlueCodeSystems
    - Skip signing on JitPack via -PskipSigning=true; make signing optional in maven.gradle
    - Update README coordinates to com.github.BlueCodeSystems
    AndreLesa committed Sep 6, 2025
    Configuration menu
    Copy the full SHA
    eb7ac09 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    c741389 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    82ecdd9 View commit details
    Browse the repository at this point in the history
  6. Update README.md

    AndreLesa authored Sep 6, 2025
    Configuration menu
    Copy the full SHA
    96a0b66 View commit details
    Browse the repository at this point in the history
Loading