[ https://issues.apache.org/jira/browse/HBASE-21005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16579260#comment-16579260 ]
Hudson commented on HBASE-21005: -------------------------------- Results for branch branch-2.1 [build #185 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/185/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (/) {color:green}+1 general checks{color} -- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/185//General_Nightly_Build_Report/] (/) {color:green}+1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/185//JDK8_Nightly_Build_Report_(Hadoop2)/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/185//JDK8_Nightly_Build_Report_(Hadoop3)/] (/) {color:green}+1 source release artifact{color} -- See build output for details. (/) {color:green}+1 client integration test{color} > Maven site configuration causes downstream projects to get a directory named > ${project.basedir} > ----------------------------------------------------------------------------------------------- > > Key: HBASE-21005 > URL: https://issues.apache.org/jira/browse/HBASE-21005 > Project: HBase > Issue Type: Bug > Components: build > Affects Versions: 2.0.0 > Reporter: Matt Burgess > Assignee: Josh Elser > Priority: Minor > Fix For: 3.0.0, 2.2.0, 2.1.1 > > Attachments: HBASE-21005.001.patch, HBASE-21005.002.patch > > > Matt told me about this interesting issue they see down in Apache Nifi's build > NiFi depends on HBase for some code that they provide to their users. As a > part of the build process of NiFi, they are seeing a directory named > {{$\{project.basedir}}} get created the first time they build with an empty > Maven repo. Matt reports that after a javax.el artifact is cached, Maven will > stop creating the directory; however, if you wipe that artifact from the > Maven repo, the next build will end up re-creating it. > I believe I've seen this with Phoenix, too, but never investigated why it was > actually happening. > My hunch is that it's related to the local maven repo that we create to > "patch" in our custom maven-fluido-skin jar (HBASE-14785). I'm not sure if we > can "work" around this by pushing the custom local repo into a profile and > only activating that for the mvn-site. Another solution would be to publish > the maven-fluido-jar to central with custom coordinates. -- This message was sent by Atlassian JIRA (v7.6.3#76005)