You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by "corneil.duplessis@gmail.com" <co...@gmail.com> on 2014/09/18 15:12:38 UTC

Problem when upgrading to 2.3.0

We have a project that has been using ivy for a long time.

A group of items in the repo was created by hand and contain multiple
artifacts per ivy.xml file
When we moved from Groovy 2.0.6 to Groovy 2.2.2 which includes Ivy 2.3.0
over 2.2.0 we ran into a problem. It seems as if the resolver is ignoring
settings or making new assumptions about the artifacts.

My grapeConfig is as follows:
<ivysettings>
  <settings defaultResolver="downloadGrapes"/>
  <resolvers>
    <chain name="downloadGrapes">
      <filesystem name="cachedGrapes">
        <ivy
pattern="${user.home}/.groovy/grapes/[organisation]/[module]/ivy-[revision].xml"/>
        <artifact
pattern="${user.home}/.groovy/grapes/[organisation]/[module]/[type]s/[artifact]-[revision].[ext]"/>
      </filesystem>
      <filesystem name="localRepo">
        <ivy
pattern="${user.home}/XXX/released/[organization]/[module]/[revision]/ivy.xml"/>
        <artifact
pattern="${user.home}/XXX/released/[organization]/[module]/[revision]/[artifact].[ext]"/>
      </filesystem>
      <ibiblio name="remote" root="http://XXXXXXXX/repo"
m2compatible="true"/>
      <ibiblio name="central" root="http://XXXXXXXX/artifactory/simple/repo"
m2compatible="true"/>
    </chain>
  </resolvers>
</ivysettings>

The ivy.xml file in question:

<ivy-module version="1.4">
  <info organisation="3rdparty" module="corba.jacorb" status="release"
revision="2.3.1" />
  <publications>
    <artifact name="jacorb-compat" ext="jar" />
    <artifact name="jacorb" ext="jar" />
  </publications>
  <dependencies>
    <dependency org="3rdparty" name="logging.slf4j" rev="1.7.5" />
  </dependencies>
</ivy-module>

In the case of 2.2 I can see ivy loading the correct ivy.xml and processes
dependencies and artifacts correctly.
In the case of 2.3 the ivy.xml is loaded and dependencies processed but the
artifacts are 'ignored'


2.2 output some lines relating to other dependencies removed
[SUCCESSFUL ] 3rdparty#corba.jacorb;2.3.1!ivy.xml(ivy.original) (1ms)
Preparing to download artifact 3rdparty#corba.jacorb;2.3.1!jacorb.jar
Preparing to download artifact 3rdparty#corba.jacorb;2.3.1!jacorb-compat.jar
trying /home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/jacorb.jar
tried /home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/jacorb.jar
downloading /home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/jacorb.jar
...
localRepo: downloading
/home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/jacorb.jar
to
/home/XXXX/.groovy/grapes/3rdparty/corba.jacorb/jars/jacorb-2.3.1.jar.part
[SUCCESSFUL ] 3rdparty#corba.jacorb;2.3.1!jacorb.jar (5ms)
trying /home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/jacorb-compat.jar
tried /home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/jacorb-compat.jar
downloading
/home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/jacorb-compat.jar ...
localRepo: downloading
/home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/jacorb-compat.jar
to
/home/XXXX/.groovy/grapes/3rdparty/corba.jacorb/jars/jacorb-compat-2.3.1.jar.part
[SUCCESSFUL ] 3rdparty#corba.jacorb;2.3.1!jacorb-compat.jar (1ms)

2.3 output
downloading /home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/ivy.xml ...
localRepo: downloading
/home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/ivy.xml
to
/home/XXXX/.groovy/grapes/3rdparty/corba.jacorb/ivy-2.3.1.xml.original.part
[SUCCESSFUL ] 3rdparty#corba.jacorb;2.3.1!ivy.xml(ivy.original) (0ms)
post 1.3 ivy file: using exact as default matcher
default-cache: parsed downloaded md file for 3rdparty#corba.jacorb;2.3.1;
parsed=3rdparty#corba.jacorb;2.3.1
checking 3rdparty#corba.jacorb;2.3.1 from localRepo against [none]
module revision kept as first found: 3rdparty#corba.jacorb;2.3.1 from
localRepo
found 3rdparty#corba.jacorb;2.3.1 in localRepo
:: downloading artifacts ::
Preparing to download artifact 3rdparty#corba.jacorb;2.3.1!corba.jacorb.jar
trying /home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/corba.jacorb.jar
tried /home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/corba.jacorb.jar
localRepo: resource not reachable for 3rdparty#corba.jacorb;2.3.1:
res=/home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/corba.jacorb.jar
WARN: [NOT FOUND  ] 3rdparty#corba.jacorb;2.3.1!corba.jacorb.jar (0ms)
WARN: ==== localRepo: tried
WARN:   /home/XXXX/XXX/released/3rdparty/corba.jacorb/2.3.1/corba.jacorb.jar

Is this a known bug?


Regards
Corneil du Plessis