Update the versions of the packages used by the Dart protoc plugin

Update the versions of the packages used by the Dart protoc plugin

R=sigmund@google.com
BUG=

Committed: https://github.com/dart-lang/protoc-plugin/commit/66d82e3

[Siggi Cherem (dart-lang), 2013-08-30 16:14:45]

mmm.. We shouldn't actually have the pubspec.lock file in the repo. Instead,
let's update the pubspec.yaml and add 'pubspec.lock' to the .gitignore.
Basically doing a 'pub install' and 'pub update' should find a version that
works, and should create the lock file for you.

I noticed that we have a git-dependency to load the protobuf client libraries, I
think we should also switch to use a normal hosted dependency (loaded from
pub.dartlang.org instead).

[Søren Gjesse, 2013-09-02 10:22:57]

On 2013/08/30 16:14:45, Siggi Cherem (dart-lang) wrote:
> mmm.. We shouldn't actually have the pubspec.lock file in the repo. Instead,
> let's update the pubspec.yaml and add 'pubspec.lock' to the .gitignore.
> Basically doing a 'pub install' and 'pub update' should find a version that
> works, and should create the lock file for you.
> 
> I noticed that we have a git-dependency to load the protobuf client libraries,
I
> think we should also switch to use a normal hosted dependency (loaded from
> http://pub.dartlang.org instead).

As I see it the protoc plugin is an application package, and therefore should
have pubspec.lock checked in. See
http://pub.dartlang.org/doc/glossary.html#application-package. We don't want
people using the protoc plugin to get other versions of the dependent libraries
than to ones we tested with when committed.

[Siggi Cherem (dart-lang), 2013-09-02 15:39:01]

On 2013/09/02 10:22:57, Søren Gjesse wrote:
> On 2013/08/30 16:14:45, Siggi Cherem (dart-lang) wrote:
> > mmm.. We shouldn't actually have the pubspec.lock file in the repo. Instead,
> > let's update the pubspec.yaml and add 'pubspec.lock' to the .gitignore.
> > Basically doing a 'pub install' and 'pub update' should find a version that
> > works, and should create the lock file for you.
> > 
> > I noticed that we have a git-dependency to load the protobuf client
libraries,
> I
> > think we should also switch to use a normal hosted dependency (loaded from
> > http://pub.dartlang.org instead).
> 
> As I see it the protoc plugin is an application package, and therefore should
> have pubspec.lock checked in. See
> http://pub.dartlang.org/doc/glossary.html#application-package. We don't want
> people using the protoc plugin to get other versions of the dependent
libraries
> than to ones we tested with when committed.

I'm not so sure. I see application packages as final applications that no one
depends on. I think we expect people to have the protoc compiler as a dependency
on their projects, in which case I believe it falls more in the category a
library package. In that case, my understanding is that .lock files won't be
used if you depend on this package, but I'll chat with Bob to better understand
that distinction.

For what it's worth, the changes you have LGTM, so feel free to submit if this
is blocking anything else.

[Søren Gjesse, 2013-09-03 11:15:47]

Committed patchset #1 manually as r66d82e3 (presubmit successful).