You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2008/03/25 05:19:25 UTC
[jira] Created: (SOLR-510) client source needs to be included in
releases
client source needs to be included in releases
----------------------------------------------
Key: SOLR-510
URL: https://issues.apache.org/jira/browse/SOLR-510
Project: Solr
Issue Type: Bug
Reporter: Hoss Man
Fix For: 1.3
All of the source code in the client directory needs to be included in our builds/releases ... solrj certainly needs to be included since the releases contain the compiled byte code already, but we should include all of the source for all of hte clients (even if we don't distributed "compiled" versions).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-510) client source needs to be included in
releases
Posted by "Koji Sekiguchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koji Sekiguchi resolved SOLR-510.
---------------------------------
Resolution: Fixed
Committed revision 659125.
> client source needs to be included in releases
> ----------------------------------------------
>
> Key: SOLR-510
> URL: https://issues.apache.org/jira/browse/SOLR-510
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Koji Sekiguchi
> Fix For: 1.3
>
> Attachments: SOLR-510.patch
>
>
> All of the source code in the client directory needs to be included in our builds/releases ... solrj certainly needs to be included since the releases contain the compiled byte code already, but we should include all of the source for all of hte clients (even if we don't distributed "compiled" versions).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (SOLR-510) client source needs to be included in
releases
Posted by "Koji Sekiguchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koji Sekiguchi reassigned SOLR-510:
-----------------------------------
Assignee: Koji Sekiguchi
> client source needs to be included in releases
> ----------------------------------------------
>
> Key: SOLR-510
> URL: https://issues.apache.org/jira/browse/SOLR-510
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Assignee: Koji Sekiguchi
> Fix For: 1.3
>
> Attachments: SOLR-510.patch
>
>
> All of the source code in the client directory needs to be included in our builds/releases ... solrj certainly needs to be included since the releases contain the compiled byte code already, but we should include all of the source for all of hte clients (even if we don't distributed "compiled" versions).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-510) client source needs to be included in
releases
Posted by "Koji Sekiguchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koji Sekiguchi updated SOLR-510:
--------------------------------
Attachment: SOLR-510.patch
The patch would do the trick?
> client source needs to be included in releases
> ----------------------------------------------
>
> Key: SOLR-510
> URL: https://issues.apache.org/jira/browse/SOLR-510
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
> Fix For: 1.3
>
> Attachments: SOLR-510.patch
>
>
> All of the source code in the client directory needs to be included in our builds/releases ... solrj certainly needs to be included since the releases contain the compiled byte code already, but we should include all of the source for all of hte clients (even if we don't distributed "compiled" versions).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.