On Sun, May 20, 2012 at 7:28 PM, Hervé BOUTEMY <[email protected]> wrote: > Le dimanche 20 mai 2012 18:46:06 Christian Grobmeier a écrit : >> That being said, we have not had a vote on that, but it seems that the >> majority of us doesn't want to use the CMS directly. Therefore we were >> initially looking for a mvn based solution. Did I understand you >> correct that the "main site" should be cared on CMS level while for >> example API docs are updated with m-scm-publish? Why can't we use mvn >> site together with m-scm-publish? > that's the problem with the CMS: there are multiple parts, some are good for > us Maven users, some are not. And using the CMS doesn't mean using its > internal site generation engine: you can have the CMS do "mvn site" to > generate html from apt, xdoc and so on. That's what's done for > maventest.apache.org.
Oh cool! Didn't know that! >> Cool, thanks for your help. > is it better to continue this discussion on Maven list or on logging? I think only less people from logging are subscribed to the maven lists. If you would join us at [email protected], then it would help much. Thanks! >> We are speaking of logging.apache.org. Inside are several components, >> like log4j1, the brandnew log4j2 which is blocked by the site release >> process, log4php, log4net and so on. The biggest problem is log4j1 and >> another urgent one is log4j2. We have the recommendation to use ASF >> CMS but so far we would prefer to use maven only solutions. All >> projects are independent, no parent project. We have a main site which >> links to the several subprojects. >> >> One of the ideas which is currently in place is to "do something with >> maven" which commits to a svn repos which is read by svnpubsub. > then with a little pom configuration, we should be able to do "mvn -Preporting > site-stage scm-publish:publish-scm" in one pass or in 2 pass "mvn -Preporting > site-stage" then "mvn scm-publish:publish-scm" That would be fine. Its still easy to use. > >> The >> repos could look like: >> >> /$asfrepos/logging/pubsub/logging/index.html --> main site >> /$asfrepos/logging/pubsub/logging/log4j/index.html --> logj41 site >> /$asfrepos/logging/pubsub/logging/log4j2/index.html --> logj42 site >> and so on. >> >> What do you think about that? > that's the structure we have in maventest with the main site and every > components. Everything is generated with Maven with "mvn site", the main site > being generated through the CMS. > The main site must take care to not delete components when updating, since it > is not responsible of their directories. The CMS does this by declaring > directories in extpaths.txt. > For logging, we'll have to work on it given the choice you'll make for main > site publishing. Thanks. Joe from Infra explained it to me/us, but not it slowly makes sense to me. > > After that, everythin can be ok with "mvn -Preporting site-stage scm- > publish:publish-scm". It can be as simple as that as soon as you don't want > subtle things like a directory by minor version or staging, which will require > some more work/knowledge. > > more precisely, if I use conventions Joe gave me for maventest, the repo would > be: > asfrepos=https://svn.apache.org/repos/infra/websites/production > $asfrepos/logging/content/index.html --> main site > $asfrepos/logging/content/log4j/index.html --> logj41 site > $asfrepos/logging/content/log4j2/index.html --> logj42 site I think that would be fine too. >> Thanks again! I feel a little bit lost and your help is highly appreciated. > Logging is the first project to ask for help, but I suppose you won't be the > only one :) > With the CMS, infra is making Maven users sick, but Maven users are making > infra mad in return: I think we should be able to show a simple path for > everybody. Actually I am pretty glad I asked here and that you responded so kindly. We had some good information from Infra but we are still stuck. Hopefully we can generate some docs out of our experiences and help others with this information. What I have missed was always the "step by step" information and the new tools are not really easy to understand. See you on general@ Cheers, Christian > > Regards, > > Hervé > >> >> Christian >> >> >> Thanks! >> > >> > somebody interested, nice! >> > >> > >> > Regards, >> > >> > Hervé >> > >> >> Christian >> > >> > [1] http://maventest.apache.org/ >> > >> > [2] >> > https://svn.apache.org/repos/infra/websites/production/maventest/content/p >> > lugins/ >> > >> > [3] >> > http://maventest.apache.org/developers/release/maven-plugin-release.html >> > >> > [4] http://maven.apache.org/sandbox/plugins/maven-scm-publish-plugin >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- http://www.grobmeier.de https://www.timeandbill.de --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
