[Android-tools-devel] getting the gradle-android plugin packaged

[Hans-Christoph Steiner]

It looks like the Android team put out a custom version of Lombok.AST:
https://github.com/rzwitserloot/lombok.ast/pull/8

It also seems like most of the dependencies are actually for build time.
Looking at the gradle jar cache of a machine used for Android development, I
can see only the lombok.ast jar:

$ find ~/.gradle/caches/modules-2/files-2.1 -name '*lombok*'
~/.gradle/caches/modules-2/files-2.1/com.android.tools.external.lombok
~/.gradle/caches/modules-2/files-2.1/com.android.tools.external.lombok/lombok-ast
~/.gradle/caches/modules-2/files-2.1/com.android.tools.external.lombok/lombok-ast/0.2.2/57e560b535ceaa14fb6f15422d74594acd6c5b64/lombok-ast-0.2.2.jar

Almost all of the dependencies listed in buildScripts/ivy.xml are not in my
gradle cache.  My guess is that those dependencies are used for the tests, so
not completely required.

.hc

Komal Sukhani:
> Yes Hans these packages were the blocker. I had started with packaging of
> lombok v0.8.4
> but it needs org.eclipse.core.runtime.jar which is not generated by eclipse
> package. So first
> eclipse package need to be updated.
> 
> Because of campus recruitment and university project I couldn't give time
> to these packages
> post GSOC period. As packages are not complete I have not uploaded my work
> on Alioth rather
> they are available on my github account.
> 
> 1. lombok.patcher <https://github.com/komalsukhani/deb-lombok.patcher>
> 2. lombok.ast <https://github.com/komalsukhani/deb-lombok.ast>
> 
> 
> Komal Sukhani
> 
> On Mon, Oct 19, 2015 at 2:21 PM, Hans-Christoph Steiner <hans at at.or.at>
> wrote:
> 
>>
>> I'm reviving the discussion of the remaining dependencies for getting the
>> gradle-android plugin included.  I think the issue below is the last
>> blocker:
>>
>>
>> -------- Forwarded Message --------
>> Subject: Re: Packaging of lombok
>> Date: Tue, 18 Aug 2015 17:32:43 +0200
>> From: Hans-Christoph Steiner <hans at at.or.at>
>> Organization: @||@
>> To: Komal Sukhani <komaldsukhani at gmail.com>, Markus Koschany <
>> apo at gambaru.de>,
>> 殷啟聰 <seamlikok at gmail.com>
>>
>>
>> What is with these java projects with their circular dependencies?  Its
>> quite
>> frustrating!  It sounds like either way you need to start with packaging
>> 0.8.4, so that's the way to start.  Then if v0.10.8 is required,
>> lombok.patcher can be added as needed.
>>
>> .hc
>>
>> Komal Sukhani:
>>> Hi all,
>>>
>>> lombok-ast is causing more problems than I thought (Its because uploader
>>> has used all
>>> libraries from his repository in this package). lombok-ast is dependent
>> on
>>> lombok v0.10.8
>>> which in-turn is dependent on lombok.patcher v0.6, but for building
>>> lombok.patcher, lombok
>>> is required. Now, we have a circular dependency.
>>> I have got two solutions for this:
>>>
>>> 1. Use lombok v0.8.4 instead of lombok v0.10.8, which doesn't require
>>> lombok.patcher.
>>>     But lombok-ast is using some class files which are added in higher
>>> version of lombok.
>>>
>>> 2. First package lombok v0.8.4  then start with packaging of
>> lombok.patcher
>>> v0.6. Finally
>>>     using lombok.patcher v0.6, create package for lombok v0.10.8.
>>>
>>> I think first option would be less time consuming, just I need to, if
>>> possible, remove dependency
>>> on those classes.
>>>
>>> What do you suggest?
>>>
>>> Komal Sukhani
>>>
>>
>>
>>
>> _______________________________________________
>> Android-tools-devel mailing list
>> Android-tools-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/android-tools-devel
>