[
https://issues.apache.org/jira/browse/THRIFT-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796301#action_12796301
]
Kay Kay commented on THRIFT-363:
--------------------------------
| Does one of us have to push the jar into the repo, or can anyone do it?
Usually - a committer after the approval from PMC should have the privileges to
do it.
| Also, unless I'm missing something, we'll have to push a new version whenever
we change things in Thrift, or at least whenever we cut a new version, right?
Yes - that would be true.
| what kind of process we'd be introducing and committing ourselves to?
Usually the versioning would be along major.minor.releaseVerisons and the
developments / PMC team of the project agree on a release checkpoint and after
a particular amount of dev cycle iterations / checkins , a new release is made.
As a thumb rule - all releases with same major / minor versions ( but
different releases ) are backward compatible w.r.t code .
Given that it has to do with protocol versioning - may be associating a minor
version with the protocol in place would be easy to begin with , so that users
are aware of the backward compatibility issues.
If you think there is heavy development going on - then the artifacts could be
published to - http://repository.apache.org/snapshots/org/apache/ , with less
stringent backward compatibility requirements and be integrated with some other
continuous build process ( Hudson, say) to publish the latest artifact after to
the snapshot repository after every successful build + test .
> Maven Deploy
> ------------
>
> Key: THRIFT-363
> URL: https://issues.apache.org/jira/browse/THRIFT-363
> Project: Thrift
> Issue Type: Improvement
> Components: Library (Java)
> Reporter: Gary Rudolph
> Fix For: 0.3
>
>
> Please, deploy libthrift into a public maven repository. Preferably, to Maven
> central, but if not at least the Apache.
> Maven Central:
> http://maven.apache.org/guides/mini/guide-central-repository-upload.html
> Apache Incubator Repository:
> http://people.apache.org/repo/m2-incubating-repository/
> The following is a sample pom.xml:
> <project xmlns="http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.facebook.thrift</groupId>
> <artifactId>libthrift</artifactId>
> <version>0.1-20090310</version>
> <packaging>jar</packaging>
> <name>Apache Thrift Library</name>
> <url>http://incubator.apache.org/thrift/</url>
> <description>Thrift is a software framework for scalable cross-language
> services development. It combines a software stack with a code generation
> engine to build services that work efficiently and seamlessly between C++,
> Java, Python, PHP, Ruby, Erlang, Perl, Haskell, C#, Cocoa, Smalltalk, and
> OCaml</description>
> <licenses>
> <license>
> <name>The Apache Software License, Version 2.0</name>
>
> <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
> <distribution>repo</distribution>
> </license>
> </licenses>
> <scm>
>
> <url>http://svn.apache.org/repos/asf/incubator/thrift/trunk</url>
> </scm>
> </project>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
