You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Nord, James" <JN...@nds.com> on 2009/05/07 18:01:24 UTC
sources attached twice during release:perform.
Hi all,
I recently updated to use the mave-source-plugin:2.1 with the following
config
<plugin>
<artifactId>maven-source-plugin</artifactId>
<version>2.1</version>
<executions>
<execution>
<id>attach-sources</id>
<phase>verify</phase>
<goals>
<goal>jar-no-fork</goal>
<goal>test-jar-no-fork</goal>
</goals>
</execution>
</executions>
</plugin>
this works as expceted for normal instals and deploys however when
running the release plugin it tries to attach the sources twice (which
fails as we have nexus setup to prevent re-deployments)
release plugin is set to the following inside pluginManagement
<plugin>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-8</version>
<configuration>
<arguments>-DskipSCMCheck</arguments>
</configuration>
</plugin>
My guess is this is being over-ridden by the super poms
"release-profile" and we have both the fork and no-fork sources being
attached.
So my question is how to disable this in either corporate pom (I don't
want to have to run mvn -P-release-profile release:perform) as I want
the updated release info - and anything that will occur in future
versions of maven that is needed.
/James
**************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmaster@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.
To protect the environment please do not print this e-mail unless necessary.
NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**************************************************************************************
Re: sources attached twice during release:perform.
Posted by David Hoffer <dh...@gmail.com>.
Try
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<version>2.0-beta-9</version>
<configuration>
...
<useReleaseProfile>false</useReleaseProfile>
</configuration>
</plugin>
On Thu, May 7, 2009 at 10:01 AM, Nord, James <JN...@nds.com> wrote:
> Hi all,
>
> I recently updated to use the mave-source-plugin:2.1 with the following
> config
>
> <plugin>
> <artifactId>maven-source-plugin</artifactId>
> <version>2.1</version>
> <executions>
> <execution>
> <id>attach-sources</id>
> <phase>verify</phase>
> <goals>
> <goal>jar-no-fork</goal>
> <goal>test-jar-no-fork</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
>
>
> this works as expceted for normal instals and deploys however when
> running the release plugin it tries to attach the sources twice (which
> fails as we have nexus setup to prevent re-deployments)
>
> release plugin is set to the following inside pluginManagement
> <plugin>
> <artifactId>maven-release-plugin</artifactId>
> <version>2.0-beta-8</version>
> <configuration>
> <arguments>-DskipSCMCheck</arguments>
> </configuration>
> </plugin>
>
> My guess is this is being over-ridden by the super poms
> "release-profile" and we have both the fork and no-fork sources being
> attached.
>
> So my question is how to disable this in either corporate pom (I don't
> want to have to run mvn -P-release-profile release:perform) as I want
> the updated release info - and anything that will occur in future
> versions of maven that is needed.
>
> /James
>
>
> **************************************************************************************
> This e-mail is confidential, the property of NDS Ltd and intended for the
> addressee only. Any dissemination, copying or distribution of this message
> or any attachments by anyone other than the intended recipient is strictly
> prohibited. If you have received this message in error, please immediately
> notify the postmaster@nds.com and destroy the original message. Messages
> sent to and from NDS may be monitored. NDS cannot guarantee any message
> delivery method is secure or error-free. Information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
> We do not accept responsibility for any errors or omissions in this message
> and/or attachment that arise as a result of transmission. You should carry
> out your own virus checks before opening any attachment. Any views or
> opinions presented are solely those of the author and do not necessarily
> represent those of NDS.
>
> To protect the environment please do not print this e-mail unless
> necessary.
>
> NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18
> 4EX, United Kingdom. A company registered in England and Wales Registered
> no. 3080780 VAT no. GB 603 8808 40-00
>
> **************************************************************************************
>