ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiller, Dean (Contractor)" <dean.hil...@broadridge.com>
Subject Maarten:issue resolved...THANKS....(and answer your question on chain)...
Date Tue, 14 Dec 2010 00:29:39 GMT
YOU ROCK!!!  The m2compatible made the 1.0.+ thing work.  That was the
last missing piece.  I think my entire environment is now working.

Regarding chain.  I reverted to 

<?xml version="1.0" encoding="UTF-8"?>
<ivy-settings>
  <settings defaultResolver="broadridge" />
  <!--Authentication required for publishing (deployment). 'Artifactory
Realm' is the realm used by Artifactory so don't change it.-->
  <credentials host="8.8.8.8" realm="Artifactory Realm" username="admin"
passwd="password"/>
  <resolvers>
    	<ibiblio name="broadridge" m2compatible="true"
root="http://8.8.8.8:8081/artifactory/libs-releases" />
	    <url name="artifactory-publish" m2compatible="true">
	    	<artifact pattern=
	
"http://8.8.8.8:8081/artifactory/libs-releases-local/[organization]/[mod
ule]/[revision]/[artifact]-[revision].[ext]"/>
	        <ivy
pattern="http://8.8.8.8:8081/artifactory/libs-releases-local/[organizati
on]/[module]/[revision]/ivy-[revision].xml" />	    	
	    </url>   
  </resolvers>
</ivy-settings>

Which does NOT work???  Maybe defaultResolver is wrong?

I get the following error in verbose...

[ivy:resolve]
[ivy:resolve] :: problems summary ::
[ivy:resolve] :::: WARNINGS
[ivy:resolve]           module not found: com.broadridge#hbase;1.0.+
[ivy:resolve]   ==== broadridge: tried
[ivy:resolve]
http://8.8.8.8:8081/artifactory/libs-releases/com/broadr
[ivy:resolve]     [1.0.0 (unreachable)]
[ivy:resolve]     -- artifact com.broadridge#hbase;1.0.+!hbase.jar:
[ivy:resolve]
http://8.8.8.8:8081/artifactory/libs-releases/com/broadr
[ivy:resolve]     [1.0.0 (unreachable)]
[ivy:resolve]           module not found: com.broadridge#tools;1.0.+
[ivy:resolve]   ==== broadridge: tried
[ivy:resolve]
http://8.8.8.8:8081/artifactory/libs-releases/com/broadr
[ivy:resolve]     [1.0.3 (unreachable), 1.0.2 (unreachable), 1.0.1
(unreachable)
[ivy:resolve]     -- artifact com.broadridge#tools;1.0.+!tools.jar:
[ivy:resolve]
http://8.8.8.8:8081/artifactory/libs-releases/com/broadr
[ivy:resolve]     [1.0.3 (unreachable), 1.0.2 (unreachable), 1.0.1
(unreachable)
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]           ::          UNRESOLVED DEPENDENCIES         ::
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]           :: com.broadridge#hbase;1.0.+: not found
[ivy:resolve]           :: com.broadridge#tools;1.0.+: not found
[ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::

HOWEVER, this ivysettings.xml file works GREAT thanks to you!!!!  It is
all working now!!! So I don't really have an issue but just thought I
would send you the data.

<?xml version="1.0" encoding="UTF-8"?>
<ivy-settings>
  <settings defaultResolver="main" />
  <!--Authentication required for publishing (deployment). 'Artifactory
Realm' is the realm used by Artifactory so don't change it.-->
  <credentials host="8.8.8.8" realm="Artifactory Realm" username="admin"
passwd="password"/>
  <resolvers>
  	<chain name="main">
    	<ibiblio name="broadridge" m2compatible="true"
root="http://8.8.8.8:8081/artifactory/libs-releases" />
	    <url name="artifactory-publish" m2compatible="true">
	    	<artifact pattern=
	
"http://8.8.8.8:8081/artifactory/libs-releases-local/[organization]/[mod
ule]/[revision]/[artifact]-[revision].[ext]"/>
	        <ivy
pattern="http://8.8.8.8:8081/artifactory/libs-releases-local/[organizati
on]/[module]/[revision]/ivy-[revision].xml" />	    	
	    </url>   
    </chain>
  </resolvers>
</ivy-settings>


-----Original Message-----
From: Maarten Coene [mailto:maarten_coene@yahoo.com] 
Sent: Monday, December 13, 2010 4:09 PM
To: ivy-user@ant.apache.org
Subject: Re: Is there a good example for using 1.+, etc(publish and
resolve)

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

Yes you do, this way your "com.broadridge" organisation will be
translated to a 
"com/broadridge" structure.

> I am also not sure I need the chain?

No, you don't.

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

That will be a problem indeed. It could be that Ivy will fail to publish
because 
of this, but I'm not sure of that...

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

You use the ibiblio resolver as default resolver. This resolver searches
for a 
pom file. If you don't want this, you'll need to define an url resolver
instead.

HTH,
Maarten




----- Original Message ----
From: "Hiller, Dean (Contractor)" <dean.hiller@broadridge.com>
To: ivy-user@ant.apache.org
Sent: Mon, December 13, 2010 8:36:56 PM
Subject: Is there a good example for using 1.+, etc(publish and resolve)

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
now.  



Currently, my ivysettings.xml file is



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

<ivy-settings>

  <settings defaultResolver="broadridge" />

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

  <credentials host="8.8.8.8" realm="Artifactory Realm" username="admin"
passwd="password"/>

  <resolvers>

      <chain>

      <ibiblio name="broadridge" m2compatible="true"
root="http://8.8.8.8:8081/artifactory/libs-release" />

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

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

              <artifact pattern=


"http://8.8.8.8:8081/artifactory/libs-release-local/[organization]/[modu
le]/[revision]/[artifact]-[revision].[ext]"/>

              <ivy
pattern="http://8.8.8.8:8081/artifactory/libs-release-local/[organizatio
n]/[module]/[revision]/ivy-[revision].xml" />

          </url>    

    </chain>

  </resolvers>

</ivy-settings>



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
example)

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

[ivy:resolve]
http://8.8.8.8:8081/artifactory/libs-release/com/broadridge/tools/1.0/to
ols-1.0.pom



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....

Thanks,

Dean


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.



      
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.


Mime
View raw message