You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Hervé Boutemy (Created JIRA)" <ji...@apache.org> on 2012/02/19 18:06:36 UTC
[jira] [Created] (INFRA-4466) please create a maventest.a.o CMS
sandbox
please create a maventest.a.o CMS sandbox
-----------------------------------------
Key: INFRA-4466
URL: https://issues.apache.org/jira/browse/INFRA-4466
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Components: CMS
Reporter: Hervé Boutemy
as discussed on infrastructure@a.o:
can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
let's call it maventest.apache.org, for example, or whatever is ok for you
the command to generate the site is "mvn site", and the generated HTML content is in target/site.
Each time the svn content is modified, the CMS should build and publish the site.
The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213041#comment-13213041 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
I "optimized" it by having it examine the commit
for situations where only the content/resources tree
was modified. In that case it just deals directly with
the changes instead of calling out to mvn.
In the hybrid approach I described, component trees
would be committed directly to the https://svn.apache.org/repos/infra/websites/production/maventest/content
tree instead of using the REST API and committing
them to the source tree in repos/asf/maven/site.
This would make the CMS builds of the base site
perform well enough for most use-cases; we'd just
need to have some way of reconstituting the component
sites in the production svn tree above in the event that
the CMS's publication feature gets wedged by svn merge
issues, which would result in clearing out all content
from the production tree and copying the site directly
from staging (which wouldn't have those component trees).
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Hervé Boutemy (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212122#comment-13212122 ]
Hervé Boutemy commented on INFRA-4466:
--------------------------------------
done
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Hervé Boutemy (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213109#comment-13213109 ]
Hervé Boutemy commented on INFRA-4466:
--------------------------------------
oh, yes, great optimization
the hybrid approach is more and more convincing.
Perhaps we can use Apache httpd rewrite rules can help too to assemble part of the whole site
another point: from the 435 component builds, 123 are "current" versions, which will change over time, the 312 other are versionned compoennt builds that are published as history and will never change
then updating these ones is more a waste than something useful
perhaps we could assemble the whole site from 3 sources:
- TLP site, with CMS and immediate publish
- current/latest components, which change on release
- components history, which never change after the release
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Schaefer closed INFRA-4466.
-------------------------------
Resolution: Fixed
Infra's work is done here AFAICT.
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213213#comment-13213213 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
Too slow Herve: the file is to be named
content/resources/extpaths.txt
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Hervé Boutemy (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212198#comment-13212198 ]
Hervé Boutemy commented on INFRA-4466:
--------------------------------------
FYI, since performance of a Maven build with Giga Bytes of static resources is something to check, I tried it on my machine: I copied more than 5 GB of maven.apache.org site to resources dir and ran a build.
First, I had to remove the build of a full jar of the site, since creating a 5GB+ .jar file takes a lot of time and does not really mean anything.
Then the result is that the build take approximately 11 minutes, 9:30 of which being in the resources copy, the rest in normal HTML generation from sources
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Hervé Boutemy (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216775#comment-13216775 ]
Hervé Boutemy commented on INFRA-4466:
--------------------------------------
done in r1293859
BTW, INFRA-4495 created for Doxia CMS
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Hervé Boutemy (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213023#comment-13213023 ]
Hervé Boutemy commented on INFRA-4466:
--------------------------------------
I did an analysis of /www/maven.apache.org content (and some cleanup for approx 300 MB...)
Here is the list of the 435 components builds I could find:
./ant-tasks
./ant-tasks-2.0.10
./ant-tasks-2.1.2
./apache
./apache-resource-bundles/apache-source-release-assembly-descriptor
./archetype
./archetype-2.0-alpha-5
./archetype-2.1
./archetype-2.2
./archetype/maven-archetype-bundles
./archiva
./archiva/1.0
./core-its
./doxia/doxia
./doxia/doxia-1.0.x
./doxia/doxia-1.1.2
./doxia/doxia-1.1.3
./doxia/doxia-1.1.4
./doxia/doxia-1.2
./doxia/doxia-sitetools
./doxia/doxia-sitetools-1.0.x
./doxia/doxia-sitetools-1.1.2
./doxia/doxia-sitetools-1.1.3
./doxia/doxia-sitetools-1.1.4
./doxia/doxia-sitetools-1.2
./doxia/doxia-tools
./doxia/doxia-tools-1.1
./doxia/doxia-tools-1.2
./embedder
./enforcer
./jxr
./jxr/jxr-2.4-SNAPSHOT
./maven-1.x
./maven-indexer
./maven-indexer-4.1.2
./maven-release
./mercury
./plugins/maven-acr-plugin
./plugins/maven-acr-plugin-1.0
./plugins/maven-antlr-plugin
./plugins/maven-ant-plugin
./plugins/maven-ant-plugin-2.1
./plugins/maven-ant-plugin-2.2
./plugins/maven-ant-plugin-2.3
./plugins/maven-antrun-plugin
./plugins/maven-antrun-plugin-1.2
./plugins/maven-antrun-plugin-1.3
./plugins/maven-antrun-plugin-1.4
./plugins/maven-antrun-plugin-1.5
./plugins/maven-antrun-plugin-1.6
./plugins/maven-antrun-plugin-1.7
./plugins/maven-archetype-plugin
./plugins/maven-archetype-plugin-1.0-alpha-7
./plugins/maven-archetype-plugin-2.0-alpha-3
./plugins/maven-archetype-plugin-2.0-alpha-4
./plugins/maven-assembly-plugin
./plugins/maven-assembly-plugin-2.1
./plugins/maven-assembly-plugin-2.2
./plugins/maven-assembly-plugin-2.2.1
./plugins/maven-assembly-plugin-2.2.2
./plugins/maven-assembly-plugin-2.2-beta-1
./plugins/maven-assembly-plugin-2.2-beta-4
./plugins/maven-assembly-plugin-2.2-beta-5
./plugins/maven-changelog-plugin
./plugins/maven-changelog-plugin-2.2
./plugins/maven-changes-plugin
./plugins/maven-changes-plugin-2.0
./plugins/maven-changes-plugin-2.1
./plugins/maven-changes-plugin-2.2
./plugins/maven-changes-plugin-2.3
./plugins/maven-changes-plugin-2.4
./plugins/maven-changes-plugin-2.5
./plugins/maven-changes-plugin-2.6
./plugins/maven-changes-plugin/xsd
./plugins/maven-checkstyle-plugin
./plugins/maven-checkstyle-plugin-2.2
./plugins/maven-checkstyle-plugin-2.3
./plugins/maven-checkstyle-plugin-2.4
./plugins/maven-checkstyle-plugin-2.5
./plugins/maven-checkstyle-plugin-2.6
./plugins/maven-checkstyle-plugin-2.7
./plugins/maven-checkstyle-plugin-2.8
./plugins/maven-checkstyle-plugin-2.9
./plugins/maven-clean-plugin
./plugins/maven-clean-plugin-2.3
./plugins/maven-clean-plugin-2.4
./plugins/maven-clean-plugin-2.4.1
./plugins/maven-clover-plugin
./plugins/maven-clover-plugin/2.4
./plugins/maven-compiler-plugin
./plugins/maven-compiler-plugin-2.1
./plugins/maven-compiler-plugin-2.2
./plugins/maven-compiler-plugin-2.3.1
./plugins/maven-compiler-plugin-2.3.2
./plugins/maven-dependency-plugin
./plugins/maven-dependency-plugin-2.1
./plugins/maven-dependency-plugin-2.3
./plugins/maven-dependency-plugin-2.4
./plugins/maven-deploy-plugin
./plugins/maven-deploy-plugin-2.4
./plugins/maven-deploy-plugin-2.5
./plugins/maven-deploy-plugin-2.6
./plugins/maven-deploy-plugin-2.7
./plugins/maven-doap-plugin
./plugins/maven-doap-plugin-1.0
./plugins/maven-doap-plugin-1.1
./plugins/maven-docck-plugin
./plugins/maven-docck-plugin-1.0
./plugins/maven-ear-plugin
./plugins/maven-ear-plugin-2.3.2
./plugins/maven-ear-plugin-2.4
./plugins/maven-ear-plugin-2.4.1
./plugins/maven-ear-plugin-2.4.2
./plugins/maven-ear-plugin-2.5
./plugins/maven-ear-plugin-2.6
./plugins/maven-ear-plugin-2.7
./plugins/maven-eclipse-plugin
./plugins/maven-eclipse-plugin-2.4
./plugins/maven-eclipse-plugin-2.5
./plugins/maven-eclipse-plugin-2.5.1
./plugins/maven-eclipse-plugin-2.6
./plugins/maven-eclipse-plugin-2.7
./plugins/maven-eclipse-plugin-2.8
./plugins/maven-eclipse-plugin-2.9
./plugins/maven-ejb-plugin
./plugins/maven-ejb-plugin-2.2
./plugins/maven-ejb-plugin-2.2.1
./plugins/maven-ejb-plugin-2.3
./plugins/maven-enforcer-plugin
./plugins/maven-enforcer-plugin-1.0.1
./plugins/maven-failsafe-plugin
./plugins/maven-failsafe-plugin-2.10
./plugins/maven-failsafe-plugin-2.11
./plugins/maven-failsafe-plugin-2.12
./plugins/maven-failsafe-plugin-2.5
./plugins/maven-failsafe-plugin-2.6
./plugins/maven-failsafe-plugin-2.7
./plugins/maven-failsafe-plugin-2.7.1
./plugins/maven-failsafe-plugin-2.7.2
./plugins/maven-failsafe-plugin-2.8
./plugins/maven-failsafe-plugin-2.8.1
./plugins/maven-failsafe-plugin-2.9
./plugins/maven-gpg-plugin
./plugins/maven-gpg-plugin-1.0
./plugins/maven-gpg-plugin-1.1
./plugins/maven-gpg-plugin-1.2
./plugins/maven-gpg-plugin-1.3
./plugins/maven-gpg-plugin-1.4
./plugins/maven-help-plugin
./plugins/maven-help-plugin-2.1
./plugins/maven-help-plugin-2.1.1
./plugins/maven-idea-plugin
./plugins/maven-idea-plugin-2.2
./plugins/maven-install-plugin
./plugins/maven-install-plugin-2.3
./plugins/maven-install-plugin-2.3.1
./plugins/maven-invoker-plugin
./plugins/maven-invoker-plugin-1.2.1
./plugins/maven-invoker-plugin-1.3
./plugins/maven-invoker-plugin-1.4
./plugins/maven-invoker-plugin-1.5
./plugins/maven-jar-plugin
./plugins/maven-jar-plugin-2.3
./plugins/maven-jar-plugin-2.3.1
./plugins/maven-jar-plugin-2.3.2
./plugins/maven-jar-plugin-2.4
./plugins/maven-jarsigner-plugin
./plugins/maven-jarsigner-plugin-1.0
./plugins/maven-jarsigner-plugin-1.1
./plugins/maven-jarsigner-plugin-1.2
./plugins/maven-javadoc-plugin
./plugins/maven-javadoc-plugin-2.5
./plugins/maven-javadoc-plugin-2.6
./plugins/maven-javadoc-plugin-2.6.1
./plugins/maven-javadoc-plugin-2.7
./plugins/maven-javadoc-plugin-2.8
./plugins/maven-javadoc-plugin-2.8.1
./plugins/maven-jxr-plugin
./plugins/maven-jxr-plugin-2.2
./plugins/maven-jxr-plugin-2.4-SNAPSHOT
./plugins/maven-linkcheck-plugin
./plugins/maven-linkcheck-plugin-1.0
./plugins/maven-linkcheck-plugin-1.0.1
./plugins/maven-linkcheck-plugin-1.1
./plugins/maven-one-plugin
./plugins/maven-patch-plugin
./plugins/maven-patch-plugin-1.1
./plugins/maven-patch-plugin-1.1.1
./plugins/maven-patch-tracker-plugin
./plugins/maven-pdf-plugin
./plugins/maven-pdf-plugin-1.0
./plugins/maven-pdf-plugin-1.1
./plugins/maven-plugin-plugin
./plugins/maven-plugin-plugin-2.4.3
./plugins/maven-plugin-plugin-2.5.1
./plugins/maven-plugin-plugin-2.6
./plugins/maven-plugin-plugin-2.7
./plugins/maven-plugin-plugin-2.8
./plugins/maven-plugin-plugin-2.9
./plugins/maven-plugins-21
./plugins/maven-pmd-plugin
./plugins/maven-pmd-plugin-2.5
./plugins/maven-pmd-plugin-2.6
./plugins/maven-pmd-plugin-2.7
./plugins/maven-pmd-plugin-2.7.1
./plugins/maven-project-info-reports-plugin
./plugins/maven-project-info-reports-plugin-2.1
./plugins/maven-project-info-reports-plugin-2.1.1
./plugins/maven-project-info-reports-plugin-2.1.2
./plugins/maven-project-info-reports-plugin-2.2
./plugins/maven-project-info-reports-plugin-2.3
./plugins/maven-project-info-reports-plugin-2.3.1
./plugins/maven-project-info-reports-plugin-2.4
./plugins/maven-rar-plugin
./plugins/maven-reactor-plugin
./plugins/maven-release-plugin
./plugins/maven-release-plugin-2.0
./plugins/maven-release-plugin-2.0-beta-8
./plugins/maven-release-plugin-2.0-beta-9
./plugins/maven-release-plugin-2.1
./plugins/maven-release-plugin-2.2
./plugins/maven-release-plugin-2.2.1
./plugins/maven-release-plugin-2.2.2
./plugins/maven-remote-resources-plugin
./plugins/maven-remote-resources-plugin-1.1
./plugins/maven-remote-resources-plugin-1.2
./plugins/maven-remote-resources-plugin-1.2.1
./plugins/maven-repository-plugin
./plugins/maven-repository-plugin-2.3
./plugins/maven-repository-plugin-2.3.1
./plugins/maven-resources-plugin
./plugins/maven-resources-plugin-2.4.1
./plugins/maven-resources-plugin-2.4.2
./plugins/maven-resources-plugin-2.4.3
./plugins/maven-resources-plugin-2.5
./plugins/maven-shade-plugin
./plugins/maven-shade-plugin-1.2.1
./plugins/maven-shade-plugin-1.2.2
./plugins/maven-shade-plugin-1.3
./plugins/maven-shade-plugin-1.3.1
./plugins/maven-shade-plugin-1.3.2
./plugins/maven-shade-plugin-1.3.3
./plugins/maven-shade-plugin-1.4
./plugins/maven-shade-plugin-1.5
./plugins/maven-site-plugin
./plugins/maven-site-plugin-2.0
./plugins/maven-site-plugin-2.0.1
./plugins/maven-site-plugin-2.0-beta-5
./plugins/maven-site-plugin-2.0-beta-7
./plugins/maven-site-plugin-2.1
./plugins/maven-site-plugin-2.1.1
./plugins/maven-site-plugin-2.2
./plugins/maven-site-plugin-2.3
./plugins/maven-site-plugin-3.0
./plugins/maven-site-plugin-3.0-beta-2
./plugins/maven-site-plugin-3.0-beta-3
./plugins/maven-source-plugin
./plugins/maven-source-plugin-2.1
./plugins/maven-source-plugin-2.1.1
./plugins/maven-source-plugin-2.1.2
./plugins/maven-stage-plugin
./plugins/maven-stage-plugin-1.0-alpha-1
./plugins/maven-stage-plugin-1.0-alpha-2
./plugins/maven-surefire-plugin
./plugins/maven-surefire-plugin-2.10
./plugins/maven-surefire-plugin-2.11
./plugins/maven-surefire-plugin-2.12
./plugins/maven-surefire-plugin-2.5
./plugins/maven-surefire-plugin-2.6
./plugins/maven-surefire-plugin-2.7
./plugins/maven-surefire-plugin-2.7.1
./plugins/maven-surefire-plugin-2.7.2
./plugins/maven-surefire-plugin-2.8
./plugins/maven-surefire-plugin-2.8.1
./plugins/maven-surefire-plugin-2.9
./plugins/maven-surefire-plugin-backup
./plugins/maven-surefire-report-plugin
./plugins/maven-surefire-report-plugin-2.10
./plugins/maven-surefire-report-plugin-2.11
./plugins/maven-surefire-report-plugin-2.12
./plugins/maven-surefire-report-plugin-2.5
./plugins/maven-surefire-report-plugin-2.6
./plugins/maven-surefire-report-plugin-2.7
./plugins/maven-surefire-report-plugin-2.7.1
./plugins/maven-surefire-report-plugin-2.7.2
./plugins/maven-surefire-report-plugin-2.8
./plugins/maven-surefire-report-plugin-2.9
./plugins/maven-toolchains-plugin
./plugins/maven-toolchains-plugin-1.0
./plugins/maven-verifier-plugin
./plugins/maven-verifier-plugin-1.0
./plugins/maven-war-plugin
./plugins/maven-war-plugin-2.1
./plugins/maven-war-plugin-2.1.1
./plugins/maven-war-plugin-2.1-alpha-2
./plugins/maven-war-plugin-2.1-beta-1
./plugins/maven-war-plugin-2.2
./plugins-sandbox
./plugins-sandbox/cactus-jcoverage-integration
./plugins-sandbox/itest
./plugins-sandbox/modello
./plugins-sandbox/style
./plugins-sandbox/webstart
./plugin-testing/maven-plugin-testing-2.0-alpha-1
./plugin-testing/maven-plugin-testing-harness
./plugin-testing/maven-plugin-testing-harness-2.0-alpha-1
./plugin-testing/maven-plugin-testing-tools
./plugin-testing/maven-plugin-testing-tools-2.0-alpha-1
./plugin-testing/maven-test-tools
./plugin-testing/maven-test-tools-2.0-alpha-1
./plugin-tools
./plugin-tools-2.4.3
./plugin-tools-2.5.1
./plugin-tools-2.8
./plugin-tools-2.9
./pom/asf
./pom/asf-10
./pom/maven
./pom/maven-21
./pom/maven-plugins
./pom/maven-plugins-22
./pom/maven-shared-components
./pom/maven-shared-components-17
./pom/skins
./ref/2.0.10
./ref/2.0.11
./ref/2.0.2
./ref/2.0.3
./ref/2.0.4
./ref/2.0.6
./ref/2.0.7
./ref/2.0.8
./ref/2.0.9
./ref/2.1.0
./ref/2.2.0
./ref/2.2.1
./ref/3.0
./ref/3.0.1
./ref/3.0.2
./ref/3.0.3
./ref/3.0.4
./ref/3.0-alpha-3
./ref/3.0-alpha-4
./ref/3.0-alpha-5
./ref/3.0-alpha-6
./ref/3.0-alpha-7
./ref/3.0-beta-1
./ref/3.0-beta-2
./ref/3.0-beta-3
./ref/maven-artifact-3.0-alpha-1
./scm
./scm-1.4
./scm-1.5
./scm-1.6
./shared/file-management
./shared/maven-archiver
./shared/maven-archiver-2.4.1
./shared/maven-archiver-2.4.2
./shared/maven-archiver-2.5
./shared/maven-artifact-resolver
./shared/maven-common-artifact-filters
./shared/maven-common-artifact-filters-1.2
./shared/maven-common-artifact-filters-1.3
./shared/maven-common-artifact-filters-1.4
./shared/maven-dependency-analyzer
./shared/maven-dependency-tree
./shared/maven-dependency-tree-1.2
./shared/maven-downloader
./shared/maven-doxia-tools
./shared/maven-doxia-tools-1.0
./shared/maven-doxia-tools-1.0.2
./shared/maven-doxia-tools-1.1
./shared/maven-doxia-tools-1.2
./shared/maven-doxia-tools-1.2.1
./shared/maven-doxia-tools-1.3
./shared/maven-doxia-tools-1.4
./shared/maven-enforcer-rule-api
./shared/maven-filtering
./shared/maven-filtering-1.0
./shared/maven-filtering-1.0-alpha-1
./shared/maven-filtering-1.0-beta-2
./shared/maven-filtering-1.0-beta-4
./shared/maven-invoker
./shared/maven-invoker-2.0.11
./shared/maven-jarsigner
./shared/maven-model-converter
./shared/maven-osgi
./shared/maven-plugin-helper
./shared/maven-plugin-testing-harness
./shared/maven-plugin-testing-tools
./shared/maven-plugin-tools
./shared/maven-reporting-api
./shared/maven-reporting-api-3.0
./shared/maven-reporting-exec
./shared/maven-reporting-exec-1.0.1
./shared/maven-reporting-impl
./shared/maven-reporting-impl-2.0.4.2
./shared/maven-reporting-impl-2.0.4.3
./shared/maven-reporting-impl-2.0.5
./shared/maven-reporting-impl-2.1
./shared/maven-reporting-impl-2.2
./shared/maven-repository-builder
./shared/maven-runtime
./shared/maven-runtime-1.0-alpha-1
./shared/maven-runtime-1.0-alpha-2
./shared/maven-script-interpreter
./shared/maven-shared-io
./shared/maven-shared-jar
./shared/maven-shared-jar-1.1
./shared/maven-shared-resources
./shared/maven-shared-resources-1
./shared/maven-test-tools
./shared/maven-verifier
./shared/maven-verifier-1.3
./skins/maven-application-skin
./skins/maven-application-skin-1.0
./skins/maven-classic-skin
./skins/maven-classic-skin-1.1
./skins/maven-default-skin
./skins/maven-default-skin-1.1
./skins/maven-fluido-skin
./skins/maven-fluido-skin-1.1
./skins/maven-stylus-skin
./skins/maven-stylus-skin-1.1
./skins/maven-stylus-skin-1.4
./surefire
./surefire-2.10
./surefire-2.8.1
./surefire-2.9
./wagon
./wagon-1.0
./wagon-1.0-beta-7
./wagon-2.0
./wagon-2.1
./wagon-2.2
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220173#comment-13220173 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
maventest.apache.org is online now. It's up to you guys
to work with extpaths.txt now and add the remaining directories.
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216741#comment-13216741 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
Please remove doxia from the extpaths.txt file as that will
be handled by a separate CMS site.
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215043#comment-13215043 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
Tentative schedule for maven support on the cms is early
next week!
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Hervé Boutemy (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216008#comment-13216008 ]
Hervé Boutemy commented on INFRA-4466:
--------------------------------------
extpaths.txt added in r1293458: see http://svn.apache.org/viewvc/maven/site/branches/INFRA-4466/trunk/content/resources/extpaths.txt?view=markup
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13212638#comment-13212638 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
Ok, I've "optimized" the build script in the maven case to do a better job of managing
changes to the content/resources/ directory that should help with performance there.
Please review that.
Also there is the possibility of using a CMS / svnpubsub hybrid approach if we cannot
get the performance to meet user's expectations. Subprojects would commit their
doc builds to the production site directly (using svn externals or Benson's plugin) and that
way they really wouldn't be mucking up the CMS's build process at all. Infra would
just need to be careful in situations where the site's production merges are wedged
and needs to be "Lazy Published", but it is a manageable situation.
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211617#comment-13211617 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
Can you insert a trunk/ dir after /INFRA-4466/ please? The CMS
expects the site to live on trunk an this will work for now.
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214662#comment-13214662 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
For an example usage see http://www.apache.orrg/extpaths.txt
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13216204#comment-13216204 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
I recommend at least for now adding a few spaces of indentation
at the start of each line, and only removing those spaces once
you've actually committed those trees to the production tree.
Otherwise any attempts to publish your site will fail, and if you
forget to update the file after committing a tree a subsequent
publish operation will remove that tree from production.
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213107#comment-13213107 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
As a result of this discussion Daniel and I are working on
some optimizations for the CMS's publish feature that will
be compatible with the approach I outlined here for hybrid
sites. All we will need from you is a list of directories that
are "external" to the build, ie exist only on the production
site. The list you have provided will serve as the specification
for this effort for maventest, simply add that list to a file
of your choosing in /content/resources/ (ie something
that gets copied to the root of the staging tree). Pick
a good name as that will be the standard for all projects
to use.
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (INFRA-4466) please create a
maventest.a.o CMS sandbox
Posted by "Joe Schaefer (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214662#comment-13214662 ]
Joe Schaefer edited comment on INFRA-4466 at 2/23/12 2:11 PM:
--------------------------------------------------------------
For an example usage see http://www.apache.org/extpaths.txt
was (Author: joes):
For an example usage see http://www.apache.orrg/extpaths.txt
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220140#comment-13220140 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
Firewall issue. Got a clean build this time, see
http://maventest.staging.apache.org/
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211485#comment-13211485 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
There are a coupla features I'd like to see from maven to make use of the CMS
more palatable for large sites like maven.apache.org. First, I would like the
ability to choose a target directory for the build from a command-line interface,
which will eliminate the need for a post-processing rsync job to copy the results.
That's not necessary for smallish sites, but is fairly important for multi-gigabyte ones.
So would a multi-threaded build process, but I assume that's more difficult to provide
near-term.
We also need to sort out how we're going to manage the "component" sites, either
as a part of the main site or as completely independent CMS-based sites. Either
way, for the CMS to provide any significant advantage over straight svnpubsub
we will need a means of introspecting the build dependencies for a given target url
and making those corresponding source files available to the user via the CMS's
redirection feature. Either providing a list of dependencies to select from, or a
"best guess" file to use, would be fine. This would obviate the need for the use
of a "content/" dir for such things, which would only be capable of doing a file
match by globbing on the extension.
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211613#comment-13211613 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
Thanks a bunch! I've updated the CMS redirection code to support maven
site trees based in the content/ dir. The -Dsite.output option will come in
handy for the build_external.pl script.
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220111#comment-13220111 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
Build failed: see the bottom of
http://ci.apache.org/builders/maventest-site-staging/builds/1/steps/compile/logs/stdio
Some permission problem somewhere I think.
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Hervé Boutemy (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13211574#comment-13211574 ]
Hervé Boutemy commented on INFRA-4466:
--------------------------------------
site available in https://svn.apache.org/repos/asf/maven/site/branches/INFRA-4466
site content is in content subdir
output HTML is by default in output directory, and you can change it with "mvn -Dsite.output=where/you/want site"
to guess a source file from an url, you just need to know that first directory is a format: apt, xdoc, resources, fml, ...
for example:
- /community.html is generated from content/apt/community.apt (it is in apt format)
- /about.html is generated from content/fml/about.fml (it is in fml format)
- /articles.html is generated from content/xdoc/articles.xml (it is in xdoc format)
and there is another convention: a source file can end in .vm to be processed by Velocity before being interpreted to HTML
for example, /index.html is generated from content/xdoc/index.xml.vm
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13214928#comment-13214928 ]
Joe Schaefer commented on INFRA-4466:
-------------------------------------
The long and short of the situation is that someone will need to
take all those paths and commit them directly to the production
site, keeping things synced with the extpaths.txt file. Ideally
a script that walks the current maven.apache.org site directory
and imports sections of the tree into svn based on the extpaths.txt
file would make the most sense.
I can try to code something up along these lines if need be,
but would like to avoid doing that work myself as it's something
the PMC needs to do. Transferring everything over to a production
version of maven.apache.org based on the work we do here is
certainly simple enough to accomplish.
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4466) please create a maventest.a.o CMS
sandbox
Posted by "Hervé Boutemy (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13213030#comment-13213030 ]
Hervé Boutemy commented on INFRA-4466:
--------------------------------------
How did you "optimize" the build script?
Given the amount of components builds aggregation, I think the svnpubsub approach would be more scalable and logical
How can we work on this?
> please create a maventest.a.o CMS sandbox
> -----------------------------------------
>
> Key: INFRA-4466
> URL: https://issues.apache.org/jira/browse/INFRA-4466
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Hervé Boutemy
>
> as discussed on infrastructure@a.o:
> can you create a CMS sandbox for http://svn.apache.org/repos/asf/maven/site/trunk ?
> let's call it maventest.apache.org, for example, or whatever is ok for you
> the command to generate the site is "mvn site", and the generated HTML content is in target/site.
> Each time the svn content is modified, the CMS should build and publish the site.
> The corresponding site would actually contain 241 files in 59 directories for 5.6MB.
> Then I could try to add to this TLP site some components' sites, like /ant-tasks/ for example, using this REST api
> This would IMHO perfectly the misc workflows we actually use to modify maven.a.o site, with only minor changes in the publish commands: no more scp.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira