updatePolicy for release repositories

I can't seem to find a detailed description of how updatePolicy affects release repository behavior. Can someone explain or point me to a document that does? I'm also interested in understanding how, if at all, updatePolicy affects release-version range resolution with regard to how often

Maven dependency size limit?

I appear to be encountering a bug in Maven 2.2.1 when downloading a dependency that is over 2 GB. Maven appears to successfully download it and issues no WARN or ERROR messages. However, the file is always truncated at 2147483647 bytes. This happens to be the max value of a Java Integer. I

Re: Referencing a property as plugin goal value

This works fine in Maven 3.0-beta-1. I guess that's one more reason to upgrade. -- View this message in context: http://maven.40175.n5.nabble.com/Referencing-a-property-as-plugin-goal-value-tp1224124p1441330.html Sent from the Maven - Users mailing list archive at Nabble.com.

Referencing a property as plugin goal value

[apologies ahead of time if this double-posted. I didn't see the first one I sent 12 hours ago] I don’t understand the behavior of plugin executions with regard to property resolution. I have a plugin configured like this: properties clover.goalsetup/clover.goal /properties ... plugin

Re: How to skip tests during release:prepare?

Have you tried this?: -Darguments='-Dmaven.test.skip=true' -- View this message in context: http://maven.40175.n5.nabble.com/How-to-skip-tests-during-release-prepare-tp1223821p1223830.html Sent from the Maven - Users mailing list archive at Nabble.com.