Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-21005

Maven site configuration causes downstream projects to get a directory named ${project.basedir}

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 3.0.0, 2.2.0, 2.1.1, 2.0.2
    • Component/s: build
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      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.

        Attachments

        1. HBASE-21005.001.patch
          460 kB
          Josh Elser
        2. HBASE-21005.002.patch
          460 kB
          Josh Elser

          Issue Links

            Activity

              People

              • Assignee:
                elserj Josh Elser
                Reporter:
                mattyb149 Matt Burgess
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: