You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2011/09/10 05:49:10 UTC
[jira] [Resolved] (OOZIE-463) OOZIE-46: Depositing artificat into
public repo
[ https://issues.apache.org/jira/browse/OOZIE-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik resolved OOZIE-463.
------------------------------------
Resolution: Fixed
> OOZIE-46: Depositing artificat into public repo
> -----------------------------------------------
>
> Key: OOZIE-463
> URL: https://issues.apache.org/jira/browse/OOZIE-463
> Project: Oozie
> Issue Type: Task
> Reporter: Mohammad Kamrul Islam
> Assignee: Angelo K. Huang
>
> Since this will be the first time of pushing oozie artifacts into maven repository, I would like to discuss the way yahoo oozie-dev plans to push.
> Our Plan:
> -----------
> 1. We want to use sonatype synchronization with central maven repositories. (https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide).
> 2. We did a POC for SANPSHOT push. (https://oss.sonatype.org/content/repositories/snapshots/com/yahoo/oozie/ )
> 3. We will need to upload the release artifacts.
> Questions:
> 1. Is Sonatype the best way?
> 2. What artifacts should be pushed for user consumption? We want to push oozie client and core jar. What else?
> Comment please.
> Regards,
> Mohammad
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira