Skip to content

[MavenCapsule] Dependencies with wildcard versions fail #37

@SamCarlberg

Description

@SamCarlberg

If I have a dependency in my build.gradle file:

dependencies {
  compile("com.example:library:+")
}

I would expect it to be resolved to the most recent version at the time of the build:

// MANIFEST.MF
Dependencies: com.example:library:1.2.3

It is currently saved as com.example:library:+, which Capsule cannot understand.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions