Skip to content
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

Deprecate APKLIB - Replaced by AAR #543

Merged
merged 1 commit into from Dec 17, 2014
Merged

Deprecate APKLIB - Replaced by AAR #543

merged 1 commit into from Dec 17, 2014

Conversation

Shusshu
Copy link
Contributor

@Shusshu Shusshu commented Dec 17, 2014

I think we should deprecated apklib in the next release because when someone has issues with apklib we all seem to tell him to use Aar instead.

If you all agree then we can merge this.

@mosabua
Copy link
Member

mosabua commented Dec 17, 2014

I agree... by the time we release 5.0 I think apklib and ndk stuff should be gone

mosabua added a commit that referenced this pull request Dec 17, 2014
Deprecate APKLIB - Replaced by AAR
@mosabua mosabua merged commit 600d48d into master Dec 17, 2014
@mosabua mosabua deleted the deprecate-apklib branch December 17, 2014 18:06
@william-ferguson-au
Copy link
Contributor

And APK_SOURCE (if it is still in there).

[image: photo]
William Ferguson
Founder and CEO, XandarMob
m:+61 425 716 870 | e:william.ferguson@xandar.com.au |
w:https://wylas-timing.com
http://lexathon.com <http://wylas-timing.com http://lexathon.com>

On Thu, Dec 18, 2014 at 4:06 AM, Manfred Moser notifications@github.com
wrote:

Merged #543
#543.


Reply to this email directly or view it on GitHub
#543 (comment)
.

@mosabua
Copy link
Member

mosabua commented Dec 17, 2014

I think we removed that already.. but yes...

@rtack
Copy link

rtack commented Dec 17, 2014

what about poor ADT eclipse users without proper Aar support? See https://github.com/rgladwell/m2e-android/issues/177 and https://github.com/kingargyle/andmore/issues/11
Is it such a burden to keep apklib support until aars work using either m2eandroid or andmore as well?

@Shusshu
Copy link
Contributor Author

Shusshu commented Dec 17, 2014

Apklib is still there. Just deprecated and will be removed in the future
when we are confident everyone has moved on.
On 17 Dec 2014 19:59, "Raphael Ackermann" notifications@github.com wrote:

what about poor ADT eclipse users without proper Aar support? See
rgladwell/m2e-android#177
https://github.com/rgladwell/m2e-android/issues/177 and
kingargyle/andmore#11 https://github.com/kingargyle/andmore/issues/11
Is it such a burden to keep apklib support until aars work using either
m2eandroid or andmore as well?


Reply to this email directly or view it on GitHub
#543 (comment)
.

@mosabua
Copy link
Member

mosabua commented Dec 18, 2014

We will definitely keep apklib until aar it well established including working integration with ADT/Andmore.. all good @rtack

@skauss
Copy link

skauss commented Dec 22, 2014

We still use apklib because aar didn't work with our project.
In case you use aar in an aar library the classes are not available inside eclipse, This make aar not usable in eclipse.
In case you deprecated apklib support we have to move to Android Studio and gradle... What I not like to do because I love Eclipse and use this IDE also in other project's than Android projects.

@mosabua
Copy link
Member

mosabua commented Dec 22, 2014

Again to clarify.. we will NOT remove apklib support until aar is an equivalent replacement for Eclipse and IntelliJ users. In fact we will probably work with the Andmore project, Me2 and M2eAndroid ... and we would love for you to help as well.

@kingargyle
Copy link

Yes the Andmore will make AAR support one of its priorities. We are in the middle of package renaming right now, and as soon as we can get a p2 site published for developers to start migrating plugins to use the new package names we'll let everyone know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants