Fixed
Status Update
No update yet.
Comments
tn...@google.com
Regarding source attachments; I'm not sure that's supported in Gradle yet.
Regarding compiler messages: They *should* be shown. There are some error message recognizers which recognize certain error messages and attempt to provide more useful context.
I've seen several bugs in this area. There's some code which attempts to recognize error messages coming out of gradle, and attributing them to either java or to aapt etc. I believe there are some bugs in that area causing not all the details to be shown.
We definitely need to hunt that down and make sure that if we don't display an improved message, we at least display the full details available from gradle.
Regarding compiler messages: They *should* be shown. There are some error message recognizers which recognize certain error messages and attempt to provide more useful context.
I've seen several bugs in this area. There's some code which attempts to recognize error messages coming out of gradle, and attributing them to either java or to aapt etc. I believe there are some bugs in that area causing not all the details to be shown.
We definitely need to hunt that down and make sure that if we don't display an improved message, we at least display the full details available from gradle.
al...@google.com
Scott is the working on showing compiler errors in Studio
sb...@google.com
One issue per bug report, please. #2 is a duplicate of 57181.
da...@gmail.com
Is there an official Gradle bug we can track about this?
searching for "source attachment" in the gradle bug tracker I find many similar tickets, all aimed at the Eclipse Plugin.
http://issues.gradle.org/browse/GRADLE-1621?jql=text%20~%20%22source%20attachment%22
searching for "source attachment" in the gradle bug tracker I find many similar tickets, all aimed at the Eclipse Plugin.
sb...@google.com
vs...@google.com
su...@gmail.com
Any news about the automatic source attachment? I am also interested in the JavaDoc incase the source is not available but the JavaDoc is.
sk...@gmail.com
I'm looking forward to seeing a fix for this. Having to search for and attach docs should be a needless extra step.
xa...@android.com
to...@gmail.com
Exist also plugin which can do this
https://github.com/xujiaao/AARLinkSources
It looks that it only modify idea libraries configuration file and inject right path to the it. Gradle itself is able to download sources and javadoc.
It looks that it only modify idea libraries configuration file and inject right path to the it. Gradle itself is able to download sources and javadoc.
ja...@gmail.com
Tried using the plugin mentioned but does not seem to work for javadoc
[Deleted User] <[Deleted User]>
Still unable to get sources / javadoc attached for Maven dependencies in Android Studio 1.1.0 + Gradle 1.1.0. Any plans to get this fixed at all?
da...@gmail.com
Any news on this?
the workaround with AARLinkSources is good if the library is open source (source available) and if it is an AAR.
does not work with javadoc only and does not work with non-AAR artifacts (jar for instance).
It also require duplicating all dependency lines...
this should really be added to Android Studio and I think that if the AARLinkSources can do it it can be done by the android gradle plugin directly too (or by an android-studio plugin).
Why is this taking so long? it's a pain to develop, even with my own libraries I see no documentation unless I manually set the source location (and re-set it every time gradle resync).
Can you give your developer some update or an ETA?
thank you
the workaround with AARLinkSources is good if the library is open source (source available) and if it is an AAR.
does not work with javadoc only and does not work with non-AAR artifacts (jar for instance).
It also require duplicating all dependency lines...
this should really be added to Android Studio and I think that if the AARLinkSources can do it it can be done by the android gradle plugin directly too (or by an android-studio plugin).
Why is this taking so long? it's a pain to develop, even with my own libraries I see no documentation unless I manually set the source location (and re-set it every time gradle resync).
Can you give your developer some update or an ETA?
thank you
ne...@gmail.com
I still run into this issue on AS 1.2RC
nm...@gmail.com
im using android studio 1.2.1.1 version and this issue still occur, really annoying, google please fix this asap, target 1.4 is too far :(
[Deleted User] <[Deleted User]>
pi...@gmail.com
1.2.2, still present.
al...@google.com
al...@google.com
tn...@google.com
1.4 Beta 3 is available in the canary channel now, with this fix.
da...@gmail.com
Thank you! I look forward for it to come in beta!
om...@gmail.com
This has been fixed for JAR but not AAR dependencies.
gu...@gmail.com
Is there any issue I can track for attaching src and javadoc for aar dependencies?
ki...@gmail.com
[Comment deleted]
ki...@gmail.com
[Comment deleted]
ki...@gmail.com
If the javadoc issue (77425) was merged to this one, can you change this issue's subject/description to contain the word javadoc?
Also, is there an open issue for attaching javadoc manually? Couldn't find such an issue and couldn't find a way to do it in Android Studio v2.1.
See a related SO post:http://stackoverflow.com/questions/38141103/firebase-android-jars-documentation-javadoc-in-android-studio
Also, is there an open issue for attaching javadoc manually? Couldn't find such an issue and couldn't find a way to do it in Android Studio v2.1.
See a related SO post:
vo...@gmail.com
Tried latest version:
com.android.tools.build:gradle:2.2.2
And javadoc is still not attached automatically.
com.android.tools.build:gradle:2.2.2
And javadoc is still not attached automatically.
kj...@gmail.com
I don't think Google devs receive updates on closed issues. At least I've never seen them respond. Probably better open a new issue and link back to this one.
fa...@gmail.com
I have just created this issue:
https://code.google.com/p/android/issues/detail?id=227239
It specifically refers to Gradle not downloading a javadoc jar dependency for AAR libraries.
Please feel free to add comments on there.
It specifically refers to Gradle not downloading a javadoc jar dependency for AAR libraries.
Please feel free to add comments on there.
Description
OS version: Windows 7 64 bit
Java JRE/JDK version: jdk1.7.0_25
I've managed to get a former Eclipse ADT project up and running in Android Studio.
I have 2 major issues left before reaching the next phase, and I'm not sure if I am missing something or if these are features that don't work.
1. No automatic source attachment for my dependencies (grails dependencies through maven).
I can manually start adding source attachments by navigating to my maven repository but I was wondering if this was already automated ?
2. No compiler errors shown in the IDE (gradlew shows them, but inside the IDE I only get a generic message:
Gradle: Execution failed for task ':MyApplication:processDebugManifest'.
> Manifest merging failed. See console for more info.
while on the commandline (using gradlew) I get more info :
BUILDER_PROCESS [stderr]: [AndroidManifest.xml:3, AndroidManifest.xml:3] Main manifest has <uses-sdk android:minSdkVersion='7'> but library uses minSdkVersion='8'
Are these features currently not available in Android Studio ?