On Fri, 29 Jan 2021 at 08:59, Stefan Bodewig wrote:
> On 2021-01-28, Jaikiran Pai wrote:
>
> > I had a quick look and to me this looks like a bug in our build.xml
> > itself and not related to Ivy.
>
> My bad. I must admit I really don't know much about Ivy at all and
> forgot how the jars we pub
On 2021-01-28, Jaikiran Pai wrote:
> I had a quick look and to me this looks like a bug in our build.xml
> itself and not related to Ivy.
My bad. I must admit I really don't know much about Ivy at all and
forgot how the jars we publish get prepared. I assumed Ivy was using our
poms, which it obvi
I've now committed that change to both master and 1.9.x branches upstream.
-Jaikiran
On 28/01/21 4:22 pm, Jaikiran Pai wrote:
Hello Stefan,
I had a quick look and to me this looks like a bug in our build.xml
itself and not related to Ivy. The source jar for testutil gets
generated as part of
Hello Stefan,
I had a quick look and to me this looks like a bug in our build.xml
itself and not related to Ivy. The source jar for testutil gets
generated as part of our Ant "test-jar-source" which is using a wrong
directory to find the testutil sources. I have opened a PR
https://github.com
Hello Stefan,
I can take a look at it later tonight and see what's going on.
-Jaikiran
On 28/01/21 2:21 pm, Stefan Bodewig wrote:
Hi
https://bz.apache.org/bugzilla/show_bug.cgi?id=65110
when creating and publishing an Ant release we seem to create empty
source jars for ant-testutil - and onl
