that did the trick. Thanks
On Tue, Feb 16, 2010 at 11:39 PM, Benjamin Bentmann <
benjamin.bentm...@udo.edu> wrote:
> Stephane Nicoll wrote:
>
> Embedded error: Error rendering Maven report: Failed during checkstyle
>> configuration
>> FileLength is not allowed as a child in Checker
>>
>
> The EA
Stephane Nicoll wrote:
Embedded error: Error rendering Maven report: Failed during checkstyle
configuration
FileLength is not allowed as a child in Checker
The EAR Plugin is still inheriting from the rather old maven-plugins:14
parent, IIRC we fixed this in later parents, so try updating to v
This is a user group question - but look below.
On 5/31/07, Brent Kersanske <[EMAIL PROTECTED]> wrote:
I've been struggling with some of maven's custom site generation tools
for a few days now.
It seems there is very little helpful information out there, and the few
bits of good information th
> I've always liked this idea and actually tried to do it in
> Turbine but nobody went for it. I think it clearly separates
> the docs and we can actually give out perms to doco folk (if
> we ever get some :-)) and not worry about them punching the core.
>
> +1
>
I've put it in JIRA to do for
On Wed, 2003-11-26 at 17:59, Brett Porter wrote:
> > I would say the normal site should point at the current
> > release docs and then use your scheme to point at any number
> > of desired branches.
>
> I agree. This was the original plan I think. I like the way Cactus does it
> too, in the top
> I would say the normal site should point at the current
> release docs and then use your scheme to point at any number
> of desired branches.
I agree. This was the original plan I think. I like the way Cactus does it
too, in the top right nav link.
But in the interim, we just keep doing what
On Wed, 2003-11-26 at 17:25, Vincent Massol wrote:
> Some ideas... :-)
>
> Why not 2 web sites:
>
> - maven.apache.org pointing to HEAD
> - maven.apache.org/1.0/ pointing to MAVEN-1_0-BRANCH
I think we need a site for the current release as well. And I suppose
any number of arbitrary branches th
On Wed, 2003-11-26 at 17:13, Brett Porter wrote:
> Just a thought... should the main site now be generated from
> MAVEN-1_0-BRANCH or HEAD?
>
> I'm +1 for the branch as it is the next release and all changes made there
> will go to HEAD eventually.
Yah, I agree. Whatever branch is slated for the
Some ideas... :-)
Why not 2 web sites:
- maven.apache.org pointing to HEAD
- maven.apache.org/1.0/ pointing to MAVEN-1_0-BRANCH
I prefer this way. On the Cactus project I tried the opposite (i.e.
default pointing to latest release) and it didn't work that well. After
a few weeks we swapped to HE
