ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Sahlbach (JIRA)" <>
Subject [jira] Created: (IVY-942) attributes organisation, organization and org should be exchangeable
Date Wed, 15 Oct 2008 14:55:44 GMT
attributes organisation, organization and org should be exchangeable

                 Key: IVY-942
             Project: Ivy
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.0-RC1
            Reporter: Andreas Sahlbach

In short a setting with this:

    <settings defaultResolver="default" defaultBranch="/trunk"/>
        <chain name="external" returnFirst="true">
            <resolver ref="ibiblio-maven2"/>

        <chain name="internal" returnFirst="true">
            <resolver ref="umsrep"/>

        <chain name="default" returnFirst="false">
            <resolver ref="internal"/>
            <resolver ref="external"/>

        <module organization="ums" name="*" matcher="glob" resolver="internal"/>

and an ivy-file with this dependency:

        <dependency org="ums" name="umsinfo" branch="/trunk" rev="latest.integration" conf="*
-> default"/>

will always go to ibiblio, because the module entry will not match. org is expanded to organisation
and ModuleRules uses a simple MapMatcher that handles an entry of organization different to

Please: clean this up. use just one attribute (maybe the neutral "org") for all attributes
that refer to an organi(s|z)ation. Same is true for "revision". Why is it "revision" in the
info tag and rev in the dependency tag? This is just error prone and will unsettle users.

If there are attributes that you want to use interchangeable, please normalize them internally
and use them consistently in ivy. Especially in this case, where the ivy-settings.xml file
can be written by someone different than the person who writes the ivy.xml with the dependency.

Besides this, rc1 works just fine here. Good work!

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message