[HBASE-21005] Maven site configuration causes downstream projects to get a directory named ${project.basedir}

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 3.0.0-alpha-1, 2.2.0, 2.1.1, 2.0.2
• Component/s: build
• Hadoop Flags: Reviewed
• Assignee: Josh Elser
• Reporter: Matt Burgess
• Created: 03/Aug/18 16:11
• Updated: 01/Nov/19 19:00
• Resolved: 14/Aug/18 18:36

Description

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.

Issue Links

• causes: DRILL-6916 Fix extraneous "${project.basedir}/src/site/resources/repo/" directory appearance
• is caused by: HBASE-14785 Hamburger menu for mobile site
• is depended upon by: HBASE-22337 Do not create ${project.basedir} in root
• is depended upon by: HIVE-22443 HBase Maven site configuration causes Hive project to get a directory named ${project.basedir}
• is related to: MSKINS-137 Enable "Hamburger menu" with top-nav only
• relates to: HBASE-22372 Revert back to upstream maven-fluido-skin for website
• relates to: HBASE-19177 Determine if custom maven-fluido-skin jar is still necessary