> I believe I now better understand the provided only adds jars if not
> already there??
Yes. What I was looking for was some way to specify "B depends on the
*source* of A located over *there*". I've now so far managed to tell
Ivy "B depends on the *jar* of A located over there".
As it comes
Hello Robert 'Bobby' Zenz,
I too have been slow to respond for good reason. I had a family crisis that
prevented me from responding.
I believe I now better understand the provided only adds jars if not
already there??
On Sat, Dec 5, 2020 at 11:13 AM Robert 'Bobby' Zenz <
I think I figured it out in a half-way sane way.
What I have now is a project looking like this:
Project
|-modules
| |-ModuleA
| | |-build.xml
| | \-ivy.xml
| \-ModuleB
| |-build.xml
| \-ivy.xml
|-build.xml
|-build-module.xml
Thanks for the fast response, sorry for my slow response.
This is what I needed on the top-level, but how do I reference
correctly project A in project B? Assuming that B depends on A?
I guess I need to set up a resolver, but so far I have a hard time
understanding what exactly I need to do.
And of course, you then just do:
ant clean deploy
from the top level directory and that will then run those targets for
all sub-projects.
-Jaikiran
On 28/11/20 9:34 pm, Jaikiran Pai wrote:
It's a bit too late here, so I'll keep this short for now. In one of
the projects that we have, which
It's a bit too late here, so I'll keep this short for now. In one of the
projects that we have, which has a similar structure, we use Ivy's
buildlist task[1] to first create the ordered list of projects that need
to be built and then invoke on that ordered list. So the top level
build.xml will
