can you check if my last commits fixed it? However, you have to build it
yourself as I'm getting a 500 when trying to deploy to apache right now,
so no snaps are deployed yet.
HTH,
-Lukas
Jeff Jensen wrote:
Yes, :-) 3.0-beta-4-SNAPSHOT. The fixes over the past months have
been very helpf
Yes, :-) 3.0-beta-4-SNAPSHOT. The fixes over the past months have
been very helpful, so I'm using the snapshot.
Sorry for my wrong word choice; you correctly suggest the deploy part,
not site gen part. I have a Hudson job that runs "mvn site-deploy
-e", so I accidentally combined the two phases
Hi Jeff,
I deduce you are testing my current development version...? ;)
I don't see how this particular commit could have broken site generation
as it only concerns the DeployMojo. However, I see that it could break
site:stage-deploy, is this what you are seeing?
I don't exclude that I bro
Hi Lukas!
I have a question on this commit, as it causes our site gen to now fail.
With the following change:
> +if ( site == null )
> +{
> +throw new MojoExecutionException(
> +"Missing site information in the distribution management of
> the project
What kind of platform is this ? We have 2 CI's that says it compiles,
as well as both jdk 1.5 and 1.6 on my local linux box.
Kristian
ti., 08.03.2011 kl. 09.51 -0500, skrev Martin Gainty:
> package org.apache.maven.surefire.booter.output;
>
> /*
> * Licensed to the Apache Software Foundation
package org.apache.maven.surefire.booter.output;
/*
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
* regarding copyright ownership. The ASF licenses this file
