On 28 April 2015 at 07:06, Sergio Fernández <[email protected]> wrote:
> Really good stuff! Thanks! >> to test it see >> https://gist.github.com/stain/3c310f87c4465541be66 > I'd also add that gist to the user guide, maybe at the end, I think brings > value to it. OK, in that case I think better put it under our source control, not sure where as it should not be part of the release build Maven-wise, so I just put it under examples/ for now. http://commonsrdf.incubator.apache.org/userguide.html#Complete_example links to https://github.com/apache/incubator-commonsrdf/blob/master/examples/src/example/UserGuideTest.java but also describes it as under the examples/ folder of the source code repository. BTW: http://commonsrdf.incubator.apache.org/source-repository.html leaves something to be desired as those git.apache.org URIs are not very useful in the browser. Ideally this should also point to GitHub repo and show basic build instructions (e.g. link to https://github.com/apache/incubator-commonsrdf#building ) I also see we have an additional top-level link in the menu "Source (git)" which goes directly to https://git-wip-us.apache.org/repos/asf?p=incubator-commonsrdf.git where it is not clear what is the source code or how to check out. > There is a velocity-base trick to use the pom version at the content (I > used it in Marmotta). I'll try to implement it for our website too. That would be brilliant. The alternative is to do something like this and deliberately not have valid <version>: http://jena.apache.org/download/maven.html .. but given that the commons-rdf site is updated per release (at least) it should be possible to do something more clever - although I suspect it could mean that it would then say -SNAPSHOT in the docs if we update the site outside a release.. -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718
