sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arvind Prabhakar (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-439) Released artifacts should embrace unwritten naming policy
Date Wed, 15 Feb 2012 18:32:59 GMT

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

Arvind Prabhakar commented on SQOOP-439:
----------------------------------------

@Jarcec - thanks for filing this. Perhaps the resolution of this issue is to update our How
To Release page on the wiki and call out the exact details of how the artifacts should be
named. I have the following suggestion:

* Source artifact is named by the project/version as usual: sqoop-1.4.1-incubating.tar.gz
  
* Binary artifacts are named by project/version with a ".bin" suffix and other details like
hadoop version etc. For example: sqoop-1.4.1-incubating.bin__hadoop-0.20.tar.gz

What do you think?
                
> Released artifacts should embrace unwritten naming policy
> ---------------------------------------------------------
>
>                 Key: SQOOP-439
>                 URL: https://issues.apache.org/jira/browse/SQOOP-439
>             Project: Sqoop
>          Issue Type: New Feature
>            Reporter: Jarek Jarcec Cecho
>            Priority: Minor
>
> We should make source artifact default by removing "-src" postfix from it's name to have
similar naming policies as other hadoop related projects.
> More info can be found on following mail thread http://markmail.org/message/krec2kionhxbrmhw

--
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

        

Mime
View raw message