hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-7593) [site] Adjustments to suit our new publishing process
Date Thu, 17 Jan 2013 05:10:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-7593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555866#comment-13555866

stack commented on HBASE-7593:

bq. What's with the tmp file path? Shouldn't think be something like 'http://hbase.apache.org'?

Maven has to have something for the url it seems.  The url used to be where we wanted to deploy
our site.  Now we deploy our site by checking it to a "special" directory and then this special
directory is checked out automatically for us under apache servers (infrastructure required
all projects change how their sites are built, this svn pubsub or else move over to using
the apache cms system for all site content).  So this url is of no use to us anymore.

It is purportedly used when you do site:deploy and site:stage.  I don't want to do site:deploy
anymore because we no longer push it out to above cited url.  site:stage you would think would
have no need for this deploy url given it takes a stagingDirectory param and even though it
has an explicit skipDeploy flag which you would think would have this goal ignore this url
spec, but it does not.

We need to put something in to this url though we no longer use it.  Hence /tmp, a harmless
space holder.  Let me add a note to the pom.

bq. ...but I believe there are hooks allowing you to tie execution of one goal to a lifecycle
phase of another.

True.  Javadoc build is a little complicated.  There is the javadoc generation per maven module
and then you need to call the aggregate goal so all the javadoc is squashed together up at
the parent project level.  We then want to copy the assembled javadoc into the site directory
so it can be part of site.

The assemble goal and the javadoc copy goal are set to trigger on the pre-site lifecycle....
and you guessed it, the javadoc copy runs just ahead of the assemble goal so the copy fails.
 I do not know of a way to jigger the order in which plugins run (in the pom they are ordered
as we want them to run but taking a guess, it seems to be running alphabetically).

I should have supplied this detail earlier.  Didn't think anyone was interested.  Good on
you Nick.

> [site] Adjustments to suit our new publishing process
> -----------------------------------------------------
>                 Key: HBASE-7593
>                 URL: https://issues.apache.org/jira/browse/HBASE-7593
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>         Attachments: site.txt

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message