Please enable JavaScript.

Coggle requires JavaScript to display documents.

System Build Automaton (Software Build Automation Tools (Maven (Def (for…

- - - - System building: the process of assembling program components, data and libs, then compiling these to create an executable system
      - Version management: ... ensure changes made to components by different devers do not interfere with ea other
        
        Codeline: a sequence of versions of source code with later versions in the sequence derived from earlier versions
        
        Baseline: specifies the component versions that are included in the system + a specification of the libs used, configuration files, etc
        
        individual system versions for different customers
        
        Sementic Versioning
        MAJOR.MINOR.PATCH
        
        MAJOR version when make incompatible API changes
        
        MINOR version when add functionality in a backwards-compatible manner
        
        PATCH version when make backwards-compatible bug fixes
      - Change management: keep track of requests for changes to the software from customers and dev-ers, working out the costs and impact of changes, and deciding the changes should be implemented
      - Release management: preparing software for external release and keep track of the system versions that have been released for customer use
- - - - Java-based software build tool for automating build processes
      - Does not impose coding conventions
      - Does not impose any heavyweight dependency management framework
      - XML to describe the code build process and its dependencies
    - - Too flexible
      - Complex (XML-based build files), need to specify a lot of things to make simple builds
      - No standard structure/layout: Devers can create their own structure/layout of the project
  - - - for java projects
      - XML-based description
      - Central repo
      - Supported by Eclipse, IntelliJ, JBuilder, NetBeans
      - Plug-in based architecture
    - - command nvm package will:
        
        compile all the Java files
        
        run any tests
        
        package the deliverable code and resources into target (e.g., target/my-app-1.0.jar)
    - - XML-based increase complexity
      - Rigid; devers are required to understand follow the conventions
  - - - Build automaton tool that builds upon the concepts of Ant and Maven
      - Build conventions, and redefind conventions
      - Project described using Groovy-based Domain Specific Language (DSL)
        
        is a dynamic language of the JVM
        
        can be added as a plug-in
        
        Allows devers to write general programming tasks in the build files
        
        Relief devers from the lacking control flow in Ant or being forced into plug-in development in Maven to declrea nonstandard tasks
        
        DSL
        
        Not general-purpose or programming language
        
        contains the language needed to describe how to build Java code and create a WAR file from the output
        
        is extensible through plug-ins
        
        Adding new task definitions
        
        Change the behaviour of existing taks
        
        Add new objects
        
        Create kewords to describe tasks that depart from the standard Gradle categories
      - Taks orders determined using a directed acycilc graph (DAC)
      - Incremental builds; up to date parts of the build tree do not need to be re-executed
      - Dependency handling (transitive dependency management)
    - - Tasks
        
        are objects
      - Commands
        
        gradle -m build: list all taks in a gradle project associated in a gradle build
        
        gradle -v, gradle --version: check version of currently installed gradle