To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jaxme has an issue affecting its community
integration.
This
+1
Niall Pemberton wrote:
Hi,
I'd like to release Commons Skin. The main change is to import
commons-maven.css into site.css so that the ApacheCon logo appears on
sites built with m2. The only other changes is to move to version 5 of
commons-parent.
A full diff of the pom.xml can be found at t
On Nov 30, 2007 11:57 AM, Dion Gillard <[EMAIL PROTECTED]> wrote:
> Did you really remove the license from the css file?
Yes - see http://tinyurl.com/23y4ud
Niall
> On 11/30/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > I'd like to release Commons Skin. The main change is to imp
Did you really remove the license from the css file?
On 11/30/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'd like to release Commons Skin. The main change is to import
> commons-maven.css into site.css so that the ApacheCon logo appears on
> sites built with m2. The only other change
+1
Niall Pemberton wrote:
> Hi,
>
> I'd like to release Commons Skin. The main change is to import
> commons-maven.css into site.css so that the ApacheCon logo appears on
> sites built with m2. The only other changes is to move to version 5
> of commons-parent.
>
> A full diff of the pom.xml c
