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

Steven Rowe commented on SOLR-2770:
-----------------------------------

bq. I'll also forward-port to trunk, which has the same problem.

Ack, trunk does *not* have the same problem - the jdk16-compiled jar in trunk 
is exactly the same as the artifact already available from Maven central 
repository.

> The Solr 3.4.0 release's maven artifacts don't include the jdk1.5-compiled 
> carrot2-core jar
> -------------------------------------------------------------------------------------------
>
>                 Key: SOLR-2770
>                 URL: https://issues.apache.org/jira/browse/SOLR-2770
>             Project: Solr
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 3.4
>            Reporter: Steven Rowe
>            Assignee: Steven Rowe
>            Priority: Minor
>         Attachments: SOLR-2770.patch
>
>
> The Solr-specific jdk1.5-compiled version of the carrot2-core jar (in 
> {{solr/contrib/clustering/lib/}}) was not part of the 3.4.0 release - there 
> should be a {{3.4.0/}} directory here but there is not: 
> http://repo1.maven.org/maven2/org/apache/solr/solr-carrot2-core/.  This 
> artifact was part of the 3.3.0 release.  The build system changes under 
> SOLR-2452 are the cause.
> [Dawid Weiss indicated on 
> SOLR-2428|https://issues.apache.org/jira/browse/SOLR-2428?focusedCommentId=13105381&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13105381]
>  that this Solr-specific jdk1.5-compiled artifact will continue to be 
> required for the remainder of the 3.X release line.

--
This message is automatically generated by JIRA.
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]

Reply via email to