Rename extension, update assets & documentation
celanthe opened this issue · 12 comments
Hi Patrick and Jan,
I hope today finds you well! This issue is being opened to ask if you would be open to renaming your extension on GitHub to reference Camunda Platform 7 rather than Camunda BPM after its release on April 12th, 2022. (For example: camunda-platform-7-graphql) This change will also likely impact any screenshots you have in the README that reference Camunda BPM or previous versions of Camunda Platform, and this will likely need to also be updated throughout the repo's documentation as a whole. You can also make use of Shields.io badges to indicate which version of Camunda your extension is compatible with.
While it is not a requirement that you rename your extension to align with Camunda Platform 7, we would greatly appreciate it if you could make these changes, and merge them anytime after April 12th, 2022.
if you have any questions or require any assistance, please do not hesitate to reach out to @camunda-community-hub/devrel! :)
I went to add  but didn't quite understand the structure in the README.
@jangalinski @pschalk please update this project when you get a chance. Thanks!
@celanthe changes are now on master, can you please also rename the repository itself?
And build is currently failing:
Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.8:deploy (default-deploy) on project camunda-platform-7-custom-batch-example-simple-spring-boot: Failed to deploy artifacts: Could not transfer artifact org.camunda.community.batch:camunda-platform-7-custom-batch-example-root:pom:1.6.0-20220429.110903-1 from/to camunda-nexus (https://artifacts.camunda.com/artifactory/camunda-platform-7-community-extensions-snapshots/): transfer failed for https://artifacts.camunda.com/artifactory/camunda-platform-7-community-extensions-snapshots/org/camunda/community/batch/camunda-platform-7-custom-batch-example-root/1.6.0-SNAPSHOT/camunda-platform-7-custom-batch-example-root-1.6.0-20220429.110903-1.pom, status: 405 Method Not Allowed -> [Help 1]
@camunda-community-hub/devrel looking for assistance here
@pschalk what would you like the repo name to be? camunda-platform-7-custom-batch?
Yes, to "camunda-platform-7-custom-batch"
I renamed the repo but still need to check the build problem - not sure if I will find the time this week - but I will try
Fixed by bcb17a1 - build is working now
@pschalk I just assumed this issue is closed now - feel free to reopen if not true (then: sorry ;-))
Many thanks @berndruecker :)
@berndruecker hm, do you know why the artifacts get not pushed into the mvn central artifactory like in the past?
=> https://mvnrepository.com/search?q=org.camunda.community.batch
Thy just appear in the camunda jfrog artifactory:
=> https://artifacts.camunda.com/ui/packages/gav:%2F%2Forg.camunda.community.batch:camunda-platform-7-custom-batch-core/1.6.0?name=camunda-platform-7-custom-batch-core&type=packages&activeTab=builds
Hi @pschalk: I did release it yesterday and it looks OK in the Sonatype Nexus. So I guess this is a timing issue and we need to wait a bit for the artifact to be discoverable...
Your right, now it's there. :)