Skip to content

Android native libs are not respected correctly if the plugin is added as depedency to another plugin #807

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.

Sign up for GitHub

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

Jump to bottom
Closed
Fatme opened this issue Aug 21, 2015 · 1 comment
Closed

Android native libs are not respected correctly if the plugin is added as depedency to another plugin #807

Fatme opened this issue Aug 21, 2015 · 1 comment
Labels
bug
Milestone
1.2.4

Comments

@Fatme
Copy link
Contributor

Fatme commented Aug 21, 2015

No description provided.

@Fatme Fatme changed the title Android native libs are not respected Android native libs are not respected correctly Aug 21, 2015
@Fatme
Copy link
Contributor Author

Fatme commented Aug 21, 2015

  1. Create new {N} plugin
  2. Add a dependency to another {N} plugin that contains android native libs
  3. Create a new project
  4. Execute tns plugin add
  5. Try to build the project

@Fatme Fatme added this to the 1.2.4 milestone Aug 21, 2015
@Fatme Fatme added the bug label Aug 21, 2015
@Fatme Fatme mentioned this issue Aug 21, 2015
Merged
@Fatme Fatme changed the title Android native libs are not respected correctly Android native libs are not respected correctly if the plugin is added as depedency to another plugin Aug 21, 2015
@vchimev vchimev closed this as completed Aug 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
1.2.4
Development

No branches or pull requests
2 participants
@Fatme @vchimev