On Sat, Mar 15, 2008 at 9:23 PM, Nathan Beyer <[EMAIL PROTECTED]> wrote:
> What did you have to download manually? The dependency downloads are > all automated via Ant targets. If that's not working, then it's a bug > or issue we need to resolve. > Yes, I've included them in the bug. This specific location gives a corrupted version. > > Maven doesn't have any magical solution for mirror usage. > Well it's not magic. But I noticed you have hardcoded all the locations of the needed jars. Dependency management is much easier in maven. If you include multiple repos, it will check all of them for the jar needed. and the checksum doesn't also needed to be hardcoded. > > -Nathan > > On Sat, Mar 15, 2008 at 5:12 AM, Tharindu Mathew <[EMAIL PROTECTED]> > wrote: > > I'm also not familiar with Ivy. > > > > I suggested maven because of the dependency management. You can > automate it. > > The biggest problem I had with this build was having to download > several > > dependencies by myself and finding mirror repositories. These problems > are > > pretty much solved in maven. > > > > > > > > On Sat, Mar 15, 2008 at 3:28 PM, Tim Ellison <[EMAIL PROTECTED]> > wrote: > > > > > Sorry to bounce around, just bringing this back to the dev list... > > > > > > Tharindu Mathew (JIRA) wrote: > > > > Yes I found another the same dependency duplicated at another > > > > location. Is there a way to make for Ant to look into multiple > > > > repositories when retrieving dependencies like maven2. > > > > > > > > Can Ant be structured in a more OOP way? Or has it been considered > to > > > > switch to maven2 as the build system? > > > > > > We are not about to switch to Maven, but it may be worth > investigating > > > Apache Ivy for dependency management. > > > > > > I think we actually have quite simple dependencies so not sure if we > > > need it (but I've not got much familiarity with Ivy). > > > > > > Regards, > > > Tim > > > > > > > > > > > > -- > > Regards, > > > > Tharindu > > > -- Regards, Tharindu
