Skip to content

Conversation

@rpanackal
Copy link
Member

@rpanackal rpanackal commented Jan 27, 2026

Context

SAP/cloud-sdk-java-backlog##464

Fix scope:

  • Introduce a new module without spring in dependency tree
    • Move all apache specific code and tests out
  • Modify template to fix imports
  • Apply in openapi-api-apache-sample

Definition of Done

  • Functionality scope stated & covered
  • Tests cover the scope above
  • Error handling created / updated & covered by the tests above
  • Documentation updated
  • Release notes updated

@rpanackal rpanackal added the please review Request to review a pull request label Jan 27, 2026
@rpanackal
Copy link
Member Author

rpanackal commented Jan 27, 2026

What consequence does this additional module for the sake of spring optionality have ?

Surely, the import namespace will be affected. Apart from that the bigger concern is new duplicated classes.

  • RFC3339DateFormat (package-private)
  • OpenApiRequestException - will include in the list of breaking changes in AI SDK on migration to apache client

@rpanackal rpanackal self-assigned this Jan 27, 2026
Copy link
Contributor

@CharlesDuboisSAP CharlesDuboisSAP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are still changes in openapi-core and openapi-generator compared to before your first Apache PR. Ideally there are no changes

*/

package com.sap.cloud.sdk.services.openapi.apache;
package com.sap.cloud.sdk.services.openapi.apache.apiclient;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Question/Major)

This is a breaking change for users that may have depended on the new classes, right?
Is this an accepted risk?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

please review Request to review a pull request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants