>>>>> Steinar Bang <s...@dod.no>: > Tried again to remove source attachments and javadoc attachments and > that made "mvn release:prepare" run without errors.
> However, "mvn release:perform" failed, and it looks like maven central > rejected the deploy because there was no source jars or javadoc jars > attached to the artifacts. > > https://gist.github.com/steinarb/d0fb744fd7c512a86efb2ed926b87caf#file-gistfile1-txt-L335 > Hm... what to do...? I put the source attachment config back, but "mvn release:prepare" failed. However, source jars turned out to be easy to fix. I just added <phase>verify</phase> as indicated in the attach source example: https://maven.apache.org/plugins/maven-source-plugin/usage.html This made "mvn release:prepare" run without errors, but "mvn release:perform" because maven central refuses jar artifacts without attached javadoc jars: https://gist.github.com/steinarb/f1f7aa4fa8b503ff1ece8be0afb18054 So I put the javadoc generation config back, and "mvn release:prepare" stopped working again. I have tried the following: 1. Remove the aggregate javadoc 2. Go back from javadoc-no-fork to javadoc as the execution goal 3. Put javadoc attachment in the <verify> phase But all of them fails in "mvn release:prepare". Unfortunately, unlike the maven-source-plugin, the maven-javadoc-plugin documentation doesn't contain a config example for creating javadoc attachments https://maven.apache.org/plugins/maven-javadoc-plugin/ Neither has google been able to serve up a maven-javadoc-plugin config that would work. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
