ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eyad Ebrahim <tya...@gmail.com>
Subject Re: Question about module builds
Date Fri, 29 Nov 2013 17:21:48 GMT
Out of a similar experience. Analyse the dependency and break it. Module C
is due
On Nov 29, 2013 6:10 PM, "Tjeerd Verhagen" <tjeerd.verhagen@gmail.com>
wrote:

> Hello,
>
> It is never good to have recursive dependencies. So think of a way to get
> these out off the way. And especially in test jars, they should never
> depend up on other test jars. In case you have some supporting classes,
> which are only used in test jars, create a normal jar, similar like the
> spring-test-util jar. It is a test cases helper jar, but not a jar which
> contains tests.
>
> Hope this helps.
>
> Kind regards, Tjeerd
>
>
> On Fri, Nov 29, 2013 at 5:56 PM, Steve Heyns <notzippy@gmail.com> wrote:
>
> > Hi
> >
> > I am trying to migrate 2 build scripts to use ivy, they are 2 separate
> > modules. What I want to publish is
> >
> > module a.jar (conf main)
> > module a test.jar (conf test)
> >
> > module b.jar (conf main)
> > module b test.jar (conf test)
> >
> > Issue is that module a test depends on module b, and module b test
> depends
> > on module a. The current way to build is to compile module a, then
> module b
> > then module a test, the module b test. To replicate this using ivy I
> would
> > need to be able to publish the source from both modules without the test
> > artifact, then publish the test artifacts. From what I understand
> > publishing only one artifact is not possible with ivy. But it seems odd
> to
> > define separate  ivy files. Anyone with ideas >
> >
> > thanks
> > Nz
> >
>

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