[
https://issues.apache.org/jira/browse/BIGTOP-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159300#comment-14159300
]
Roman Shaposhnik commented on BIGTOP-1473:
------------------------------------------
Everything that comes out of Bigtop has to follow an overall versioning. In
general, publishing a Maven artifact is a simple matter of running mvn deploy.
The easiest way to make it happen is to work on restructuring on Bigtop's top
level Maven build so that it actually recursively deploys everything that needs
to be deployed.
I filed BIGTOP-1479 to track this. Would love for folks to help fixing it.
> Enable publishing of BigPetStore jars
> -------------------------------------
>
> Key: BIGTOP-1473
> URL: https://issues.apache.org/jira/browse/BIGTOP-1473
> Project: Bigtop
> Issue Type: New Feature
> Components: blueprints
> Affects Versions: backlog
> Reporter: RJ Nowling
> Fix For: 0.9.0
>
>
> BigPetStore and its new associated data generator may be of use to other
> projects. For example, Apache Drill includes log-synth, a similar
> domain-driven data generator for producing log data. Doing so would also
> have the benefit of increasing public awareness of BigTop.
> We'll also need versioned releases so that changes can be managed. I'm
> assuming the best way to do this is to publish BigPetStore JARs from BigTop
> into Maven central. Feedback from other BigTop users and committers would be
> useful for helping us figure out how best to do this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
