On Wed, Jan 26, 2011 at 9:22 AM, Lukas Theussl <ltheu...@apache.org> wrote:

>
> Dennis Lundberg wrote:
>
>> Hi
>>
>> On Wed, Jan 26, 2011 at 2:15 AM, Benjamin Bentmann<
>> benjamin.bentm...@udo.edu>  wrote:
>>
>>  Dennis Lundberg wrote:
>>>
>>>  Staging repo:
>>>
>>>> https://repository.apache.org/content/repositories/maven-072/
>>>>
>>>> Staging site:
>>>> http://maven.apache.org/plugins/maven-changes-plugin-2.4/
>>>>
>>>>
>>> +1
>>>
>>> Not sure whether this is expected from the staging site but the links
>>> "changes.xml" and "changes.xsd" below the "Reference" menu in the left
>>> nav
>>> bar yield 404s.
>>>
>>>
>> A quick check tells me that the same problem can be found on the 2.3
>> staging
>> site as well, but both files are available (with the correct date) on the
>> last production site deploy. So we should be OK for the final site deploy,
>> but I'll have a closer look tonight to see if I can fix it for staging as
>> well.
>>
>
> The modello-plugin runs in the pre-site phase, but I suppose you just used
> the (documented) site:stage-deploy goal without running 'site' first, so the
> xsd was not generated.


Yes, that's right. The documented release procedure for staging a plugins
site is not correct. When deploying the real site, this is not a problem.


> This will be no issue in site-plugin-2.3, see
> http://jira.codehaus.org/browse/MSITE-533.
>

Unitl that is released and used, the workaround is to run 'mvn site' prior
to running 'mvn site:stage-deploy -Preporting'



>
> Cheers,
> -Lukas
>
>
>
>
>>
>>
>>>
>>> Benjamin
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>>>
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Dennis Lundberg

Reply via email to