Is there some plugin in your build that is forking the whole build?
On Wed, Jun 2, 2010 at 10:29 AM, Alan D. Cabrera <l...@toolazydogs.com> wrote: > I have a root POM that defines are deploy profile that generates source, > javadoc, and signing. > > When I use this profile: > > mvn clean install -P deploy > > My artifacts get doubly signed, e.g. > > http://oss.sonatype.org/content/repositories/papoose-snapshots/org/papoose/cmpn/papoose-http/1.0-SNAPSHOT/papoose-http-1.0-20100602.142421-2-javadoc.jar.asc.asc > > Does anyone know what I am doing wrong? > > > Regards, > Alan > > <profiles> > > <profile> > <id>deploy</id> > <activation> > <activeByDefault>false</activeByDefault> > </activation> > > <build> > <plugins> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-gpg-plugin</artifactId> > <executions> > <execution> > <id>sign-artifacts</id> > <phase>verify</phase> > <goals> > <goal>sign</goal> > </goals> > </execution> > </executions> > </plugin> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-javadoc-plugin</artifactId> > <executions> > <execution> > <id>attach-javadocs</id> > <goals> > <goal>jar</goal> > </goals> > </execution> > </executions> > </plugin> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-source-plugin</artifactId> > <version>2.0.4</version> > <executions> > <execution> > <id>attach-sources</id> > <goals> > <goal>jar</goal> > </goals> > </execution> > </executions> > </plugin> > </plugins> > > </build> > </profile> > > </profiles> > >
