-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support custom scalaTag (e.g _2.11, _2.12, _2.13) instead of _? #80
Labels
Milestone
Comments
aha if i put appendixPattern to _2.11 then it changes the pattern for 2.12 also to _2.11. |
borissmidt
added a commit
to borissmidt/gradle-crossbuild-scala
that referenced
this issue
Jun 13, 2020
borissmidt
added a commit
to borissmidt/gradle-crossbuild-scala
that referenced
this issue
Jun 15, 2020
borissmidt
added a commit
to borissmidt/gradle-crossbuild-scala
that referenced
this issue
Jun 15, 2020
borissmidt
changed the title
Support to set archive.appendixPattern to ScalaLangVersion (_2.11)
Support to custom scalaTag instead of _?
Jun 16, 2020
borissmidt
added a commit
to borissmidt/gradle-crossbuild-scala
that referenced
this issue
Jun 16, 2020
borissmidt
added a commit
to borissmidt/gradle-crossbuild-scala
that referenced
this issue
Jun 16, 2020
borissmidt
added a commit
to borissmidt/gradle-crossbuild-scala
that referenced
this issue
Jun 17, 2020
Merged
prokod
changed the title
Support to custom scalaTag instead of _?
Support mixing cross built modules with plain modules in a multi module projects (Support to custom scalaTag instead of _?)
Jun 25, 2020
prokod
added a commit
that referenced
this issue
Jun 25, 2020
Merged
prokod
changed the title
Support mixing cross built modules with plain modules in a multi module projects (Support to custom scalaTag instead of _?)
Support custom scalaTag (e.g _2.11, _2.12, _2.13) instead of _?
Jul 27, 2020
This was referenced Aug 13, 2020
Merged
prokod
added a commit
that referenced
this issue
Aug 23, 2020
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey I might have a hacky solution for a complex problem this plugin doesn't compose well with the play plugin.
So we have a project like
But because i need to tag the dependencies as _? then the app sub project tells me hey i cannot resolve this dependency with _?. Because your plugin doesn't apply to the old play plugin.
So i simple solution would be to set the archive.appendixPattern to _2.11 and be done with it. But then the plugin complains that it cannot resolve the _2.11 for a 2.12 build.
So currently i resolved it by doing:
But if this 'feature' was supported the i could just change a project to a cross compiled lib by just applying the plugin and no need to switch dependencies to the dependency with _? notation.
I tried play-framework but that disabled the tests for some weird reason (and it is out of the scope of this ticket)
The text was updated successfully, but these errors were encountered: