[
https://issues.apache.org/jira/browse/HBASE-30214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HBASE-30214:
-----------------------------------
Labels: pull-request-available (was: )
> Add m2e.disableTestClasspathFlag=true to fix Eclipse test classpath for
> workspace projects
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-30214
> URL: https://issues.apache.org/jira/browse/HBASE-30214
> Project: HBase
> Issue Type: Improvement
> Components: build
> Affects Versions: 3.0.0
> Reporter: Aman Poonia
> Priority: Minor
> Labels: pull-request-available
>
> When importing HBase into Eclipse using m2e with all modules as workspace
> projects, test source folders get marked with `test="true"` in generated
> .classpath files. This causes test-scoped sibling dependencies (e.g.
> hbase-common:test-jar) to be invisible when editing test sources in
> dependent modules like hbase-server.
> Fix: add `m2e.disableTestClasspathFlag=true` to the existing
> `eclipse-specific` profile in the root pom.xml. This prevents m2e from
> setting the `test="true"` attribute on test source classpath entries.
> The property is inherited by all child modules and has zero effect on
> CLI Maven builds.
> After "Maven → Update Project" in Eclipse, the regenerated .classpath
> entries for test sources no longer carry `test="true"`, confirming the fix.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
