[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2012-03-22 Thread protobuf
Comment #16 on issue 158 by cva...@gmail.com: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 Does the maven plugin get pushed to central also? -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2011-03-10 Thread protobuf
Comment #15 on issue 158 by g...@google.com: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 The upload has been released too oss.sonatype.org. It should mirror to central soon. -- You received this message because you are subscribed to the Google

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2011-03-10 Thread protobuf
Comment #14 on issue 158 by g...@google.com: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 I lost my PGP keys (again) so, I got held up last week. I'm starting this again now. Hopefully, it should be in the repo within the next few hours. -- Yo

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2011-03-09 Thread protobuf
Comment #13 on issue 158 by spat...@gmail.com: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 Just wondering if 2.4.0 will be pushed to the repo anytime soon. Thanks. -- You received this message because you are subscribed to the Google Groups "Proto

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2011-02-15 Thread protobuf
Comment #12 on issue 158 by g...@google.com: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 I hadn't seen that the new version was uploaded. I'll try to get that out this week. Sorry for the delay. -- You received this message because you are su

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2011-02-15 Thread protobuf
Comment #11 on issue 158 by m.boga...@hydrodesk.com: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 How about 2.4.0a? -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2011-01-26 Thread protobuf
Updates: Status: Fixed Owner: g...@google.com Comment #10 on issue 158 by g...@google.com: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 I have to apologize for ignoring this issue. They were assigned to an old account and I wasn't

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2011-01-25 Thread protobuf
Comment #9 on issue 158 by tj.rothw...@gmail.com: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 It appears that 2.4.0's release beat the 2.3.0 push to Google's maven repository. http://code.google.com/p/google-maven-repository/source/browse/reposi

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2010-04-30 Thread protobuf
Comment #8 on issue 158 by octo47: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 please, add this to pom, so we can have sources in repository. org.apache.maven.plugins maven-source-plugin attach-sources jar

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2010-02-23 Thread protobuf
Comment #7 on issue 158 by jasonab: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 The artifact is now in the maven central repository, although not in the Google repository. -- You received this message because you are listed in the owner or CC fiel

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2010-02-10 Thread protobuf
Comment #6 on issue 158 by gk5...@kickstyle.net: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 The issue has been with repository sync, not with deployment. I'm looking into it today. -- You received this message because you are listed in the ow

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2010-02-10 Thread protobuf
Comment #5 on issue 158 by jhuxhorn: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 This should really be included in the normal release procedure. -- You received this message because you are listed in the owner or CC fields of this issue, or because y

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2010-02-10 Thread protobuf
Comment #4 on issue 158 by jarek.odzga: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 Any prospect on when 2.3.0 is available in maven repo? This should be fairly simple thing to do... -- You received this message because you are listed in the owner

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2010-02-08 Thread protobuf
Comment #3 on issue 158 by dmda...@gmail.com: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 A SNAPSHOT mvn option would be nice, too. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred

[protobuf] Re: Issue 158 in protobuf: Push 2.3.0 maven artifact to repo

2010-01-15 Thread protobuf
Updates: Summary: Push 2.3.0 maven artifact to repo Owner: gk5885 Comment #2 on issue 158 by ken...@google.com: Push 2.3.0 maven artifact to repo http://code.google.com/p/protobuf/issues/detail?id=158 Renaming and re-assigning to Greg. Greg, can you publish the 2.3.0 release