Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID;
  b=eg9rxu5siNDW3KUD6e93U+DoSR/+WsxHkgVGiVHi4sPry7pWtS3evGZIvGZsNJzdDJSuLkCoP0wAEdLG18quEGjdPr95ouKdVVmzFN0+Q9yWC5RxI04KIR2Gg7Rh6zepBfaxUDMFvXshtwy5wtxhJGOUypJMK82X92Jj0eUVlfQ=;
Date: Fri, 8 Feb 2008 12:29:51 -0800 (PST)
From: Adrian Sandor <aditsu@yahoo.com>
Subject: Re: Add maven2 resolver?
To: Ant Developers List <dev@ant.apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1628638084-1202502591=:79589"
Message-ID: <464779.79589.qm@web32510.mail.mud.yahoo.com>

--0-1628638084-1202502591=:79589
Content-Type: text/plain; charset=us-ascii

Hi, IMHO it would be much better to build a clean, well-organized and reliable ivy repository instead of supporting that maven garbage. By the way, why was IvyRep abandoned? I think that would be the best solution, to have an official ivy rep., ideally containing artifacts too.
I have nothing against [better] supporting maven reps for those who prefer it, but I don't see why it should have a higher priority than supporting an ivy rep.
Anyway, I've never used maven (and from what I read about it, I avoided a world of suffering), and during the few minutes I spent with the ibiblio resolver before ditching it, I found these main problems:
- bad org names
- very old versions for some modules
- source and javadoc artifacts not supported (except by IvyDE)
Therefore the only solution was to manually build an "enterprise repository" from scratch. This could be avoided if an IvyRep was maintained (at least I could do "install").

Just a new user's opinion :)

Adrian

----- Original Message ----
From: Xavier Hanin <xavier.hanin@gmail.com>
To: Ant Developers List <dev@ant.apache.org>
Sent: Saturday, February 9, 2008 2:44:15 AM
Subject: Add maven2 resolver?


Hi,

Now 
that 
Ivy 
is 
using 
maven 
2 
repository 
as 
default 
public 
repository, 
and
that 
we 
see 
many 
people 
trying 
to 
leverage 
maven 
2 
repositories, 
I'm
wondering 
if 
we 
shouldn't 
introduce 
a 
maven2 
resolver. 
This 
resolver 
would
basically 
be 
the 
equivalent 
of 
ibiblio 
resolver 
with 
m2compatible 
set 
to
true. 
The 
advantage 
is 
a 
better 
name, 
and 
we 
can 
make 
also 
other
improvements. 
For 
instance, 
we 
could 
set 
checkConsistency 
to 
false 
on 
this
resolver, 
since 
pretty 
often 
people 
complain 
about 
inconsitencies 
in 
maven2
repo 
(see 
for 
instance 
last 
comments 
on 
[1]). 
We 
may 
also 
set 
the
changingPattern 
to 
make 
SNAPSHOT 
dependencies 
work 
(more 
than 
that 
needs 
to
be 
done, 
this 
should 
be 
addressed 
in 
IVY-501). 
We 
may 
even 
try 
to 
make 
this
resolver 
leverage 
maven2 
cache, 
for 
people 
who 
work 
with 
both 
Ivy 
and 
maven
2 
on 
the 
same 
machine.

WDYT?

Xavier

[1]
http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html
-- 
Xavier 
Hanin 
- 
Independent 
Java 
Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/


      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping
--0-1628638084-1202502591=:79589--