[ 
https://issues.apache.org/jira/browse/KAFKA-16801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848254#comment-17848254
 ] 

Greg Harris commented on KAFKA-16801:
-------------------------------------

I think the options are:
 # Prevent the 'test' task from existing for these subprojects so it can't fail
 # Trying to find a flag in the build which lets us keep the old behavior
 # Adding a single dummy Junit test
 # Moving these sources to `main`

I don't know if 1 or 2 is even possible in the gradle model, the test target 
might be mandatory, and the new behavior might be mandatory.

(3) seems like it would be a stop-gap solution, but isn't good if these are 
commonly used without a junit dependency, as that would make the dummy junit 
classes unloadable.

(4) is what we did recently (KAFKA-14759) with connect:test-plugins, but is the 
most disruptive. If these are only used in the system tests (no outside 
dependencies) then I think this would probably be the best option.

> Streams upgrade :test target doesn't find any junit tests
> ---------------------------------------------------------
>
>                 Key: KAFKA-16801
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16801
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: streams
>            Reporter: Greg Harris
>            Priority: Major
>              Labels: newbie
>
> No test executed. This behavior has been deprecated.    
> This will fail with an error in Gradle 9.0.    
> There are test sources present but no test was executed. Please check your 
> test configuration.    
> [Documentation|https://docs.gradle.org/8.7/userguide/upgrading_version_8.html#test_task_fail_on_no_test_executed]
>     
> 23 usages
>  
> Task::streams:upgrade-system-tests-0100:test    
> Task::streams:upgrade-system-tests-0101:test    
> Task::streams:upgrade-system-tests-0102:test    
> Task::streams:upgrade-system-tests-0110:test    
> Task::streams:upgrade-system-tests-10:test    
> Task::streams:upgrade-system-tests-11:test    
> Task::streams:upgrade-system-tests-20:test    
> Task::streams:upgrade-system-tests-21:test    
> Task::streams:upgrade-system-tests-22:test    
> Task::streams:upgrade-system-tests-23:test    
> Task::streams:upgrade-system-tests-24:test    
> Task::streams:upgrade-system-tests-25:test    
> Task::streams:upgrade-system-tests-26:test    
> Task::streams:upgrade-system-tests-27:test    
> Task::streams:upgrade-system-tests-28:test    
> Task::streams:upgrade-system-tests-30:test    
> Task::streams:upgrade-system-tests-31:test    
> Task::streams:upgrade-system-tests-32:test    
> Task::streams:upgrade-system-tests-33:test    
> Task::streams:upgrade-system-tests-34:test    
> Task::streams:upgrade-system-tests-35:test    
> Task::streams:upgrade-system-tests-36:test    
> Task::streams:upgrade-system-tests-37:test



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to