Skip to content

any plan to export individual APIs as separate artifacts? #70

Description

@patflynn

I've noticed the the datastore and storage packages aren't setup to generate their own artifacts. Are there any plans to do this? Java developers would typically expect each service API to be broken out and included as their own artifact.

Activity

  1. aozarov commented on May 18, 2015

    @aozarov
    Contributor

    There is some discussion about it also in issue #39. The current plan is to keep having the aggregate jar that includes all services and then later on (based on demand or when we will have more services and such separation would be meaningful) we will add an artifact per service (likely via pom modules).

  2. patflynn commented on May 19, 2015

    @patflynn
    Author

    My preference would be for it to happen as soon as you have more than one API. It looks like you'll need separate documentation pages for datastore vs gcs pretty soon, you probably wouldn't want to include the markdown in the java package path so you'll need to break them out by parent directories. At that point you basically have the directory structure you need for the multi-module setup.

  3. jgeewax commented on May 20, 2015

    @jgeewax

    This also follows the AWS Java trend, where everything is in a single jar.

  4. patflynn commented on May 20, 2015

    @patflynn
    Author

    AWS seems to offer both. Each API individually, and an uber-jar for the
    whole thing. That would be my preference.

    On Wed, May 20, 2015 at 11:32 AM, JJ Geewax notifications@github.com
    wrote:

    This also follows the AWS Java trend, where everything is in a single jar.

    —
    Reply to this email directly or view it on GitHub
    #70 (comment)
    .

  5. jgeewax commented on May 21, 2015

    @jgeewax

    Ah that's a good point. I'm fine with singular pieces as well as the jar with everything... is that a complicated thing for us to do ?

  6. aozarov commented on May 22, 2015

    @aozarov
    Contributor

    Not trivial as this will including structural changes, code changes and deployment related changes ( (travis, maven, site, ..). As suggested above, I did plan to. My plan was to deal with it when we have more services and it will become more meaningful though I thought to give it a try after finishing storage. I will give a try sooner.

  7. self-assigned this
    on May 22, 2015
  8. aozarov commented on May 26, 2015

    @aozarov
    Contributor

    Fixed by #74

  9. 5 remaining items

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

🚨 criticalP0 critical issue. Requires immediate fixtriage meI really want to be triaged.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions