You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Felix Knecht <fe...@apache.org> on 2007/11/04 17:44:51 UTC
Re: Buildsystem studio
I've still no commit access to the sandbox directory. Never the less I started to adapt the doc "Build Apache Directory
Studio" and put it into the Apache Directory Sandbox [1] (I think that's the way do to).
Still some questions I couldn't find (or haven't seen) an answer in the docs:
a) Which svn:keywords are set and used? Looking at some files I can see different svn:keywords set, but they not always
seem to match with the references in the code.
If no rule exists yet I'd like to suggest the following:
svn:keyword Id
/**
* Foo bar
*
* @author <a href="mailto:dev@directory.apache.org">Apache Directory Project</a>
* @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z felix $
*/
b) I haven't found any documentation about project/modules/code which is done automatically (e.g. maven reports, maven
site, JavaDocs, ...).
Is this all done either in the cwiki or packaged into a downloadable/buildable distribution?
c) Do any ideas about automated continuous integration exists, e.g. continuum?
Regards
Felix
[1] http://cwiki.apache.org/confluence/x/txEB
Re: Buildsystem studio
Posted by Emmanuel Lecharny <el...@gmail.com>.
Stefan Seelmann wrote:
> Felix Knecht schrieb:
>
>> I've still no commit access to the sandbox directory.
>>
>
> That's bad. Emmanuel, could you help please?
>
Damnit !!! I have added Felix to the authorized committers, but I forgot
to commit the file :)
Fixed.
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
Re: Buildsystem studio
Posted by Emmanuel Lecharny <el...@gmail.com>.
>> Yes, we have a continous build. Chris Custine set it up together with PAM.
>>
>
> Is this 'tool' based or just a cron job - or do I missunderstand PAM (Pluggable Authentication Modul)?
>
It's a tool based.
Pam = Pierre-Arnaud Marcelot, aka 'Plugin Apache Master' ;)
> Felix
>
>
>
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
Re: Buildsystem studio
Posted by Stefan Seelmann <se...@apache.org>.
Felix Knecht schrieb:
>>> Never the less I started to adapt the doc "Build Apache Directory
>>> Studio" and put it into the Apache Directory Sandbox [1] (I think that's the way do to).
>>>
>> Just perfect, is the maven build already working? I am very curious :-)
>
> More or less. I can build
> - userguides
> - updatesite
> - single distribution for linux (at least I could yesterday).
>
> At the moment there are some things still done via ant-run tasks within maven. This could be avoided writing our own
> maven plugins for this.
>
>> Yes, we have a continous build. Chris Custine set it up together with PAM.
>
> Is this 'tool' based or just a cron job - or do I missunderstand PAM (Pluggable Authentication Modul)?
>
Oh, sorry. PAM is the acronym of Pierre-Arnaud Marcelot ;-)
@Chris, Pierre-Arnaud: Could you please give some more information?
Regards,
Stefan
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
>> Never the less I started to adapt the doc "Build Apache Directory
>> Studio" and put it into the Apache Directory Sandbox [1] (I think that's the way do to).
>>
>
> Just perfect, is the maven build already working? I am very curious :-)
More or less. I can build
- userguides
- updatesite
- single distribution for linux (at least I could yesterday).
At the moment there are some things still done via ant-run tasks within maven. This could be avoided writing our own
maven plugins for this.
>
> Yes, we have a continous build. Chris Custine set it up together with PAM.
Is this 'tool' based or just a cron job - or do I missunderstand PAM (Pluggable Authentication Modul)?
Felix
Re: Buildsystem studio
Posted by Stefan Seelmann <se...@apache.org>.
Felix Knecht schrieb:
> I've still no commit access to the sandbox directory.
That's bad. Emmanuel, could you help please?
> Never the less I started to adapt the doc "Build Apache Directory
> Studio" and put it into the Apache Directory Sandbox [1] (I think that's the way do to).
>
Just perfect, is the maven build already working? I am very curious :-)
> Still some questions I couldn't find (or haven't seen) an answer in the docs:
>
> a) Which svn:keywords are set and used? Looking at some files I can see different svn:keywords set, but they not always
> seem to match with the references in the code.
>
> If no rule exists yet I'd like to suggest the following:
>
> svn:keyword Id
>
> /**
> * Foo bar
> *
> * @author <a href="mailto:dev@directory.apache.org">Apache Directory Project</a>
> * @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z felix $
> */
>
Hm, I am not familiar with svn:keywords. However in our source file we
use the following header:
/**
* ...
*
* @author <a href="mailto:dev@directory.apache.org">Apache Directory
Project</a>
* @version $Rev$, $Date$
*/
> b) I haven't found any documentation about project/modules/code which is done automatically (e.g. maven reports, maven
> site, JavaDocs, ...).
> Is this all done either in the cwiki or packaged into a downloadable/buildable distribution?
>
We have an ant task "javadoc" to generate Javadocs. But no other
automatically generated docu. The other cwiki pages are created manually.
>
> c) Do any ideas about automated continuous integration exists, e.g. continuum?
Yes, we have a continous build. Chris Custine set it up together with PAM.
>
> Regards
> Felix
>
> [1] http://cwiki.apache.org/confluence/x/txEB
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
After having some diner apologize for the questions below. For sure you'll this has been discussed in the beginning and
it's not up to me to rise such questions (they just came up because obviously not that much people new about the CI server).
Reading Chris' mail to setup a new server maybe this weekend it's definitely not the time to put a working system into
question.
Sorry
Felix
>>
>> I think Chris setup TeamCity from JetBrains on his servers.
>
> Just back from the TeamCity page to questions:
> 1. maven 2.0.6 is bundled but you can also configure an external one 2.0.4 - 2.0.6. We should be sure that 2.0.7 works
> also because 2.0.6 is quite buggy (probably it will work).
> 2. It's recommend to use MySQL instead of hsqldb as backend db. I'm not sure if ASF can run into license problems when
> using MySQL instead of hsqldb (which I also wouldn't recommend). This should be check in advance even when we get
> TeamCity as OSS project for free.
> 3. Do we have some (internal or external) synergies when using TeamCity instead of an ASF product?
>
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
>
> >
> > c) Do any ideas about automated continuous integration exists,
> e.g. continuum?
> >
> We tried continuum once upon a time, we also tried bamboo, and we
> currently have some another continuous integration server running,
>
>
> I think Chris setup TeamCity from JetBrains on his servers.
Just back from the TeamCity page to questions:
1. maven 2.0.6 is bundled but you can also configure an external one 2.0.4 - 2.0.6. We should be sure that 2.0.7 works
also because 2.0.6 is quite buggy (probably it will work).
2. It's recommend to use MySQL instead of hsqldb as backend db. I'm not sure if ASF can run into license problems when
using MySQL instead of hsqldb (which I also wouldn't recommend). This should be check in advance even when we get
TeamCity as OSS project for free.
3. Do we have some (internal or external) synergies when using TeamCity instead of an ASF product?
Once Chris
> get's some free
> time we intend to move this setup over to a dedicated server with much
> more power and
> network bandwidth. The resources have been acquired it's just a time thing.
>
> Felix if you want to be involved in building up this environment let me
> know and we can
> work together with Chris as well to set it up sooner rather than later.
>
If I can help I'll do.
> but
> we would like to speed up the tests a lot before fully activating the
> continuous build again. FYI, building the server 'cost' 20 minutes on my
> laptop, and around 10 minutes on a fast server. We also have had by
> spamming experience with continuous integration (a mail every 3 minutes
> sent to the full dev list - 200 peeps - 2 days long ...), so we are not
> really keen to play this game again, unless someone who *knows* how to
> correctly setup such an environment handle it (ie, not me, obviously :)
>
>
> Yes this was killing Chris' hardware and there were some other issues.
> However
> we should not have the same issues with the new dedicated machine. Once
> we have
> this changelog and the ability to revert the server for tests instead of
> stopping,
> destroying, reinstalling and restarting the server the tests will run on
> the order of
> 5-10X faster. I personally use a ramdrive to speed things up but I only
> get a 2X
> improvement: this is a hack.
>
> Anyways I would like to setup the new build/CI server to do a few things:
>
> o synchronize a partial read-only mirror repository off of
> http://svn.apache.org/repos/asf/directory
> o use this read-only repository for checkouts and to trigger events via
> custom hooks
> - takes load off of Apache repository
> - much faster since checkouts are local
> - simplifies managing custom hooks
> o build unofficial daily snapshots and expose for testing and download
> o perform standard CI sequence with repository changes
> o integrate VSLDAP conformance tests with CI on dedicated VSLDAP server
> o deploy builds to SLAMD environment for accumulating a panel of simple
> performance metrics
> used to correlate changes to the server
>
> This is pretty ambitious and will take some time but we have the tools
> to do the job. The pay
> off I think with automating all this is huge and so the time expense is
> well worth it.
Yep it sounds like a lot of work is waiting.
Felix
>
> Alex
>
>
>
>
>
Re: Buildsystem studio
Posted by Alex Karasulu <ak...@apache.org>.
Hi guys,
On 11/5/07, Emmanuel Lecharny <el...@gmail.com> wrote:
>
> Hi Felix,
>
> Felix Knecht wrote:
> > I've still no commit access to the sandbox directory. Never the less I
> started to adapt the doc "Build Apache Directory
> > Studio" and put it into the Apache Directory Sandbox [1] (I think that's
> the way do to).
> >
> Hmmm... Let me check that this afternoon...
> > Still some questions I couldn't find (or haven't seen) an answer in the
> docs:
> >
> > a) Which svn:keywords are set and used? Looking at some files I can see
> different svn:keywords set, but they not always
> > seem to match with the references in the code.
> >
> There is no current list of used svn:keywords...
> > If no rule exists yet I'd like to suggest the following:
> >
> > svn:keyword Id
> >
> > /**
> > * Foo bar
> > *
> > * @author <a href="mailto:dev@directory.apache.org">Apache Directory
> Project</a>
> > * @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z felix
> $
> > */
> >
> We are not using names into header. Here are our coding standards :
>
> http://cwiki.apache.org/DIRxDEV/coding-standards.html
I guess this is the result of a substitution performed by SVN on the Id
macro. I don't think
Felix was intending to add an @author tag which is essentially the basis of
the ASF wide
recommendation.
I know there are distinct rules about the @author tag but did we ever agree
on whether or not
to use other tags like Id, Date, Revision etc? Can't remember sorry.
> b) I haven't found any documentation about project/modules/code which is
> done automatically (e.g. maven reports, maven
> > site, JavaDocs, ...).
> > Is this all done either in the cwiki or packaged into a
> downloadable/buildable distribution?
> >
> We don't anymore generate the site from code, we use confluence for that.
>
> We should generate Javadocs though, but I'm not a maven guru enough to
> guarantee that the current maven configuration allows that. And I would
> add that I would be very pleased if you can tell me ;)
>
> Generating maven reports would be a very valuable addition, too !
+1
It would be nice if we integrated nicely the javadocs and reports so they
deployed to areas that our
confluence generated site can point to by default.
>
> > c) Do any ideas about automated continuous integration exists, e.g.
> continuum?
> >
> We tried continuum once upon a time, we also tried bamboo, and we
> currently have some another continuous integration server running,
I think Chris setup TeamCity from JetBrains on his servers. Once Chris
get's some free
time we intend to move this setup over to a dedicated server with much more
power and
network bandwidth. The resources have been acquired it's just a time thing.
Felix if you want to be involved in building up this environment let me know
and we can
work together with Chris as well to set it up sooner rather than later.
but
> we would like to speed up the tests a lot before fully activating the
> continuous build again. FYI, building the server 'cost' 20 minutes on my
> laptop, and around 10 minutes on a fast server. We also have had by
> spamming experience with continuous integration (a mail every 3 minutes
> sent to the full dev list - 200 peeps - 2 days long ...), so we are not
> really keen to play this game again, unless someone who *knows* how to
> correctly setup such an environment handle it (ie, not me, obviously :)
Yes this was killing Chris' hardware and there were some other issues.
However
we should not have the same issues with the new dedicated machine. Once we
have
this changelog and the ability to revert the server for tests instead of
stopping,
destroying, reinstalling and restarting the server the tests will run on the
order of
5-10X faster. I personally use a ramdrive to speed things up but I only get
a 2X
improvement: this is a hack.
Anyways I would like to setup the new build/CI server to do a few things:
o synchronize a partial read-only mirror repository off of
http://svn.apache.org/repos/asf/directory
o use this read-only repository for checkouts and to trigger events via
custom hooks
- takes load off of Apache repository
- much faster since checkouts are local
- simplifies managing custom hooks
o build unofficial daily snapshots and expose for testing and download
o perform standard CI sequence with repository changes
o integrate VSLDAP conformance tests with CI on dedicated VSLDAP server
o deploy builds to SLAMD environment for accumulating a panel of simple
performance metrics
used to correlate changes to the server
This is pretty ambitious and will take some time but we have the tools to do
the job. The pay
off I think with automating all this is huge and so the time expense is well
worth it.
Alex
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hey Chris,
No problem.
Tell me if you need some help to build this up.
P-A
On Nov 5, 2007 8:06 PM, Chris Custine <cc...@apache.org> wrote:
>
> We are in the process of moving the build server over to a more powerful
> platform and I have been delayed because of the new job. I think we have
> all of the hardware in order now so maybe this weekend...
>
> Chris
>
Re: Buildsystem studio
Posted by Chris Custine <cc...@apache.org>.
On 11/5/07, Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
>
> Hi Felix and everyone,
>
> I can't wait to test this new Maven build... :)
>
> As Stefan said, we have a continuous integration build system running on
> Chris Custine's server. The address is : http://builds.organicelement.com, but it seems to be down today...
We are in the process of moving the build server over to a more powerful
platform and I have been delayed because of the new job. I think we have
all of the hardware in order now so maybe this weekend...
Chris
As far as I remember the server is running TeamCity and uses the 'release'
> ant task from Studio's build system to generate archives (.zip and .tar.gz
> files) for each OS/Platform.
>
> Regards,
> Pierre-Arnaud (aka PAM...)
>
> On Nov 5, 2007 11:57 AM, Felix Knecht <fe...@apache.org> wrote:
>
> > >>
> > > There is no current list of used svn:keywords...
> > >> If no rule exists yet I'd like to suggest the following:
> > >>
> > >> svn:keyword Id
> > >>
> > >> /**
> > >> * Foo bar
> > >> *
> > >> * @author <a href="mailto:dev@directory.apache.org">Apache Directory
> > >> Project</a>
> > >> * @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z
> > felix $
> > >> */
> > >>
> > > We are not using names into header. Here are our coding standards :
> > >
> > > http://cwiki.apache.org/DIRxDEV/coding-standards.html
> >
> > It's not a fix name, but just the name of the committer who did the
> > latest commit:
> >
> >
> > http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html
> >
> > In most java classes I can find the svn:keywords [date and/or revision]
> > already now. But they are not used consequently
> > the same way and also not always set as svn:keywords to the file when
> > used within the file.
> >
> > >
> > >> b) I haven't found any documentation about project/modules/code which
> > >> is done automatically (e.g. maven reports, maven
> > >> site, JavaDocs, ...).
> > >> Is this all done either in the cwiki or packaged into a
> > >> downloadable/buildable distribution?
> > >>
> > > We don't anymore generate the site from code, we use confluence for
> > that.
> > >
> > > We should generate Javadocs though, but I'm not a maven guru enough to
> >
> > > guarantee that the current maven configuration allows that. And I
> > would
> > > add that I would be very pleased if you can tell me ;)
> > >
> > > Generating maven reports would be a very valuable addition, too !
> >
> > I'll try to add this to the maven studio build.
> >
> > >>
> > >> c) Do any ideas about automated continuous integration exists, e.g.
> > >> continuum?
> > >>
> > > We tried continuum once upon a time, we also tried bamboo, and we
> > > currently have some another continuous integration server running, but
> > > we would like to speed up the tests a lot before fully activating the
> > > continuous build again. FYI, building the server 'cost' 20 minutes on
> > my
> > > laptop, and around 10 minutes on a fast server. We also have had by
> > > spamming experience with continuous integration (a mail every 3
> > minutes
> > > sent to the full dev list - 200 peeps - 2 days long ...), so we are
> > not
> > > really keen to play this game again, unless someone who *knows* how to
> > > correctly setup such an environment handle it (ie, not me, obviously
> > :)
> >
> > I think there are already running some continuum instances within
> > apache. Maybe the infrastructure team has more
> > knowledge about such running instances and if the directory project can
> > hang on onto an already existing instance.
> >
> >
> > > I have added you in
> > > http://cwiki.apache.org/confluence/display/directory/The+team
> >
> > Thanks. I already did but haven't noticed the alphabetic ordering and
> > added me at the bottom. So this is fixed now.
> > >
> > > Fell free to add a picture (small one :), your web site, blog, to this
> > > page !
> >
> > I only have my companys website if this would also be ok?
> >
> > >
> > > Thanks !
> > >
> >
> >
>
Re: Buildsystem studio
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Felix and everyone,
I can't wait to test this new Maven build... :)
As Stefan said, we have a continuous integration build system running on
Chris Custine's server. The address is : http://builds.organicelement.com ,
but it seems to be down today...
As far as I remember the server is running TeamCity and uses the 'release'
ant task from Studio's build system to generate archives (.zip and .tar.gz
files) for each OS/Platform.
Regards,
Pierre-Arnaud (aka PAM...)
On Nov 5, 2007 11:57 AM, Felix Knecht <fe...@apache.org> wrote:
> >>
> > There is no current list of used svn:keywords...
> >> If no rule exists yet I'd like to suggest the following:
> >>
> >> svn:keyword Id
> >>
> >> /**
> >> * Foo bar
> >> *
> >> * @author <a href="mailto:dev@directory.apache.org">Apache Directory
> >> Project</a>
> >> * @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z felix
> $
> >> */
> >>
> > We are not using names into header. Here are our coding standards :
> >
> > http://cwiki.apache.org/DIRxDEV/coding-standards.html
>
> It's not a fix name, but just the name of the committer who did the latest
> commit:
>
>
> http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html
>
> In most java classes I can find the svn:keywords [date and/or revision]
> already now. But they are not used consequently
> the same way and also not always set as svn:keywords to the file when used
> within the file.
>
> >
> >> b) I haven't found any documentation about project/modules/code which
> >> is done automatically (e.g. maven reports, maven
> >> site, JavaDocs, ...).
> >> Is this all done either in the cwiki or packaged into a
> >> downloadable/buildable distribution?
> >>
> > We don't anymore generate the site from code, we use confluence for
> that.
> >
> > We should generate Javadocs though, but I'm not a maven guru enough to
> > guarantee that the current maven configuration allows that. And I would
> > add that I would be very pleased if you can tell me ;)
> >
> > Generating maven reports would be a very valuable addition, too !
>
> I'll try to add this to the maven studio build.
>
> >>
> >> c) Do any ideas about automated continuous integration exists, e.g.
> >> continuum?
> >>
> > We tried continuum once upon a time, we also tried bamboo, and we
> > currently have some another continuous integration server running, but
> > we would like to speed up the tests a lot before fully activating the
> > continuous build again. FYI, building the server 'cost' 20 minutes on my
> > laptop, and around 10 minutes on a fast server. We also have had by
> > spamming experience with continuous integration (a mail every 3 minutes
> > sent to the full dev list - 200 peeps - 2 days long ...), so we are not
> > really keen to play this game again, unless someone who *knows* how to
> > correctly setup such an environment handle it (ie, not me, obviously :)
>
> I think there are already running some continuum instances within apache.
> Maybe the infrastructure team has more
> knowledge about such running instances and if the directory project can
> hang on onto an already existing instance.
>
>
> > I have added you in
> > http://cwiki.apache.org/confluence/display/directory/The+team
>
> Thanks. I already did but haven't noticed the alphabetic ordering and
> added me at the bottom. So this is fixed now.
> >
> > Fell free to add a picture (small one :), your web site, blog, to this
> > page !
>
> I only have my companys website if this would also be ok?
>
> >
> > Thanks !
> >
>
>
Re: Buildsystem studio
Posted by Felix Knecht <fe...@apache.org>.
>>
> There is no current list of used svn:keywords...
>> If no rule exists yet I'd like to suggest the following:
>>
>> svn:keyword Id
>>
>> /**
>> * Foo bar
>> *
>> * @author <a href="mailto:dev@directory.apache.org">Apache Directory
>> Project</a>
>> * @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z felix $
>> */
>>
> We are not using names into header. Here are our coding standards :
>
> http://cwiki.apache.org/DIRxDEV/coding-standards.html
It's not a fix name, but just the name of the committer who did the latest commit:
http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html
In most java classes I can find the svn:keywords [date and/or revision] already now. But they are not used consequently
the same way and also not always set as svn:keywords to the file when used within the file.
>
>> b) I haven't found any documentation about project/modules/code which
>> is done automatically (e.g. maven reports, maven
>> site, JavaDocs, ...).
>> Is this all done either in the cwiki or packaged into a
>> downloadable/buildable distribution?
>>
> We don't anymore generate the site from code, we use confluence for that.
>
> We should generate Javadocs though, but I'm not a maven guru enough to
> guarantee that the current maven configuration allows that. And I would
> add that I would be very pleased if you can tell me ;)
>
> Generating maven reports would be a very valuable addition, too !
I'll try to add this to the maven studio build.
>>
>> c) Do any ideas about automated continuous integration exists, e.g.
>> continuum?
>>
> We tried continuum once upon a time, we also tried bamboo, and we
> currently have some another continuous integration server running, but
> we would like to speed up the tests a lot before fully activating the
> continuous build again. FYI, building the server 'cost' 20 minutes on my
> laptop, and around 10 minutes on a fast server. We also have had by
> spamming experience with continuous integration (a mail every 3 minutes
> sent to the full dev list - 200 peeps - 2 days long ...), so we are not
> really keen to play this game again, unless someone who *knows* how to
> correctly setup such an environment handle it (ie, not me, obviously :)
I think there are already running some continuum instances within apache. Maybe the infrastructure team has more
knowledge about such running instances and if the directory project can hang on onto an already existing instance.
> I have added you in
> http://cwiki.apache.org/confluence/display/directory/The+team
Thanks. I already did but haven't noticed the alphabetic ordering and added me at the bottom. So this is fixed now.
>
> Fell free to add a picture (small one :), your web site, blog, to this
> page !
I only have my companys website if this would also be ok?
>
> Thanks !
>
Re: Buildsystem studio
Posted by Emmanuel Lecharny <el...@gmail.com>.
Hi Felix,
Felix Knecht wrote:
> I've still no commit access to the sandbox directory. Never the less I started to adapt the doc "Build Apache Directory
> Studio" and put it into the Apache Directory Sandbox [1] (I think that's the way do to).
>
Hmmm... Let me check that this afternoon...
> Still some questions I couldn't find (or haven't seen) an answer in the docs:
>
> a) Which svn:keywords are set and used? Looking at some files I can see different svn:keywords set, but they not always
> seem to match with the references in the code.
>
There is no current list of used svn:keywords...
> If no rule exists yet I'd like to suggest the following:
>
> svn:keyword Id
>
> /**
> * Foo bar
> *
> * @author <a href="mailto:dev@directory.apache.org">Apache Directory Project</a>
> * @version $Id: AbstractStudioMojo.java 350 2007-10-28 12:01:17Z felix $
> */
>
We are not using names into header. Here are our coding standards :
http://cwiki.apache.org/DIRxDEV/coding-standards.html
> b) I haven't found any documentation about project/modules/code which is done automatically (e.g. maven reports, maven
> site, JavaDocs, ...).
> Is this all done either in the cwiki or packaged into a downloadable/buildable distribution?
>
We don't anymore generate the site from code, we use confluence for that.
We should generate Javadocs though, but I'm not a maven guru enough to
guarantee that the current maven configuration allows that. And I would
add that I would be very pleased if you can tell me ;)
Generating maven reports would be a very valuable addition, too !
>
> c) Do any ideas about automated continuous integration exists, e.g. continuum?
>
We tried continuum once upon a time, we also tried bamboo, and we
currently have some another continuous integration server running, but
we would like to speed up the tests a lot before fully activating the
continuous build again. FYI, building the server 'cost' 20 minutes on my
laptop, and around 10 minutes on a fast server. We also have had by
spamming experience with continuous integration (a mail every 3 minutes
sent to the full dev list - 200 peeps - 2 days long ...), so we are not
really keen to play this game again, unless someone who *knows* how to
correctly setup such an environment handle it (ie, not me, obviously :)
> Regards
> Felix
>
> [1] http://cwiki.apache.org/confluence/x/txEB
>
>
Thanks a lot for those insights, felix. There are really interesting.
I have added you in
http://cwiki.apache.org/confluence/display/directory/The+team
Fell free to add a picture (small one :), your web site, blog, to this
page !
Thanks !
--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org