My next problem is to try and understand ivy's grouping model.
It looks like you can pick any name out of a hat for your project; its the classic 'flat' naming scheme which, as everyone who has used on winXP in a big organisation will vouch for, doesnt scale. It doesnt scale for files in a directory tree either; most unix filesystems' performance collapses once you have a few thousand files in a directory, and dont support >64K worth of inodes. Things like apache directory browsing fail pretty badly too, which is why ibiblio,org/maven is so slow (that an inadequate caching of previously dynamically generated content).
1. Can do you declare a hierarchical group name? org.apache.something, org/ex/something?
2. Ivyrep uses organisation/artifact groupings, such as apache/commons-logging; m1 used artifact/jarsk, and m2 goes to group/artifact/version, where group is mapped from split.by.package to split/by/package.
Is there a goal to have organisations mapped consistently, so that apache -> org.apache, sun to com.sun, etc?
3. If I am creating ivy.xml files for org.smartfrog, what name should I use? -steve
