Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 7 of 7 for allowed (0.2 sec)

  1. api/maven-api-plugin/src/main/mdo/plugin.mdo

              <description>
                The configurator type to use when injecting parameter values into this Mojo. The value is normally deduced
                from the Mojo's implementation language, but can be specified to allow a custom ComponentConfigurator
                implementation to be used.
              </description>
            </field>
            <field>
              <name>composer</name>
              <version>1.0.0/1.1.0</version>
    XML
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Sun Apr 14 17:14:22 GMT 2024
    - 23.6K bytes
    - Viewed (0)
  2. maven-core/pom.xml

                  <include>org.apache.maven.settings</include>
                  <include>org.apache.maven.toolchain</include>
                  <include>org.apache.maven.usability</include>
                </includes>
                <!-- allowed non-binary backwards compatible changes -->
                <excludes>
                  <!-- START default constructor on Plexus/JSR 330 components -->
    XML
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Thu Apr 25 08:48:58 GMT 2024
    - 15.4K bytes
    - Viewed (0)
  3. api/maven-api-model/src/main/mdo/maven.mdo

                FOR INTERNAL USE ONLY. This is a unique identifier assigned to each
                resource to allow Maven to merge changes to this resource that take
                place during the execution of a plugin. This field must be managed
                by the generated parser and formatter classes in order to allow it
                to survive model interpolation.
              </description>
              <type>String</type>
    XML
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Tue Apr 23 13:29:46 GMT 2024
    - 115.1K bytes
    - Viewed (0)
  4. maven-core/src/main/mdo/extension.mdo

                Other values define only the prefix of classes/resources being exposed. Their binary name must be equal to the prefix or starting with the prefix (followed by "." or "$").
                In particular this includes all subpackages. Despite the element name one can also only expose individual classes of a particular package by adding its binary name as value.
              ]]></description>
    XML
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Wed Feb 07 21:28:01 GMT 2024
    - 3.5K bytes
    - Viewed (0)
  5. api/maven-api-settings/src/main/mdo/settings.mdo

              <name>servers</name>
              <version>1.0.0+</version>
              <description>
                Configuration of server-specific settings, mainly authentication
                method. This allows configuration of authentication on a per-server
                basis.
              </description>
              <association>
                <type>Server</type>
                <multiplicity>*</multiplicity>
              </association>
    XML
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Sat Feb 17 18:40:11 GMT 2024
    - 33.3K bytes
    - Viewed (0)
  6. maven-core/src/test/resources-project-builder/jdk-activation/pom.xml

      <groupId>org.apache.maven.its.mng1957</groupId>
      <artifactId>test</artifactId>
      <version>1.0-SNAPSHOT</version>
    
      <name>Maven Integration Test :: MNG-1957</name>
      <description>
        Test that JDK profile activation allows version ranges.
      </description>
    
      <build>
        <plugins>
          <plugin>
            <groupId>org.apache.maven.its.plugins</groupId>
            <artifactId>maven-it-plugin-expression</artifactId>
    XML
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Sun Mar 29 19:02:56 GMT 2020
    - 2.8K bytes
    - Viewed (0)
  7. apache-maven/src/assembly/maven/conf/settings.xml

       | the build process. Profiles provided in the settings.xml are intended to provide local machine-
       | specific paths and repository locations which allow the build to work in the local environment.
       |
       | For example, if you have an integration testing plugin - like cactus - that needs to know where
    XML
    - Registered: Sun May 05 03:35:11 GMT 2024
    - Last Modified: Mon Jun 19 15:06:01 GMT 2023
    - 11K bytes
    - Viewed (0)
Back to top