Hello,
The page http://jakarta.apache.org/commons/components.html is out of date
WRT lang, httpclient and maybe others.
If every project has a project.xml, maybe the page could be auto-generated
when project is rev'ed?
Gary
--- Gary Gregory [EMAIL PROTECTED] wrote:
Hello,
The page http://jakarta.apache.org/commons/components.html is out of
date
WRT lang, httpclient and maybe others.
If every project has a project.xml, maybe the page could be
auto-generated
when project is rev'ed?
I'd like to see that
I've been playing with something that might be able to replace it, based
on project.xml's:
http://www.apache.org/~bayard/pergamum/j-c/html-j-c-new/community_jakarta-commons.html
Basically a multiproject website that is driven from the top down. Maven
probably has something similar, I was
David Graham wrote:
--- Gary Gregory [EMAIL PROTECTED] wrote:
Hello,
The page http://jakarta.apache.org/commons/components.html is out of
date
WRT lang, httpclient and maybe others.
If every project has a project.xml, maybe the page could be
auto-generated
when project is rev'ed?
I'd like to
On Fri, 2 Jan 2004, David Graham wrote:
--- Gary Gregory [EMAIL PROTECTED] wrote:
Hello,
The page http://jakarta.apache.org/commons/components.html is out of
date
WRT lang, httpclient and maybe others.
If every project has a project.xml, maybe the page could be
auto-generated
--- Martin Cooper [EMAIL PROTECTED] wrote:
On Fri, 2 Jan 2004, David Graham wrote:
--- Gary Gregory [EMAIL PROTECTED] wrote:
Hello,
The page http://jakarta.apache.org/commons/components.html is out of
date
WRT lang, httpclient and maybe others.
If every project has a
I lied. I'm not really talking about a multiproject website as Maven's
multiproject is single-inheritence based and my ideas are more multi-mixin
based.
For example, how can I have Commons-Lang in 3 multiproject websites?
Maven's default website is something I'm already using,
I can see that the release information could easily get out of date, so
I'd be OK with removing that from the page. However, I'd still like to
keep the grouping of released, pre-released, etc. because that is also
useful information for newcomers (and quick-stop visitors).
Sounds good
Stephen Colebourne wrote:
I can see that the release information could easily get out of date, so
I'd be OK with removing that from the page. However, I'd still like to
keep the grouping of released, pre-released, etc. because that is also
useful information for newcomers (and quick-stop
On Fri, 2 Jan 2004, Phil Steitz wrote:
Stephen Colebourne wrote:
+1, keep page, no release links
Agreed. If there are no objections, I will fix this (and the
[configuration] move) this weekend.
Phil
None from me.
Hen
10 matches
Mail list logo
