You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Andrew Bayer (Created) (JIRA)" <ji...@apache.org> on 2011/11/29 17:23:42 UTC

[jira] [Created] (BIGTOP-281) Ivy home for Debian builds should be set to $HOME/.ivy2

Ivy home for Debian builds should be set to $HOME/.ivy2
-------------------------------------------------------

                 Key: BIGTOP-281
                 URL: https://issues.apache.org/jira/browse/BIGTOP-281
             Project: Bigtop
          Issue Type: Improvement
          Components: Debian
    Affects Versions: 0.2.0
            Reporter: Andrew Bayer
            Assignee: Andrew Bayer


Currently, the ivy.home in the Debian rules for all Ivy-related projects is defined as `pwd`/debian/.ivy, meaning that each component build needs to pull down the entire world each time. This is rather inefficient. Optimally, we would set this to $HOME/.ivy2, so that we reuse the same ivy home for all builds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (BIGTOP-281) Ivy home for Debian builds should be set to $HOME/.ivy2

Posted by "Andrew Bayer (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Bayer updated BIGTOP-281:
--------------------------------

    Attachment: trunk-BIGTOP-281.diff.txt
                hadoop-23-BIGTOP-281.diff.txt

Not 100% sure the same patch will apply on both trunk and hadoop-23, so here's a patch for each branch.
                
> Ivy home for Debian builds should be set to $HOME/.ivy2
> -------------------------------------------------------
>
>                 Key: BIGTOP-281
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-281
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Debian
>    Affects Versions: 0.2.0
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>         Attachments: hadoop-23-BIGTOP-281.diff.txt, trunk-BIGTOP-281.diff.txt
>
>
> Currently, the ivy.home in the Debian rules for all Ivy-related projects is defined as `pwd`/debian/.ivy, meaning that each component build needs to pull down the entire world each time. This is rather inefficient. Optimally, we would set this to $HOME/.ivy2, so that we reuse the same ivy home for all builds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (BIGTOP-281) Ivy home for Debian builds should be set to $HOME/.ivy2

Posted by "Bruno Mahé (Commented JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159557#comment-13159557 ] 

Bruno Mahé commented on BIGTOP-281:
-----------------------------------

+1
                
> Ivy home for Debian builds should be set to $HOME/.ivy2
> -------------------------------------------------------
>
>                 Key: BIGTOP-281
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-281
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Debian
>    Affects Versions: 0.2.0
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>         Attachments: hadoop-23-BIGTOP-281.diff.txt, trunk-BIGTOP-281.diff.txt
>
>
> Currently, the ivy.home in the Debian rules for all Ivy-related projects is defined as `pwd`/debian/.ivy, meaning that each component build needs to pull down the entire world each time. This is rather inefficient. Optimally, we would set this to $HOME/.ivy2, so that we reuse the same ivy home for all builds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Resolved] (BIGTOP-281) Ivy home for Debian builds should be set to $HOME/.ivy2

Posted by "Andrew Bayer (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/BIGTOP-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Bayer resolved BIGTOP-281.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.3.0

Fixed in trunk and hadoop-0.23.
                
> Ivy home for Debian builds should be set to $HOME/.ivy2
> -------------------------------------------------------
>
>                 Key: BIGTOP-281
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-281
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Debian
>    Affects Versions: 0.2.0
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>             Fix For: 0.3.0
>
>         Attachments: hadoop-23-BIGTOP-281.diff.txt, trunk-BIGTOP-281.diff.txt
>
>
> Currently, the ivy.home in the Debian rules for all Ivy-related projects is defined as `pwd`/debian/.ivy, meaning that each component build needs to pull down the entire world each time. This is rather inefficient. Optimally, we would set this to $HOME/.ivy2, so that we reuse the same ivy home for all builds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Commented] (BIGTOP-281) Ivy home for Debian builds should be set to $HOME/.ivy2

Posted by "Bruno Mahé (Commented JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/BIGTOP-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159540#comment-13159540 ] 

Bruno Mahé commented on BIGTOP-281:
-----------------------------------

Did you try a build with that patch?
If I remember correctly, it is set to `pwd`/debian/.ivy on purpose because of the chrooting.
                
> Ivy home for Debian builds should be set to $HOME/.ivy2
> -------------------------------------------------------
>
>                 Key: BIGTOP-281
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-281
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Debian
>    Affects Versions: 0.2.0
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>         Attachments: hadoop-23-BIGTOP-281.diff.txt, trunk-BIGTOP-281.diff.txt
>
>
> Currently, the ivy.home in the Debian rules for all Ivy-related projects is defined as `pwd`/debian/.ivy, meaning that each component build needs to pull down the entire world each time. This is rather inefficient. Optimally, we would set this to $HOME/.ivy2, so that we reuse the same ivy home for all builds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira