Can we agree on what problems remain currently before Benedikt wastes time on this? AFAIK the remaining problems are:
- Commons Weaver TM link above left menu has Maven artifactId embedded in the href. I haven't yet found where this is coming from; - source info pages for modules also use artifactId inappropriately; hopefully this can be corrected by simply specifying the scm info per module pom If I am correct, the most benefit would come from Bene's investigation of the first issue. Thanks, Matt On Feb 14, 2014 10:13 AM, "sebb" <[email protected]> wrote: > On 14 February 2014 08:54, Benedikt Ritter <[email protected]> wrote: > > The VFS site [1] looks good to me. > > Agreed, VFS + fluido does not have the problems exhibited by Weaver. > > > I'll have a look at the configuration of weaver tomorrow. > > Thanks! > > > Benedikt > > > > [1] http://people.apache.org/~britter/commons-sites-fluido/commons-vfs/ > > > > > > 2014-02-14 2:24 GMT+01:00 Matt Benson <[email protected]>: > > > >> That last is due to the rework of module names. Most of these issues > have > >> been fixed in the last commit. There is an issue where the "Apache > Commons > >> Weaver TM" link points to the wrong place, but I think we'll need to fix > >> that in the skin. The scm issues Bernd noted in the other thread are > going > >> to be a bit more painful to sort out and are definitely a multimodule > >> problem. Does the site generally look better now? > >> > >> Thanks, > >> Matt > >> > >> > >> On Thu, Feb 13, 2014 at 7:14 PM, sebb <[email protected]> wrote: > >> > >> > Just noticed more footer errors, see: > >> > > >> > > >> > > >> > http://commons.apache.org/proper/commons-weaver/commons-weaver/source-repository.html > >> > > >> > > >> > http://commons.apache.org/proper/commons-weaver/commons-weaver/project-info.html > >> > > >> > Also the header shows > >> > > >> > Apache Commons Weaver Parent POM (tm) Last Published: 13 > February > >> > 2014 > >> > > >> > There also seem to be additional commons-weaver path segments in lots > >> > of links, for example: > >> > > >> > The _Commons Weaver Core_ defines a > >> > links to > >> > > >> > http://commons.apache.org/proper/commons-weaver/commons-weaver/index.html > >> > which is actually not about the core. > >> > > >> > Not sure what has happened here. This may not be due to the new skin, > >> > but it is clearly wrong. > >> > > >> > > >> > On 14 February 2014 01:05, sebb <[email protected]> wrote: > >> > > Parent POM > >> > > > >> > > On 14 February 2014 01:04, Matt Benson <[email protected]> > wrote: > >> > >> Are you saying it actually shows ellipses, or are you talking about > >> > "Parent > >> > >> POM"? > >> > >> > >> > >> Matt > >> > >> > >> > >> > >> > >> On Thu, Feb 13, 2014 at 6:48 PM, sebb <[email protected]> wrote: > >> > >> > >> > >>> There's a problem with the weaver wbesite footer, it says: > >> > >>> > >> > >>> Apache Commons, Apache Commons Weaver Parent POM, Apache, ...are > >> > >>> trademarks of ... > >> > >>> > >> > >>> AFAIK, VFS is also a multi-module build, but it does not havethe > same > >> > >>> problem. It is currently using the old skin. > >> > >>> > >> > >>> I don't know if the "foot fault" is a problem with the skin or a > >> > >>> configuration error, but it needs to be fixed please. > >> > >>> > >> > >>> > --------------------------------------------------------------------- > >> > >>> To unsubscribe, e-mail: [email protected] > >> > >>> For additional commands, e-mail: [email protected] > >> > >>> > >> > >>> > >> > > >> > > > > > > > > -- > > http://people.apache.org/~britter/ > > http://www.systemoutprintln.de/ > > http://twitter.com/BenediktRitter > > http://github.com/britter > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
