Oops. I meant maven-site-scm-publish plugin Ralph
On May 19, 2012, at 1:33 PM, Ralph Goers <[email protected]> wrote: > My understanding is the asf-svnpubsub-plugin is the predecessor to the > maven-site-scm-plugin that I mentioned. > > Ralph > > On May 19, 2012, at 9:12 AM, Christian Grobmeier <[email protected]> wrote: > >> I just found this: >> http://maven.apache.org/sandbox/plugins/asf-svnpubsub-plugin/index.html >> >> Did we consider that one? It looks nice and integrates well with >> maven. It seems to checkout a specific url from svn, compares it with >> the locally generated site and then commits a diff to the publishing >> tree. From there its taken by svnpubsub. >> >> From what I understood so far, it should be easiest to use that >> plugin. We would need to check out every site with every change, but >> as the pubsub works on a separate tree, i think its no problem. >> >> WDYT? >> >> On Sat, May 19, 2012 at 5:30 PM, Christian Grobmeier >> <[email protected]> wrote: >>> On Fri, May 18, 2012 at 5:54 PM, Ralph Goers <[email protected]> >>> wrote: >>>> This topic has died down a bit. My concern here is that I am pretty much >>>> read to do a release of Log4j 2 but I really don't know how to publish the >>>> web site. The process I use to build Log4j 2 is >>> >>> Thanks for brining up the topic again. >>> >>>> 1. Check it out from SVN. >>>> 2. Run "mvn -P release-notes generate-resources (then commit the generated >>>> notes for a real release). >>>> 3. Run "mvn -P apache-release install (this step would be replaced by mvn >>>> release:prepare release:package in a real release) >>>> 4. Run mvn site (would be on the tagged branch). >>>> 5. Run mvn site:stage-deploy or mvn site:deploy to deploy the site >>>> somewhere. >>>> >>>> I'm imagining that I would need to use the maven-site-scm-publish plugin to >>>> commit the site to where it needs to go but we haven't agreed on what to >>>> tell INFRA regarding https://issues.apache.org/jira/browse/INFRA-4699. >>>> >>>> I'm not really sure where to go from here. >>> >>> Me either :-| >>> >>> Lets sum up what we have now: >>> - log4j1 does "mvn site" to localhost and then commits the generated >>> file to svn trunk. From there it will be taken with "svn up". This >>> process does not work well with pubsub because changes are visible >>> instantly. It needs to be changed. >>> >>> - log4j2 seem to do everything locally and just upload the generated >>> files to either a staging folder or the real folder. This is my >>> preferred approach >>> >>> - log4php does it (if i remember correctly) like log4j2 >>> >>> - I don't know bout the other logging sites. >>> >>> - Infra wants to see svnpubsub in action or that we use the CMS >>> >>> >>> Honestly my preferred approach is to have the rules in place you >>> mentioned in the issue. Ivans new main site is so simple, it really >>> does not need a CMS. The other pages should be taken with maven, as >>> usual. >>> >>> That being said, it seems there is a maven plugin which works with the >>> CMS. Even when I really have no fun trying out the CMS, we might ask >>> if we can get some kind of a sandbox to try it out. Probably we can >>> work as we always did and we don't need to use the CMS interface >>> directly. >>> >>> If we can use the CMS, we need to touch all pom files to enable it. >>> Basically it looks pretty straightforward, just moving the site-folder >>> to $project/content >>> >>> So, how about asking about getting access to a sandbox CMS and trying >>> the maven build? >>> >>> Cheers >>> Christian >>> >>> >>> >>>> >>>> Ralph >>>> >>>> On May 2, 2012, at 2:11 AM, Ivan Habunek wrote: >>>> >>>> Hi all, >>>> >>>> I was away for a bit so I didn't comment earlier. >>>> >>>> My idea is to generate the site using Twig [1], a nice PHP templating >>>> engine, in combination with Textile markup [2], which is much more >>>> versatile >>>> than most other common markup languages (such as markdown, apt, ...). >>>> >>>> I have already converted the logging web site. The code can be found here: >>>> http://svn.apache.org/repos/asf/logging/site/branches/experimental-twig-textile/ >>>> >>>> And I have deployed the generated web for demo here: >>>> http://bezdomni.net/logging/ >>>> >>>> This idea is obviously not compatible with the Apache CMS solution. >>>> Frankly, >>>> I would prefer this solution to the CMS since, from what I have seen, the >>>> CMS is quite a pain to use. >>>> >>>> Regards, >>>> Ivan >>>> >>>> [1] http://twig.sensiolabs.org/ >>>> [2] http://textile.sitemonks.com/ >>>> >>>> >>>> On 2 May 2012 10:44, Christian Grobmeier <[email protected]> wrote: >>>>> >>>>> On Mon, Apr 23, 2012 at 4:06 AM, Ralph Goers <[email protected]> >>>>> wrote: >>>>>> >>>>>> On Apr 20, 2012, at 12:14 PM, Christian Grobmeier wrote: >>>>>> >>>>>> >>>>>> What i thought was, why not to clean it up? Your proposed solutions >>>>>> seem to be the cleanest way and updating everything just when we need >>>>>> an update to the main site feels somehow wrong >>>>>> >>>>>> >>>>>> Joe has now proposed using the CMS for the main Logging web site along >>>>>> with expaths.txt + svnpubsub for each sub-project. Each sub-project >>>>>> would >>>>>> then use svn externals so they could be independently managed. This >>>>>> sounds >>>>>> perfect to me. >>>>> >>>>> OK I understand svn externals is like "symlinks for svn". Sounds ok. >>>>> >>>>> I am a bit concerned on the CMS. Ivan has put much effort in the website >>>>> design: >>>>> >>>>> http://svn.apache.org/repos/asf/logging/site/branches/experimental-redesign/src/site/pages/ >>>>> >>>>> I will ask infra (on the ticket) if it is possible to either use that >>>>> design for the CMS or if we can bypass the CMS feature for this one >>>>> too... >>>>> >>>>> Cheers >>>>> Christian >>>>> >>>>> >>>>>> Ralph >>>>> >>>>> >>>>> >>>>> -- >>>>> http://www.grobmeier.de >>>>> https://www.timeandbill.de >>>> >>>> >>>> >>> >>> >>> >>> -- >>> http://www.grobmeier.de >>> https://www.timeandbill.de >> >> >> >> -- >> http://www.grobmeier.de >> https://www.timeandbill.de
