Skip to content

don't trust scmInfo (Forked repositories) #178

Open
@MasseGuillaume

Description

@MasseGuillaume

Anyone could publishing with a scm that they dont own. (ex: publish ScalaKata with akka/akka).

Maven central enforce the ownership of groupId, but I assume they dont enforce the ownership of scm.

This could be solved by creating a mapping between groupId and scm for maven central and user to scm for Bintray

{
   "com.typesage.akka": ["akka/akka"],
   "com.scalakata": ["masseguillaume/scalakata"]
}

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions