Hi Angela, In order to help you and resolve the issues you need to share the errors you are facing together with the Java version and OS you are using. Preferably as a JIRA issue. In general I think it makes sense to already build javadoc during CI builds to detect those issues earlier.
Thanks, Konrad > On 28. Oct 2022, at 09:29, Angela Schreiber <[email protected]> wrote: > > Hi > > Yesterday I aimed to release org.apache.sling.feature.cpconverter 1.1.22. > However, the release process failed during mvn release:preform due to javadoc > errors. > > Surprisingly, it reported errors for classes I most definitely have released > before. > > Could that be due to the latest parent.pom 49 (it was updated on August 18 > 2022? > > I reverted the commits from the prepare phase in order not to leave a > half-way done release behind. Carsten Ziegeler<mailto:[email protected]>, > since you managed to release the module a few days ago, would you be able to > help me out and release it again? > > In the long run it would be preferrable if everyone could cut releases > without having to worry about javadoc issues that have been present for years. > > Kind regards > Angela > >
