Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-9109

Add support for custom ivysettings.xml

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 6.1
    • None
    • None

    Description

      Currently solr/lucene/common-build.xml hardcodes file ivy-settings.xml in the ivy.configure task. It means that, unlike all other CDH components that use Ant, Solr does not allow the user to provide a custom ivysettings.xml.

      In the Cauldron CDH build, we need to make some adjustments in the build process to satisfy CDH-internal build dependencies with artifacts generated locally, rather than download them from repo1.maven.org etc. E.g. all component should use locally-generated avro-snapshot jars instead of publicly released ones, etc. For Ant, we achieve that by giving it a special ivysettings.xml file, that limits artifact downloading to the local on-disk maven repository and Cloudera artifactory server.

      All CDH components except Solr allow the user to specify a custom ivysettings.xml file by overriding -Divysettings.xml property. We need to add the same feature to Solr. It can be easily achieved by changing several lines in solr/lucene/common-build.xml.

      Attachments

        1. SOLR-9109.patch
          0.0 kB
          Misha Dmitriev
        2. SOLR-9109.patch
          8 kB
          Steven Rowe
        3. SOLR-9109.patch
          8 kB
          Steven Rowe
        4. SOLR-9109.patch
          9 kB
          Steven Rowe
        5. SOLR-9109.patch
          10 kB
          Steven Rowe
        6. 0001-Support-for-custom-ivysettings.xml.patch
          2 kB
          Misha Dmitriev

        Issue Links

          Activity

            People

              sarowe Steven Rowe
              misha@cloudera.com Misha Dmitriev
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: