You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Carlos Sanchez <ca...@apache.org> on 2007/05/17 00:00:46 UTC
Building the reports
Right now if I try to build the maven site from a subproject it fails
due to references to a template
Template file '...felix\tools\maven2\maven-bundle-plugin\src\site\maven-site.vm'
does not exist
Any interest if I refactor it to use site.xml to add the links (will
work in any subproject as it's deployed to the repo) and maven skins
for the css (do you realy need a custom css?)
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Building the reports
Posted by Carlos Sanchez <ca...@apache.org>.
On 5/18/07, Marcel Offermans <ma...@luminis.nl> wrote:
> >> One question I have, btw, is do we create a site for each subproject,
> >> or one big site with all of them? Since probably each subproject will
> >> do a separate release, it might make sense to have a site per
> >> subproject (with subproject not necessarily mapping to one individual
> >> bundle, some subprojects have multiple bundles).
> > the site is generated for each module and then in the parent you can
> > do some aggregate stuff, the cool thing is that i don't have to build
> > the whole project to get a submodule report, which is cool for team
> > work.
>
> Is there a way to create a deeper hierarchy than only the project/
> submodule you describe now? I'm thinking of project/module/bundle.
maven uses the parent site location + artifactId
if you have A -> B -> C and A site is deployed to /site then
B goes to /site/B
C goes to /site/B/C
by default
>
> Greetings, Marcel
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Building the reports
Posted by Felix Meschberger <Fe...@day.com>.
Hi,
To be honest, I would love to use any CI server, but I don't think
> there is such a server at apache now.
There is a thing called Zones, which is actually something like a virtual
server. In such a such, we can setup a CI. We have a zone with Continuum
over in the Jackrabbit Project.
More information can be found here:
http://www.apache.org/dev/solaris-zones.html
Regards
Felix
Re: Building the reports
Posted by Marcel Offermans <ma...@luminis.nl>.
Hello Carlos,
On May 17, 2007, at 6:15 , Carlos Sanchez wrote:
> so basically the maven site is not used at all
> I may give it a try then
Ok, thanks!
> I'd suggest you to use Continuum :D <selfpromotion> is the best CI
> server! </selfpromotion>
:)
To be honest, I would love to use any CI server, but I don't think
there is such a server at apache now.
>> One question I have, btw, is do we create a site for each subproject,
>> or one big site with all of them? Since probably each subproject will
>> do a separate release, it might make sense to have a site per
>> subproject (with subproject not necessarily mapping to one individual
>> bundle, some subprojects have multiple bundles).
> the site is generated for each module and then in the parent you can
> do some aggregate stuff, the cool thing is that i don't have to build
> the whole project to get a submodule report, which is cool for team
> work.
Is there a way to create a deeper hierarchy than only the project/
submodule you describe now? I'm thinking of project/module/bundle.
Greetings, Marcel
Re: Building the reports
Posted by Carlos Sanchez <ca...@apache.org>.
so basically the maven site is not used at all
I may give it a try then
I'd suggest you to use Continuum :D <selfpromotion> is the best CI
server! </selfpromotion>
All that you mention javadocs, source html, code coverage,... and all
the maven reports available can be generated with maven and continuum
just uses that, and then you can do it either in the command line or
in the CI
the site is generated for each module and then in the parent you can
do some aggregate stuff, the cool thing is that i don't have to build
the whole project to get a submodule report, which is cool for team
work.
On 5/16/07, Marcel Offermans <ma...@luminis.nl> wrote:
> Hello Carlos,
>
> On May 17, 2007, at 0:49 , Richard S. Hall wrote:
>
> > On May 16, 2007, at 6:00 PM, Carlos Sanchez wrote:
> >
> >> Right now if I try to build the maven site from a subproject it fails
> >> due to references to a template
> >>
> >> Template file '...felix\tools\maven2\maven-bundle-plugin\src\site
> >> \maven-site.vm'
> >> does not exist
> >>
> >> Any interest if I refactor it to use site.xml to add the links (will
> >> work in any subproject as it's deployed to the repo) and maven skins
> >> for the css (do you realy need a custom css?)
> >
> > I don't know anything about our site, but it sounds good to
> > me...perhaps you should wait to see what Marcel has to say...
>
> Currently, the whole Felix website is generated from the Confluence
> wiki. Confluence has an "auto export" plugin that takes care of this.
> We are using the wiki for our site, instead of generating it from
> maven, because the wiki makes it easier for people to comment or
> contribute. So at the moment, we don't really use the site.xml which
> is probably why it's broken right now. I did setup a template once to
> make sure that the maven site would generate the same header and main
> menu (on the left) but that's a long time ago and I did not keep it
> up to date because we've never used it.
>
> To be honest, I do think we eventually need to include some generated
> artifacts on the website. Ideally, I would like to have a build
> server (preferably Bamboo from Atlassian, which is very nice if you
> ask me) to do continuous (and nightly) builds. Bamboo can then also
> generate artifacts like JavaDoc, (JUnit) test reports, etc. Probably
> we could use maven in this setup (I'm no maven expert, but it can
> probably generate all such artifacts).
>
> In short, if you can fix the site.xml to do this kind of stuff, yes
> please! :)
>
> One question I have, btw, is do we create a site for each subproject,
> or one big site with all of them? Since probably each subproject will
> do a separate release, it might make sense to have a site per
> subproject (with subproject not necessarily mapping to one individual
> bundle, some subprojects have multiple bundles).
>
> Greetings, Marcel
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Building the reports
Posted by Marcel Offermans <ma...@luminis.nl>.
Hello Carlos,
On May 17, 2007, at 0:49 , Richard S. Hall wrote:
> On May 16, 2007, at 6:00 PM, Carlos Sanchez wrote:
>
>> Right now if I try to build the maven site from a subproject it fails
>> due to references to a template
>>
>> Template file '...felix\tools\maven2\maven-bundle-plugin\src\site
>> \maven-site.vm'
>> does not exist
>>
>> Any interest if I refactor it to use site.xml to add the links (will
>> work in any subproject as it's deployed to the repo) and maven skins
>> for the css (do you realy need a custom css?)
>
> I don't know anything about our site, but it sounds good to
> me...perhaps you should wait to see what Marcel has to say...
Currently, the whole Felix website is generated from the Confluence
wiki. Confluence has an "auto export" plugin that takes care of this.
We are using the wiki for our site, instead of generating it from
maven, because the wiki makes it easier for people to comment or
contribute. So at the moment, we don't really use the site.xml which
is probably why it's broken right now. I did setup a template once to
make sure that the maven site would generate the same header and main
menu (on the left) but that's a long time ago and I did not keep it
up to date because we've never used it.
To be honest, I do think we eventually need to include some generated
artifacts on the website. Ideally, I would like to have a build
server (preferably Bamboo from Atlassian, which is very nice if you
ask me) to do continuous (and nightly) builds. Bamboo can then also
generate artifacts like JavaDoc, (JUnit) test reports, etc. Probably
we could use maven in this setup (I'm no maven expert, but it can
probably generate all such artifacts).
In short, if you can fix the site.xml to do this kind of stuff, yes
please! :)
One question I have, btw, is do we create a site for each subproject,
or one big site with all of them? Since probably each subproject will
do a separate release, it might make sense to have a site per
subproject (with subproject not necessarily mapping to one individual
bundle, some subprojects have multiple bundles).
Greetings, Marcel
Re: Building the reports
Posted by "Richard S. Hall" <he...@ungoverned.org>.
On May 16, 2007, at 6:00 PM, Carlos Sanchez wrote:
> Right now if I try to build the maven site from a subproject it fails
> due to references to a template
>
> Template file
> '...felix\tools\maven2\maven-bundle-plugin\src\site\maven-site.vm'
> does not exist
>
> Any interest if I refactor it to use site.xml to add the links (will
> work in any subproject as it's deployed to the repo) and maven skins
> for the css (do you realy need a custom css?)
I don't know anything about our site, but it sounds good to
me...perhaps you should wait to see what Marcel has to say...
-> richard
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride