org.apache.maven.its.mng3906 d 0.1 jar maven-core-it file:///${basedir}/repo true true . pom.xml src/** src/main/resources META-INF/maven/org.apache.maven.its.mng3906/d/pom.properties #Generated by Maven #Sun Dec 14 12:11:46 CET 2008 version=0.1 groupId=org.apache.maven.its.mng3906 artifactId=d...

                if (orgModelVersion != intModelVersion) {
                    model.setModelVersion(intModelVersion);
                }
                visit(model.getParent());
                // GroupId
                String orgGroupId = model.getGroupId();
                String intGroupId = interpolate(orgGroupId);
                if (orgGroupId != intGroupId) {
                    model.setGroupId(intGroupId);

 *
 * <p><a id="iteration"></a>
 *
 * <p><b>Key-grouped iteration.</b> All view collections follow the same iteration order. In all
 * current implementations, the iteration order always keeps multiple entries with the same key
 * together. Any creation method that would customarily respect insertion order (such as {@link
 * #copyOf(Multimap)}) instead preserves key-grouped order by inserting entries for an existing key

org.apache.maven.its.mng3906 a 0.1 jar maven-core-it file:///${basedir}/repo true true . pom.xml src/** src/main/resources META-INF/maven/org.apache.maven.its.mng3906/a/pom.properties #Generated by Maven #Sun Dec 14 12:10:53 CET 2008 version=0.1 groupId=org.apache.maven.its.mng3906 artifactId=a...

org.apache.maven.its.mng3906 b 0.1 jar maven-core-it file:///${basedir}/repo true true . pom.xml src/** src/main/resources META-INF/maven/org.apache.maven.its.mng3906/b/pom.properties #Generated by Maven #Sun Dec 14 12:11:28 CET 2008 version=0.1 groupId=org.apache.maven.its.mng3906 artifactId=b...

    protected void assertPluginDescriptor(
            MojoDescriptor mojoDescriptor, String groupId, String artifactId, String version) {
        assertNotNull(mojoDescriptor);
        PluginDescriptor pd = mojoDescriptor.getPluginDescriptor();
        assertNotNull(pd);
        assertEquals(groupId, pd.getGroupId());
        assertEquals(artifactId, pd.getArtifactId());
        assertEquals(version, pd.getVersion());

        String src = source.getGroupId();
        if (src != null) {
            if (sourceDominant || target.getGroupId() == null) {
                target.setGroupId(src);
                target.setLocation("groupId", source.getLocation("groupId"));
            }
        }
    }

    protected void mergeModel_ArtifactId(
            Model target, Model source, boolean sourceDominant, Map<Object, Object> context) {

 *
 * <p><a id="iteration"></a>
 *
 * <p><b>Key-grouped iteration.</b> All view collections follow the same iteration order. In all
 * current implementations, the iteration order always keeps multiple entries with the same key
 * together. Any creation method that would customarily respect insertion order (such as {@link
 * #copyOf(Multimap)}) instead preserves key-grouped order by inserting entries for an existing key

`33.5.0-android`. For more about depending on Guava, see
[using Guava in your build].

To add a dependency on Guava using Maven, use the following:

```xml
<dependency>
  <groupId>com.google.guava</groupId>
  <artifactId>guava</artifactId>
  <version>33.5.0-jre</version>
  <!-- or, for Android: -->
  <version>33.5.0-android</version>
</dependency>
```

To add a dependency using Gradle:

        }

        return "";
    }

    static String getGroupId(Model model) {
        String groupId = model.getGroupId();
        if (groupId == null && model.getParent() != null) {
            groupId = model.getParent().getGroupId();
        }
        return groupId;
    }

    static String getVersion(Model model) {
        String version = model.getVersion();