You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2012/03/09 08:45:43 UTC
[INFO] Karaf and ServiceMix website
Hi all,
as you probably know, the Apache Infrastructure team has mandated that
all projects move to the new svnpubsub process for publishing their
website by the end of the year.
The purpose is to reduce the sync time and the I/O required to the sync.
The Infra worked with the Maven team, and a simple mvn site:deploy works
fine.
However, as our website use scalate, we do:
mvn install
mvn scalate:deploy
So it's not a pure mvn site:deploy.
I'm going to discuss with Joe (from the Infra) to see if it could work
"out of the box" using scalate:deploy or if we need to perform some
update on scalate to use something similar to site:deploy.
A possible workaround is to use:
mvn scalate:sitegen
mvn site:deploy
I think it should work.
I will keep you posted about that.
Regards
JB
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [INFO] Karaf and ServiceMix website
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Dan,
and thanks for the tip.
I will have to talk with Joe to know what he prefers.
Regards
JB
On 03/09/2012 01:35 PM, Daniel Kulp wrote:
>
> If you want to simplify this, I believe you won't even need the "deploy"
> stuff at all for this. What you will need is the ability to run:
>
> mvn some:target -Doutput.dir=/path/to/svn/location
>
> and Joe can handle the rest. He'll setup a build that will run that once
> an hour (or can trigger on an svn change in this case) and that's it. You
> would commit the change, buildbot will trigger, site is live in minutes.
>
> Dan
>
>
>
> On Friday, March 09, 2012 08:45:43 AM Jean-Baptiste Onofré wrote:
>> Hi all,
>>
>> as you probably know, the Apache Infrastructure team has mandated that
>> all projects move to the new svnpubsub process for publishing their
>> website by the end of the year.
>>
>> The purpose is to reduce the sync time and the I/O required to the sync.
>>
>> The Infra worked with the Maven team, and a simple mvn site:deploy works
>> fine.
>> However, as our website use scalate, we do:
>>
>> mvn install
>> mvn scalate:deploy
>>
>> So it's not a pure mvn site:deploy.
>>
>> I'm going to discuss with Joe (from the Infra) to see if it could work
>> "out of the box" using scalate:deploy or if we need to perform some
>> update on scalate to use something similar to site:deploy.
>>
>> A possible workaround is to use:
>>
>> mvn scalate:sitegen
>> mvn site:deploy
>>
>> I think it should work.
>>
>> I will keep you posted about that.
>>
>> Regards
>> JB
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [INFO] Karaf and ServiceMix website
Posted by Daniel Kulp <dk...@apache.org>.
On Friday, March 09, 2012 07:35:22 AM Daniel Kulp wrote:
> If you want to simplify this, I believe you won't even need the "deploy"
> stuff at all for this. What you will need is the ability to run:
>
> mvn some:target -Doutput.dir=/path/to/svn/location
>
> and Joe can handle the rest. He'll setup a build that will run that once
> an hour (or can trigger on an svn change in this case) and that's it.
> You would commit the change, buildbot will trigger, site is live in
> minutes.
Actually, what's interesting about thsi is he MAY be able to wire in the
"src" tree into the CMS and you can use the CMS to edit the src and then
buildbot would then do the build and such. No need to checkout the site
for a simple change.
Dan
>
> Dan
>
> On Friday, March 09, 2012 08:45:43 AM Jean-Baptiste Onofré wrote:
> > Hi all,
> >
> > as you probably know, the Apache Infrastructure team has mandated that
> > all projects move to the new svnpubsub process for publishing their
> > website by the end of the year.
> >
> > The purpose is to reduce the sync time and the I/O required to the sync.
> >
> > The Infra worked with the Maven team, and a simple mvn site:deploy works
> > fine.
> > However, as our website use scalate, we do:
> >
> > mvn install
> > mvn scalate:deploy
> >
> > So it's not a pure mvn site:deploy.
> >
> > I'm going to discuss with Joe (from the Infra) to see if it could work
> > "out of the box" using scalate:deploy or if we need to perform some
> > update on scalate to use something similar to site:deploy.
> >
> > A possible workaround is to use:
> >
> > mvn scalate:sitegen
> > mvn site:deploy
> >
> > I think it should work.
> >
> > I will keep you posted about that.
> >
> > Regards
> > JB
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: [INFO] Karaf and ServiceMix website
Posted by Daniel Kulp <dk...@apache.org>.
If you want to simplify this, I believe you won't even need the "deploy"
stuff at all for this. What you will need is the ability to run:
mvn some:target -Doutput.dir=/path/to/svn/location
and Joe can handle the rest. He'll setup a build that will run that once
an hour (or can trigger on an svn change in this case) and that's it. You
would commit the change, buildbot will trigger, site is live in minutes.
Dan
On Friday, March 09, 2012 08:45:43 AM Jean-Baptiste Onofré wrote:
> Hi all,
>
> as you probably know, the Apache Infrastructure team has mandated that
> all projects move to the new svnpubsub process for publishing their
> website by the end of the year.
>
> The purpose is to reduce the sync time and the I/O required to the sync.
>
> The Infra worked with the Maven team, and a simple mvn site:deploy works
> fine.
> However, as our website use scalate, we do:
>
> mvn install
> mvn scalate:deploy
>
> So it's not a pure mvn site:deploy.
>
> I'm going to discuss with Joe (from the Infra) to see if it could work
> "out of the box" using scalate:deploy or if we need to perform some
> update on scalate to use something similar to site:deploy.
>
> A possible workaround is to use:
>
> mvn scalate:sitegen
> mvn site:deploy
>
> I think it should work.
>
> I will keep you posted about that.
>
> Regards
> JB
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
Re: [INFO] Karaf and ServiceMix website
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Thanks for the update James and awesome ;)
It was the only part that I planned to verify ;)
The other things is the way that we publish the documentation on the
website (the location on people.apache.org especially).
Thanks again,
Regards
JB
On 03/09/2012 09:03 AM, James Strachan wrote:
> FWIW scalate:deploy is using pretty much identical code under the
> covers- reusing the same mvn wagon stuff to do the upload; so I'd have
> thought it'd just work.
>
> On 9 March 2012 07:45, Jean-Baptiste Onofré<jb...@nanthrax.net> wrote:
>> Hi all,
>>
>> as you probably know, the Apache Infrastructure team has mandated that all
>> projects move to the new svnpubsub process for publishing their website by
>> the end of the year.
>>
>> The purpose is to reduce the sync time and the I/O required to the sync.
>>
>> The Infra worked with the Maven team, and a simple mvn site:deploy works
>> fine.
>> However, as our website use scalate, we do:
>>
>> mvn install
>> mvn scalate:deploy
>>
>> So it's not a pure mvn site:deploy.
>>
>> I'm going to discuss with Joe (from the Infra) to see if it could work "out
>> of the box" using scalate:deploy or if we need to perform some update on
>> scalate to use something similar to site:deploy.
>>
>> A possible workaround is to use:
>>
>> mvn scalate:sitegen
>> mvn site:deploy
>>
>> I think it should work.
>>
>> I will keep you posted about that.
>>
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [INFO] Karaf and ServiceMix website
Posted by James Strachan <ja...@fusesource.com>.
FWIW scalate:deploy is using pretty much identical code under the
covers- reusing the same mvn wagon stuff to do the upload; so I'd have
thought it'd just work.
On 9 March 2012 07:45, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi all,
>
> as you probably know, the Apache Infrastructure team has mandated that all
> projects move to the new svnpubsub process for publishing their website by
> the end of the year.
>
> The purpose is to reduce the sync time and the I/O required to the sync.
>
> The Infra worked with the Maven team, and a simple mvn site:deploy works
> fine.
> However, as our website use scalate, we do:
>
> mvn install
> mvn scalate:deploy
>
> So it's not a pure mvn site:deploy.
>
> I'm going to discuss with Joe (from the Infra) to see if it could work "out
> of the box" using scalate:deploy or if we need to perform some update on
> scalate to use something similar to site:deploy.
>
> A possible workaround is to use:
>
> mvn scalate:sitegen
> mvn site:deploy
>
> I think it should work.
>
> I will keep you posted about that.
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
--
James
-------
FuseSource
Email: james@fusesource.com
Web: http://fusesource.com
Twitter: jstrachan, fusenews
Blog: http://macstrac.blogspot.com/
Open Source Integration and Messaging
Re: [INFO] Karaf and ServiceMix website
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Thanks for the update Olivier.
I think it should work as the pubsub can monitor a location whatever the
content is. It can run a Jenkins build just after.
I will keep you posted about the result of the Joe's talk.
Regards
JB
On 03/10/2012 03:02 PM, Olivier Lamy wrote:
> Hello
>
> 2012/3/9 Jean-Baptiste Onofré<jb...@nanthrax.net>:
>> Hi all,
>>
>> as you probably know, the Apache Infrastructure team has mandated that all
>> projects move to the new svnpubsub process for publishing their website by
>> the end of the year.
>>
>> The purpose is to reduce the sync time and the I/O required to the sync.
>>
>> The Infra worked with the Maven team, and a simple mvn site:deploy works
>> fine.
> Not exactly.
> The usual site:deploy won't work anymore as today.
> Some start of doc: http://www.apache.org/dev/cmsadoption.html#maven .
> Basically a buildbot job pool svn to know if there are some changes in
> svn (with maven site xdoc or apt files), if yes mvn site is launched
> in a maven build and content/diff of generated site is committed to
> svn. Then with asf cms ui you have to publish the site.
> You can probably discuss with joe to have a test instance as we did for maven.
>
> HTH,
> --
> Olivier
>
>> However, as our website use scalate, we do:
>>
>> mvn install
>> mvn scalate:deploy
>>
>> So it's not a pure mvn site:deploy.
>>
>> I'm going to discuss with Joe (from the Infra) to see if it could work "out
>> of the box" using scalate:deploy or if we need to perform some update on
>> scalate to use something similar to site:deploy.
>>
>> A possible workaround is to use:
>>
>> mvn scalate:sitegen
>> mvn site:deploy
>>
>> I think it should work.
>>
>> I will keep you posted about that.
>>
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [INFO] Karaf and ServiceMix website
Posted by Olivier Lamy <ol...@apache.org>.
Hello
2012/3/9 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> Hi all,
>
> as you probably know, the Apache Infrastructure team has mandated that all
> projects move to the new svnpubsub process for publishing their website by
> the end of the year.
>
> The purpose is to reduce the sync time and the I/O required to the sync.
>
> The Infra worked with the Maven team, and a simple mvn site:deploy works
> fine.
Not exactly.
The usual site:deploy won't work anymore as today.
Some start of doc: http://www.apache.org/dev/cmsadoption.html#maven .
Basically a buildbot job pool svn to know if there are some changes in
svn (with maven site xdoc or apt files), if yes mvn site is launched
in a maven build and content/diff of generated site is committed to
svn. Then with asf cms ui you have to publish the site.
You can probably discuss with joe to have a test instance as we did for maven.
HTH,
--
Olivier
> However, as our website use scalate, we do:
>
> mvn install
> mvn scalate:deploy
>
> So it's not a pure mvn site:deploy.
>
> I'm going to discuss with Joe (from the Infra) to see if it could work "out
> of the box" using scalate:deploy or if we need to perform some update on
> scalate to use something similar to site:deploy.
>
> A possible workaround is to use:
>
> mvn scalate:sitegen
> mvn site:deploy
>
> I think it should work.
>
> I will keep you posted about that.
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [INFO] Karaf and ServiceMix website
Posted by James Strachan <ja...@fusesource.com>.
FWIW scalate:deploy is using pretty much identical code under the
covers- reusing the same mvn wagon stuff to do the upload; so I'd have
thought it'd just work.
On 9 March 2012 07:45, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi all,
>
> as you probably know, the Apache Infrastructure team has mandated that all
> projects move to the new svnpubsub process for publishing their website by
> the end of the year.
>
> The purpose is to reduce the sync time and the I/O required to the sync.
>
> The Infra worked with the Maven team, and a simple mvn site:deploy works
> fine.
> However, as our website use scalate, we do:
>
> mvn install
> mvn scalate:deploy
>
> So it's not a pure mvn site:deploy.
>
> I'm going to discuss with Joe (from the Infra) to see if it could work "out
> of the box" using scalate:deploy or if we need to perform some update on
> scalate to use something similar to site:deploy.
>
> A possible workaround is to use:
>
> mvn scalate:sitegen
> mvn site:deploy
>
> I think it should work.
>
> I will keep you posted about that.
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
--
James
-------
FuseSource
Email: james@fusesource.com
Web: http://fusesource.com
Twitter: jstrachan, fusenews
Blog: http://macstrac.blogspot.com/
Open Source Integration and Messaging