[
https://issues.apache.org/jira/browse/THRIFT-4120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333325#comment-16333325
]
Alexander Volanis commented on THRIFT-4120:
-------------------------------------------
With the work to address THRIFT-4259 the Maven publication has been automated
to the point of just configuring GPG key parameters and Maven Nexus user
credentials and executing `make maven-publish`. This process will now correctly
generate a proper `.pom` file to go alongside the distribution JAR files in the
Maven staging area for release.
> pom files are not generated or provided in the build
> ----------------------------------------------------
>
> Key: THRIFT-4120
> URL: https://issues.apache.org/jira/browse/THRIFT-4120
> Project: Thrift
> Issue Type: Bug
> Components: Build Process, Java - Library
> Affects Versions: 0.10.0
> Reporter: Christopher Tubbs
> Priority: Major
>
> It appears pom files are being manually created and uploaded to the Nexus
> staging repository when thrift jars are uploaded there. They should be
> version-controlled and part of the source tarball, or created during the
> build process.
> This affects both libthrift.jar and libfb303.jar
> Including these files in the source tree, or created during the build would
> make it easier for downstream packagers to reproduce good Maven artifacts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
