[ https://issues.apache.org/jira/browse/SOLR-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Misha Dmitriev updated SOLR-9109: --------------------------------- Attachment: SOLR-9109.patch 0001-Support-for-custom-ivysettings.xml.patch > Add support for custom ivysettings.xml > -------------------------------------- > > Key: SOLR-9109 > URL: https://issues.apache.org/jira/browse/SOLR-9109 > Project: Solr > Issue Type: Improvement > Reporter: Misha Dmitriev > Attachments: 0001-Support-for-custom-ivysettings.xml.patch, > SOLR-9109.patch > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org