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. But we'll look at that later, since that's not your priority.
> > >> What is left to leave sandbox? > > > > 1. interest/feedback > > Interest!! :-) nice to hear, I was starting to feel a little bit alone > > That won't change the release process question but at least ease usage: > > "mvn - Preporting site-deploy" > > would look nice, but I am really not looking for pure beauty. I would > be glad to solve our problems first, then look for beauty. > > > for the moment, I just published latest documentation: [4] (sync > > pending...) tel me what project/component you want to migrate to > > svnpubsub and we can work toward this precise case > > Cool, thanks for your help. is it better to continue this discussion on Maven list or on logging? > > 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" > 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. 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 > > > And hopefully you'll have projects with less content than Maven itself, > > because Maven migration to svnpubsub is really a big task: I'd be happy to > > start with smaller content > > Sure! > > 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. 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]
