Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for focus (0.16 sec)

  2. github.com/gradle/gradle

    README.md 

    [![CII Best Practices](https://bestpractices.coreinfrastructure.org/projects/4898/badge)](https://bestpractices.coreinfrastructure.org/projects/4898)
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Sun Mar 24 20:49:08 GMT 2024
    - 3.9K bytes
    - Viewed (0)
  3. github.com/gradle/gradle

    build-logic-commons/code-quality-rules/src/main/resources/classycle/classycle_report_resources.zip 

    list.document.write(".link { cursor:pointer;text-decoration:underline; } "); list.document.writeln("th { background-color:#aaaaaa; } </style></head><body>"); list.document.writeln(text); list.document.writeln("</body></html>"); list.document.close(); list.focus(); } //--> Analysis of Date: Summary no class cycles class cycle class cycles class layers classes (using external classes) grouped in packages no package cycles package cycle package cycles no package packages Type Number of classes Averaged (maximum)...
    ZIP Archive
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Wed Dec 09 08:14:05 GMT 2020
    - 23.4K bytes
    - Viewed (0)
  4. github.com/gradle/gradle

    architecture/standards/0004-use-a-platform-architecture.md 

    2024-02-07

## Context

The Gradle code base is essentially a large monolith, without strong internal boundaries.
This has a number of negative effects on productivity, including:

- Unclear ownership of code.
- Difficult to focus on one particular area.
- Unintended coupling between areas of the code, including tests.

## Decision

Organize the Gradle code base into a set of coarse-grained "architecture modules".
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Sun Feb 25 22:19:29 GMT 2024
    - 4.5K bytes
    - Viewed (0)
  5. github.com/gradle/gradle

    architecture-standards/0004-use-a-platform-architecture.md 

    2024-02-07

## Context

The Gradle code base is essentially a large monolith, without strong internal boundaries.
This has a number of negative effects on productivity, including:

- Unclear ownership of code.
- Difficult to focus on one particular area.
- Unintended coupling between areas of the code, including tests.

## Decision

Organize the Gradle code base into a set of coarse-grained "architecture modules".
    Plain Text
    - Registered: Wed Feb 14 11:36:15 GMT 2024
    - Last Modified: Wed Feb 07 00:56:13 GMT 2024
    - 4.5K bytes
    - Viewed (0)
Back to top