> As far as group / artifact name compatibility, at least in the case of > Kafka we need different artifact names anyway, and people are going to > have to make changes to their build files for spark 2.0 anyway. As > far as keeping the actual classes in org.apache.spark to not break > code despite the group name being different, I don't know whether that > would be enforced by maven central, just looked at as poor taste, or > ASF suing for trademark violation :)
Sonatype, has strict instructions to only permit org.apache.* to originate from repository.apache.org. Exceptions to that must be approved by VP, Infrastructure. ------ Sent via Pony Mail for dev@spark.apache.org. View this email online at: https://pony-poc.apache.org/list.html?dev@spark.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
