Hi,
I did some of the branch and version maintenance I mentioned in the
other mail.
In the spirit of "fresh start", does it make sense for moving
components/trunk to maven3/trunk in SVN? If so, would someone actively
working on it like to make the move?
It may make sense to also/instead
On 07/07/2009, at 1:43 AM, John Casey wrote:
done. the reason this wasn't working is that the JDK version was set
to 1.4, but maven 2.2.0 requires 1.5.
but the build is Maven 2.0.x, jdk 1.4 - so it should be building with
1.4 and an earlier version of Maven?
I'm emailing you separately w
done. the reason this wasn't working is that the JDK version was set to
1.4, but maven 2.2.0 requires 1.5. I'm emailing you separately with your
reset password, then if you could login and change it to something
secure, that'd be great.
-john
Brett Porter wrote:
On 06/07/2009, at 11:05 PM,
Great job :)
I wonder if it is possible to use other format.
We use rst as site document format, and we made a doxia-module to
embbded it.
But could not generate a pdf, is there anything special to do in our
side to make this works with the pdf plugin ?
Tony.
Le Mon, 29 Jun 2009 15:38:38 +020
On 06/07/2009, at 11:05 PM, Hudson wrote:
[locks-and-latches] Checking to see if we really have the locks
[locks-and-latches] Have all the locks, build can start
Java specification version: 1.4
This release of Maven requires Java version 1.5 or greater.
[locks-and-latches] Releasing all the loc
