Github user aalexandrov commented on the pull request:
https://github.com/apache/flink/pull/477#issuecomment-83491250
One more thing. If we agree to add suffixes and ship multi-build artifacts,
and we are going to restructure the maven projects anyway, why not add suffixes
to both sets of artifacts?
I understand the appeal of adding suffix only for 2.11 for backward
compatibility reasons, but with the envisioned package restructure everybody
will have to touch their poms when migrating client code anyway.
Adding a suffix consistently for all versions makes dependency management
easier on the client side. Users can then configure their dependency entries
like this
```xml
<properties>
<scala.tools.version>2.11</scala.tools.version> <!-- or 2.10 -->
</properties>
<dependencies>
<!-- Flink -->
<dependency>
<groupId>org.apache.flink</groupId>
<projectId>flink-core_${scala.tools.version}</projectId>
<version>0.9<version>
</dependency>
<!-- Other Scala-version specific dependencies -->
<dependency>
<groupId>org.scalanlp</groupId>
<projectId>breeze_${scala.tools.version}</projectId>
<version>0.10</version>
</dependency>
</dependencies>
```
and switch from 2.10 to 2.11 by just changing the property value.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
