-
Notifications
You must be signed in to change notification settings - Fork 211
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
Upstream cgruber/rules_kotlin changes to main repo. #205
Conversation
…precated (for this use-case anyway) `deps=`
* deps-to-exports: Make the no-srcs android_library use `exports=` instead of the now-deprecated (for this use-case anyway) `deps=` Add IntelliJ With Blaze and AndroidStudio With Blaze files to gitignore.
…e_no_les_dos * upstream/legacy-1.2-support: Add renovate.json (bazelbuild#176) Have the no-srcs android_library in android.bzl use exports= instead of deps= (bazelbuild#153) Fix mixed UTF-8 Java and Kotlin builds (bazelbuild#178) update bazel toolchains pin and add toolchain config target (bazelbuild#177) Update README.md Update bazel-toolchains (bazelbuild#173) Create CODEOWNERS (bazelbuild#171) Fix http_jar Cleanup for Bazel incompatible changes (bazelbuild#169) Run Buildifier to reformat files and apply automated fixes (bazelbuild#166) Update bazel-toolchains pin (bazelbuild#168) Update bazel_toolchains pin. (bazelbuild#157) Use Skylark version of http_archive. (bazelbuild#155) Update bazel-toolchains pin. (bazelbuild#154)
* upstream/master: Don't test on Ubuntu 14.04 (bazelbuild#183) Update deps for 0.26.0. (bazelbuild#191) update pin to bazel toolchains repo (bazelbuild#184) Update README.md Create ROADMAP.md
…shade dagger, avoiding leakage of the bytecode from the builder into compilation jobs peformed by the builder. Fixes bazelbuild#192
Shade dagger dep, to avoid leaking into a kapt dagger compilation.
…path. Currently, because there's no strict deps mechanism, that means basically use the full transitive closure. This fixes (or works around) but bazelbuild#132
… ctx.attr.runtime_deps is a list of deps, not a list of javainfos.
Make the compile time classpath use the full transitive compile classpath
Ensure that the runtime deps pass along their javainfo if present
Exposes a toolchain function (define_kt_toolchain) to allow the specification of non-default chains. Sets the default chain to 1.3.21. Removes the now-removed use-coroutines flag, which is permanently on. This also sets the compiler to permit use of experimental APIs. This is needed for people migrating from the older experimental coroutines to the new ones, during migration. This should be configurable, but for now it's just set. Also fixes up some tests and does some minor cleaning. Fixes bazelbuild#159 > Note: This no longer supports using pre-1.3 kotlinc distributions. You can make a toolchain that sets the language and api levels to 1.3, but you must use a 1.3+ kotlinc.
…iemntal versions. Regenerate the deps.
Enable Kotlin 1.3 in the rules_kotlin.
Update the readme to include information about the fork and recent re…
Minor edit to the readme.
…er option. Fixes #10.
Use modern APIs to unblock 0.27.0
Update for release legacy-modded-0.26.1-02
…explicitly opened usages. Also make sure older JVMs just ignore these options if they don't know about them.
Quiesce Java9+ module warnings about reflective access
…ons, and generate a compatibility matrix.
…new version testing here.
Add a test script to measure compatibility with various bazel versions.
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
To preserve the history, I plan on doing a proper merge, from the command line, rather than a squash-and-merge. |
Also, the goal here is to merge the branch mostly as-is, with subsequent clean-ups based on suggestions, if any. |
@pbsf and @puffnfresh, could you please do the consent message thing from the google cla bot above? |
@googlebot I consent. |
1 similar comment
@googlebot I consent. |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
if jar.basename in source_tally: | ||
artifacts += [struct(class_jar = jar, source_jar = source_tally[jar.basename], ijar = None)] | ||
else: | ||
artifacts += [struct(class_jar = jar, ijar = None)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this no longer exists, but shouldn't this be needed to align the source jar to the actual jar if you're using the jars
attr to import more than one pair of jars?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But you're not pulling in more than one pair of jars - jars=
can only take in one real jar and one source jar. If you have more than one non-source jar and optionally one source jar, it should blow up, so this alignment isn't necessary (and you get the behaviour around the one pair you do get in the function call I extracted out.)
Co-Authored-By: Jin <jin@users.noreply.github.com>
… already been moved to another repo.
Ok, I think I got all the comments addressed so far. @jin - was it just you doing the review, or were thomas and others going to pile in (they're auto-listed, and I didn't want to mess with the reviewers list) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this!
No description provided.