Aw crud.
Thanks for your help guys but this turned out to be a case of
developer headspace and timing. ;-)
I forgot that I had to call maven:prepare first. My assumption at the
time was that it would be called by maven:perform if it was required.
Not the case though.
Works great now.
Jim C.
---
Not massively complicated, have a look at the responses to this query
about a similar issue. In this case a need to prevent deploying the
sources jar as part of a release.
http://stackoverflow.com/questions/437085/mvn-releaseperform-without-source-ending-up-in-artifactory
On Thu, 2009-12-10 at 10
How complicated is that to do? We don't generally use profiles around
here so I've little experience with them.
On Thu, Dec 10, 2009 at 9:48 AM, Adam Leggett (UPCO)
wrote:
> I believe its the default release profile that triggers the site
> deployment stuff. There is an option for setting custom
I believe the only difference here is that this is a property and I am
using xml but I imagine it is the same thing.
On Thu, Dec 10, 2009 at 9:50 AM, Olivier Lamy wrote:
> You can configure used goals with this :
> http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#goals
>
> 2
You can configure used goals with this :
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#goals
2009/12/10 Jim Collings :
> The objective is to prevent maven's attempt at site deployment.
> Everything else, though, I want. Problem is that when I use the xml
> below, it ONLY i
I believe its the default release profile that triggers the site
deployment stuff. There is an option for setting custom ones on the
perform mojo:
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#releaseProfiles
On Thu, 2009-12-10 at 09:25 -0500, Jim Collings wrote:
> The o
The objective is to prevent maven's attempt at site deployment.
Everything else, though, I want. Problem is that when I use the xml
below, it ONLY installs.
So I added goals with install:
org.apache.maven.plugins
maven-release-plugin
...someversion
