Ext version 3.0

[osc-lab]

For your information I remove your file EbicsUploadParams and replace it by EbicsParams that I use for Upload and Fetch documents.

[uwemaurer]

Thank you for your work. Is the change complete already?

• I see in DownloadInitializationRequestElement.java the EbicsParams is added but it seems not used anywhere.
• Why was the record converted to a class? Are you trying to run it on older Java versions?
• I think we don't need the V2 and V3 functions (this library is for V3 only) so just add a method with the new EbicsParam as parameter (no need to mark them as V2 or V3)

[osc-lab]

Dear Uwe

>>see in [ https://github.com/ebics-java/ebics-java-client/pull/42/files#diff-36403ba901a26680d3ae7710e247578771027ad720caba9a20eed49f906bc20d | DownloadInitializationRequestElement.java ] the EbicsParams is added but it seems not used anywhere.

the class is used in FileTransfert line 211 regarding the send/fetchFile<version> it was for separate them but it can be change as you like. De: "Uwe Maurer" ***@***.***> À: "ebics-java/ebics-java-client" ***@***.***> Cc: "osc-lab" ***@***.***>, "Author" ***@***.***> Envoyé: Mercredi 3 Décembre 2025 09:09:50 Objet: Re: [ebics-java/ebics-java-client] Ext version 3.0 (PR #42) uwemaurer left a comment [ #42 (comment) | (ebics-java/ebics-java-client#42) ] Thank you for your work. Is the change complete already? * I see in [ https://github.com/ebics-java/ebics-java-client/pull/42/files#diff-36403ba901a26680d3ae7710e247578771027ad720caba9a20eed49f906bc20d | DownloadInitializationRequestElement.java ] the EbicsParams is added but it seems not used anywhere. * Why was the record converted to a class? Are you trying to run it on older Java versions? * I think we don't need the V2 and V3 functions (this library is for V3 only) so just add a method with the new EbicsParam as parameter (no need to mark them as V2 or V3) — Reply to this email directly, [ #42 (comment) | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AN2AB2RCM3NGG3DP7Z3JKGT372LE5AVCNFSM6AAAAACNZ7MLKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMBVGU3TQMBTHE | unsubscribe ] . You are receiving this because you authored the thread. Message ID: ***@***.***>

[mstohr1975]

Same root cause as on #45/#46: the dependency-submission step runs on fork PRs where the token cannot write dependency graph snapshots (403 "Resource not accessible by integration").

Suggested workflow adjustment in .github/workflows/maven.yml:

jobs:
  build:
    permissions:
      contents: write
    steps:
      # ...
      - name: Update dependency graph
        if: github.event_name == 'push' || github.event.pull_request.head.repo.full_name == github.repository
        uses: advanced-security/maven-dependency-submission-action@571e99aab1055c2e71a1e2309b9691de18d6b7d6

The set-output message is a warning from the action/toolkit version and not the failing cause. The failing cause is the 403 POST to /dependency-graph/snapshots.