René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[chore] Move Javadoc failures away from end-to-end test phase","articleBody":"Moved from https://github.com/gojek/feast/pull/407#issuecomment-570924534\r\n\r\nCurrently the maven-javadoc-plugin is bound to the `jar` goal, so it triggers when end-to-end tests run `mvn package`.\r\n\r\nAn end-to-end test phase is a frustrating time to fail on malformatted Javadoc… (and generating them is a bit of a waste of time outside of release preparation). Perhaps we can do something like:\r\n\r\n1. For tests, run `mvn package` with `-Dmaven.javadoc.skip`\r\n1. Worry about Javadoc cleanup at release preparation time, automated in a release build\r\n\r\nOr if you'd like for contributors to maintain error-free Javadoc proactively:\r\n\r\n1. Run some type of Coding Standards check early in PR build steps, including invoking a goal from the Javadoc plugin\r\n1. For tests, run `mvn package` with `-Dmaven.javadoc.skip`\r\n\r\nJavadoc skip could be enabled by default in the root build, and disabled in a release profile.","author":{"url":"https://github.com/ches","@type":"Person","name":"ches"},"datePublished":"2020-01-05T16:44:16.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/408/feast/issues/408"}