cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-11244) Update Android Project Structure to be more compatible with Android Studio
Date Tue, 28 Nov 2017 23:33:00 GMT

    [ https://issues.apache.org/jira/browse/CB-11244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16269710#comment-16269710
] 

ASF GitHub Bot commented on CB-11244:
-------------------------------------

janpio commented on issue #389: CB-11244: Studio Project Compatibility: Now with merge commit
URL: https://github.com/apache/cordova-android/pull/389#issuecomment-347699944
 
 
   - When installed package.json is still ` "version": "6.5.0-dev",` - bug or feature? (Couldn't
find the file in the PR)
   - Is it necessary to change the output paths for APKs? I imagine lots of automation is
hardcoded on the old paths (Example from my own code: https://github.com/ionic-zone/fastlane-plugin-ionic/blob/master/lib/fastlane/plugin/ionic/actions/ionic_action.rb#L118)
   - `.gitignore` for `/build` does not work for the new build output paths (and should probably
get more/better paths for other stuff as well, but I am not sure on the "standard" here)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Update Android Project Structure to be more compatible with Android Studio
> --------------------------------------------------------------------------
>
>                 Key: CB-11244
>                 URL: https://issues.apache.org/jira/browse/CB-11244
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: cordova-android
>            Reporter: Joe Bowser
>            Assignee: Joe Bowser
>            Priority: Blocker
>              Labels: CordovaAndroidSix, android-next
>
> Currently our existing Android projects have the old Android Project structure created
by default, even for new projects, which makes no sense since we no longer support Eclipse
as the default project editor and have moved to Android Studio for Android development.
> The main reason for doing this is to clean up dependencies and to allow for projects
and dependencies to work more like how modern Android projects work and to remove as much
custom Gradle code as possible.  This would also allow us in the future to move towards having
Android Plugin code work as Android Libraries with Resources instead of just copying things
across, which gives us the ability to add JUnit tests and bundled resources.  This would dramatically
increase the quality of plugins such as InAppBrowser, and third party plugins such as the
Barcode Scanner.
> This would have to be done on the next major version, and the upgrade would be tricky
to do.  However, the benefits at this point would greatly outweigh the costs of maintaining
the old project structure.  The old cordova-common code in Cordova-Android 5.0.x would allow
for plugins in the short term to work with both projects until we get the new project structure
ready.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org


Mime
View raw message