Duh, sorry, yes, thanks, I see them now too.
http://jakarta.apache.org/commons/images/
Mark R. Diggory wrote:
Ok, I'll add the images (and possibly adjust the url's in the css).
Henri Yandell wrote:
Because the images needed are not in:
http://jakarta.apache.org/commons/images/
which is wher
Ok, I'll add the images (and possibly adjust the url's in the css).
Henri Yandell wrote:
Because the images needed are not in:
http://jakarta.apache.org/commons/images/
which is where the relative link in the stylesheet appears to look [rather
than being relative to the location of the html page
Because the images needed are not in:
http://jakarta.apache.org/commons/images/
which is where the relative link in the stylesheet appears to look [rather
than being relative to the location of the html page].
I've copied the images created by a new site generation of io
[http://www.apache.org/
I wonder why your headings are "square" while others are "rounded".
http://jakarta.apache.org/commons/collections/
http://jakarta.apache.org/commons/math/
http://jakarta.apache.org/commons/lang/
-Mark
Henri Yandell wrote:
Just pushed up a new version of this to
http://jakarta.apache.org/commons
Just pushed up a new version of this to
http://jakarta.apache.org/commons/el/pending-maven/index.html
with Mark's latest changes.
Hen
On Wed, 18 Feb 2004, Henri Yandell wrote:
>
> I've mavenised the [el] project. Bit confused as to why it looks so
> different from the Digester/Lang sites etc.
Henri Yandell wrote:
Can't say I get the style issue, but was just worried that I wasn't
getting the standard.
On the logo issue, shouldn't the white jakarta logo be the default one in
the super-pom if that's the style commons are going with?
Just did it earlier, its now standard.
I need to go r
Can't say I get the style issue, but was just worried that I wasn't
getting the standard.
On the logo issue, shouldn't the white jakarta logo be the default one in
the super-pom if that's the style commons are going with?
I need to go read the commons-build/ stuff I suspect.
Hen
On Thu, 19 Feb
Henri, I copied the css from your project up into the style directory,
which should automatically update your look.
-Mark
Henri Yandell wrote:
I've mavenised the [el] project. Bit confused as to why it looks so
different from the Digester/Lang sites etc. It has the same css. Am I
using a bad ve
Henri,
No, everything should now stay the same no matter your version of Maven.
This css style is actually hardcoded into
jakarta.apache.org/commons/style
Stephen Colebourne had initially added this css to the commons-build as
the global. If there isn't agreement on the styles, I'd recommend w
I've mavenised the [el] project. Bit confused as to why it looks so
different from the Digester/Lang sites etc. It has the same css. Am I
using a bad version of Maven? [I'm on rc1].
Anyway, it's:
http://jakarta.apache.org/commons/el/pending-maven/
The look and feel isn't good, the logos are bad
On Tue, 17 Feb 2004, matthew.hawthorne wrote:
> I don't think that Maven has inheritable properties files. That's
> something that
> a lot of people seem to ask about.
Ditto, I'm pretty sure there's no inheritence of this.
> Maybe the best way to go about this is to create a small plugin? It
I'll also comment, that by taking over our own commons-site.jsl for the
overall look and feel of the site, we can really customize things like
navigation menu and overal layout of the site to our own specifications!
We will not be dependent on anyone (even developers of the maven xdoc
plugin) i
matthew.hawthorne wrote:
Mark R. Diggory wrote:
Ok, this appears to work across the site as long as the
project.properties for each subproject contains
maven.xdoc.jsl=../commons-build/commons-site.jsl
It appears that even when the the project.xml extends
../commons-build/project.xml that the
Mark R. Diggory wrote:
Ok, this appears to work across the site as long as the
project.properties for each subproject contains
maven.xdoc.jsl=../commons-build/commons-site.jsl
It appears that even when the the project.xml extends
../commons-build/project.xml that the
../commons-build/project.p
Ok, this appears to work across the site as long as the
project.properties for each subproject contains
maven.xdoc.jsl=../commons-build/commons-site.jsl
It appears that even when the the project.xml extends
../commons-build/project.xml that the
../commons-build/project.properties are not inclu
The first NPE was my fault for plaing ${basedir} before the jsl
filename. After this though, there appear to be some Context parameters
that are not set. This is a discrepancy I suspect between xdoc 1.4 and
1.5. My solution is to use the 1.4 site.jsl from the 1.4 xdoc plugin and
just hardcode t
Stephen Colebourne wrote:
I tried doing a [convert] build with maven rc1 and the jsl failed with a
NPE.
I got it too, and havn't had time to track it down.
I don't have time to track it down ATM. Would it not be easier to copy
the project.css into each commons project? Or add to the maven xml
I tried doing a [convert] build with maven rc1 and the jsl failed with a
NPE. I don't have time to track it down ATM. Would it not be easier to copy
the project.css into each commons project? Or add to the maven xml in each
project to retrieve the latest version?
Stephen
From: "Mark R. Diggory" <
This should be placed into commons-build/xdocs/style/project.css which
will make it automatically included into the maven site generation.
As well, I've also added the following to commons-build
http://cvs.apache.org/viewcvs.cgi/jakarta-commons/commons-build/commons-site.jsl
and the follwoing l
I have added a project.css file to the common-build area. It can be used as
a theme file or whatever, and should produce reasonably similar results
using both the 1.4 and 1.5 xdoc plugin. (Getting a similar result is
difficult as everything has changed and the combination of technologies just
ain't
I'm somewhat baffled why there are all these menu xdocs inside
the"stylesheet" directory
http://cvs.apache.org/viewcvs.cgi/jakarta-commons/commons-build/xdocs/stylesheets/menus/
plus "stylesheets" needs to be changed to "style" to be recognized in rc1.
-Mark
I agree we need to use our own sty
"Stephen Colebourne" <[EMAIL PROTECTED]> wrote on 17/02/2004
08:14:21 AM:
> The point is that maven keep changing their mind.
>
> First came classic blue top
> Second came white top, big font, red section titles
> Third (current) is white top, good left, but ridiculous section titles
> see htt
Michael Heuer wrote:
On Mon, 16 Feb 2004, Stephen Colebourne wrote:
The point is that maven keep changing their mind.
First came classic blue top
Second came white top, big font, red section titles
Third (current) is white top, good left, but ridiculous section titles
see http://maven.apache
Michael Heuer wrote:
On Mon, 16 Feb 2004, Stephen Colebourne wrote:
The point is that maven keep changing their mind.
First came classic blue top
Second came white top, big font, red section titles
Third (current) is white top, good left, but ridiculous section titles
see http://maven.apache.o
On Mon, 16 Feb 2004, Stephen Colebourne wrote:
> The point is that maven keep changing their mind.
>
> First came classic blue top
> Second came white top, big font, red section titles
> Third (current) is white top, good left, but ridiculous section titles
> see http://maven.apache.org
>
> We
The point is that maven keep changing their mind.
First came classic blue top
Second came white top, big font, red section titles
Third (current) is white top, good left, but ridiculous section titles
see http://maven.apache.org
We need to divorce ourselves from this. The current project.css on
yeah. just noticed that again myself.
let's build a maven/new version in project-template and deprecated
proposal when we've subsumed all its features.
Hen
On Mon, 16 Feb 2004, Stephen Colebourne wrote:
> There was actually already a 'template' project in the sandbox, but I can
> never remembe
There was actually already a 'template' project in the sandbox, but I can
never remember the name. Ahh. [proposal].
Stephen
From: "Mark R. Diggory" <[EMAIL PROTECTED]>
> I was thinking sandbox, because thats where all projects start out and
> its logical that they won't know where commons-build
Stephen, most of the maven site already have stylesheets to address your
concern.
Tim
On Mon, 16 Feb 2004, Stephen Colebourne wrote:
> Once again, this misses the point for me. The newer maven style is much
> worse not better. We need a L+F that is controlled by commons, not by
> whatever maven
From: "Mark R. Diggory" <[EMAIL PROTECTED]>
> ${maven.xdoc.theme.url}
>
> the contents of this css will override any project.css or print.css
> properties.
Are you proposing that 'theme' is the best override point for a commons css?
It sounds as though its placed about right. It appears to not be
yes they do, there are a few things there that don't need to be though:
these can be left out of the project.xml
http://jakarta.apache.org/commons/io/
jakarta.apache.org
/www/jakarta.apache.org/commons/io/
scm:cvs:pserver:[EMAIL PROTECTED]:/home/cvspublic:jakarta-commons/io
Henri Yandell wrote:
On Mon, 16 Feb 2004, Mark R. Diggory wrote:
I think we should setup a project-template directory somewhere, maybe in
the sandbox. It will contian something like:
project-template/
project-template/LICENSE.txt
Currently the LICENSE.txt in commons-build is the new 2.0 one,
Henri Yandell wrote:
I'd just started in commons-build/template, but sandbox sounds fine too.
If you want to just point me to the ideal maven config [I started using
IO], then I can go ahead and get most of it done for you and let you fix
any minor issues left.
Hen
I was thinking sandbox, becau
On 16 Feb 2004, at 03:56, Tim O'Brien wrote:
Hey, someone is publishing Commons Maven sites with an unreleased
version of Maven. Probably either from Maven's CVS HEAD, or a beta
version.
BeanUtils, Betwixt, and Digester all have the newish Maven L+F. A
decision was reached a while back to st
Once again, this misses the point for me. The newer maven style is much
worse not better. We need a L+F that is controlled by commons, not by
whatever maven decides to do today. I'll try and play tonight.
Stephen
- Original Message -
From: <[EMAIL PROTECTED]>
> And the 'new look and feel
And the 'new look and feel' can be done by using RC1 and the included
xdocs/project.css (from memory).
--
dIon Gillard, Multitask Consulting
"Martin Cooper" <[EMAIL PROTECTED]> wrote on 16/02/2004 03:17:00 PM:
>
>
> > -Original Message-
> > From: Tim O'Brien [mailto:[EMAIL PROTECTED]
Alright, Mark I defer to your wise judgement.
Thanks, BTW, for coordinating the java-repository stuff, that's a good
step in the right direction.
Tim
Mark R. Diggory wrote:
Tim,
You don't need to be working with the cvs head of maven to get this look
and feel, simply upgrading the xdoc plugin
Tim,
You don't need to be working with the cvs head of maven to get this look
and feel, simply upgrading the xdoc plugin to its latest release (1.5)
produces the new L&F.
%maven -DgroupId=maven -DartifactId=maven-xdoc-plugin -Dversion=1.5
plugin:download
And your site will have the new look a
Martin Cooper wrote:
-Original Message-
From: Tim O'Brien [mailto:[EMAIL PROTECTED]
Hey, someone is publishing Commons Maven sites with an unreleased
version of Maven. Probably either from Maven's CVS HEAD, or a
beta version.
BeanUtils, Betwixt, and Digester all have the newish Maven L+F.
> -Original Message-
> From: Tim O'Brien [mailto:[EMAIL PROTECTED]
> Sent: Sunday, February 15, 2004 7:57 PM
> To: [EMAIL PROTECTED]
> Subject: [all] maven sites
>
>
> Hey, someone is publishing Commons Maven sites with an unreleased
> version of Maven. Probably either from Maven's CVS H
40 matches
Mail list logo
