thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Erickson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (THRIFT-3351) Publishing Dart Bindings for Thrift to Pub (pub.dartlang.org)
Date Tue, 12 Sep 2017 15:57:00 GMT

     [ https://issues.apache.org/jira/browse/THRIFT-3351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mark Erickson updated THRIFT-3351:
----------------------------------
    Description: 
The thrift library for Dart has been released in 0.10.0

In order for developers to actually make use of the library, the Dart package needs to be
published to https://pub.dartlang.org. The current workaround is to create a new GitHub repo
with a copy of the Dart thrift library, and reference that in consuming Dart code via a Git
reference, which is not ideal.

This may become a little better with Dart 1.25.0 (not released yet), which [adds the ability|https://github.com/dart-lang/sdk/blob/1.25.0-dev.16.3/CHANGELOG.md#tool-changes]
to reference a library in a subdirectory via git. But it would still be better to explicitly
publish releases for Dart to pub.dartlang.org.

More information here: 
- https://www.dartlang.org/tools/pub/publishing
- https://www.dartlang.org/tools/pub/cmd/pub-lish.html

Since we're creating the Dart bindings for Thrift, we are also more than willing to publish
them to Pub - but we wanted to give the apache thrift team the opportunity to handle this
process. Ownership of the publishing process can be shared by adding multiple email addresses
to the uploader list, and the uploader list can be updated at any time. It does require a
Google email address (gmail or Google Apps) to perform the upload.

  was:
The thrift library for Dart has been released in 0.10.0

In order for developers to actually make use of the library, the Dart package needs to be
published to https://pub.dartlang.org. The current workaround is to create a new GitHub repo
with a copy of the Dart thrift library, and reference that in consuming Dart code via a Git
reference, which is not ideal.

More information here: 
- https://www.dartlang.org/tools/pub/publishing
- https://www.dartlang.org/tools/pub/cmd/pub-lish.html

Since we're creating the Dart bindings for Thrift, we are also more than willing to publish
them to Pub - but we wanted to give the apache thrift team the opportunity to handle this
process. Ownership of the publishing process can be shared by adding multiple email addresses
to the uploader list, and the uploader list can be updated at any time. It does require a
Google email address (gmail or Google Apps) to perform the upload.


> Publishing Dart Bindings for Thrift to Pub (pub.dartlang.org)
> -------------------------------------------------------------
>
>                 Key: THRIFT-3351
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3351
>             Project: Thrift
>          Issue Type: Story
>          Components: Dart - Library
>            Reporter: Evan Weible
>            Assignee: Jake Farrell
>
> The thrift library for Dart has been released in 0.10.0
> In order for developers to actually make use of the library, the Dart package needs to
be published to https://pub.dartlang.org. The current workaround is to create a new GitHub
repo with a copy of the Dart thrift library, and reference that in consuming Dart code via
a Git reference, which is not ideal.
> This may become a little better with Dart 1.25.0 (not released yet), which [adds the
ability|https://github.com/dart-lang/sdk/blob/1.25.0-dev.16.3/CHANGELOG.md#tool-changes] to
reference a library in a subdirectory via git. But it would still be better to explicitly
publish releases for Dart to pub.dartlang.org.
> More information here: 
> - https://www.dartlang.org/tools/pub/publishing
> - https://www.dartlang.org/tools/pub/cmd/pub-lish.html
> Since we're creating the Dart bindings for Thrift, we are also more than willing to publish
them to Pub - but we wanted to give the apache thrift team the opportunity to handle this
process. Ownership of the publishing process can be shared by adding multiple email addresses
to the uploader list, and the uploader list can be updated at any time. It does require a
Google email address (gmail or Google Apps) to perform the upload.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message