[jira] [Commented] (BEAM-3138) Stop depending on Test JARs
[ https://issues.apache.org/jira/browse/BEAM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17546762#comment-17546762 ] Kenneth Knowles commented on BEAM-3138: --- This issue has been migrated to https://github.com/apache/beam/issues/18593 > Stop depending on Test JARs > --- > > Key: BEAM-3138 > URL: https://issues.apache.org/jira/browse/BEAM-3138 > Project: Beam > Issue Type: Bug > Components: io-java-gcp, runner-core, sdk-java-core, sdk-java-harness >Reporter: Thomas Groh >Priority: P3 > Labels: Clarified, beam-fixit > Time Spent: 50m > Remaining Estimate: 0h > > Testing components can be in a testing or otherwise signaled package, but > shouldn't really be depended on by depending on a test jar in the test scope. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (BEAM-3138) Stop depending on Test JARs
[ https://issues.apache.org/jira/browse/BEAM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17143141#comment-17143141 ] Beam JIRA Bot commented on BEAM-3138: - This issue was marked "stale-P2" and has not received a public comment in 14 days. It is now automatically moved to P3. If you are still affected by it, you can comment and move it back to P2. > Stop depending on Test JARs > --- > > Key: BEAM-3138 > URL: https://issues.apache.org/jira/browse/BEAM-3138 > Project: Beam > Issue Type: Bug > Components: io-java-gcp, runner-core, sdk-java-core, sdk-java-harness >Reporter: Thomas Groh >Priority: P3 > Labels: beam-fixit > Time Spent: 50m > Remaining Estimate: 0h > > Testing components can be in a testing or otherwise signaled package, but > shouldn't really be depended on by depending on a test jar in the test scope. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (BEAM-3138) Stop depending on Test JARs
[ https://issues.apache.org/jira/browse/BEAM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17128854#comment-17128854 ] Beam JIRA Bot commented on BEAM-3138: - This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3. Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean. > Stop depending on Test JARs > --- > > Key: BEAM-3138 > URL: https://issues.apache.org/jira/browse/BEAM-3138 > Project: Beam > Issue Type: Bug > Components: io-java-gcp, runner-core, sdk-java-core, sdk-java-harness >Reporter: Thomas Groh >Priority: P2 > Labels: beam-fixit, stale-P2 > Time Spent: 50m > Remaining Estimate: 0h > > Testing components can be in a testing or otherwise signaled package, but > shouldn't really be depended on by depending on a test jar in the test scope. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (BEAM-3138) Stop depending on Test JARs
[ https://issues.apache.org/jira/browse/BEAM-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659679#comment-16659679 ] Kenneth Knowles commented on BEAM-3138: --- I've noticed this is causing needless overhead in the compilation of Nexmark - it depends on the shadowTest configuration of GCP IO, which then pulls in shadowTest of the SDK core. So there's a real cost to this misconfiguration. > Stop depending on Test JARs > --- > > Key: BEAM-3138 > URL: https://issues.apache.org/jira/browse/BEAM-3138 > Project: Beam > Issue Type: Bug > Components: io-java-gcp, runner-core, sdk-java-core, sdk-java-harness >Reporter: Thomas Groh >Priority: Minor > Time Spent: 50m > Remaining Estimate: 0h > > Testing components can be in a testing or otherwise signaled package, but > shouldn't really be depended on by depending on a test jar in the test scope. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
