cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robby Pelssers <Robby.Pelss...@nxp.com>
Subject RE: cocoon-parent pom breaking build
Date Fri, 06 Jan 2012 10:59:24 GMT
I only added the style.css without a license. That is fixed now.

Sorry for the inconvenience people.  Was not fully aware of this.

Robby

From: Robby Pelssers [mailto:Robby.Pelssers@nxp.com]
Sent: Friday, January 06, 2012 11:56 AM
To: dev@cocoon.apache.org
Subject: RE: cocoon-parent pom breaking build

Ok. So you're saying every single file needs the ASL header?  Or do we have a list of which
files should have that header?

Curious to find out if that plugin is able to handle different filetypes correct as I will
need to use different types of commenting for java, css, xml etc.

Robby

From: Francesco Chicchiriccò [mailto:ilgrosso@apache.org]
Sent: Friday, January 06, 2012 11:52 AM
To: dev@cocoon.apache.org
Subject: Re: cocoon-parent pom breaking build

On 06/01/2012 11:41, Robby Pelssers wrote:
Hi guys,

I think the cocoon-parent pom is causing issues.  But as I am using maven3 it might be wise
that I don't touch that file as it might break with others still using maven 2.

Can someone using maven 2 take a look if he finds errors in that pom?

Robby, the build is broken by cocoon-sample, because rat plugin finds "too many approved licenses",
i.e. there are new files without the needed ASL header.

Look at https://builds.apache.org/job/Cocoon-trunk/135/console (towards the end) for details.

Regards.

--

Francesco Chicchiriccò



Apache Cocoon Committer and PMC Member

http://people.apache.org/~ilgrosso/

Mime
View raw message