I'm +1 to publish Ivy to a maven repository, even without a stable API. We can publish to a private repository first (eg http://incubator.apache.org/ivy/repository), to ensure we get things clean and usable. We could publish the alpha 2 release to this private repository, then for the beta 1 see if we can publish it to the central or snapshot repo. The work to do for this is create a maven pom as suggested by steve, and automate the publication in our ant build. It may be a good opportunity to create some Ivy tasks to ease that (ivy to pom conversion?). For the packaging I would stick with one big fat jar, with all dependencies declared as optional. We will do better later.
Xavier On 7/30/07, Gilles Scokart <[EMAIL PROTECTED]> wrote: > > 2007/7/30, Steve Loughran <[EMAIL PROTECTED]>: > > > > Three options > > > > -a big fat jar with all the optional dependencies declared as mandatory > > -a big fat jar with no optional dependencies > > -lots of little jars with the optional dependencies pulled in. > > > > You can also create a super bundle that pulls in the little JARs > > > > steve > > > > Personally, I thing it is too early to have little jars. I think it > will only make sense when we will have defined our API. > > But maybe having a small jar with the ant task depending on the 'big > fat' jar containing all the rest would be nice in a first step. > > > -- > Gilles SCOKART > -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://incubator.apache.org/ivy/ http://www.xoocode.org/
