+1 for the Maven approach, it was straightforward for me to try when attempting to modify a Commons webpage, I like that you can just build it locally, and unlike stuff like Jekyll or the default perl CMS, no strange system libraries to install.
Gary, how would we fit into Commons website-wise while incubating? Could we still use the same system, but publish to commonsrdf.incubator.apache.org? On 11 Mar 2015 21:01, "Gary Gregory" <[email protected]> wrote: > I do not think this VOTE is needed. > > If this component is to live in the Commons project, we already have all > that set up. Just see the site for any the recent components like > https://commons.apache.org/proper/commons-codec/. We have a parent POM to > handle common stuff between components. There are some variations between > the sites for components, sure, but nothing major. > > Gary > > On Wed, Mar 11, 2015 at 1:31 PM, Lewis John Mcgibbney < > [email protected]> wrote: > > > Hi Folks, > > Based on Geoffrey Core's request on INFRA-9260 [0], I would like to open > an > > VOTE for the website build layout. The VOTE will be open for at least 72 > > hours. > > > > Options are > > > > 0 svnpubsub > > 1 CMS (default-Perl-build) > > 2 CMS (Maven-build) > > 3 CMS (Ant-build) > > 4 CMS (Shell-build) > > > > [ ] +1 I VOTE for option ${insert option here} > > [ ] +/-0 I don't care either way but would rather see ${insert option > here} > > [ ] -1 I hate them all and I am not having a good day > > > > Thanks > > Lewis > > > > [0] https://issues.apache.org/jira/browse/INFRA-9260 > > > > -- > > *Lewis* > > > > > > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second Edition > <http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory >
