![]() We hope this will make your life a tad easier. Composite builds work nicely with the option that delegates the IDE build and run actions to Gradle: ![]() Note, this feature requires Gradle 3.1 or higher. Now you can make any changes to the attached projects and immediately get feedback-IntelliJ IDEA will use module dependencies instead of binary ones. Then, refresh your Gradle project, and you’re all set. With composite builds, everything is much, much simpler. All you have to is to attach the Gradle projects of these libraries via the Add button in the Gradle tool window ( my-utils in our case), and then select Compose Build Configuration from the context menu for the original project. Normally you’d need to open the sources of these libraries as separate projects, make the changes, build, upload new artifacts to the repository, then update the dependencies in your project and only after that, verify if the changes worked ok. Now, you’d like to change something in these libraries (a very common case). Imagine your project has compilation time dependencies to org.sample:number-utils and org.sample:string-utils: This and all future builds will have the Gradle composite builds support, so you can substitute any of your project dependencies with another project. ![]() Fresh IntelliJ IDEA 2016.3 EAP build, packed with various improvements is here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |