Hello Chris
Le 04/09/12 00:56, Mattmann, Chris A (388J) a écrit :
Hrm, I wonder if it's complaining that we need a site.vm (velocity macro file)
to generate the site. We
moved to the ASF CMS (per SIS-31 [1]) and Ross Laidlaw helped us get there so
maybe Ross can
suggest how best to build the site now that we don't use Maven to build it
anymore.
Do you mean that the web site is generated not by "mvn site", but by
something else? In such case, we don't really need to fix "mvn site". Or
better and easier, we just need to remove the following lines from the
root pom.xml to fix the issue:
<plugin>
<artifactId>maven-site-plugin</artifactId>
- <configuration>
- <templateDirectory>src/site</templateDirectory>
- <template>site.vm</template>
- </configuration>
</plugin>
Removing the above lines (for now) allow the site build to pass. If
everyone agree, I propose to temporarily remove this configuration. This
would allow me to tune the pom.xml configuration as proposed in
https://issues.apache.org/jira/browse/SIS-56 and test the result (except
the release goal).
On SIS-31 [1], Adam Estrada also uploaded a skeleton version of a new website
theme based on Twitter bootstrap, so it would be great to actually implement
that and get it out there.
I had a look and I have been surprised, its look good!
I'm of Jenkins as a CI tool, and I think it would be fairly easy to set up. In
fact,
I tested this and just went ahead and set us up a Jenkins job:
https://builds.apache.org/job/sis-trunk/
Thanks! I like Jenkins too. Is this one configured for nightly builds?
At which hour? Does it deploys the artifacts and the web site? (actually
I would propose to not deploy yet, since I would like to do SIS-56 first).
Martin
