Hi Jon, I think you could use the verifier-plugin for checking file existence.
https://maven.apache.org/plugins/maven-verifier-plugin/verify-mojo.html Am So., 2. Feb. 2020 um 17:55 Uhr schrieb Jon Harper <jon.harpe...@gmail.com>: > > Hi list, > > I would like to use maven-enforcer-plugin to ensure that javadocs are > attached in release mode before installing. That's because I use > $ mvn package javadoc:aggregate-jar deploy > to build, so if someone forgets to call the aggregate-jar goal, the > release will be missing the javadoc. > > I don't see any rule to enforce this (the closest I found is > https://github.com/elastic/attached-artifact-enforcer which does the > opposite, ensure that something is not attached). > > Is it possible to do what I want using the standard rules ? If not, > would you consider to add new rules for this ? > > Thanks, > Jon > > Note: I need to use javadoc:aggregate-jar on the command line and not > part of the lifecycle because: > - I want the aggregated javadoc to be attached to the root pom > artifact, not some child "distribution"-like artifact > - I want the aggregated javadoc to be created after the submodules > have been built. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
