ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiller, Dean (Contractor)" <>
Subject Is there a good example for using 1.+, etc(publish and resolve)
Date Mon, 13 Dec 2010 19:36:56 GMT
I keep changing my ivysettings.xml file as I run into issues(like
javadoc stops downloading because of a change but binary is still
downloaded) or in my most recent adventure, it is not even resolving


Currently, my ivysettings.xml file is


<?xml version="1.0" encoding="UTF-8"?>


  <settings defaultResolver="broadridge" />

  <!--Authentication required for publishing (deployment). 'Artifactory
Realm' is the realm used by Artifactory so don't change it.-->

  <credentials host="" realm="Artifactory Realm" username="admin"



      <ibiblio name="broadridge" m2compatible="true"
root="" />

          <url name="artifactory-publish" m2compatible="true">

                <!-- You can use  m2compatible="true" instead of
specifying your own pattern -->

              <artifact pattern=


n]/[module]/[revision]/ivy-[revision].xml" />






NOTICE the m2compatible....

I am not sure I need m2compatible on the url resolver?  

I am also not sure I need the chain?

On top of that the artifact pattern does not have [type] which means
sources/javadoc might have trouble? (But that was the artifactory

Why is the consumer looking for a pom???  I published a ivy xml file


[ivy:resolve]           module not found: com.broadridge#hbase;1.0

[ivy:resolve]   ==== broadridge: tried



I am not sure how to use "pattern" attribute when m2compatible is true
as in that case, shouldn't it be publishing a pom.xml file?  Is there
any examples on this?  I am trying to publish a virtual module and
consume it.  The publish with the above file worked but now consuming it
is not working L.


Very confused user....



This message and any attachments are intended only for the use of the addressee and
may contain information that is privileged and confidential. If the reader of the 
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.

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