neo4j/5.26.0 package update

[octo-sts]

[octo-sts]

Gen AI suggestions to solve the build error:

• Detected Error: tar: can't open 'packaging/standalone/target/neo4j-*.tar.gz': No such file or directory

• Error Category: Build

• Failure Point: The final packaging step after Maven build when trying to extract the tar.gz artifact

• Root Cause Analysis: The Maven build appears to have warnings but completed, however the expected neo4j-*.tar.gz artifact was not generated in the expected location. This suggests the Maven build may have silently failed to produce the distribution archive.

• Suggested Fix:

1. Modify the Maven command to explicitly build the distribution:

pipeline:
  - runs: |
      export LANG=en_US.UTF-8
      mvn package -DskipTests=true -T$(nproc)C -q -P deployment-only

2. Add explicit error checking:

  - runs: |
      export LANG=en_US.UTF-8
      mvn package -DskipTests=true -T$(nproc)C -q -P deployment-only
      
      if [ ! -f packaging/standalone/target/neo4j-*.tar.gz ]; then
        echo "Distribution archive not found"
        exit 1
      fi

• Explanation:

• The -P deployment-only profile explicitly enables Neo4j's distribution packaging
• The default build may skip distribution assembly without the profile
• Adding error checking makes build failures more obvious

• Additional Notes:

• The XStream and Scala warnings are not causing the failure
• The tar command fails because the previous steps didn't produce the expected artifact
• Consider adding -B to Maven command to run in non-interactive mode
• May want to add -Dquiet=true to reduce Maven output spam

• References:

• Neo4j Build Docs: https://neo4j.com/docs/operations-manual/current/installation/
• Maven Profile Docs: https://maven.apache.org/guides/introduction/introduction-to-profiles.html

[octo-sts]

Gen AI suggestions to solve the build error:

Based on the build error output, I'll analyze and provide a solution:

• Detected Error: tar: can't open 'packaging/standalone/target/neo4j-*.tar.gz': No such file or directory

• Error Category: Build

• Failure Point: Final packaging step in the pipeline where it attempts to extract the built Neo4j tarball

• Root Cause Analysis: The Maven build appears to complete (with warnings) but the expected Neo4j tarball was not generated in the expected location. This suggests the Maven build target for the standalone package was not properly executed.

• Suggested Fix:

pipeline:
  - uses: git-checkout
    with:
      repository: https://github.com/neo4j/neo4j
      tag: ${{package.version}}
      expected-commit: 17dc7f7e1787c451938b97666a06afd3695987ca

  - uses: maven/pombump

  - runs: |
      export LANG=en_US.UTF-8
      
      # Build the standalone distribution specifically
      mvn package -DskipTests=true -T$(nproc)C -q -pl packaging/standalone -am
      
      mkdir -p ${{targets.destdir}}/usr/share/java/neo4j
      
      tar --strip-components=1 -xf packaging/standalone/target/neo4j-community-${{package.version}}-unix.tar.gz -C ${{targets.destdir}}/usr/share/java/neo4j
      
      mkdir -p ${{targets.destdir}}/usr/bin
      for i in neo4j neo4j-admin cypershell; do
        ln -sf /usr/share/java/neo4j/bin/$i ${{targets.destdir}}/usr/bin/$i
      done

• Explanation:

1. The original build wasn't specifically targeting the standalone package
2. The fix explicitly builds the standalone module and its dependencies
3. The tarball name has been made more specific to match Neo4j's actual output format
4. The -pl flag targets the specific module while -am builds dependent modules

• Additional Notes:

• The XStream and Scala warnings in the build output are not causing the failure
• The core issue is the missing tarball artifact
• Maven multi-module projects often need explicit module targeting for specific artifacts
• The community edition tarball naming convention is used since this appears to be the community version

• References:

• Neo4j Build Documentation: https://neo4j.com/docs/operations-manual/current/installation/
• Maven Module Build Guide: https://maven.apache.org/guides/mini/guide-multiple-modules.html

[developer-guy]

kudos @debasishbsws, thanks for fixing the issue!!!!!