[
https://issues.apache.org/jira/browse/BOOKKEEPER-1042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989236#comment-15989236
]
ASF GitHub Bot commented on BOOKKEEPER-1042:
--------------------------------------------
Github user eolivelli commented on the issue:
https://github.com/apache/bookkeeper/pull/134
@merlimat I think that those project need to have the same version as the
other modules.
Actually they are used to create artifacts for compat tests but for
instance the artifacts which support version 4.5.0 are different from the ones
for the 4.4.0 version, see the protobuf and guava upgrades for instance.
If they had to be 'fixed' I think they should be kept outside the project,
but I think this is not the case, in fact if it was the case we could have used
directly the released artifacts
> Deploy SNAPSHOTS of master to public Apache Repository
> ------------------------------------------------------
>
> Key: BOOKKEEPER-1042
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1042
> Project: Bookkeeper
> Issue Type: Task
> Components: build
> Reporter: Enrico Olivelli
> Assignee: Enrico Olivelli
> Priority: Minor
>
> It would be useful to deploy regularly current master to Maven Central so
> that it will be simpler for downstream projects to test new version without
> the need of custom local repositories
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
