To be more precise, I generated the site, copied the files over to the
checkout folder, did a commit, and yet after the commit, still there is
a very old version of my projects page.
Leonardo do we have problems here?
Werner
Am 10.12.12 16:49, schrieb Werner Punz:
Hia, shouldnt svnpubsub be working?
I published updated documentation to the svn location, and I am still
getting the old files.
Werner
Am 06.12.12 12:55, schrieb Werner Punz:
Ok I have to answer myself, some of the links do not work (the module
links) with a simple site:site, as it seems.
Werner
Am 06.12.12 12:38, schrieb Werner Punz:
Hi Leonardo, just a short question, wouldn´t it be simpler just to make
a site:site and then copy the files over from the target directory?
Or am I missing something vital there?
Werner
Am 28.11.12 17:41, schrieb Leonardo Uribe:
Hi
The <server> entry goes into .m2/settings.xml
regards,
Leonardo
2012/11/28, Leonardo Uribe <lu4...@gmail.com>:
Hi
Yes, it is something like that, but it requires some extra details
1. Define a local server to do the site:stage-deploy using scp (note
the change in the pom.xml related to myfaces-local-staging)
<server>
<id>myfaces-local-staging</id>
<username>mylocaluser</username>
<password>mylocalpwd</password>
</server>
2. The idea is use two folders (/myfaces-site/checkout and
/myfaces-site/site), and do a hard copy from site to checkout before
commit the content under checkout folder.
The idea is write a guide and do the necessary changes in all pom.xml
files.
I have deployed the site for the release, but it seems something is
still not working well for svnpubsub, so I reopened the issue on
INFRA.
regards,
Leonardo Uribe
2012/11/27, Grant Smith <grantsm...@apache.org>:
Leo,
OK, I'll wait for you to finish the release process before I try to
make
any documentation changes. If I understand you correctly, once you
make
the
above changes, all I need to do to build the docs and deploy them
are:
1. mvn site:stage-deploy (in EACH of the modules)
2. svn commit
Is that correct ?
Thanks,
-Grant.
On Tue, Nov 27, 2012 at 7:18 AM, Leonardo Uribe <lu4...@gmail.com>
wrote:
Hi
This is the provisional changes done in site pom.xml to deploy the
site. I have locally two folders:
/home/lu4242/myfaces-site/checkout
/home/lu4242/myfaces-site/site
The idea is do the changes in myfaces-site/site and then do a manual
copy/commit for checkout.
regards,
Leonardo
Index: .
===================================================================
--- . (revision 1401760)
+++ . (working copy)
@@ -34,23 +34,54 @@
<description>This is the MyFaces Site</description>
<url>http://myfaces.apache.org</url>
+ <properties>
+
<site.mainDirectory>${user.home}/myfaces-site/checkout</site.mainDirectory>
+
<siteContent.path>${user.home}/myfaces-site/site</siteContent.path>
+ <!-- it's a default location for performance reason (not
checkout
the content all the time)
+ you can override this value in your settings. -->
+ <scmCheckout.path>\${site.mainDirectory}</scmCheckout.path>
+
<siteDeploy.url>file://${user.home}/myfaces-site/site</siteDeploy.url>
+ </properties>
+
<build>
<defaultGoal>site</defaultGoal>
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-ssh-external</artifactId>
- <version>1.0-beta-7</version>
+ <version>2.2</version>
</extension>
</extensions>
<pluginManagement>
<plugins>
<plugin>
<artifactId>maven-site-plugin</artifactId>
- <version>3.0</version>
+ <version>3.1</version>
</plugin>
</plugins>
</pluginManagement>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-scm-publish-plugin</artifactId>
+ <version>1.0-beta-1</version>
+ <configuration>
+ <pubScmUrl>scm:svn:
https://svn.apache.org/repos/asf/myfaces/site/publish/</pubScmUrl>
+ <tryUpdate>true</tryUpdate>
+
<checkoutDirectory>${scmCheckout.path}</checkoutDirectory>
+ <content>\${siteContent.path}</content>
+ </configuration>
+ </plugin>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-site-plugin</artifactId>
+ <configuration>
+
<stagingRepositoryId>myfaces-local-staging</stagingRepositoryId>
+ <stagingSiteURL>${siteDeploy.url}</stagingSiteURL>
+ </configuration>
+ </plugin>
+ </plugins>
+
</build>
<reporting>
<plugins>
@@ -65,7 +96,7 @@
<developerConnection>scm:svn:
https://svn.apache.org/repos/asf/myfaces/site/trunk</developerConnection>
<url>http://svn.apache.org/viewcvs.cgi/myfaces/site/trunk</url>
</scm>
-
+<!--
<distributionManagement>
<site>
<id>apache.website</id>
@@ -73,6 +104,14 @@
<url>scpexe://people.apache.org/www/myfaces.apache.org</url>
</site>
</distributionManagement>
-
+-->
+ <distributionManagement>
+ <site>
+ <id>myfaces-local-staging</id>
+ <name>Apache Website</name>
+ <url>scp://localhost/home/lu4242/myfaces-site</url>
+ </site>
+ </distributionManagement>
+
</project>
2012/11/27, Leonardo Uribe <lu4...@gmail.com>:
Hi
Since svnpubsub is working, do a site:deploy does not work.
Instead,
you need to:
1. checkout locally
http://svn.apache.org/repos/asf/myfaces/site/publish/
WARNING: Our site is huge, that will take a lot of time
2. Use a local site:stage-deploy like is described here:
http://maven.apache.org/plugins/maven-scm-publish-plugin/examples/multi-module-configuration.html
Remember all our projects are multi-module, so
maven-scm-publish-plugin does not help.
3. Manual commit
We need to update all myfaces projects to use this strategy, the
idea
is do that with the current release process of myfaces core
2.1.10 /
2.0.16 . I'm still trying to find how to do the necessary
changes in
our pom.xml
regards,
Leonardo Uribe
2012/11/27 Werner Punz <werner.p...@gmail.com>:
Ping: Leonardo, how can we publish currently our documentation?
Werner
Am 26.11.12 13:57, schrieb Werner Punz:
Am 23.11.12 16:16, schrieb Grant Smith:
Leo & Werner,
Thanks for the update on this. For now, I want to be able to
edit
the
xdocs, and have the resulting changes appear on the website. Any
Idea
how to accomplish this simple task ?
Guess only Leonardo can answer that for now.
Werner
On Thu, Nov 22, 2012 at 12:59 PM, Leonardo Uribe
<lu4...@gmail.com
<mailto:lu4...@gmail.com>> wrote:
Hi
2012/11/22 Werner Punz <werner.p...@gmail.com
<mailto:werner.p...@gmail.com>>:
> As for the site. Not sure if this one already is
served by
svnpubsub or
> still by the old system. Leonardo knows more. My guess
is it
still is served
> by the old system. I guess his plan is to have the
entire
site
hosted by
> svnpubsub for now, and then gradually move over to the
CMS
once
it is in
> place. But I am not sure, Leo can you fill us in here?
svnpubsub is already working, which was the mandatory
task to
do
this year.
All myfaces site has been moved to:
http://svn.apache.org/repos/asf/myfaces/site/publish/
In theory the CMS was built on top of svnpubsub, so I
suppose
there is a
relationship between both:
"... The publication links in the CMS are essentially
merge +
commit
operations in subversion which are tied into the live site
via
svnpubsub.
That means publishing in the CMS is virtually
instantaneous.
..."
I still have not tried the details about how it works,
but in
theory
you need to
put the files inside a subfolder inside publish folder and
later
this will be
consumed by the cms and published properly in the mirror
(I'm
speculating
here).
regards,
Leonardo Uribe
--
Grant Smith - V.P. Information Technology
Marathon Computer Systems, LLC.
--
Grant Smith - V.P. Information Technology
Marathon Computer Systems, LLC.
