Skip to content

Remove dependency on Nebula plugin for 2.x #4032

Closed

Description

@akarnokd

(Previously came up in #3170)

In the past, the Nebula plugin was source of trouble and RxAndroid got rid of it some time ago. This suggests and issue tracks the removal of Nebula and the replacement of its relevant features:

  • Remove from build.gradle
  • Make sure creating a release through Github still triggers an upload to maven from Travis CI
  • Make sure patch version numbers are automatically incremented and inferred

Activity

  1. added this to the 2.0 RC 1 milestone on Jun 19, 2016
  2. ZacSweers commented on Jun 23, 2016

    @ZacSweers
    Contributor

    What were the benefits of it? From what I remember the most common usage was its provided plugin but that exists natively through gradle now as compileOnly.

    The maven releases via travis should totally be doable.

    Automating patch versions should be easy too, could easily make that a tiny gradle task

  3. akarnokd commented on Jun 23, 2016

    @akarnokd
    MemberAuthor

    Great! Anybody who wants to tackle this, a PR are welcome. Please notify us if someone starts working on this so won't get PR conflicts on build.gradle updates (like PMD).

  4. modified the milestones: 2.0 RC 3, 2.0 RC 1 on Aug 25, 2016
  5. modified the milestones: 2.0, 2.0 RC 3 on Sep 23, 2016
  6. akarnokd commented on Oct 25, 2016

    @akarnokd
    MemberAuthor

    Closing. I don't have the skill and nobody else picked this up. The current nebula setup works anyway.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions