Replies: 2 comments 2 replies
-
Have you tried configuring |
Beta Was this translation helpful? Give feedback.
0 replies
-
Seems like I've missed that option. Using: <artifactOverride>
<groupId>org.mapstruct</groupId>
<artifactId>mapstruct-jdk8</artifactId>
<sourceJar>false</sourceJar>
<javadocJar>false</javadocJar>
</artifactOverride> works great. Thanks @aalmiray. Should we close this or do you think that supporting relocation artifacts is something that JReleaser (I guess this is https://github.com/kordamp/pomchecker) should support? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been trying to setup JReleaser for MapStruct. However, I hit some hurdles. I've used Moditect as an inspiration for setting it up.
There seems to be an issue with the Maven Deployer validation. In MapStruct we have an artifact that has been relocated. i.e. it has:
This artifact does not have any javadoc or sources attached to it. This Maven Central allows deploying such an artifact.
Task List
Steps to Reproduce
./mvnw -ntp -B --file pom.xml -Ppublication,stage -Dmaven.site.skip=true -Drelease=true
./mvnw -ntp -B --file pom.xml -pl :mapstruct-parent -Pjreleaser jreleaser:release -Djreleaser.dry.run=true
Expected Behaviour
The maven central verification does not fail.
Actual Behaviour
The maven central verification fails due to missing javadoc and sources artifacts
Environment Information
Beta Was this translation helpful? Give feedback.
All reactions