You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2010/02/19 02:36:27 UTC

[jira] Created: (AVRO-421) src & doc tarballs not right

src & doc tarballs not right
----------------------------

                 Key: AVRO-421
                 URL: https://issues.apache.org/jira/browse/AVRO-421
             Project: Avro
          Issue Type: Bug
          Components: build
            Reporter: Doug Cutting
            Assignee: Doug Cutting
             Fix For: 1.3.0


The src tarball has build/ at the start of the path of all the files in it.  That should be removed.

The doc tarball does not contain the documentation.  It should.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (AVRO-421) src & doc tarballs not right

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AVRO-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835546#action_12835546 ] 

Doug Cutting commented on AVRO-421:
-----------------------------------

C is also commented out of the top-level dist target.

> src & doc tarballs not right
> ----------------------------
>
>                 Key: AVRO-421
>                 URL: https://issues.apache.org/jira/browse/AVRO-421
>             Project: Avro
>          Issue Type: Bug
>          Components: build
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 1.3.0
>
>
> The src tarball has build/ at the start of the path of all the files in it.  That should be removed.
> The doc tarball does not contain the documentation.  It should.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (AVRO-421) src & doc tarballs not right

Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AVRO-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Doug Cutting resolved AVRO-421.
-------------------------------

    Resolution: Fixed

I just committed a fix for this.

> src & doc tarballs not right
> ----------------------------
>
>                 Key: AVRO-421
>                 URL: https://issues.apache.org/jira/browse/AVRO-421
>             Project: Avro
>          Issue Type: Bug
>          Components: build
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 1.3.0
>
>
> The src tarball has build/ at the start of the path of all the files in it.  That should be removed.
> The doc tarball does not contain the documentation.  It should.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (AVRO-421) src & doc tarballs not right

Posted by "Matt Massie (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AVRO-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835602#action_12835602 ] 

Matt Massie commented on AVRO-421:
----------------------------------

It looks like the C dist target was accidentally commented out by Scott at svn r902301 (AVRO-349. Fix C++ build for post-AVRO-163).

Please uncomment the top-level dist target for C as part of the fix for this JIRA.  

> src & doc tarballs not right
> ----------------------------
>
>                 Key: AVRO-421
>                 URL: https://issues.apache.org/jira/browse/AVRO-421
>             Project: Avro
>          Issue Type: Bug
>          Components: build
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 1.3.0
>
>
> The src tarball has build/ at the start of the path of all the files in it.  That should be removed.
> The doc tarball does not contain the documentation.  It should.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.