[
https://issues.apache.org/jira/browse/SOLR-4916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13700262#comment-13700262
]
Mark Miller commented on SOLR-4916:
-----------------------------------
Well that's no help - even if all of this is tied up to the classpaths used, it
doesn't seem to be a mechanism for shielding modules from each other AFAICT. I
guess the main use case is for downstream projects to have the ability to
filter out these dependencies and avoid pulling down the test time dependencies
- but it seems we would care about that in the maven shadow build, not here -
we don't publish based on the ivy files right?
In that case, it would seem we should simply do the same thing as with some of
the other jars in core that are excluded from the webapp - exclude them in the
build.xml and have the maven build treat them as part of a test configuration?
[~steve_rowe], does any of that make any sense?
> Add support to write and read Solr index files and transaction log files to
> and from HDFS.
> ------------------------------------------------------------------------------------------
>
> Key: SOLR-4916
> URL: https://issues.apache.org/jira/browse/SOLR-4916
> Project: Solr
> Issue Type: New Feature
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: 5.0, 4.4
>
> Attachments: SOLR-4916-ivy.patch, SOLR-4916.patch, SOLR-4916.patch,
> SOLR-4916.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
