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 Aaron Siri <aa...@acsiri.com> on 2009/03/11 19:10:32 UTC
Re: Newbie: failed dependencies and local (team) repositories for
non-open-source stuff
We have been using Nexus as both a caching proxy for the public repos and to
manage our own artifacts.
Probably worth looking into. http://nexus.sonatype.org/
It is maven centric but works fine with Ivy as well.
-Aaron
On Wed, Mar 11, 2009 at 10:17 AM, Marc Logemann <li...@logemann.org> wrote:
> Hi,
>
> since a few hours i am trying out ivy and so far i am excited. I hate maven
> but i like dependency management, so ivy and ant is the way to go.
> But two question arise:
>
> Question 1)
>
> I am trying to resolve spring-context dependency as defined in my ivy.xml
> file like this:
>
> <dependency org="org.springframework" name="spring-context" rev="2.5.5"/>
>
> which results in :
>
> :: problems summary ::
> :::: WARNINGS
> module not found: javax.ejb#ejb;3.0
> ==== local: tried
> /Users/ml/.ivy2/local/javax.ejb/ejb/3.0/ivys/ivy.xml
> -- artifact javax.ejb#ejb;3.0!ejb.jar:
> /Users/ml/.ivy2/local/javax.ejb/ejb/3.0/jars/ejb.jar
> ==== shared: tried
> /Users/ml/.ivy2/shared/javax.ejb/ejb/3.0/ivys/ivy.xml
> -- artifact javax.ejb#ejb;3.0!ejb.jar:
> /Users/ml/.ivy2/shared/javax.ejb/ejb/3.0/jars/ejb.jar
> ==== public: tried
> http://repo1.maven.org/maven2/javax/ejb/ejb/3.0/ejb-3.0.pom
> -- artifact javax.ejb#ejb;3.0!ejb.jar:
> http://repo1.maven.org/maven2/javax/ejb/ejb/3.0/ejb-3.0.jar
> [FAILED ] javax.jms#jms;1.1!jms.jar: (0ms)
> ==== shared: tried
> /Users/ml/.ivy2/shared/javax.jms/jms/1.1/jars/jms.jar
> ==== public: tried
> http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
> [FAILED ]
> com.bea.wlplatform#commonj-twm;1.1!commonj-twm.jar: (0ms)
> ==== shared: tried
>
> /Users/ml/.ivy2/shared/com.bea.wlplatform/commonj-twm/1.1/jars/commonj-twm.jar
> ==== public: tried
>
> http://repo1.maven.org/maven2/com/bea/wlplatform/commonj-twm/1.1/commonj-twm-1.1.jar
> ::::::::::::::::::::::::::::::::::::::::::::::
> :: UNRESOLVED DEPENDENCIES ::
> ::::::::::::::::::::::::::::::::::::::::::::::
> :: javax.ejb#ejb;3.0: not found
> ::::::::::::::::::::::::::::::::::::::::::::::
>
> ::::::::::::::::::::::::::::::::::::::::::::::
> :: FAILED DOWNLOADS ::
> :: ^ see resolution messages for details ^ ::
> ::::::::::::::::::::::::::::::::::::::::::::::
> :: javax.jms#jms;1.1!jms.jar
> :: com.bea.wlplatform#commonj-twm;1.1!commonj-twm.jar
> ::::::::::::::::::::::::::::::::::::::::::::::
>
>
>
> Now i wondering why such a common library has broken deps. Can it be that
> the default reposity that ivy uses (i think via default config inside
> ivy.jar) is kind of a mess? Should people define more than one repository to
> reduce changes that things like that happen?
>
> Question 2)
>
> I have some non-open source libraries which should be made available in a
> team or company repository. What to do exactly to achieve this? Have not
> found too much on this. (BTW i would love to buy an ivy book at some book
> store, but there is none isnt it?).
>
> Thanks for some hints....
>
>
> ---
> regards
> Marc Logemann
> http://www.logemann.org
> http://www.logentis.de
>
>
>
>
>
Re: Newbie: failed dependencies and local (team) repositories for non-open-source stuff
Posted by Marc Logemann <li...@logemann.org>.
will give it a try.....
---
regards
Marc Logemann
http://www.logemann.org
http://www.logentis.de
Am 11.03.2009 um 19:10 schrieb Aaron Siri:
> We have been using Nexus as both a caching proxy for the public
> repos and to
> manage our own artifacts.
>
> Probably worth looking into. http://nexus.sonatype.org/
>
> It is maven centric but works fine with Ivy as well.
>
> -Aaron
>
>
>
> On Wed, Mar 11, 2009 at 10:17 AM, Marc Logemann <li...@logemann.org>
> wrote:
>
>> Hi,
>>
>> since a few hours i am trying out ivy and so far i am excited. I
>> hate maven
>> but i like dependency management, so ivy and ant is the way to go.
>> But two question arise:
>>
>> Question 1)
>>
>> I am trying to resolve spring-context dependency as defined in my
>> ivy.xml
>> file like this:
>>
>> <dependency org="org.springframework" name="spring-context"
>> rev="2.5.5"/>
>>
>> which results in :
>>
>> :: problems summary ::
>> :::: WARNINGS
>> module not found: javax.ejb#ejb;3.0
>> ==== local: tried
>> /Users/ml/.ivy2/local/javax.ejb/ejb/3.0/ivys/ivy.xml
>> -- artifact javax.ejb#ejb;3.0!ejb.jar:
>> /Users/ml/.ivy2/local/javax.ejb/ejb/3.0/jars/ejb.jar
>> ==== shared: tried
>> /Users/ml/.ivy2/shared/javax.ejb/ejb/3.0/ivys/ivy.xml
>> -- artifact javax.ejb#ejb;3.0!ejb.jar:
>> /Users/ml/.ivy2/shared/javax.ejb/ejb/3.0/jars/ejb.jar
>> ==== public: tried
>> http://repo1.maven.org/maven2/javax/ejb/ejb/3.0/ejb-3.0.pom
>> -- artifact javax.ejb#ejb;3.0!ejb.jar:
>> http://repo1.maven.org/maven2/javax/ejb/ejb/3.0/ejb-3.0.jar
>> [FAILED ] javax.jms#jms;1.1!jms.jar: (0ms)
>> ==== shared: tried
>> /Users/ml/.ivy2/shared/javax.jms/jms/1.1/jars/jms.jar
>> ==== public: tried
>> http://repo1.maven.org/maven2/javax/jms/jms/1.1/jms-1.1.jar
>> [FAILED ]
>> com.bea.wlplatform#commonj-twm;1.1!commonj-twm.jar: (0ms)
>> ==== shared: tried
>>
>> /Users/ml/.ivy2/shared/com.bea.wlplatform/commonj-twm/1.1/jars/
>> commonj-twm.jar
>> ==== public: tried
>>
>> http://repo1.maven.org/maven2/com/bea/wlplatform/commonj-twm/1.1/commonj-twm-1.1.jar
>> ::::::::::::::::::::::::::::::::::::::::::::::
>> :: UNRESOLVED DEPENDENCIES ::
>> ::::::::::::::::::::::::::::::::::::::::::::::
>> :: javax.ejb#ejb;3.0: not found
>> ::::::::::::::::::::::::::::::::::::::::::::::
>>
>> ::::::::::::::::::::::::::::::::::::::::::::::
>> :: FAILED DOWNLOADS ::
>> :: ^ see resolution messages for details ^ ::
>> ::::::::::::::::::::::::::::::::::::::::::::::
>> :: javax.jms#jms;1.1!jms.jar
>> :: com.bea.wlplatform#commonj-twm;1.1!commonj-twm.jar
>> ::::::::::::::::::::::::::::::::::::::::::::::
>>
>>
>>
>> Now i wondering why such a common library has broken deps. Can it
>> be that
>> the default reposity that ivy uses (i think via default config inside
>> ivy.jar) is kind of a mess? Should people define more than one
>> repository to
>> reduce changes that things like that happen?
>>
>> Question 2)
>>
>> I have some non-open source libraries which should be made
>> available in a
>> team or company repository. What to do exactly to achieve this?
>> Have not
>> found too much on this. (BTW i would love to buy an ivy book at
>> some book
>> store, but there is none isnt it?).
>>
>> Thanks for some hints....
>>
>>
>> ---
>> regards
>> Marc Logemann
>> http://www.logemann.org
>> http://www.logentis.de
>>
>>
>>
>>
>>