It appeared to have worked. Thank you again, Hervé.
The site is in place now, where it should be
http://maven.apache.org/plugins-archives/plugin-testing-archives/LATEST
--
Regards,
Igor
On 12/7/2013, 9:33, Hervé BOUTEMY wrote:
no, your changes were properly staged in r889475 (from websites repository)
you can see the result at http://maven.staging.apache.org/extpaths.txt
and it will be published in production site as soon as you "CMS publish" the
site (see
[2])
notice that the publication may fail since extpaths.txt actually refers to
/plugin-
testing-archives that does not exist yet (or "any more", depends on your point
of
view)
before "SCM publishing", you'll need to (re)create /plugin-testing-archives
I just did it for you with following command: "svn cp
https://svn.apache.org/repos/infra/websites/production/maven/content/plugin-testing-archives@889111
https://svn.apache.org/repos/infra/websites/production/maven/content/";
I let you enjoy next CMS publication, to see that
http://maven.apache.org/plugin-testing-archives is available both before and
after the publication.
Regards,
Hervé
[2] http://maven.staging.apache.org/developers/website/deploy-maven-website.html
Le samedi 7 décembre 2013 08:12:49 Igor Fedorenko a écrit :
How do I make changes to extpaths.txt? My changes to svn [1] got
overwritten during site deploy as far as I can tell.
[1] http://svn.apache.org/viewvc?view=revision&revision=r1548906
--
Regards,
Igor
On 12/7/2013, 1:10, Hervé BOUTEMY wrote:
plugin-testing-archives is not in extpaths.txt [1]
than any deployment of the main site will remove what you deployed
you need to add an entry, then either redeploy content or remember the
revision of the previous deployment to cp the revision to actual trunk
tell me if you need me to help (no time to do it for the moment, but I
should be able to do it a little bit later)
Regards,
Hervé
[1] http://maven.apache.org/extpaths.txt
Le vendredi 6 décembre 2013 17:40:31 Igor Fedorenko a écrit :
I don't know what happened to the documentation site.
It worked earlier today. I still have
~/maven-sites/plugin-testing-archives/LATEST with svn info pointing at
https://svn.apache.org/repos/infra/websites/production/maven/content/plug
in-> testing-archives/LATEST but that svn is not there any more.
I did have to do "svn mkdir" to create that svn directory. I wonder if
somebody or something deleted it.
Can somebody with understanding of maven site publishing double-check
maven plugin testing is setup properly?
--
Regards,
Igor
On 12/6/2013, 16:15, Mirko Friedenhagen wrote:
+0.9 (non-binding). As before:
* Checked SHA1 of maven-plugin-testing-3.0.0-source-release.zip
* Ran "mvn -V verify" on Mac OS X 10.9:
* JDK 1.6.0_51, Maven 3.0.5 and Maven 3.1.1
* JDK 1.7.0_45, Maven 3.0.5 and Maven 3.1.1
* JDK 1.8.0-ea, Maven 3.0.5 and Maven 3.1.1
However, for me,
http://maven.apache.org/plugin-testing-archives/LATEST leads to a 404
(Page Not Found).
Regards
Mirko
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Fri, Dec 6, 2013 at 2:11 PM, Igor Fedorenko <[email protected]>
wrote:
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740&versio
n=
18839
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MPLUGINTESTING%20A
ND
%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
Staging repo:
https://repository.apache.org/content/repositories/maven-017/
https://repository.apache.org/content/repositories/maven-017/org/apache
/m
aven/plugin-testing/maven-plugin-testing/3.0.0/maven-plugin-testing-3.0
.0
-source-release.zip
Source release checksum(s):
SHA1(maven-plugin-testing-3.0.0-source-release.zip)=
126853d4e5f29fedbd173305fe9e0a00407699e8
Staging site:
http://maven.apache.org/plugins-archives/plugin-testing-archives/LATEST
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
