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

chore: publish to maven central with gradle #122

Merged
merged 4 commits into from
Feb 20, 2023

Conversation

manikmagar
Copy link
Contributor

Removing JReleaser until a sample project is published successfully. Using Gradle publishing configuration to publish artifacts to maven central.

1.0.1-SNAPSHOT was published to Sonatype during workflow testing.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 20, 2023

Unit Test Results

202 tests  ±0   202 ✔️ ±0   10s ⏱️ -1s
  46 suites ±0       0 💤 ±0 
  46 files   ±0       0 ±0 

Results for commit e6bb8ef. ± Comparison against base commit 1ba09e7.

♻️ This comment has been updated with latest results.

@manikmagar manikmagar merged commit f1e260e into master Feb 20, 2023
@manikmagar manikmagar deleted the chore/maven-central-deploy branch February 20, 2023 14:29
@aalmiray
Copy link

May I ask what happened at https://github.com/avioconsulting/mule-linter/actions/runs/4009022238/jobs/6883889673? Sadly the trace.log was not saved thus can't tell exactly what caused the problem when creating a stating repository in Nexus.

@manikmagar
Copy link
Contributor Author

My bad, I missed saving the trace.log. For another sample project, I was getting below error in the log -

Caused by: java.lang.IllegalStateException: repository comavioconsulting-1026 is not in expected state(s). Expected one of [RELEASED, NOT_FOUND], actual is CLOSED
	at jreleaser.shadow.org.jreleaser.sdk.nexus2.Nexus2.waitForState(Nexus2.java:195)
	at jreleaser.shadow.org.jreleaser.sdk.nexus2.Nexus2.lambda$releaseStagingRepository$7(Nexus2.java:171)
	at jreleaser.shadow.org.jreleaser.sdk.nexus2.Nexus2.wrap(Nexus2.java:258)
	... 27 more

I might have assumed the same issue here and just stopped looking further. Surprisingly, the sample project and the same pipeline on linter worked. Another PR #127 related to that :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants