Josh Elser created HBASE-21005:
----------------------------------
Summary: 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
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)
