+1
21. jun. 2015 21.14 skrev "Tibor Digana" :
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12331401
>
> There is still one issue left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resol
Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12331401
There is still one issue left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-verifi
> Maybe CMS commits in SVN on the same in the
> background, but if it does then I can do the same in svn even better.
yes
> Ideas?
I tried to explain it in a simple way and with a figure in
http://maven.apache.org/developers/website/deploy-maven-website.html
the main thing is to understand that t
Karl,
Done.
The steps reflected my changes immediately on public page
http://maven.apache.org/shared/
No more waiting one day for CMS job. Thanks.
The only question, for next time release, is what happened after I went
through https://cms.apache.org/maven/publish
1. Did the publish take successf
Hi Tibor,
On 6/20/15 11:07 PM, Tibor Digana wrote:
I updated CMS page http://maven.apache.org/shared/
Hm...neiter the staging site (http://maven.staging.apache.org/shared/)
nor the original site http://maven.apache.org/shared/ show a change...
> Can you show me what you updated, maybe I sho
