> it doesn't really matter if it's ant scripts, or ivy declarations, or > maven pom entries -- the point is the same. > > We can't distribute the jars, but we can distribute programatic means for > users to fetch teh jars themselves. > > (even if we magicly switched to ivy or maven for dependency management, > problems like this build failure would still exist if a/the dependency > repo was down at build time, and we'd still likely distribute "fat" binary > tar balls containing all the dependency jars whose licenses are compatible > with the ASL. (users who download the binary artifacts shouldn't *have* > to know ivy/maven to use LUcene, anymore then they have to know ant right > now)
No. Today's point was that if dependency jars live in local dependency management cache, such build failures are very unlikely to happen. Unless you change dep version and repo goes down at the same time. You can surely hack up such a cache in ant. -- Kirill Zakharenko/Кирилл Захаренко (ear...@gmail.com) Home / Mobile: +7 (495) 683-567-4 / +7 (903) 5-888-423 ICQ: 104465785 --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
