[
https://issues.apache.org/jira/browse/HBASE-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-3560:
-------------------------
Attachment: 3560.txt
Here is one approach. It adds new flag to configuration
hbase.defaults.for.version.skip and sets this flag to true in the
src/test/resources/hbase-site.xml, the test configuration we usually have
before hbase-default.xml on CP because it has all the config. suitable to test
runs.
If fellas are good w/ this, I'll add to faq how to handle the exception if seen.
If someone has better idea, well and good.
> the hbase-default entry of "hbase.defaults.for.version" causes tests not to
> run via not-maven
> ---------------------------------------------------------------------------------------------
>
> Key: HBASE-3560
> URL: https://issues.apache.org/jira/browse/HBASE-3560
> Project: HBase
> Issue Type: Bug
> Reporter: ryan rawson
> Attachments: 3560.txt
>
>
> using the default setup of a maven project for intellij, tests fail because
> the hbase-default.xml contains a token @@@VERSION@@@. The maven build
> creates a substitute file, but this file isn't by default on the classpath.
> Is there a different place to put the hbase-default.xml file than
> target/classes? That is excluded from the classpath because IJ has it's own
> compiler. Including that path in the project classpath seems dangerous.
> Can we get the output to go to just 'target' or
> 'target/generated-sources/org' perhaps?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
