Yes, it does. As I stated, it works correctly when I specify branches in the
ivy.xml and resolve dependencies (and publish dependencies). It's just when I
try and list modules through the API or the ant tasks.
Also, when I list them through the API, I get duplicates of some of the
revisions
Could you try again with the latest Ivy snapshot?
If I remember correctly, we fixed some branch-related issues. So it might solve
your problem.
Maarten
- Original Message
From: James Davis james.da...@atsid.com
To: ivy-user@ant.apache.org ivy-user@ant.apache.org
Sent: Mon, May 3,
Ivy is worthless if I can't put my own jars in the repository (as is
dependency management in general). Surely there is a way to do this?
mjparme wrote:
I have created a shared repository with ivy:install and that went pretty
much trouble free. I installed some jars we use commonly in our
Maybe it is ivy:publish you are looking for?
http://ant.apache.org/ivy/history/latest-milestone/use/publish.html
Maarten
- Original Message
From: mjparme mjparme...@west.com
To: ivy-user@ant.apache.org
Sent: Mon, May 3, 2010 4:41:04 PM
Subject: Re: Adding proprietary jar to shared
Perhaps I'm misunderstanding something in your post. This is possible,
since you're talking about Maven, and I know almost nothing about
Maven). However, it sounds to me like you want ivy:publish, which is
pretty clearly discussed in the Ivy documentation.
That is what I am looking for, thank you! I am unsure how I missed that, I
have read a large majority of the documentation on the Ivy website and paid
close attention to the ANT task documentation. Maybe I did read it and it
didn't click with me what I would use it foroh well, thanks for the
Thanks for the tip about putting the modules all in one file. I know next to
nothing about Maven as well. Actually new to the whole dependency management
thing. I have always thought it was a solution looking for a problem.
However, figured I would test it out on a project and see for myself.
I
I just tried both routes with the latest snapshot (was built 9 days ago
according to Hudson). No changes.
Here is the resolver patterns that I'm using:
property name=ivy.ats.ivysvn.root
value=svn+ssh://server_name/storage/svn/dependency/ /
property name=ivy.ats.ivysvn.repo.path
I think your problem might be related to IVY-1122.
https://issues.apache.org/jira/browse/IVY-1122
If you could avoid making your [branch] token optional, I think it might work.
Maybe you could try with 2 ivy/artifact patterns? (I'm not sure the svn
resolver supports this though)
svn ...
ivy
This does appear to be the issue. I removed the optional branch markups and
created a second svn resolver with the branch parts listed as non-optional (so,
I had two svn resolvers one with branches as non-optional and the other without
any reference to branches).
When I tried the ant task, I
Hello,
I have a couple of questions regarding ivy in a multi-module environment.
Is it possible in ivy to optionally 'resolve' a dependency directly to
a classes directory instead of a jar? This would be a useful thing to
be able to do during development. As I understand IvyDE does do
something
On Mon, May 3, 2010 at 6:55 PM, Mike Goodwin mike.good...@cantab.netwrote:
The second thing is, is it possible to create a resolver which will
checkout and build a dependency from source control? Is it possible to
configure such a resolver inside the dependee project/ivy.xml so that
it can be
12 matches
Mail list logo
