Hi Andi,
I see failures when the environment variable for forrest is not configured,
this seems to have worked before and probably would be good to not require
forrest when people just want to compile the sources:
BUILD FAILED
/opt/poi-benchmark/sources/build.xml:64: Cannot find
/opt/poi-benchmark/sources/${env.FORREST_HOME}/main/forrest.build.xml
imported from /opt/poi-benchmark/sources/build.xml
If I specify "optional=true" for the import, then some targets like "site"
are missing and ant still complains, seems the dependency on
forrest-sources is a bit to tight now, would probably be better to invoke
the forrest-tasks via a nested ant-call instead.
Dominik.
On Fri, Jul 20, 2018 at 5:17 PM, Mark Murphy <jmarkmur...@gmail.com> wrote:
> Looks good except the Powered by Apache logo is partially blocked by the
> search tab.
>
> On Thu, Jul 19, 2018 at 5:56 PM Andreas Beeker <kiwiwi...@apache.org>
> wrote:
>
> > Hi,
> >
> > I've fixed the rewrite rules and the build.
> >
> > AFAIK there's no jenkins job to generate the site - only the javadoc,
> > otherwise we would need to find a way to inject the forrest resolver into
> > the ant runtime.
> >
> > What do you think about the new tabs layout?
> >
> > The reason for the site subdirs were the corresponding tab dir relations.
> >
> > Andi
> >
> >
> >
>
