Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 12 for where (0.13 sec)

  1. .github/pull_request_template.md

     - [ ] Format the pull request title like `[MNG-XXX] SUMMARY`,
           where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue.
     - [ ] Also format the first line of the commit message like `[MNG-XXX] SUMMARY`.
           Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message.
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Tue Dec 20 13:14:27 GMT 2022
    - 1.9K bytes
    - Viewed (0)
  2. maven-core/src/site/apt/inheritance.apt

    Inheritance in Maven
    
     In order the understand how inheritance works in Maven there are a few notions that you must be familiar with:
    
     * The maven super model
    
     * how parent poms are processed
    
     * the order in which elements in the POM are overridden
    
     * minimum element-set for a valid project pom
    
    
    Maven super model
    
     Inheritance is recursive in Maven but there is a special model which is the implicit super parent in the lineage
    Plain Text
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Mon Jul 18 17:22:19 GMT 2022
    - 3.5K bytes
    - Viewed (0)
  3. CONTRIBUTING.md

    Making and Submitting Changes
    --------------
    
    We accept Pull Requests via GitHub. The [developer mailing list][dev-ml-list] is the
    main channel of communication for contributors.  
    There are some guidelines which will make applying PRs easier for us:
    + Create a topic branch from where you want to base your work (this is usually the master branch).
      Push your changes to a topic branch in your fork of the repository.
    + Make commits of logical units.
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Sun Oct 10 09:48:27 GMT 2021
    - 4.7K bytes
    - Viewed (0)
  4. maven-core/src/site/apt/offline-mode.apt

      the network is not). Therefore, let's concentrate on the state where no
      network <beyond localhost> exists, and leave the more extreme state to users
      to diagnose and correct as necessary.
    
    * Why is Offline Mode Important?
    
      Offline mode is essential for breaking the requirement that m2 operate in a
      network-connected environment. It means legitimizing a development environment
      in which there is no network connection, and providing a robust m2 service
    Plain Text
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Mon Mar 18 00:24:53 GMT 2024
    - 10.6K bytes
    - Viewed (0)
  5. README.md

    Documentation
    -------------
    
    More information can be found on [Apache Maven Homepage][maven-home].
    Questions related to the usage of Maven should be posted on
    the [Maven User List][users-list].
    
    
    Where can I get the latest release?
    -----------------------------------
    You can download the release source from our [download page][maven-download].
    
    Contributing
    ------------
    
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Sun Mar 03 21:28:30 GMT 2024
    - 4.3K bytes
    - Viewed (0)
  6. maven-core/src/site/apt/getting-to-container-configured-mojos.apt

      That should be all there is to it.
    
    * MojoDescriptor
    
      Remove set/getMojoConfiguration(..), as it will become obsolete.
    
    * MavenSession
    
      We may need to enable the context injection here, since this will be
      instantiated per-project. If we always inject the same context parameters,
      and are careful to inject nulls where things are missing, we should be
    Plain Text
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Mon Jan 30 15:20:35 GMT 2023
    - 4.1K bytes
    - Viewed (0)
  7. apache-maven/src/assembly/maven/lib/jansi-native/README.txt

    This directory contains Jansi native libraries extracted from Jansi JAR.
    
    You can add your own build for platforms not natively supported by Jansi.
    See here [1] on how to compile for your platform and here [2] how libraries
    follow Jansi's directory and filename conventions.
    
    [1] https://github.com/fusesource/jansi/tree/master/src/main/native
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Mon Jul 18 17:22:19 GMT 2022
    - 486 bytes
    - Viewed (0)
  8. maven-core/lifecycle-executor.txt

    We have a lifecycle mapping for the packaging of *jar* below. You see that for this packaging we have a *default* lifecycle and a list of phases where each phase is a comma separated list of goals to run and they are in the form groupId:artifactId:version.
    
    <configuration>
      <lifecycles>
        <lifecycle>
          <id>default</id>
          <phases>
            <process-resources>org.apache.maven.plugins:maven-resources-plugin:resources</process-resources>
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Mon Jul 18 17:22:19 GMT 2022
    - 9.7K bytes
    - Viewed (0)
  9. maven-core/plugin-manager.txt

    // 3 the component model -> interfaces for the plugin
    
    // The plugin manager should load up a directory structure of plugins.
    // - a plugin per directory where the plugin is present with its deps
    // - a plugin that has its dependencies packaged up with it
    // - implement filters and create a test where a plugin fails if the right classes are not filtered
    // - plugins with a dependency the same as the core but different versions, make it fail then fix it
    
    Plain Text
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Mon Jul 18 22:45:13 GMT 2022
    - 12.9K bytes
    - Viewed (0)
  10. maven-core/src/site/apt/configuration-management.apt

         |
         +--- maven.properties
    +-----+
    
    * Group configuration
    
     As far as properties go for an entire build the maven.properties could be placed at
     the top of the group but I'm not really sure how this might work. There could probably
     also be a directory for plugins.xml and maven.properties.
    
    * Project configuration
    
     At the project level all configuration is achieved by tweaking the POM. One of the differences between
    Plain Text
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Mon Mar 18 00:24:53 GMT 2024
    - 5.8K bytes
    - Viewed (0)
Back to top