Hi

It seems the staging area is working:

http://myfaces.staging.apache.org/index1.html

but when I tried to publish the site nothing is happening.

Anyway, with the staging area we can start to move the documentation.

regards,

Leonardo Uribe

2013/1/17 Leonardo Uribe <lu4...@gmail.com>:
> Hi
>
> It seems the issue has been fixed, but first we need to try.
>
> Does anyone knows how to create a helloworld page using apache cms?
>
> regards,
>
> Leonardo Uribe
>
> 2012/12/12 Werner Punz <werner.p...@gmail.com>:
>> Hi I already created the ticket for Infra:
>>
>> https://issues.apache.org/jira/browse/INFRA-5633
>>
>>
>> Werner
>>
>>
>> Am 12.12.12 02:55, schrieb Leonardo Uribe:
>>
>>> Hi
>>>
>>> It seems we need some help to understand how to deal with this. Checking:
>>>
>>> http://www.apache.org/dev/project-site.html
>>>
>>> It says this:
>>>
>>> "... The infrastructure team currently supports two main mechanisms for
>>> publishing and maintaining project sites:
>>>
>>>   - svnpubsub, which allows the static contents of a designated svn folder
>>> (example) to automatically published as the project web site at
>>> http://project.apache.org/. The project team can use any site build
>>> mechanism it wants as long as the above requirements are met.
>>>   - Apache CMS, which provides a simple browser-based user interface for
>>> editing, staging and publishing site content in Markdown, HTML or any
>>> other source format for which support has been added. See the CMS
>>> reference and adoption for more details. The Apache CMS uses
>>> svnpubsub as the underlying mechanism for publishing a site. ..."
>>>
>>> We have fixed the first problem, upgrade our maven site to svnpubsub
>>> before end 2012. Now we need to integrate Apache CMS content into
>>> our site generated by maven.
>>>
>>> How to do that? In the same page it says:
>>>
>>> "... Do project sites have to use svnpubsub?
>>>
>>> Yes. Infrastructure will mandate transition to svnpubsub over this year.
>>> (svnpubsub requires the generated site files to be in a Subversion tree
>>> somewhere. For CMS users this tree will be the CMS build output tree.)
>>> ..."
>>>
>>> By deduction (I'm speculating based on the info we have), we need
>>> two folders:
>>>
>>> - One consumed by svnpubsub that is the output for Apache CMS and
>>> that will be changed too using maven site + manual commit:
>>>
>>> http://svn.apache.org/repos/asf/myfaces/site/publish/
>>>
>>> - The other one is the source content for Apache CMS.
>>>
>>> http://svn.apache.org/repos/asf/myfaces/site/cms-site/
>>>
>>> Since Werner has confirmed that svnpubsub, in my understanding the last
>>> step we need is enable Apache CMS folder (cms-site) and set this up
>>> so the output can be put in the folder used by svnpubsub. To do that, we
>>> just need to create another issue in INFRA, so they can do their magic.
>>>
>>> regards,
>>>
>>> Leonardo Uribe
>>>
>>> 2012/12/11 Werner Punz <werner.p...@gmail.com>:
>>>>
>>>> Ok the information was wrong as it seems we do not need the cms in
>>>> svnpubsub. Sorry for the wrong info.
>>>>
>>>>
>>>> Werner
>>>>
>>>> Am 11.12.12 10:59, schrieb Werner Punz:
>>>>
>>>>> Ok I am picking up the works on the CMS again, as it seems the cms
>>>>> folder has to be hosted under svnpubsub.
>>>>>
>>>>>
>>>>> [10:53am] werpu: how do you mix svnpubsub and the cms content btw? does
>>>>> the cms folder have to be in the svnpubsub folder?
>>>>> [10:53am] werpu: sorry for the noob questions
>>>>> [10:53am] werpu: but we have svnpubsub already working and i am now
>>>>> trying to find the best way to get cms in
>>>>> [10:54am] Humbedooh: afaik, the cms just picks up changes via svnpubsub
>>>>> and generates content
>>>>> [10:55am] Humbedooh: so yes, it'd have to be something that runs off
>>>>> svnpubsub for it to work
>>>>> [10:55am] werpu: ok
>>>>>
>>>>>
>>>>> So I will move the cms folder to svnpubsub and then I will open a ticket
>>>>> to get the CMS in for the content which will be hosted there.
>>>>>
>>>>> Werner
>>>>>
>>>>>
>>>>> Am 11.12.12 09:36, schrieb Werner Punz:
>>>>>>
>>>>>>
>>>>>> Ok it definitely now is working, I did a minor change in one of my
>>>>>> pages
>>>>>> and after about 10 minutes after the commit the change now is online.
>>>>>> There seems to be s light rsync induced delay between the changes and
>>>>>> going online.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Werner
>>>>>>
>>>>>>
>>>>>> Am 11.12.12 09:20, schrieb Werner Punz:
>>>>>>>
>>>>>>>
>>>>>>> Hia looks good to me now, I have the latest changes now online.
>>>>>>>
>>>>>>> Werner
>>>>>>>
>>>>>>>
>>>>>>> Am 10.12.12 22:02, schrieb Grant Smith:
>>>>>>>>
>>>>>>>>
>>>>>>>> <grantsmith> danielsh, apparently (according to Leonardo) the
>>>>>>>> svnpubsub
>>>>>>>> is still not working, for example
>>>>>>>> http://myfaces.apache.org/extensions/validator/download.html is not
>>>>>>>> reflecting changes
>>>>>>>> <danielsh> grantsmith: .us or .eu
>>>>>>>> <grantsmith> danielsh, pardon ?
>>>>>>>> <danielsh> try myfaces.us.a.o grantsmith
>>>>>>>> <danielsh> that one should work
>>>>>>>> <grantsmith> ah, you are correct. Is there a lag ?
>>>>>>>> <danielsh> rsync blew up while i was afk
>>>>>>>> <danielsh> rerunnin
>>>>>>>> <gmcdonald> boo
>>>>>>>> <grantsmith> oh i see. OK, thank you!
>>>>>>>> * stevegill (~steven...@sjfw1-a.adobe.com
>>>>>>>> <mailto:steven...@sjfw1-a.adobe.com>) has joined #asfinfra
>>>>>>>> <danielsh> if it's not fixed tomorrow reopen the ticket grantsmith
>>>>>>>> <grantsmith> will do, many thanks.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Dec 10, 2012 at 11:33 AM, Leonardo Uribe <lu4...@gmail.com
>>>>>>>> <mailto:lu4...@gmail.com>> wrote:
>>>>>>>>
>>>>>>>>      Hi
>>>>>>>>
>>>>>>>>      It seems it is not working yet. I updated extval site (1.2.6,
>>>>>>>> 2.0.6
>>>>>>>>      release) some days ago and the page still does not have the
>>>>>>>> changes.
>>>>>>>>      I'm keeping an eye on this page:
>>>>>>>>
>>>>>>>>      http://myfaces.apache.org/extensions/validator/download.html
>>>>>>>>
>>>>>>>>      regards,
>>>>>>>>
>>>>>>>>      Leonardo Uribe
>>>>>>>>
>>>>>>>>      2012/12/10 Grant Smith <grantsm...@apache.org
>>>>>>>>      <mailto:grantsm...@apache.org>>:
>>>>>>>>       > I just had a chat in #asfinfra about this:
>>>>>>>>       >
>>>>>>>>       >
>>>>>>>>       > grantsmith> danielsh, any chance you could revisit INFRA-5280
>>>>>>>> ?
>>>>>>>>       > <danielsh> kyds?
>>>>>>>>       > <wayita> Your sysadmins are not arrays. When mentioning a
>>>>>>>> jira
>>>>>>>>      issue, please
>>>>>>>>       > say what it is about, not just its number. Thanks
>>>>>>>>       > <grantsmith> ah. lol.. it's regarding the Myfaces svnpubsub
>>>>>>>>       > <danielsh> what do you need
>>>>>>>>       > <grantsmith> well, mainly for it to work...
>>>>>>>>       > <grantsmith> no problem if you're too busy now
>>>>>>>>       > <danielsh> what's the status?
>>>>>>>>       > <danielsh> iirc that ticket is waitforinfra after one of you
>>>>>>>> guys
>>>>>>>>      removed
>>>>>>>>       > the symlink
>>>>>>>>       > <grantsmith> we had to remove some symlinks, which we have
>>>>>>>> done
>>>>>>>>       > <danielsh> (the one I mailed you about a few weeks before
>>>>>>>> that..)
>>>>>>>>       > <danielsh> right
>>>>>>>>       > <grantsmith> as of dec 04
>>>>>>>>       > <danielsh> so next steps is to run 'svn cleanup' manually on
>>>>>>>> your
>>>>>>>>      wc's
>>>>>>>>       > <danielsh> or maybe that's not needed
>>>>>>>>       > <danielsh> let me have a look now
>>>>>>>>       > <grantsmith> thanks
>>>>>>>>       > <danielsh> jira desc 5280
>>>>>>>>       > <danielsh> ok so your wc needs cleanu p
>>>>>>>>       > <danielsh> so i'll do that now
>>>>>>>>       > <danielsh> then check that up works
>>>>>>>>       > <danielsh> hopefully it'll just work if all symlink sare gone
>>>>>>>>       > <grantsmith> ok many thanks, i'll relay this to the mailing
>>>>>>>> list
>>>>>>>>       > <danielsh> wait a minute
>>>>>>>>       > <danielsh> i am actually running that now
>>>>>>>>       > <danielsh> if you wait 5m you can report them it's been done
>>>>>>>>       >
>>>>>>>>       >
>>>>>>>>       > Can you guys see if it's working now ?
>>>>>>>>       >
>>>>>>>>       >
>>>>>>>>       > On Mon, Dec 10, 2012 at 8:12 AM, Leonardo Uribe
>>>>>>>> <lu4...@gmail.com
>>>>>>>>      <mailto:lu4...@gmail.com>> wrote:
>>>>>>>>       >>
>>>>>>>>       >> Hi
>>>>>>>>       >>
>>>>>>>>       >> 2012/12/10 Werner Punz <werner.p...@gmail.com
>>>>>>>>      <mailto:werner.p...@gmail.com>>:
>>>>>>>>       >> > 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?
>>>>>>>>       >> >
>>>>>>>>       >>
>>>>>>>>       >> Yes, see:
>>>>>>>>       >>
>>>>>>>>       >> https://issues.apache.org/jira/browse/INFRA-5280
>>>>>>>>       >>
>>>>>>>>       >> I removed some symbolic links that caused some problems, but
>>>>>>>> we need
>>>>>>>>       >> to wait infra guys to do some additional steps.
>>>>>>>>       >>
>>>>>>>>       >> regards,
>>>>>>>>       >>
>>>>>>>>       >> Leonardo Uribe
>>>>>>>>       >>
>>>>>>>>       >> > 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
>>>>>>>>      <mailto: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
>>>>>>>>      <mailto: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 <mailto: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
>>>>>>>>      <http://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
>>>>>>>>      <mailto: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
>>>>>>>>      <mailto: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>
>>>>>>>>       >> >>>>>>>>>>>> <mailto:lu4...@gmail.com
>>>>>>>>      <mailto:lu4...@gmail.com>>> wrote:
>>>>>>>>       >> >>>>>>>>>>>>
>>>>>>>>       >> >>>>>>>>>>>>      Hi
>>>>>>>>       >> >>>>>>>>>>>>
>>>>>>>>       >> >>>>>>>>>>>>      2012/11/22 Werner Punz
>>>>>>>> <werner.p...@gmail.com
>>>>>>>>      <mailto:werner.p...@gmail.com>
>>>>>>>>       >> >>>>>>>>>>>>      <mailto: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.
>>>>>>>>       >> >>>>>>>>
>>>>>>>>       >> >>>>>>>>
>>>>>>>>       >> >>>>>>>>
>>>>>>>>       >> >>>>>>>>
>>>>>>>>       >> >>>>>>>
>>>>>>>>       >> >>>>>>
>>>>>>>>       >> >>>>>
>>>>>>>>       >> >>>>
>>>>>>>>       >> >>>>
>>>>>>>>       >> >>>
>>>>>>>>       >> >>>
>>>>>>>>       >> >>
>>>>>>>>       >> >>
>>>>>>>>       >> >
>>>>>>>>       >>
>>>>>>>>       >> --
>>>>>>>>       >> Grant Smith - V.P. Information Technology
>>>>>>>>       >> Marathon Computer Systems, LLC.
>>>>>>>>       >>
>>>>>>>>       >>
>>>>>>>>       >>
>>>>>>>>       >
>>>>>>>>
>>>>>>>>      --
>>>>>>>>      Grant Smith - V.P. Information Technology
>>>>>>>>      Marathon Computer Systems, LLC.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>

Reply via email to