-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Replace transitive_*_jars in java_common.create_provider with deps #3769
Comments
cc: @ittaiz |
Great, thanks.
Just to make sure- this will respect neverlink semantics, right?
…On Wed, 20 Sep 2017 at 11:02 Irina Iancu ***@***.***> wrote:
cc: @ittaiz <https://github.com/ittaiz>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3769 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABUIF3vfee26mnk4kL4in77VSl1nZX_Sks5skMamgaJpZM4PdfEx>
.
|
Friendly ping |
@iirina Stumbled on to a problem and I'm not sure if it should be a new issue or an expansion of this one.
The reason I think this is related to this issue is because I think the real problem is the level of abstraction the current provider allows. Ideally I think it should support the API you mentioned above but also include WDYT? You can see my attempt of using this feature in the following rules_scala branch |
@dbabkin is currently implementing this. |
Exciting! Thanks!
…On Tue, 12 Dec 2017 at 17:09 Irina Iancu ***@***.***> wrote:
@dbabkin <https://github.com/dbabkin> is currently implementing this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3769 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABUIF4BJEVLUufe4QaClsX2XVGU8UmOTks5s_pcWgaJpZM4PdfEx>
.
|
Hi, |
Hi, This task is in the progress right now. New API supports creating JavaInfo with JavaCompilationArgsProvider only. |
Hi,
Thanks for the update!
This isn't exposed to skylark right? AFAIR JavaCompilationArgsProvider
isn't exposed to skylark
…On Tue, 9 Jan 2018 at 18:42 dbabkin ***@***.***> wrote:
Hi,
Bazel contributor here. :) Terribly sorry for delay in reply.
This task is in the progress right now.
First, very limited part of new API is about to be finished. Commit will
be pushed today or tomorrow.
I'm not sure about release 0.10.0. Please follow the status of release
0.10 cut on this ticket:
#3958 <#3958>
New API supports creating JavaInfo with JavaCompilationArgsProvider only.
The next sub-task in scope of this story is to implement the list of all
others providers.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3769 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABUIFx8cGLgaIQlFbGSa8_JheotxC3o-ks5tI5bcgaJpZM4PdfEx>
.
|
No, it's not. It's just an implementation detail, meaning more work will be needed to make the new API 100% reliable. I cannot tell right now if this will make the release, since it seems difficult to even cut an RC right now. |
Hi Ittai, We do not expose JavaCompilationArgsProvider itself. To create JavaInfo, you need to use constructor [2]. Please refer our tests for example [3]
Others methods from JavaInfo returns empty result now. To fix that I need to implement other providers. This is my priority at the moment. |
Hi, |
Hi,
|
@dbabkin Thanks a lot! It sounds like there are a lot more moving pieces now. Will the documentation be updated when this ships? |
Hi Oscar, Yes I will add documentation to bazel.build web site after I finish implementation. |
changes pushed. |
Thanks! |
The current
transitive_*_jars
arguments injava_common.create_provider
are hard to understand and present some shortcomings. For example, you cannot create a provider with transitive source jars or other transitive information thatJavaInfo
encapsulates (and might not even be exposed).The current (old) API:
should be replaced by this:
The text was updated successfully, but these errors were encountered: