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: Configurations really hard to understand
Date Wed, 15 Aug 2007 18:51:02 GMT
On 8/15/07, Andy Piper <andyp@bea.com> wrote:
>
> Yeah, so this is what I need too and am doing with virtual modules
> (with a <publications/> section. It feels a little contrived however,
> and I agree this particular use-case should be much simpler to
> define. The simple things should be easy and complicated things
> possible. Right now ivy configurations are very powerful, but not
> ever simple from my POV...


Do you see a way to make them simpler, besides better documentation? It's
difficult to see how complex conf mapping is from my POV (as being at the
origin of this concept), so I think an easier solution should better come
from the community.

Xavier

andy
>
> At 19:16 15/08/2007, Jeffrey Blattman wrote:
> >i've never needed Ivy configurations. i need what maven has, and
> >that's how i tried to apply it. i always understood configurations
> >to be a generalized version of maven scopes as you are calling them.
> >in fact i think i read that someone in the ivy docs.
> >
> >all i want to do is
> >
> >1. define a config
> >2. be able to associate a config w/ a dependency
> >3. be able to reference the dependencies by config name in
> >ivy:resolve, retrieve, cachpath, etc
> >
> >i.e., configs are just a grouping of dependencies.
> >
> >it just seems like configurations could be greatly simplified to do
> >the above and still handle 98% of the use cases. you don't need to
> >"->" syntax do this for example.
> >
> >Xavier Hanin wrote:
> >>On 8/15/07, Jeffrey Blattman <jeffrey.blattman@gmail.com> wrote:
> >>
> >>>i don't mean to rain on dmitry's great explanation, but i think this
> >>>might be the crux of the problem. there is one way to do it on maven,
> >>>and no one has any questions about it. i to was / am confused by
> >>>configurations in Ivy.
> >>>
> >>
> >>
> >>Not sure to get what you are meaning. Do you mean that we should only
> >>provide one way to specify configuration mapping, or that we should
> simply
> >>not provide flexible configuration mapping as we do? Maven has no
> concept of
> >>configuration, they have scopes which are predefined and do not allow
> things
> >>as flexible as you can do with Ivy. But maybe providing an easy to use
> >>configuration mapping in Ivy could help users who don't want to take
> care
> >>about understanding the real flexibility of configurations.
> >>
> >>Xavier
> >>
> >>Dmitriy Korobskiy wrote:
> >>
> >>>>2. How to specify this mapping? There are many ways in Ivy to do it.
> >>>>
> >>>Let's start
> >>>
> >>>>with explicit abbreviated mapping for each dependency:
> >>>>
> >>>>
> >>>>
> >>
> >>
> >>
> >>
>
>
> Notice:  This email message, together with any attachments, may contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
> entities,  that may be confidential,  proprietary,  copyrighted  and/or
> legally privileged, and is intended solely for the use of the individual or
> entity named in this message. If you are not the intended recipient, and
> have received this message in error, please immediately return this by email
> and then delete it.
>



-- 
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/

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