[
https://issues.apache.org/jira/browse/KAFKA-17479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-17479.
--
Resolution: Fixed
This has been done for a while now
> Utilize Gradle build cache on Git
[
https://issues.apache.org/jira/browse/KAFKA-18278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-18278.
Resolution: Fixed
> the name and description of `run-gradle` is incorr
Chia-Ping Tsai created KAFKA-18278:
--
Summary: the name and description of `run-gradle` is incorrect
Key: KAFKA-18278
URL: https://issues.apache.org/jira/browse/KAFKA-18278
Project: Kafka
Dejan Stojadinović created KAFKA-18142:
--
Summary: Switch Kafka's Gradle build shadow plugin to
`com.gradleup.shadow`
Key: KAFKA-18142
URL: https://issues.apache.org/jira/browse/KAFKA-
[
https://issues.apache.org/jira/browse/KAFKA-17974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-17974.
Fix Version/s: 4.0.0
Resolution: Fixed
> Upgrade gradle from 8.10 to 8.1
Chia-Ping Tsai created KAFKA-17974:
--
Summary: Upgrade gradle from 8.10 to 8.10.2
Key: KAFKA-17974
URL: https://issues.apache.org/jira/browse/KAFKA-17974
Project: Kafka
Issue Type
Greg Harris created KAFKA-17798:
---
Summary: Add forbidden-apis linting to gradle build
Key: KAFKA-17798
URL: https://issues.apache.org/jira/browse/KAFKA-17798
Project: Kafka
Issue Type
[
https://issues.apache.org/jira/browse/KAFKA-17673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur resolved KAFKA-17673.
--
Resolution: Fixed
Fixed in https://github.com/apache/kafka/pull/17336
> Gradle Build Scan
David Arthur created KAFKA-17673:
Summary: Gradle Build Scan PR check not showing
Key: KAFKA-17673
URL: https://issues.apache.org/jira/browse/KAFKA-17673
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-17352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Federico Valeri resolved KAFKA-17352.
-
Resolution: Done
> Upgrade Gradle Enterprise to develocity plu
[
https://issues.apache.org/jira/browse/KAFKA-17180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-17180.
Fix Version/s: 4.0.0
Resolution: Fixed
> Upgrade gradle from 8.8 to 8
David Arthur created KAFKA-17352:
Summary: Upgrade Gradle Enterprise to develocity plugin
Key: KAFKA-17352
URL: https://issues.apache.org/jira/browse/KAFKA-17352
Project: Kafka
Issue Type
Chia-Ping Tsai created KAFKA-17180:
--
Summary: Upgrade gradle from 8.8 to 8.9
Key: KAFKA-17180
URL: https://issues.apache.org/jira/browse/KAFKA-17180
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-16804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Harris resolved KAFKA-16804.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Replace gradle archivesBaseName w
Greg Harris created KAFKA-16804:
---
Summary: Replace gradle archivesBaseName with archivesName
Key: KAFKA-16804
URL: https://issues.apache.org/jira/browse/KAFKA-16804
Project: Kafka
Issue Type
Greg Harris created KAFKA-16800:
---
Summary: Resolve Gradle 9.0 deprecations
Key: KAFKA-16800
URL: https://issues.apache.org/jira/browse/KAFKA-16800
Project: Kafka
Issue Type: Task
[
https://issues.apache.org/jira/browse/KAFKA-16490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai resolved KAFKA-16490.
Fix Version/s: 3.8.0
Resolution: Fixed
> Upgrade gradle from 8.6 to
Chia-Ping Tsai created KAFKA-16490:
--
Summary: Upgrade gradle from 8.6 to 8.7
Key: KAFKA-16490
URL: https://issues.apache.org/jira/browse/KAFKA-16490
Project: Kafka
Issue Type: Improvement
Unluckily, I'm going to migrate the build jdk of kafka 2.7 from jdk11 to
jdk21, while gradle doesn't support jdk21...
最红 <1559063...@qq.com.invalid> 于2023年11月15日周三 17:27写道：
> Are there any problems building kafka with gradle?
> You should take a look at the build.gradle f
rain.liang created KAFKA-15829:
--
Summary: How to build Kafka 2.7 with maven instead of gradle?
Key: KAFKA-15829
URL: https://issues.apache.org/jira/browse/KAFKA-15829
Project: Kafka
Issue Type
rain.liang created KAFKA-15810:
--
Summary: Is there a solution to build Kafka-2.7 with gradle-8.4
and jdk-21?
Key: KAFKA-15810
URL: https://issues.apache.org/jira/browse/KAFKA-15810
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-15521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison resolved KAFKA-15521.
Fix Version/s: 3.7.0
Resolution: Fixed
> Refactor build.gradle to align gra
Mickael Maison created KAFKA-15521:
--
Summary: Refactor build.gradle to align gradle swagger plugin with
swagger dependencies
Key: KAFKA-15521
URL: https://issues.apache.org/jira/browse/KAFKA-15521
Said BOUDJELDA created KAFKA-15494:
--
Summary: Remove deprecation call of task registration of Gradle on
build.gradle and use tasks.register instead
Key: KAFKA-15494
URL: https://issues.apache.org/jira/browse
ing
> incompatible with Gradle 8.x
> ---
>
> Key: KAFKA-15235
> URL: https://issues.apache.org/jira/browse/KAFKA-15235
> Project: Kafka
>
Eike Thaden created KAFKA-15235:
---
Summary: No test coverage reports for Java due to settings for
Jacoco being incompatible with Gradle 8.x
Key: KAFKA-15235
URL: https://issues.apache.org/jira/browse/KAFKA-15235
Hello,
Thanks much Divij for the reports and for links
This is issue is not related to a the current used version of Gradle,
it's occurs even on older versions, and every time it happens with zinc
incremental scala compiler, and this because a timeout
on a lock of zinc caches, pos
%20*%0A%3E%20Timeout%20waiting%20to%20lock%20*%20cache%20(/home/jenkins/.gradle/caches/*/*%20It%20is%20currently%20in%20use%20by%20another%20Gradle%20instance.%0A%20%20Owner%20PID:%20*%0A%20%20Our%20PID:%20*%0A%20%20Owner%20Operation:%20%0A%20%20Our%20operation:%20%0A%20%20Lock%20file:%20/home
he latest one, I cannot find any build with the error.
If there's more info, please share with us.
Thank you.
Luke
On Thu, Jul 20, 2023 at 4:41 AM Divij Vaidya
wrote:
> If you see CI failures with the error above, it is possible caused by
> recent gradle upgrade we merged at
> ht
If you see CI failures with the error above, it is possible caused by
recent gradle upgrade we merged at
https://github.com/apache/kafka/pull/14032
I will take a look at it tomorrow and revert the commit if required.
Meanwhile, if someone else gets a chance, please investigate this.
--
Divij
Divij Vaidya created KAFKA-15217:
Summary: Consider usage of Gradle toolchain to specify Java version
Key: KAFKA-15217
URL: https://issues.apache.org/jira/browse/KAFKA-15217
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-14804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison resolved KAFKA-14804.
Fix Version/s: 3.5.0
Resolution: Fixed
> Connect docs fail to build with Gra
David Arthur created KAFKA-14804:
Summary: Connect docs fail to build with Gradle Swagger plugin
2.2.8
Key: KAFKA-14804
URL: https://issues.apache.org/jira/browse/KAFKA-14804
Project: Kafka
Greg Harris created KAFKA-14767:
---
Summary: Gradle build fails with missing commitId after git gc
Key: KAFKA-14767
URL: https://issues.apache.org/jira/browse/KAFKA-14767
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-14680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-14680.
-
Fix Version/s: 3.5.0
Resolution: Fixed
> Gradle version upgrade 7 --&
Dejan Stojadinović created KAFKA-14680:
--
Summary: Gradle version upgrade 7 -->> 8
Key: KAFKA-14680
URL: https://issues.apache.org/jira/browse/KAFKA-14680
Project: Kafka
Issu
it created a massive amount of files that Gradle ended up scanning on
> startup. I just deleted all of these temporarily files and now all is fine!
>
> --
> Matthew de Detrich
> Aiven Deutschland GmbH
> Immanuelkirchstraße 26, 10405 Berlin
> Amtsgericht Charlottenburg, HRB 209
So I figured out the problem, it has nothing to do with Kafka itself.
I was trying out another IDE that used LSP with Java and when it index’ed Kafka
it created a massive amount of files that Gradle ended up scanning on startup.
I just deleted all of these temporarily files and now all is fine
Does this happen consistently?
Ismael
On Tue, Aug 2, 2022 at 4:00 AM Matthew Benedict de Detrich
wrote:
> After syncing my fork with upstream Kafka at some point in time in the
> past I noticed that Gradle takes significantly longer to load, i.e.
> spending 5+ minutes in the conf
After syncing my fork with upstream Kafka at some point in time in the past I
noticed that Gradle takes significantly longer to load, i.e. spending 5+
minutes in the configuration phase when the Gradle runner starts.
Is anyone else experiencing this problem?
--
Matthew de Detrich
Aiven
[
https://issues.apache.org/jira/browse/KAFKA-9948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dulvin Witharane resolved KAFKA-9948.
-
Resolution: Not A Bug
> Gradle Issue
>
>
> Key
hantaoluo created KAFKA-13039:
-
Summary: kafka 0.10.1 gradle build failed
Key: KAFKA-13039
URL: https://issues.apache.org/jira/browse/KAFKA-13039
Project: Kafka
Issue Type: Bug
).
> Version upgrades: gradle (6.8.3 -->> 7.0.1) and gradle shadow plugin (6.1.0
> -->> 7.0.0)
> ---
>
> Key: KAFKA-12728
> URL: https://issues.apac
Dejan Stojadinović created KAFKA-12764:
--
Summary: Exapnd Gradle build for Scala 3.0 ?
Key: KAFKA-12764
URL: https://issues.apache.org/jira/browse/KAFKA-12764
Project: Kafka
Issue Type
Colin McCabe created KAFKA-12755:
Summary: Add server-common, server-tools gradle modules
Key: KAFKA-12755
URL: https://issues.apache.org/jira/browse/KAFKA-12755
Project: Kafka
Issue Type
Dejan Stojadinović created KAFKA-12728:
--
Summary: Update Gradle version: 6.8 -->> 7.0
Key: KAFKA-12728
URL: https://issues.apache.org/jira/browse/KAFKA-12728
Project: Kafka
Issu
[
https://issues.apache.org/jira/browse/KAFKA-8009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-8009.
Resolution: Fixed
This was fixed a while back.
> Uppgrade Jenkins job Gradle version from 4.1
[
https://issues.apache.org/jira/browse/KAFKA-12593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Roesler resolved KAFKA-12593.
--
Resolution: Fixed
> Some Scala, Python, and Gradle files contain the wrong license hea
port.
>
> On 2021/03/10 14:07:08, Alexandre Dupriez wrote:
> > Hi Community,
> >
> > I tried to build Kafka from trunk on my environment today (2021, March
> > 10th) and it failed with the following Gradle error at the beginning
> > of the build, while Gradle co
10th) and it failed with the following Gradle error at the beginning
> of the build, while Gradle configures project from build.gradle:
>
> "Could not get unknown property 'compileJava' for root project
> '' of type org.gradle.api.Project."
>
> Th
Can you please verify if the issue occurs with `./gradlew`? That's the only
supported mechanism.
Ismael
On Wed, Mar 10, 2021 at 1:31 PM Alexandre Dupriez <
alexandre.dupr...@gmail.com> wrote:
> Hi Ismael,
>
> Thanks for your quick response. I used the system-installed gr
Hi Ismael,
Thanks for your quick response. I used the system-installed gradle.
Surprisingly, the same command works successfully as well on my laptop
but not on the target environment - both use the same version of
Gradle (6.8.3) and JDK (1.8), and start with an empty Gradle cache.
Note the error
Hi Alexandre,
Did you use `./gradlew releaseTarGz` (you should never use the system
installed gradle)? That works for me. Also `./gradlew clean releaseTarGz`
works for me.
Ismael
On Wed, Mar 10, 2021 at 8:42 AM Ismael Juma wrote:
> Interesting, I didn't have the same problem. I&#
Interesting, I didn't have the same problem. I'll try to reproduce.
Ismael
On Wed, Mar 10, 2021, 6:07 AM Alexandre Dupriez
wrote:
> Hi Community,
>
> I tried to build Kafka from trunk on my environment today (2021, March
> 10th) and it failed with the following Gradle
Hi Community,
I tried to build Kafka from trunk on my environment today (2021, March
10th) and it failed with the following Gradle error at the beginning
of the build, while Gradle configures project from build.gradle:
"Could not get unknown property 'compileJava' for root pro
[
https://issues.apache.org/jira/browse/KAFKA-12415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-12415.
-
Resolution: Fixed
> Prepare for Gradle 7.0 and restrict transitive scope for non
Ismael Juma created KAFKA-12415:
---
Summary: Prepare for Gradle 7.0 and restrict transitive scope for
non api dependencies
Key: KAFKA-12415
URL: https://issues.apache.org/jira/browse/KAFKA-12415
Project
Dejan Stojadinović created KAFKA-12293:
--
Summary: Remove JCenter and Bintray repositories mentions out of
Gradle build (sunset is announced for those repositories)
Key: KAFKA-12293
URL: https
[
https://issues.apache.org/jira/browse/KAFKA-10256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-10256.
--
Resolution: Won't Fix
> Create a server gradle module for Java code needed only by
Colin McCabe created KAFKA-10256:
Summary: Create a server gradle module for Java code needed only
by servers
Key: KAFKA-10256
URL: https://issues.apache.org/jira/browse/KAFKA-10256
Project: Kafka
[
https://issues.apache.org/jira/browse/KAFKA-9720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-9720.
Assignee: Ismael Juma
Resolution: Fixed
> Update gradle to
Dulvin Witharane created KAFKA-9948:
---
Summary: Gradle Issue
Key: KAFKA-9948
URL: https://issues.apache.org/jira/browse/KAFKA-9948
Project: Kafka
Issue Type: Bug
Components: build
Hi all,
There have been 3 releases since Java 11, so we are halfway to the next
long-term support release (Java 17). It's a good time for Apache Kafka to
start testing with post Java 11 JDKs.
In order to do that, we need to upgrade to Gradle 6.3 which requires some
changes to how we run
ijuma commented on issue #8519:
URL: https://github.com/apache/kafka/pull/8519#issuecomment-616531362
retest this please
This is an automated message from the Apache Git Service.
To respond to the message, please log on to Gi
ijuma opened a new pull request #8519:
URL: https://github.com/apache/kafka/pull/8519
Also remove deprecated `=` in resolutionStrategy.
With these changes, the build works with Java 14 and Scala 2.12. The
same will apply to Scala 2.13 when Scala 2.13.2 is released (should
happen
ijuma commented on issue #7677:
URL: https://github.com/apache/kafka/pull/7677#issuecomment-616272581
@omkreddy I've done a bunch of testing and this seems to work as expected
generally.
One part that I wasn't completely sure about is the behavior of `./gradlew
uploadArchivesAll` in
ijuma commented on issue #7677:
URL: https://github.com/apache/kafka/pull/7677#issuecomment-616271179
I tested `./gradlew install` with trunk versus this PR after `./gradlew
clean`:
* trunk: BUILD SUCCESSFUL in 1m 23s
* this PR: BUILD SUCCESSFUL in 1m 50s
I think that's OK
inactivity on this ticket and no comment after inquiry.
> SBT and Gradle create jars without expected Maven files
> ---
>
> Key: KAFKA-1265
> URL: https://issues.apache.org/jira/br
David Arthur created KAFKA-9720:
---
Summary: Update gradle to 6.0+
Key: KAFKA-9720
URL: https://issues.apache.org/jira/browse/KAFKA-9720
Project: Kafka
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/KAFKA-8786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-8786.
Fix Version/s: 2.5.0
Resolution: Fixed
> Deprecated Gradle features making it incompati
I was trying to use this gradle task and it works, but the files are all
having a timestamp appended to the version. Places like maven central don't
have these timestamps. Is there an option to not have the timestamps
appended when running this task?
Thanks,
Carl
Aljoscha Pörtner created KAFKA-8786:
---
Summary: Deprecated Gradle features making it incompatible with
Gradle 6.0.
Key: KAFKA-8786
URL: https://issues.apache.org/jira/browse/KAFKA-8786
Project
I added a comment.
On Wed, Jun 19, 2019 at 8:10 AM Dejan Stojadinović
wrote:
> Skip to this comment, please:
> https://github.com/apache/kafka/pull/5454#issuecomment-501969180
>
> Regards,
> Dejan
>
Skip to this comment, please:
https://github.com/apache/kafka/pull/5454#issuecomment-501969180
Regards,
Dejan
M. Manna created KAFKA-8394:
---
Summary: Cannot Start a build with New Gradle Version
Key: KAFKA-8394
URL: https://issues.apache.org/jira/browse/KAFKA-8394
Project: Kafka
Issue Type: Bug
Dejan Stojadinović created KAFKA-8009:
-
Summary: Uppgrade Jenkins job Gradle version from 4.10.2 to 5.x
Key: KAFKA-8009
URL: https://issues.apache.org/jira/browse/KAFKA-8009
Project: Kafka
I used to see your issue but I was on an older version of gradle and we
upgraded to 4.8.1.
On gradle 5.0 that issue goes away on my box:
guozhang @kafka-work: gradle --version
Gradle 5.0
Hey friends,
I'm wondering anyone has seen this error before:
Could not find method annotationProcessor() for arguments
[org.openjdk.jmh:jmh-generator-annprocess:1.21] on object of type
org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.
Basically I'm building the trun
FuQiao Wang created KAFKA-7706:
--
Summary: Spotbugs task fails with Gradle 5.0
Key: KAFKA-7706
URL: https://issues.apache.org/jira/browse/KAFKA-7706
Project: Kafka
Issue Type: Bug
[
https://issues.apache.org/jira/browse/KAFKA-7676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-7676.
Resolution: Cannot Reproduce
> Compile Kafka failed with Gradle
Jiangtao Liu created KAFKA-7676:
---
Summary: Kafka compile failed with Gradle 5.0
Key: KAFKA-7676
URL: https://issues.apache.org/jira/browse/KAFKA-7676
Project: Kafka
Issue Type: Bug
Hi All,
Am facing issue when trying to build with gradle kafka repo locally.
Below is the error am hitting,
> Could not GET 'http://dl.bintray.com/content/netflixoss/external-g
radle-plugins/gradle/plugin/com/github/spotbugs/spotbugs-gradle-plugin/1.6.5/spo
tbugs-gradle-plug
Sarvesh Tamba created KAFKA-7581:
Summary: Issues in building kafka using gradle on a Ubuntu based
docker container
Key: KAFKA-7581
URL: https://issues.apache.org/jira/browse/KAFKA-7581
Project
Ismael Juma created KAFKA-7390:
--
Summary: Enable the find-sec-bugs spotBugs plugin for Gradle
Key: KAFKA-7390
URL: https://issues.apache.org/jira/browse/KAFKA-7390
Project: Kafka
Issue Type
Andy LoPresto created KAFKA-7356:
Summary: Add gradle task for dependency listing
Key: KAFKA-7356
URL: https://issues.apache.org/jira/browse/KAFKA-7356
Project: Kafka
Issue Type: New Feature
0.0 with gradle 3.2.1
> ---
>
> Key: KAFKA-6224
> URL: https://issues.apache.org/jira/browse/KAFKA-6224
> Project: Kafka
> Issue Type: Bug
> Components: build
>
[
https://issues.apache.org/jira/browse/KAFKA-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-6390.
Resolution: Fixed
> Update ZooKeeper to 3.4.11, Gradle and other minor upda
Hello again all,
It turns out that the implementation I provided was not correct after all.
The issue was gradle tracked the compiled source files included via
> compile project(':streams').sourceSets.main.output
and included them in the release tarball.
Ewen found the issue and
[
https://issues.apache.org/jira/browse/KAFKA-6390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma reopened KAFKA-6390:
> Update ZooKeeper to 3.4.11, Gradle and other minor upda
gt; >
> > +1
> > Original message From: "Matthias J. Sax" <
> matth...@confluent.io> Date: 3/22/18 9:07 PM (GMT-08:00) To:
> dev@kafka.apache.org Subject: Re: Gradle strategy for exposing and using
> public test-utils modules
> > +1 from my side.
+1
> 在 2018年3月23日，下午12:20，Ted Yu 写道：
>
> +1
> Original message From: "Matthias J. Sax"
> Date: 3/22/18 9:07 PM (GMT-08:00) To:
> dev@kafka.apache.org Subject: Re: Gradle strategy for exposing and using
> public test-utils modules
> +1 fr
+1
Original message From: "Matthias J. Sax"
Date: 3/22/18 9:07 PM (GMT-08:00) To:
dev@kafka.apache.org Subject: Re: Gradle strategy for exposing and using public
test-utils modules
+1 from my side.
-Matthias
On 3/22/18 5:12 PM, John Roesler wrote:
> Yep, I&
t
>>>> would all be good if we followed a similar pattern, so I'll describe
>> the
>>>> streams approach along with one challenge we had to overcome:
>>>>
>>>> =
>>>&
gt; > = Project Structure =
> > > =
> > >
> > > The directory structure goes:
> > >
> > > kafka/streams/ <- main module code here
> > > /test-utils/ <- test utilities m
/test-utils/ <- test utilities module here
> > /examples/<- example usages here
> >
> > Likewise, the artifacts are:
> >
> > kafka-streams
> > kafka-streams-test-utils
> > kafka-streams-examples
> >
> > And finally, the
re goes:
>
> kafka/streams/ <- main module code here
> /test-utils/ <- test utilities module here
> /examples/<- example usages here
>
> Likewise, the artifacts are:
>
> kafka-streams
> kafka-streams-test-utils
ages here
Likewise, the artifacts are:
kafka-streams
kafka-streams-test-utils
kafka-streams-examples
And finally, the Gradle build structure is:
:streams
:streams:test-utils
:streams:examples
=
= Problem 1: circular build =
=
In eat-your-o
uture releases,
which would cover this motivation.
> add gradle option for building tarball with test jars
> -
>
> Key: KAFKA-5509
> URL: https://issues.apache.org/jira/browse/KAFKA-5509
>
[
https://issues.apache.org/jira/browse/KAFKA-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-5895.
Resolution: Fixed
Fix Version/s: 1.1.0
> Gradle 3.0+ is needed on the bu
GitHub user ijuma opened a pull request:
https://github.com/apache/kafka/pull/4345
KAFKA-6390: Update ZooKeeper to 3.4.11, Gradle and other minor updates
Updates:
- Gradle, gradle plugins and maven artifact updated
- Bug fix updates for ZooKeeper, Jackson, EasyMock and
1 - 100 of 533 matches
Mail list logo
