ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xavier Hanin" <xavier.ha...@gmail.com>
Subject Re: Ivy 2.0.0-alpha-1
Date Tue, 03 Jul 2007 11:57:27 GMT
On 7/3/07, Tjeerd Verhagen <tjeerd.verhagen@gmail.com> wrote:
>
> On 7/3/07, Xavier Hanin <xavier.hanin@gmail.com> wrote:
> >
> > On 7/3/07, Tjeerd Verhagen <tjeerd.verhagen@gmail.com> wrote:
> > >
> > > I would go for names like
> > >
> > > ivy-core (or just ivy) and
> >
> > Using just ivy would be confusing for old ivy users, who were used to
> have
> > everything in this jar.
>
> Yes, you're right there!
>
> ivy-ant
> >
> >
> > I prefer ivy-full or ivy-all, it's more self explaining IMO. Indeed we
> > could
> > have a jar with no optional thing at all (this would be the core), then
> a
> > jar with all optional things but ant related one (used for IvyDE or
> > embedded), and a jar with everything (used in most cases, including in
> > Ant).
> >
> > WDYT?
>
> If I understand the last bit correct, this would create another jar?
>
> IMO the real problem, is not the fact that there are multple jars, but
> what's in what jar and which jar is intended for what (at least for me it
> was at the beging). So a little readme.txt / jars_readme.txt, inside the
> jars directory (and also somewhere in the manual) would be appreciated,
> explaining the purpos of the defferend jars. (The jars_readme.txt can
> easily
> created by some ant 'echo' tasks.)
>
> Then the names of the jars become also less important :)


I agree, the problem is a documentation problem more than anything else.

Xavier

Tjeerd
>
> Xavier
> >
> > which is quite self explaining in my opinion.
> > >
> > >
> > > On 7/3/07, Xavier Hanin <xavier.hanin@gmail.com> wrote:
> > > >
> > > > On 7/3/07, Tjeerd Verhagen <tjeerd.verhagen@gmail.com> wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > the same question arrised to me, as I find the names also no so
> self
> > > > > explaining
> > > > >
> > > > >
> > > > > ivy-core-2.0.0-alpha-1-incubating.jar  -->  The Ivy core system
> > > > > ivy-2.0.0-alpha-1-incubating.jar  --> The Ivy core system + The
> Ant
> > > > tasks
> > > > >
> > > > > So when using in combination with Ant the ivy-2*.jar is enough.
> > > >
> > > >
> > > > Indeed, we plan to review the packaging before 2.0 final. The
> current
> > > > packaging is mainly historical, Ivy was previously packaged as only
> > one
> > > > jar
> > > > (ivy-[version].jar). Then the need for a jar without the Ant tasks
> > > raised
> > > > for IvyDE, and we created the "core", which isn't really what we
> call
> > > the
> > > > core in development. In development the core is what can be built
> > > without
> > > > dependencies, and our build script first builds the core, then use
> the
> > > > freshly built core to resolve Ivy optional dependencies, and then
> > build
> > > > the
> > > > parts of Ivy depending on these optional dependencies. So we may
> > change
> > > > the
> > > > artifact names and packaging in coming versions.
> > > >
> > > > Xavier
> > > >
> > > > On 7/3/07, hezjing <hezjing@gmail.com> wrote:
> > > > > >
> > > > > > Hi!
> > > > > >
> > > > > > The apache-ivy-2.0.0-alpha-1-incubating-bin.tar.gz contains
2
> JARs
> > > > > >
> > > > > > 1) ivy-2.0.0-alpha-1-incubating.jar
> > > > > > 2) ivy-core-2.0.0-alpha-1-incubating.jar
> > > > > >
> > > > > >
> > > > > > May I know what is the different between these 2 JARs?
> > > > > >
> > > > > > Should I copy both JARs into $ANT_HOME/lib?
> > > > > >
> > > > > >
> > > > > > --
> > > > > >
> > > > > > Hez
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Xavier Hanin - Independent Java Consultant
> > > > Creator of Ivy, xooki and xoocode.org
> > > > More about me: http://xhab.blogspot.com/
> > > >
> > >
> >
> >
> >
> > --
> > Xavier Hanin - Independent Java Consultant
> > Creator of Ivy, xooki and xoocode.org
> > More about me: http://xhab.blogspot.com/
> >
>



-- 
Xavier Hanin - Independent Java Consultant
Creator of Ivy, xooki and xoocode.org
More about me: http://xhab.blogspot.com/

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message