Provide option to skip remote check if deploy lifecycle is not executed about exists-maven-plugin

[chonton]

By default, the remote goal is bound to the verify phase. To work as expected, this goal must be executed before the maven-deploy-plugin's deploy goal, which is bound to the deploy phase. You could change the binding of the remote goal to the deploy phase with the following:

      <plugin>
        <groupId>org.honton.chas</groupId>
        <artifactId>exists-maven-plugin</artifactId>
        <executions>
          <execution>
            <goals>
              <goal>remote</goal>
            </goals>
              <phase>deploy</phase>
          </execution>
        </executions>
      </plugin>

However, the deploy goal will still run first because "When multiple executions are given that match a particular phase, they are executed in the order specified in the POM, with inherited executions running first.".

My recommendation is to wrap the exists-maven-plugin in a profile that is activated only in the build host

  <profiles>
    <profile>
      <id>deploy-only-on-specific-host</id>
      <activation>
        <property>
          <name>build-server</name>
          <value>name</value>
        </property>
      </activation>
      <build>
        <plugin>
          <groupId>org.honton.chas</groupId>
          <artifactId>exists-maven-plugin</artifactId>
          <executions>
            <execution>
              <goals>
                <goal>remote</goal>
              </goals>
                <phase>deploy</phase>
            </execution>
          </executions>
        </plugin>
      </build>
    </profile>
  </profiles>