I agree that graduating into an existing TLP seems like the best outcome
here. If the Phoenix community is interested, that seems like a great
target as one of the primary consumers of Tephra.
Any thoughts on how this would impact CDAP. development, the other primary
consumer of Tephra?
Is
anew opened a new pull request #96: (TEPHRA-303) Fix build with maven 3.6.1
URL: https://github.com/apache/incubator-tephra/pull/96
Apparently maven 3.6.1 has issues with relative paths. Changing .. to
${project.parent.basedir} seems to fix that.
[
https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875244#comment-16875244
]
Andreas Neumann commented on TEPHRA-303:
Running mvn --debug, I see that it uses:
{code:java}
[
https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875239#comment-16875239
]
Andreas Neumann commented on TEPHRA-303:
It failed for me on Linux, where I have maven 3.6.1.
[
https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875226#comment-16875226
]
Lars Hofhansl commented on TEPHRA-303:
--
Thanks [~anew]!
> HBase 1.1 tests don't compile
>
[
https://issues.apache.org/jira/browse/TEPHRA-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875223#comment-16875223
]
Andreas Neumann commented on TEPHRA-303:
Looks like my versions I slightly different.
