Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use aggregation for digiwf-integrations #760

Closed
lmoesle opened this issue Sep 25, 2023 · 1 comment · Fixed by #891
Closed

Use aggregation for digiwf-integrations #760

lmoesle opened this issue Sep 25, 2023 · 1 comment · Fixed by #891

Comments

@lmoesle
Copy link
Contributor

lmoesle commented Sep 25, 2023

We should seperate the digiwf-integrations from the digiwf-core parent using maven aggregation to maintain each integration separately. With this approach we could keep legacy integrations on an older version without migrating them to e.g. Spring Boot 3.

Todo

  • Use maven aggregation for the digiwf-integrations
    • Each integration should be a standalone application
    • We don't have to migrate every integration (especially the legacy ones)
  • Build an digiwf-integration-parent
    • We will keep the parent for further changes after the SB upgrade
@darenegade
Copy link
Member

@StephanStrehlerCGI StephanStrehlerCGI self-assigned this Oct 26, 2023
StephanStrehlerCGI added a commit that referenced this issue Oct 26, 2023
StephanStrehlerCGI added a commit that referenced this issue Oct 26, 2023
* #760: add integration parent module

* #760: clean up integration parent module

* #760: clean up poms
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants