Do you guys think it'd make sense to find site:run to install phase? This way - in theory at least - site will always be executing install first? It might be too small of an issue though which might be totally workarounded with two sequential maven runs.
Cos On Tue, Apr 29, 2014 at 02:54PM, Konstantin Boudnik wrote: > Thank you guys - this is the most responsive community I've seen around! > > On Tue, Apr 29, 2014 at 02:48PM, Andrew Purtell wrote: > > Ah, and if I read to the end ( sorry - sometimes don't do that when annoyed > > - unrelated to this :-) ), then indeed you did clean ~/.m2 and then > > attempted a list of targets including site. > > > > Install jars to the local Maven cache before invoking javadoc or site > > targets. > > > > > > On Tue, Apr 29, 2014 at 2:44 PM, Andrew Purtell <[email protected]> wrote: > > > > > Is this because we frob the Maven versions after rolling the source > > > tarball? See https://hbase.apache.org/book/releasing.html > > > > > > Do 'mvn -DskipTests clean install' first, then something that pulls in > > > javadoc or site targets and you should be fine. My guess is you did that > > > at > > > one point, then moved to a different box or somehow wiped out local 0.98.1 > > > artifacts in your ~/.m2. > > > > > > > > > On Tue, Apr 29, 2014 at 2:38 PM, Konstantin Boudnik > > > <[email protected]>wrote: > > > > > >> This is a bit weird, but since last night I can't build 0.98.1 anymore > > >> because > > >> of the following error: > > >> > > >> [ERROR] Failed to execute goal > > >> org.apache.maven.plugins:maven-site-plugin:3.3:site (default-site) on > > >> project > > >> hbase: failed to get report for > > >> org.apache.maven.plugins:maven-javadoc-plugin: > > >> Failed to execute goal on project hbase-server: Could not resolve > > >> dependencies > > >> for project org.apache.hbase:hbase-server:jar:0.98.1: The following > > >> artifacts > > >> could not be resolved: org.apache.hbase:hbase-common:jar:0.98.1, > > >> org.apache.hbase:hbase-protocol:jar:0.98.1, > > >> org.apache.hbase:hbase-client:jar:0.98.1, > > >> org.apache.hbase:hbase-prefix-tree:jar:0.98.1, > > >> org.apache.hbase:hbase-common:jar:tests:0.98.1, > > >> org.apache.hbase:hbase-hadoop-compat:jar:0.98.1, > > >> org.apache.hbase:hbase-hadoop-compat:jar:tests:0.98.1, > > >> org.apache.hbase:hbase-hadoop2-compat:jar:0.98.1, > > >> org.apache.hbase:hbase-hadoop2-compat:jar:tests:0.98.1: Could not > > >> find > > >> artifact org.apache.hbase:hbase-common:jar:0.98.1 in apache release > > >> (https://repository.apache.org/content/repositories/releases/) -> > > >> [Help 1] > > >> > > >> Naturally, such artifacts aren't available in the aforementioned repo, > > >> because > > >> only *-hadoop1 and *-hadoop2 versions are there. I am using the same > > >> maven > > >> command as before. But even the standard release command > > >> mvn clean install -DskipTests site assembly:single -Prelease > > >> > > >> doesn't work anymore. I am building with clean ~/.m2, if it makes any > > >> difference. Anyone here has a similar experience? > > >> > > >> Thanks in advance, > > >> Cos > > >> > > >> On Tue, Apr 22, 2014 at 07:26PM, Konstantin Boudnik wrote: > > >> > Right, thanks! Also, it moved + plus set of artifacts got changed. No > > >> matter - > > >> > I got the packaging working again, so once HBase has 0.98.2 out of the > > >> door it > > >> > will be right there in Bigtop 0.8.0. Appreciate the help, guys! > > >> > > > >> > Cos > > >> > > > >> > On Tue, Apr 22, 2014 at 04:20PM, Ted Yu wrote: > > >> > > Please use assembly:single > > >> > > > > >> > > See http://hbase.apache.org/book.html#maven.release > > >> > > > > >> > > Cheers > > >> > > > > >> > > > > >> > > On Tue, Apr 22, 2014 at 4:17 PM, Konstantin Boudnik <[email protected]> > > >> wrote: > > >> > > > > >> > > > Guys, > > >> > > > > > >> > > > can anyone point me to the right direction about the tar.gz binary > > >> > > > assembly in > > >> > > > 0.98? When we were building bigtop releases out of 0.94.x we were > > >> expecting > > >> > > > target/hbase*tar.gz to be present. > > >> > > > > > >> > > > It seems the things have changes somewhat 'cause not > > >> assembly:assembly nor > > >> > > > package targets create the tarballs anymore. Am I doing something > > >> wrong? > > >> > > > Sorry > > >> > > > if it has been answered elsewhere... > > >> > > > > > >> > > > -- > > >> > > > Regards, > > >> > > > Cos > > >> > > > > > > > -- > > Best regards, > > > > - Andy > > > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > > (via Tom White)
