I think no because what we want it is to be sure that what we publish is coming
from what you have in the branch (no more, no less).
Using a switch in SVN could keep various unwanted local files.
Arnaud Héritier
aherit...@apache.org
On Dec 1, 2010, at 8:50 PM, Phillip Hellewell wrote:
Would
Would it make sense when using SVN to have release:perform do an svn
switch (to the tag created by release:prepare) rather than check out
the tag?
Phillip
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
Hi Neil,
neil hart wrote on Monday, March 12, 2007 8:26 PM:
By default release:perform does a site:deploy-site. This builds all
of the reports, etc. I'd like to limit it to do just deploying the
jars that are created by:
- mvn jar:jar
- mvn jar:test-jar
- mvn
Got it. I'm using:
build
pluginManagement
plugins
plugin
artifactIdmaven-release-plugin/artifactId
configuration
goalsdeploy/goals
/configuration
/plugin
By default release:perform does a site:deploy-site. This builds all of the
reports, etc. I'd like to limit it to do just deploying the jars that are
created by:
- mvn jar:jar
- mvn jar:test-jar
- mvn source:jar
- mvn source:test-jar
Basically override the goals. How do I do
You can probably achieve what you're looking for with 2 profiles: one
that you use when when you want to do release:perform and another for
all other times.
I don't believe the site plugin has a skip configuration element like
maven.test.skip but I've discussed adding a skip property to all
