maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henrik Skriver Rasmussen <skrive...@gmail.com>
Subject Re: Maven deploy plugin 2.8.1 - deploy-file goal - unable to avoid attachedArtifacts from being deployed in execute
Date Thu, 13 Feb 2014 10:36:48 GMT
Hi Anders

I have a multi-module project with this structure:

 A (root and parent pom project)
 - module 1 - builds a jar as artifact
 - module 2  - uses module 1 jar artifact in assembly tries to deploy the
assembled zip file to artifactory.

This is the module 2 pom file with YYYY inserted to replace project
specific names.

<project xmlns="http://maven.apache.org/POM/4.0.0"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">

<modelVersion>4.0.0</modelVersion>

<parent>

 <groupId>YYYY</groupId>

 <artifactId>YYYY</artifactId>

 <version>1.1-SNAPSHOT</version>

</parent>

 <artifactId>scripts</artifactId>

<packaging>pom</packaging>

<name>scripts</name>

<description>YYYY</description>

 <properties>

 <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

 <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>

 <main.basedir>${project.parent.basedir}</main.basedir>

</properties>

  <build>

 <plugins>

 <plugin>

  <groupId>org.apache.maven.plugins</groupId>

  <artifactId>maven-install-plugin</artifactId>

  <version>2.5.1</version>

  <configuration>

  <skip>true</skip>

  </configuration>

 </plugin>

 <plugin>

  <groupId>org.apache.maven.plugins</groupId>

  <artifactId>maven-assembly-plugin</artifactId>

  <version>2.4</version>

  <configuration>

  <skip>true</skip>

  </configuration>

 </plugin>

 <plugin>

  <groupId>org.apache.maven.plugins</groupId>

  <artifactId>maven-deploy-plugin</artifactId>

  <version>2.8.1</version>

  <configuration>

  <skip>true</skip>

  </configuration>

 </plugin>

   </plugins>

</build>

 <profiles>

 <profile>

<id>deployprofile</id>

 <build>

  <plugins>

  <plugin>

   <groupId>org.codehaus.mojo</groupId>

   <artifactId>exec-maven-plugin</artifactId>

   <version>1.2.1</version>

   <executions>

   <execution>

    <id>Copy  into target folder and copy service jar into files/default
</id>

    <phase>package</phase>

    <goals>

    <goal>exec</goal>

    </goals>

    <configuration>

    <executable>${project.basedir}/build_cookbook.sh</executable>

    <arguments>

     <argument>${project.parent.artifactId}</argument>

     <argument>${project.parent.version}</argument>

    </arguments>

    </configuration>

   </execution>

   </executions>

  </plugin>

  <plugin>

   <groupId>org.apache.maven.plugins</groupId>

   <artifactId>maven-assembly-plugin</artifactId>

   <version>2.4</version>

      <executions>

   <execution>

    <id>deployprofile</id>

    <phase>package</phase>

    <goals>

    <goal>single</goal>

    </goals>

    <configuration>

    <finalName>${project.parent.artifactId}-${project.parent.version}
</finalName>

    <outputDirectory>${project.build.directory}/</outputDirectory>

    <filtering>true</filtering>

    <descriptors>

     <descriptor>assembly/dist.xml</descriptor>

    </descriptors>

    </configuration>

   </execution>

   </executions>

  </plugin>

  <plugin>

   <groupId>org.apache.maven.plugins</groupId>

   <artifactId>maven-deploy-plugin</artifactId>

   <executions>

   <execution>

    <id>cookbook</id>

    <phase>deploy</phase>

    <goals>

    <goal>deploy-file</goal>

    </goals>

    <configuration>

                      <primaryArtifact>false</primaryArtifact>

    <repositoryId>artifactory</repositoryId>

    <packaging>zip</packaging>

    <url>${project.distributionManagement.snapshotRepository.url}</url>

    <generatePom>false</generatePom>

    <artifactId>${project.parent.artifactId}</artifactId>

    <groupId>${project.parent.groupId}</groupId>

    <version>${project.parent.version}</version>

    <classifier>deploymentfile</classifier>

    <file>


${project.build.directory}/${project.parent.artifactId}-${project.parent.version}-deploymentfile.zip

    </file>

    </configuration>

   </execution>

   </executions>

  </plugin>

  </plugins>

 </build>

 </profile>

</profiles>

</project>


Med venlig hilsen
Henrik Skriver Rasmussen


On Thu, Feb 13, 2014 at 2:15 PM, Anders Hammar <anders@hammar.net> wrote:

> You need to provide more info on what you're doing! Is the
> deploy:deploy-file bound to the build lifecycle of a project? How?
>
> /Anders
>
>
> On Thu, Feb 13, 2014 at 11:06 AM, Henrik Skriver Rasmussen <
> skriver79@gmail.com> wrote:
>
> > Hi
> >
> > I have a question about the expected behaviour of the deploy:deploy-file
> > goal in the maven deploy plugin 2.8.1 which I am currently using to
> deploy
> > one file.
> >
> > It surprised me that no matter what I did I kept getting more artifacts
> > deployed that I asked for and the reason is in the
> > org.apache.maven.plugin.deploy.DeployFileMojo.execute line 376 where the
> > attached artifacts are also deployed.
> >
> > Is this intended behaviour and if so how can I avoid this from happening?
> >
> > The goal name deploy-file indicates that one artifact (possible incl.
> > pom/metadata) is to be deployed and not also a throng of other artifacts.
> >
> > I will be happy to provide a patch where this is aspect is removed.
> >
> > Thank you in advance
> >
> > regards
> > Henrik Skriver Rasmussen
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message