ansaurus

Question

Maven error with multiple executions in maven-deploy-plugin

Answer 1

A:

This is a bit verbose but may help:

<profiles>
  <profile>
    <id>deploy-j-interop</id>
    <build>
      <defaultGoal>deploy:deploy-file</defaultGoal>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-deploy-plugin</artifactId>
          <version>2.4</version>
          <configuration>
            <repositoryId>openscada-external</repositoryId>
            <url>${openscada.distrib.repository}</url>
          </configuration>
          <executions>
            <execution>
              <id>j-interop</id>
              <goals>
                <goal>deploy-file</goal>
              </goals>
              <configuration>
                <file>../openscada_opc_dcom/lib/j-interop.jar</file>
                <pomFile>../openscada_opc_dcom/lib/j-interop.pom</pomFile>
              </configuration>
            </execution>
          </executions>
        </plugin>
      </plugins>
    </build>
  </profile>

  <profile>
    <id>deploy-j-interopdeps</id>
    <build>
      <defaultGoal>deploy:deploy-file</defaultGoal>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-deploy-plugin</artifactId>
          <version>2.4</version>
          <configuration>
            <repositoryId>openscada-external</repositoryId>
            <url>${openscada.distrib.repository}</url>
          </configuration>
          <executions>
            <execution>
              <id>j-interopdeps</id>
              <goals>
                <goal>deploy-file</goal>
              </goals>
              <configuration>
                <file>../openscada_opc_dcom/lib/j-interopdeps.jar</file>
                <pomFile>../openscada_opc_dcom/lib/j-interopdeps.pom</pomFile>
              </configuration>
            </execution>
          </executions>
        </plugin>
      </plugins>
    </build>
  </profile>

  <profile>
    <id>deploy-jcifs</id>
    <build>
      <defaultGoal>deploy:deploy-file</defaultGoal>
      <plugins>
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-deploy-plugin</artifactId>
          <version>2.4</version>
          <configuration>
            <repositoryId>openscada-external</repositoryId>
            <url>${openscada.distrib.repository}</url>
          </configuration>
          <executions>
            <execution>
              <id>jcifs</id>
              <goals>
                <goal>deploy-file</goal>
              </goals>
              <configuration>
                <file>../openscada_opc_dcom/lib/jcifs-1.2.9.jar</file>
                <pomFile>../openscada_opc_dcom/lib/jcifs-1.2.9.pom</pomFile>
              </configuration>
            </execution>
          </executions>
        </plugin>
      </plugins>
    </build>
  </profile>
</profiles>

You would run it using the command:

mvn -P deploy-j-interop deploy-j-interopdeps deploy-jcifs

Boris Pavlović 2009-03-16 13:07:28

I guess that would work, but I want to specify just one profile and not each one separately.

Mauli 2009-03-16 15:19:14

What about trying to write your own plugin which will deal with multiple files?

Boris Pavlović 2009-03-16 23:22:27

Answer 2

A:

I guess maven tries to also execute the default execution, where <file> is not specified. It's usually a good idea to configure the plugins in pluginManagement, and explicitly bind the the different executions to specific phases.

Try to put an explicit '' and '' elements in the default plugin configuration. You can put garbage inside, to see if the default execution get executed, and if it does, make one of the executions a default.

siddhadev 2009-03-18 11:49:17

Answer 3

+2 A:

The reason why this happens is that when a plugin is invoked from the command line like you've done, it has no phase or execution associated with it. This means it picks up the unnamed execution configuration, which is the config outside the execution block.

If you really want to run multiple executions, bind them to a phase and then invoke that phase. In this case each execution will run with its own configuration.

The real unasked question here is why you are using deploy-file to deploy a bunch of stuff like this? If it's 3rd party stuff, you should get a repo manager like Nexus and upload them once to a repository for your whole team to use.

Brian Fox 2009-04-12 01:50:20

Answer 4

A:

To do all the deploys at once (as described by Boris) you can add:

<profile>
  <profiles>
    <id>MyId1</id>
    <activation><property>DeployAll</property></activation>
    ...
</profiles>
<profile>
  <id>MyId2</id>
  <activation><property>DeployAll</property></activation>
  ...

And then use

mvn -DDeployAll

Steven Christenson 2010-01-22 21:38:43

ansaurus

tags:

views:

answers:

Maven error with multiple executions in maven-deploy-plugin

related questions