[ 
https://issues.apache.org/jira/browse/SOLR-5848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Rowe reopened SOLR-5848:
------------------------------


I looked at {{kite-morphlines-core-0.11.0.jar}} on both of the Cloudera 
repositories used by Ivy in the Lucene/Solr build:

{noformat}
<ibiblio name="cloudera" 
root="https://repository.cloudera.com/artifactory/repo"; m2compatible="true" />
<ibiblio name="releases.cloudera.com" 
root="https://repository.cloudera.com/content/repositories/releases"; 
m2compatible="true" />
{noformat}

Both of these repos contain the same jar, with checksum: 
d937428805e0e1e4e074769d732ea61293cbe5e8 

On trunk, {{solr/licenses/kite-morphlines-core-0.11.0.jar.sha1}} contains: 
6dfd4325dcd202e24104ff1eb604fcf4322b917c

[[email protected]], this seems bad, given that Maven repos are supposed 
to be immutable - do you think Cloudera will restore the former versions of the 
jars?  Or should Solr switch to the checksums for the new versions of the jars?

> Morphlines is not resolving
> ---------------------------
>
>                 Key: SOLR-5848
>                 URL: https://issues.apache.org/jira/browse/SOLR-5848
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Dawid Weiss
>            Assignee: Mark Miller
>            Priority: Critical
>             Fix For: 4.8, 5.0
>
>
> This version of morphlines does not resolve for me and Grant.
> {code}
> ::::::::::::::::::::::::::::::::::::::::::::::
> ::          UNRESOLVED DEPENDENCIES         ::
> ::::::::::::::::::::::::::::::::::::::::::::::
> :: org.kitesdk#kite-morphlines-saxon;0.11.0: not found
> :: org.kitesdk#kite-morphlines-hadoop-sequencefile;0.11.0: not found
> {code}
> Has this been deleted from Cloudera's repositories or something? This would 
> be pretty bad -- maven repos should be immutable...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to