[
https://issues.apache.org/jira/browse/SAMZA-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Riccomini updated SAMZA-34:
---------------------------------
Description:
Our gradle build script only supports building artifacts with one Scala version
at a time. You can run:
{noformat}
./gradlew -PscalaVersion=2.8.1 clean publishToMavenLocal
{noformat}
or
{noformat}
./gradlew -PscalaVersion=2.9.2 clean publishToMavenLocal
{noformat}
But you can't run a single build command that generates both 2.8.1, and 2.9.2
versions (for example). This is what SBT does. I think we'll need this in order
to publish artifacts to Maven, since I believe Maven require all artifacts to
be published in a single build.
We should test this. If we can publish to Maven without this change, this is a
pretty low priority item. If we can't publish to Maven unless we make this
change, it's relatively high priority.
was:
Our gradle build script only supports building artifacts with one Scala version
at a time. You can run:
{noformat}
./gradlew -PscalaVersion=2.8.1 clean publishToMavenLocal
{noformat}
or
{noformat}
./gradlew -PscalaVersion=2.9.2 clean publishToMavenLocal
{noformat}
But you can't run a single build command that generates both 2.8.1, and 2.9.2
versions (for example). This is what SBT does. I think we'll need this in order
to publish artifacts to Maven, since I believe Maven require all artifacts to
be published in a single build.
We should test this. If we can publish to Maven with this change, this is a
pretty low priority item. If we can't publish to Maven unless we make this
change, it's relatively high priority.
> Cross build all Scala versions in a single build
> ------------------------------------------------
>
> Key: SAMZA-34
> URL: https://issues.apache.org/jira/browse/SAMZA-34
> Project: Samza
> Issue Type: Bug
> Components: build
> Affects Versions: 0.6.0
> Reporter: Chris Riccomini
>
> Our gradle build script only supports building artifacts with one Scala
> version at a time. You can run:
> {noformat}
> ./gradlew -PscalaVersion=2.8.1 clean publishToMavenLocal
> {noformat}
> or
> {noformat}
> ./gradlew -PscalaVersion=2.9.2 clean publishToMavenLocal
> {noformat}
> But you can't run a single build command that generates both 2.8.1, and 2.9.2
> versions (for example). This is what SBT does. I think we'll need this in
> order to publish artifacts to Maven, since I believe Maven require all
> artifacts to be published in a single build.
> We should test this. If we can publish to Maven without this change, this is
> a pretty low priority item. If we can't publish to Maven unless we make this
> change, it's relatively high priority.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
