pril 07, 2007 10:04 PM
To: Maven Developers List
Subject: Re: [Vote] Move plugin site.xml up to Maven or Shared
Makes sense. Another option is to have those links in the bottom of
the left nav on every site too.
I'm not against either of those solutions, as long as the links
section isn't t
On 08/04/2007, at 1:12 PM, Brian E. Fox wrote:
I'm not familiar enough yet with the site and related tech to know how
to fix this. It seems like changing the skin isn't what we want,
somehow
we need to tell site not to make these externalLinks.
The Maven site overrides this in a custom sit
hed date should be to the right of the breadcrumbs to make
everything consistent.
Pointers?
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 07, 2007 10:04 PM
To: Maven Developers List
Subject: Re: [Vote] Move plugin site.xml up to Maven or Shared
Makes
it's nice to have
those links right there all the time.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 07, 2007 9:47 PM
To: Maven Developers List
Subject: Re: [Vote] Move plugin site.xml up to Maven or Shared
I definitely agree with the breadcru
there all the time.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 07, 2007 9:47 PM
To: Maven Developers List
Subject: Re: [Vote] Move plugin site.xml up to Maven or Shared
I definitely agree with the breadcrumbs on the left. I don't mind
I definitely agree with the breadcrumbs on the left. I don't mind
where the publish date goes as long as it's consistent (maybe bottom
is more suitable/traditional).
For the links, I find them to be too noisy with all the subprojects.
On the main site these were put into the left nav. I thi
>
> I will make the changes and stage the main site before pushing it out.
>
> What are we doing with the links that are present on plugins but
> not on
> the main site? It seems to me that they should be the same in both
> locations (either with or without).
>I think it makes sense for them to
On 06/04/2007, at 7:28 AM, Brian E. Fox wrote:
Binding: +6(Brian, John, Dennis, Brett, Jason, Emmanuel)
Non-Binding: + 3(Andy,John T, Maria)
John T is a PMC member - is there an out of date reference somewhere
that doesn't list him?
I will make the changes and stage the main site before
Binding: +6(Brian, John, Dennis, Brett, Jason, Emmanuel)
Non-Binding: + 3(Andy,John T, Maria)
I will make the changes and stage the main site before pushing it out.
What are we doing with the links that are present on plugins but not on
the main site? It seems to me that they should be the same i
+1 for moving to the Maven POM
-john
On 4/4/07, Andrew Williams <[EMAIL PROTECTED]> wrote:
[X] Move to Maven Pom, with the note that extra site.xmls might be
nice for breadcrumbs and extra links etc.
Andy
On 3 Apr 2007, at 03:39, Brian E. Fox wrote:
> Currently only plugins get a nice looki
[X] Move to Maven Pom, with the note that extra site.xmls might be
nice for breadcrumbs and extra links etc.
Andy
On 3 Apr 2007, at 03:39, Brian E. Fox wrote:
Currently only plugins get a nice looking skin that matches the main
maven.apache.org page because the site.xml exists in the plugin
Brian E. Fox wrote:
Currently only plugins get a nice looking skin that matches the main
maven.apache.org page because the site.xml exists in the plugin project.
Other things like shared get a homely looking default skin. I see two
options here:
1. Move the site.xml up to the maven pom.
+1 Move to Maven Pom
On 4/3/07, John Tolentino <[EMAIL PROTECTED]> wrote:
+1 [ X ] Move to Maven Pom
On 4/3/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> Currently only plugins get a nice looking skin that matches the main
> maven.apache.org page because the site.xml exists in the plugin proje
+1 [ X ] Move to Maven Pom
On 4/3/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
Currently only plugins get a nice looking skin that matches the main
maven.apache.org page because the site.xml exists in the plugin project.
Other things like shared get a homely looking default skin. I see two
option
Brian E. Fox a écrit :
Currently only plugins get a nice looking skin that matches the main
maven.apache.org page because the site.xml exists in the plugin project.
Other things like shared get a homely looking default skin. I see two
options here:
1. Move the site.xml up to the maven
+1 Move to Maven pom
Brian E. Fox wrote:
Currently only plugins get a nice looking skin that matches the main
maven.apache.org page because the site.xml exists in the plugin project.
Other things like shared get a homely looking default skin. I see two
options here:
1. Move the site.xm
I'm in favour of 'moving' it up. I think you'll still need this
site.xml though it'll be mostly empty (maybe add breadcrumbs?). The
TODO's already in there tell that story.
We'll also need to do a maven pom release after that change.
- Brett
On 03/04/2007, at 12:45 PM, Jason van Zyl wrote:
On 2 Apr 07, at 10:39 PM 2 Apr 07, Brian E. Fox wrote:
Currently only plugins get a nice looking skin that matches the main
maven.apache.org page because the site.xml exists in the plugin
project.
Other things like shared get a homely looking default skin. I see two
options here:
1.
18 matches
Mail list logo
