On 8 September 2011 10:54, Simone Tripodi <simonetrip...@apache.org> wrote:
> HA! gotcha!
> the <distributionManagement> section is missing in the Configuration
> pom, what you need is adding
>
>  <distributionManagement>
>    <!-- Cannot define in parent ATM, see COMMONSSITE-26 -->
>    <site>
>      <id>people.apache.org</id>

The "standard" name is apache.website, according to COMMONSSITE-26,
but it does not matter too much.

>      <name>Apache Commons Site</name>
>      
> <url>${commons.deployment.protocol}://people.apache.org/www/commons.apache.org/configuration</url>
>    </site>
>  </distributionManagement>

Perhaps we should add an example section to Commons Parent, but
commented out, and a note to say it should be included in component
POMs?

> and run
>
>    mvn site-deploy -Dcommons.deployment.protocol=scp
>
> I preferred creating an 'apache' profile in my ~/.m2/settings.xml
> where I defined all the properties related to ASF projects:
>
>    <profiles>
>        <profile>
>            <id>apache</id>
>            <activation>
>                <activeByDefault>false</activeByDefault>
>            </activation>
>            <properties>
>                <commons.deployment.protocol>scp</commons.deployment.protocol>
>                <mavenExecutorId>forked-path</mavenExecutorId>
>                <gpg.keyname>19FEA27D</gpg.keyname>
>            </properties>
>        </profile>
>    </profile>
>
> So when I deploy the site I run
>
>    mvn sote-deploy -P apache
>

s/sote/site/

> Hope that helps, alles gute! :)
> Simo
>
> http://people.apache.org/~simonetripodi/
> http://www.99soft.org/
>
>
>
> On Thu, Sep 8, 2011 at 11:07 AM, Oliver Heger
> <oliver.he...@oliver-heger.de> wrote:
>> Hi Simone,
>>
>> many thanks for your support, but there seems to be a different problem. I
>> did run mvn site:site before. Obviously maven does not know where to deploy
>> the site.
>>
>> Well, it is possible to copy the site per hand to its location at
>> people.apache.org. I was also able to adapt the distribution-management
>> section of commons-vfs as proposed by Ralph.
>>
>> But I wonder why there are no default settings for all components. Did the
>> components you were working on define their specific distribution-management
>> section?
>>
>> Tante grazie
>> Oliver
>>
>> Am 07.09.2011 22:25, schrieb Simone Tripodi:
>>>
>>> Hi Oliver!
>>> AFAIK mvn site:deploy has effect only once ran site:site, so the right
>>> way to publish a site is
>>>
>>>     mvn site:site site:deploy
>>>
>>> I used to run the shortcut
>>>
>>>     mvn site-deploy
>>>
>>> At least is how it worked for sites I deployed.
>>> HTH, alles gute!
>>> Simo
>>>
>>> http://people.apache.org/~simonetripodi/
>>> http://www.99soft.org/
>>>
>>>
>>>
>>> On Wed, Sep 7, 2011 at 10:12 PM, Oliver Heger
>>> <oliver.he...@oliver-heger.de>  wrote:
>>>>
>>>> This may be a dump question, but I have trouble with deploying the site
>>>> for
>>>> configuration.
>>>>
>>>> According to [1] a mvn site:deploy should be sufficient to do the job.
>>>> However, maven complains that there are no site information in the
>>>> distribution management element.
>>>>
>>>> Well, this is true for the pom of configuration and also for other
>>>> components. I thought that this information would already be provided by
>>>> the
>>>> parent pom, no? What am I missing?
>>>>
>>>> TIA
>>>> Oliver
>>>>
>>>> [1] http://commons.apache.org/releases/publish-site.html
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to