On Mon, Nov 14, 2005 at 05:55:48AM +0100, Stefan Bodewig wrote:
On Sun, 13 Nov 2005, Bill Barker [EMAIL PROTECTED] wrote:
Stefan Bodewig [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
The version of dom4j that Maven 1.0.2 uses is quite old - some
prerelase of 1.4. Maybe we
We probably need a compatibility option, but it's listed on the known
incompatibility pages.
We actually started validating the project.xml files. Some people have
a lot of random content in there that was previously silenty ignored.
Maybe its worth considering them a failed build for the
On Mon, Nov 14, 2005 at 09:53:01PM +1100, Brett Porter wrote:
We probably need a compatibility option, but it's listed on the known
incompatibility pages.
Aw, that sucks as a concept! I thought maven1 was going to stay compatible
and there'd be painfulness only once (maven1 - maven2)?
We
On 11/14/05, Leo Simons [EMAIL PROTECTED] wrote:
On Mon, Nov 14, 2005 at 09:53:01PM +1100, Brett Porter wrote:
We probably need a compatibility option, but it's listed on the known
incompatibility pages.
Aw, that sucks as a concept! I thought maven1 was going to stay compatible
and there'd
