Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for Sense (0.14 sec)

  1. build-logic/documentation/src/main/groovy/gradlebuild/docs/GradleUserManualPlugin.java

            excludedPackages.add("org.gradle.platform.base.test");
            return excludedPackages;
        }
    
        // TODO: This doesn't really make sense to be part of the user manual generation, but it's so tied up into it
        // it's left here for a future project.
        private void generateDefaultImports(Project project, TaskContainer tasks, GradleDocumentationExtension extension) {
    Java
    - Registered: Wed Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Mar 01 05:46:51 GMT 2024
    - 17.7K bytes
    - Viewed (0)
  2. build-logic/documentation/src/main/groovy/gradlebuild/docs/GradleJavadocsPlugin.java

            // TODO: Staging directory should be a part of the Javadocs extension
            // TODO: Pull out more of this configuration into the extension if it makes sense
            // TODO: in a typical project, this may need to be the regular javadoc task vs javadocAll
    
            ObjectFactory objects = project.getObjects();
            // TODO: This breaks if version is changed later
    Java
    - Registered: Wed Apr 24 11:36:11 GMT 2024
    - Last Modified: Mon Oct 16 13:03:20 GMT 2023
    - 6.9K bytes
    - Viewed (0)
  3. Development.md

    2. That should be it. The suggestion will be displayed in the "Try" section.
    
    ### Remove generic suggestions
    
    For some scenarios, it doesn't make sense to display all the generic suggestions we currently have.
    E.g. `--stacktrace` for a compilation error is not helpful.
    
    To influence the generic suggestions Gradle displays, the NonGradleCause interface was introduced.
    Plain Text
    - Registered: Wed Apr 24 11:36:11 GMT 2024
    - Last Modified: Tue Feb 06 22:54:40 GMT 2024
    - 1.8K bytes
    - Viewed (0)
  4. CONTRIBUTING.md

    * Keep commits discrete. Avoid including multiple unrelated changes in a single commit.
    * Keep commits self-contained. Avoid spreading a single change across multiple commits. A single commit should make sense in isolation.
    
    ### Testing changes
    
    After making changes, you can test your code in 2 ways:
    
    1. Run tests.
    Plain Text
    - Registered: Wed Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Feb 09 15:30:53 GMT 2024
    - 15.6K bytes
    - Viewed (0)
Back to top