I applied the changes described here.
Then started similar jobs for sandbox (only cli2 currently) (I don't
want to put parent snapshot in all: to avoid complain :-) )
This means parent and sandbox parent releases are needed.
Result here: http://people.apache.org/~olamy/commons-content/
Not all modules content is here.
To ease stuff I will probably import manually content from people.a.o
to svn tree (I did that for dormant).
Make sense ?
As it migration will be possible.


2013/1/9 Olivier Lamy <ol...@apache.org>:
> 2013/1/9 Gary Gregory <garydgreg...@gmail.com>:
>> On Wed, Jan 9, 2013 at 4:36 AM, Olivier Lamy <ol...@apache.org> wrote:
>>
>>> 2013/1/8 Olivier Lamy <ol...@apache.org>:
>>> > 2013/1/8 Phil Steitz <phil.ste...@gmail.com>:
>>> >> On 1/7/13 3:57 PM, sebb wrote:
>>> >>> On 7 January 2013 16:06, Gary Gregory <garydgreg...@gmail.com> wrote:
>>> >>>> Is CP in a proper state for a release WRT svn pub?
>>> >>> Dunno.
>>> >>>
>>> >>> Given that a faulty CP version can just be ignored, why not just bring
>>> >>> it up to date as much as poss and release anyway so it can be used for
>>> >>> testing?
>>> >>>
>>> >>> BTW, https://issues.apache.org/jira/browse/MPOM-32 has at last been
>>> >>> fixed; hopefully there will be a new release of AP soon.
>>> > I wil try early next week.
>>> >>
>>> >> I think we need
>>> >> https://issues.apache.org/jira/browse/INFRA-5657
>>> >>
>>> >> to get the right info in the pom.
>>> > correct.
>>> > BTW 99% chance the url will be
>>> > https://svn.apache.org/repos/infra/websites/production/commons/content
>>> > :-)
>>>
>>> Some progress.
>>> But still TODO see my comments
>>> https://issues.apache.org/jira/browse/INFRA-5657
>>>
>>
>> This sounds painful, every single component has to be ported to the new
>> system before any release can happen.
>> Ouch.
> Agree.
> Note: in Maven project (which have similar structure with some sub sub
> projects) we start around jun with test instance.
> Currently I didn't want to break to much configuration here.
> So projects are deployed as today which need some extra configuration
> in each pom.
> They are deployed to something like:
> * commons.a.o/collections
> * commons.a.o/io
> * commons.a.o/math
> * etc..
>
> This need to know the path with a property in each pom:
> * <commons.site.path>collections</commons.site.path>
> * etc..
>
> This need to add a line in the extpaths file
> (https://svn.apache.org/repos/asf/commons/cms-site/trunk/content/resources/extpaths.txt)
> * collections
> * etc..
>
> What I would prefer is to deploy to generic path:
> instead of 
> https://svn.apache.org/repos/infra/websites/production/commons/content/collections/
> could be  
> https://svn.apache.org/repos/infra/websites/production/commons/content/propers/${project.artifactId}
>
> https://svn.apache.org/repos/infra/websites/production/commons/content/propers/commons-collections
>
> With a redirect rule to redirect commons.a.o/collections to
> commons.a.o/propers/commons-collections
> Maybe we can use RedirectMatch which could work for all.
>
> Something similar for sandbox.
>
> This means an easier migration:
> * just inherit parent (no extra configuration needed) (except for non
> generated content like javadoc from previous versions)
> * faster publish tru the cms interface (due to small number of content
> in extpaths file)
>
> If it makes sense I can work a bit on that.
>
> /Olivier
>
>>
>> Gary
>>
>>>
>>> >
>>> >>
>>> >> Phil
>>> >>>
>>> >>>> Gary
>>> >>>>
>>> >>>> --
>>> >>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>> >>>> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
>>> >>>> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
>>> >>>> Blog: http://garygregory.wordpress.com
>>> >>>> Home: http://garygregory.com/
>>> >>>> Tweet! http://twitter.com/GaryGregory
>>> >>> ---------------------------------------------------------------------
>>> >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> >>> For additional commands, e-mail: dev-h...@commons.apache.org
>>> >>>
>>> >>>
>>> >>
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> >> For additional commands, e-mail: dev-h...@commons.apache.org
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Olivier Lamy
>>> > Talend: http://coders.talend.com
>>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>>
>>
>> --
>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
>> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to