-
Notifications
You must be signed in to change notification settings - Fork 7
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
chore(#346): rename maven group names digiwf-connector #544
Conversation
name: build services | ||
|
||
on: [ push, pull_request ] | ||
|
||
jobs: | ||
build-maven: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v3 | ||
- name: Set up JDK 11 | ||
uses: actions/setup-java@v3 | ||
with: | ||
java-version: '11' | ||
distribution: 'adopt' | ||
server-id: camunda-bpm-nexus-ee | ||
server-username: CAMUNDA_USER_REF | ||
server-password: CAMUNDA_TOKEN_REF | ||
|
||
- name: Build with Maven | ||
run: mvn --batch-mode --update-snapshots --no-transfer-progress verify -f pom-old.xml | ||
env: | ||
CAMUNDA_USER_REF: ${{ secrets.CAMUNDA_USER }} | ||
CAMUNDA_TOKEN_REF: ${{ secrets.CAMUNDA_USER_PASSWORD }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Den Workflow musst du nicht anpassen - Siehe POM Kommentar
<modules> | ||
<module>digiwf-engine</module> | ||
<module>digiwf-connector</module> | ||
<module>digiwf-schema-registry</module> | ||
<module>digiwf-task</module> | ||
<module>digiwf-libs</module> | ||
<module>digiwf-process</module> | ||
<module>digiwf-gateway</module> | ||
<module>digiwf-integrations</module> | ||
<module>digiwf-coverage</module> | ||
</modules> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Genau dieser Teil muss komplett raus. Das ist die Aggregation und kann eigenständig in einer POM gelöst sein.
Dann hat man zwei weitere POMs, die nur als Parent dienen mit den unterschiedlichen groupIDs, aber alle Module weiterhin in der Aggregation-POM zusammen gebaut über einen Befehl
Ich mache den PR nochmal zu und einen neuen auf, das geht einfacher |
Description
Short description or comments
Reference
Issues #346