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

Symantic: Create the notion of a module instead of "project source set" #34

Open
calvertdw opened this issue Dec 7, 2017 · 0 comments

Comments

@calvertdw
Copy link
Member

calvertdw commented Dec 7, 2017

Overview

The extraSourceSets property, the ihmc.sourceSetProject method, and the README all refer to "source set projects", which are a key feature of this plugin and one of it's main purposes: to seperate the classpaths of Gradle source sets in IDEs.

Problem and Proposed Solution

It is hard to talk about these things without a good name that people can hang on to. Since it is essentially a central feature to the plugin, they should be given a name. "Module" is a good choice because there is no notion of a "module" in Gradle, and IntelliJ uses the term to mean essentially, "a collection of source with it's own seperate classpath".

Technical Actions

Deprecate extraSourceSets, rename to modules

modules contains "main" by default, and will be automatically added if not specified.
For example modules = ["main", "test"] and modules = ["test"] would both setup both a "main" and a "test" module.

ihmc-rosie pushed a commit that referenced this issue Dec 8, 2017
… externalDependencyVersion to filteredVersion.
@calvertdw calvertdw changed the title Symantic: Create the notion of a module instead of saying "project source set" Symantic: Create the notion of a module instead of "project source set" Dec 12, 2017
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

No branches or pull requests

1 participant