[ 
https://issues.apache.org/jira/browse/SOLR-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15284865#comment-15284865
 ] 

Misha Dmitriev commented on SOLR-9109:
--------------------------------------

I am not familiar with fine-level details of how Ant works, so let's make sure 
that we are on the same page and clarify what happens here. Currently (before 
my change) there is the following relationship between files under solr/lucene 
(arrow means "sources" or "includes"):

common-build.xml -> ivy-settings.xml -> ivy-versions.properties

after my change:

common-build.xml -> ivy-versions.properties
common-build.xml -> ivy-settings.xml (or another ivysettings file if 
supplied/overridden)

So, does the visibility scope of properties from ivy-versions.properties 
(that's what I understand you are concerned about) change after my 
modification? Even if yes, does it matter given that ivy-versions.properties 
belongs to solr/lucene and I don't change anything in it?

> 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

Reply via email to