Gilles Scokart wrote:
Cool, I think we should share those errors with the maven team. They
usually don't accept to patch meta-data, but when it is invalid XML I
think they would accept.
Posted to the repository mailing list already. Apparently the ΓΈ
thing was a hack done to m2 to support some
On 13/03/2008, Xavier Hanin <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 13, 2008 at 2:44 PM, Gilles Scokart <[EMAIL PROTECTED]> wrote:
> > Cool, I think we should share those errors with the maven team. They
> > usually don't accept to patch meta-data, but when it is invalid XML I
> > think they
On Thu, Mar 13, 2008 at 2:44 PM, Gilles Scokart <[EMAIL PROTECTED]> wrote:
> Cool, I think we should share those errors with the maven team. They
> usually don't accept to patch meta-data, but when it is invalid XML I
> think they would accept.
Yes, but we'd need to filter this list first, to gi
Cool, I think we should share those errors with the maven team. They
usually don't accept to patch meta-data, but when it is invalid XML I
think they would accept.
Concerning the comparision with the maven resultion I started a few
month ago (during javapolis) to write some tests to compare trans
Hi,
As you may have noticed on the ivy user list I've just setup a small
web site for searching Maven 2 repository:
http://javarepo.xoocode.org/
To implement this I've used Ivy Pom parser to parse poms from the
maven 2 repository, to extract some basic information like the
description and home pa
