Re: Staging the latest documentation and sync...
I didn't check if it is needed or not, I just did what was not obvious you can either test and do the upgrade if you have the problem, or just upgrade to be sure since it is easy Regards, Hervé Le mercredi 11 juillet 2012 08:17:33 Barrie Treloar a écrit : On Wed, Jul 11, 2012 at 7:48 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I did the work on the plugin in r1359931 and prepared the htaccess in r1359934 Thanks. I take it the upgrade m-site-p to 3.1 wasn't needed? I can't see it being specifically being defined so we are just inheriting from maven-parent:21 - 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
Re: Staging the latest documentation and sync...
no stress, the update is easy just: 1. remove m-site-p plugin configuration from m-enforcer-p 's pom.xml 2. add a RedirectMatch rule into .htaccess [1] just after maven-archetype- plugin rule (to sort alphabetically) Et voilà :) The plugin will be staged as a normal module, the redirect rule simply helps people used to find plugins in /plugins/maven-xxx-plugin Notice it could be useful to upgrade m-site-p to 3.1 in enforcer parent pom to benefit from MSITE-602 fix (wrong staging directory...) Regards, Hervé [1] http://svn.apache.org/viewvc/maven/site/trunk/src/site/filtered- resources/.htaccess?revision=1345430view=markup Le mardi 10 juillet 2012 12:37:02 Barrie Treloar a écrit : On Tue, Jul 10, 2012 at 9:51 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: ah ok, I got it it's a specific configuration written in maven-enforcer-plugin [del] IMHO, enforcer should switch. Tell me if you need help. Ahh, my itch was to fix the bug and push a release. I'm not sure if it stretches to upgrading :) but that choice is making me feel guilty, so if you can point me at some documentation and examples then I can at least look at the amount of effort required to ease my soul. - 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
Re: Staging the latest documentation and sync...
I did the work on the plugin in r1359931 and prepared the htaccess in r1359934 Regards, Hervé Le mardi 10 juillet 2012 08:18:54 Hervé BOUTEMY a écrit : no stress, the update is easy just: 1. remove m-site-p plugin configuration from m-enforcer-p 's pom.xml 2. add a RedirectMatch rule into .htaccess [1] just after maven-archetype- plugin rule (to sort alphabetically) Et voilà :) The plugin will be staged as a normal module, the redirect rule simply helps people used to find plugins in /plugins/maven-xxx-plugin Notice it could be useful to upgrade m-site-p to 3.1 in enforcer parent pom to benefit from MSITE-602 fix (wrong staging directory...) Regards, Hervé [1] http://svn.apache.org/viewvc/maven/site/trunk/src/site/filtered- resources/.htaccess?revision=1345430view=markup Le mardi 10 juillet 2012 12:37:02 Barrie Treloar a écrit : On Tue, Jul 10, 2012 at 9:51 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: ah ok, I got it it's a specific configuration written in maven-enforcer-plugin [del] IMHO, enforcer should switch. Tell me if you need help. Ahh, my itch was to fix the bug and push a release. I'm not sure if it stretches to upgrading :) but that choice is making me feel guilty, so if you can point me at some documentation and examples then I can at least look at the amount of effort required to ease my soul. - 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
Re: Staging the latest documentation and sync...
On Wed, Jul 11, 2012 at 7:48 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: I did the work on the plugin in r1359931 and prepared the htaccess in r1359934 Thanks. I take it the upgrade m-site-p to 3.1 wasn't needed? I can't see it being specifically being defined so we are just inheriting from maven-parent:21 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Staging the latest documentation and sync...
Le lundi 9 juillet 2012 10:30:36 Barrie Treloar a écrit : Can someone have a look at the web page http://maven.apache.org/developers/release/maven-plugin-release.html and compare that automated results with the recommended manual steps. From what I can tell the automated steps now put things at /www/maven.apache.org/staging no, there is no staging directory. Where did you get this info? But the manual steps say /www/maven.apache.org/plugins/ yes, that's what's actually used, either with site:stage-deploy or manual scp Regards, Hervé
Re: Staging the latest documentation and sync...
On Tue, Jul 10, 2012 at 6:24 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: From what I can tell the automated steps now put things at /www/maven.apache.org/staging no, there is no staging directory. Where did you get this info? From the command logs.. mvn site site:stage-deploy -Preporting ... INFO] --- maven-site-plugin:3.0:stage-deploy (default-cli) @ maven-enforcer-plugin --- [INFO] Using this server ID for stage deploy: apache.website [INFO] Using this base URL for stage deploy: scp://people.apache.org/www/maven.apache.org/staging [INFO] Parent project loaded from repository: org.apache.maven:maven-parent:pom:21 [INFO] Parent project loaded from repository: org.apache:apache:pom:10 Using private key: /Users/barrie/.ssh/baerr...@apache.org scp://people.apache.org/www/maven.apache.org/staging/ - Session: Opened [INFO] Pushing /Users/barrie/ide/maven/enforcer/target/checkout/maven-enforcer-plugin/target/site [INFO] to scp://people.apache.org/www/maven.apache.org/staging/plugins/maven-enforcer-plugin Executing command: mkdir -p /www/maven.apache.org/staging/plugins/maven-enforcer-plugin Executing command: mkdir -p /www/maven.apache.org/staging/plugins/maven-enforcer-plugin Executing command: scp -t /www/maven.apache.org/staging/plugins/maven-enforcer-plugin/wagon307783794266116250.zip Uploading: plugins/maven-enforcer-plugin/wagon307783794266116250.zip to scp://people.apache.org/www/maven.apache.org/staging/ # Transfer finished. 396475 bytes copied in 11.214 seconds Executing command: cd /www/maven.apache.org/staging/plugins/maven-enforcer-plugin; unzip -q -o wagon307783794266116250.zip; rm -f wagon307783794266116250.zip Executing command: chmod -Rf g+w,a+rX /www/maven.apache.org/staging/ scp://people.apache.org/www/maven.apache.org/staging/ - Session: Disconnecting scp://people.apache.org/www/maven.apache.org/staging/ - Session: Disconnected - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Staging the latest documentation and sync...
ah ok, I got it it's a specific configuration written in maven-enforcer-plugin IIUC, it's a try to handle the case where a project (defining its top level directory) contains a plugin (published in /plugins/), with the question of the staging directory. This is a question common with archetype, surefire, plugin-tools, and scm, for which we looked for a global solution over the last year. The actual consensus (just surefire isn't done yet) is to publish the plugin in the top level directory (no specific m-site-p configuration for the plugin module) and a rewrite rule in site's .htaccess. AFAIK, this will be a prerequisite when we switch to svnpubsub, because svnpubsub would cause hard problems to the enforcer's solution. IMHO, enforcer should switch. Tell me if you need help. Regards, Hervé Le mardi 10 juillet 2012 08:03:24 Barrie Treloar a écrit : On Tue, Jul 10, 2012 at 6:24 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: From what I can tell the automated steps now put things at /www/maven.apache.org/staging no, there is no staging directory. Where did you get this info? From the command logs.. mvn site site:stage-deploy -Preporting ... INFO] --- maven-site-plugin:3.0:stage-deploy (default-cli) @ maven-enforcer-plugin --- [INFO] Using this server ID for stage deploy: apache.website [INFO] Using this base URL for stage deploy: scp://people.apache.org/www/maven.apache.org/staging [INFO] Parent project loaded from repository: org.apache.maven:maven-parent:pom:21 [INFO] Parent project loaded from repository: org.apache:apache:pom:10 Using private key: /Users/barrie/.ssh/baerr...@apache.org scp://people.apache.org/www/maven.apache.org/staging/ - Session: Opened [INFO] Pushing /Users/barrie/ide/maven/enforcer/target/checkout/maven-enforcer-plugin/targ et/site [INFO] to scp://people.apache.org/www/maven.apache.org/staging/plugins/maven-enforcer- plugin Executing command: mkdir -p /www/maven.apache.org/staging/plugins/maven-enforcer-plugin Executing command: mkdir -p /www/maven.apache.org/staging/plugins/maven-enforcer-plugin Executing command: scp -t /www/maven.apache.org/staging/plugins/maven-enforcer-plugin/wagon3077837942 66116250.zip Uploading: plugins/maven-enforcer-plugin/wagon307783794266116250.zip to scp://people.apache.org/www/maven.apache.org/staging/ # Transfer finished. 396475 bytes copied in 11.214 seconds Executing command: cd /www/maven.apache.org/staging/plugins/maven-enforcer-plugin; unzip -q -o wagon307783794266116250.zip; rm -f wagon307783794266116250.zip Executing command: chmod -Rf g+w,a+rX /www/maven.apache.org/staging/ scp://people.apache.org/www/maven.apache.org/staging/ - Session: Disconnecting scp://people.apache.org/www/maven.apache.org/staging/ - Session: Disconnected - 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
Re: Staging the latest documentation and sync...
On Tue, Jul 10, 2012 at 9:51 AM, Hervé BOUTEMY herve.bout...@free.fr wrote: ah ok, I got it it's a specific configuration written in maven-enforcer-plugin [del] IMHO, enforcer should switch. Tell me if you need help. Ahh, my itch was to fix the bug and push a release. I'm not sure if it stretches to upgrading :) but that choice is making me feel guilty, so if you can point me at some documentation and examples then I can at least look at the amount of effort required to ease my soul. - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Staging the latest documentation and sync...
Can someone have a look at the web page http://maven.apache.org/developers/release/maven-plugin-release.html and compare that automated results with the recommended manual steps. From what I can tell the automated steps now put things at /www/maven.apache.org/staging But the manual steps say /www/maven.apache.org/plugins/ - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Staging the latest documentation and sync...
Just following http://maven.apache.org/developers/release/maven-plugin-release.html and Staging the latest documentation. The stage completed successfully and its been a few hours since but the staging documentation is still not available. I have not verified the folder permissions to 0775 and files permissions to 0664, but I remember seeing the ssh commands doing that. Will check when I have a decent network connection. The sync link points to http://www.apache.org/dev/project-site.html which talks about svnpubsub. Where did we get with that? - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Staging the latest documentation and sync...
2012/7/6 Barrie Treloar baerr...@gmail.com: Just following http://maven.apache.org/developers/release/maven-plugin-release.html and Staging the latest documentation. The stage completed successfully and its been a few hours since but the staging documentation is still not available. I have not verified the folder permissions to 0775 and files permissions to 0664, but I remember seeing the ssh commands doing that. Will check when I have a decent network connection. The sync link points to http://www.apache.org/dev/project-site.html which talks about svnpubsub. Where did we get with that? I think Benson and Hervé start some jobs on that. But need probably more testing (and releasing the plugin). - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
