Unfortunately AFAIK we have to have a successful local install before the site goal will work. That's even what we end up doing when building the website:
https://github.com/apache/hbase/blob/master/dev-support/jenkins-scripts/generate-hbase-website.sh#L169 On the plus side, there's a maven profile you can activate to make it so that first maven install command does as little work as possible. The answer to the "why is this dependency needed?" is also in the comments of that script: the javadoc plugin insists on forking an entire additional build that needs test scoped dependencies. On Mon, Nov 19, 2018 at 6:16 PM Zach York <[email protected]> wrote: > > Hey All, > > I was recently trying to build a HBase RC using Apache Bigtop (In my setup > it's easier to have it build with bigtop to test on cluster) and I ran into > a rather curious error. The build was failing because it was trying to > download the hbase-annotations:test jar from maven central instead of > locally. This is only an issue when building with Bigtop or building with > the site option (mvn install site). I did a bit of research and it seems > like it is due to the fact that maven executes both goals in order for each > module instead of completely executing one goal before the other. Obviously > I can remove the site option from the build command, but that causes a > whole bunch of other errors since the spec files expect the docs to be > present. > > So my question is whether we can improve this or is the best I can do to > run the install and site as two separate commands? What does site need from > the annotations test jar? > > I understand that this is a bit of an edge case, but since it is used by > Apache Bigtop, it would be nice to improve it. > > Thanks, > Zach
