[jira] [Updated] (SOLR-9109) Add support for custom ivysettings.xml
[ https://issues.apache.org/jira/browse/SOLR-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated SOLR-9109: - Attachment: SOLR-9109.patch Okay, I'll commit it - here's the final patch with a CHANGES.txt entry and some comments in the Ivy settings files. I expect 6.1 will be released in roughly a month. Once the process starts, which it has yet to do for 6.1, it takes 2-4 weeks for a release to be put together, vetted, and published, assuming no major problems are found. > 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, SOLR-9109.patch, SOLR-9109.patch, SOLR-9109.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
[jira] [Updated] (SOLR-9109) Add support for custom ivysettings.xml
[ https://issues.apache.org/jira/browse/SOLR-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated SOLR-9109: - Attachment: SOLR-9109.patch bq. Can we change the forbiddenapis one to work in a similar way? I can do that in a separate commit, but as you are already working on it, maybe change it! Sure, this version of the patch adds a "ivyversions." prefix to the properties loaded in that target. > 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, SOLR-9109.patch, SOLR-9109.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
[jira] [Updated] (SOLR-9109) Add support for custom ivysettings.xml
[
https://issues.apache.org/jira/browse/SOLR-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Rowe updated SOLR-9109:
-
Attachment: SOLR-9109.patch
Sorry, previous patch didn't work because I changed a file name without
changing where it was referred from.
Using this version of the patch, {{ant clean-jars resolve}} works for me.
I also successfully specified an alternative xml settings file via {{ant
-Dxmlsettings.xml=/path/to/my-settings.xml clean-jars resolve}} (after first
removing the default nested ivy settings file) - note that I provided a full
path there, because the relative path is interpreted relative to the
{{lucene/}} subdir, not the top-level directory.
> 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, SOLR-9109.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
[jira] [Updated] (SOLR-9109) Add support for custom ivysettings.xml
[ https://issues.apache.org/jira/browse/SOLR-9109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Rowe updated SOLR-9109: - Attachment: SOLR-9109.patch Note that the tag in ivy-settings.xml populates Ivy variables, not Ant properties, so there is no property leakage outside of the scope in which those definitions are required. This patch should enable what you want while still retaining the exact same scope as previously, by using nested ivy-settings.xml files. > 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, 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
[jira] [Updated] (SOLR-9109) Add support for custom ivysettings.xml
[ 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
