One thing I noticed was the repository configurations. In particular the
"releases" disabled and "snapshots" enabled. Like this:
Have you tested this out? I've found that when 'releases' is disabled, the
repository seems to be completely ignored if you're not using explicit
dependency versions. For example, the dependency downloads if the version is
"2-SNAPSHOT", but it doesn't if the version is "[1,3)". I'm still trying to
track down exactly what's causing this for me, but I thought I'd check. I
suspect it has something to do with ArtifactRepositoryMetadata's 
isSnapshot()method being hardcoded to return false, but I'm still trying to
narrow it down farther.
From: Brett Porter
Sent: Monday, August 21, 2006 2:44 AM
To: Maven Developers List
Subject: Re: Request for review of wiki notes on patching maven plugins
On 16/8/06 12:30 PM, Barrie Treloar wrote:http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins
I've written up my notes on what I have done to patch maven plugins
that describes how to build the trunk of a plugin, apply patches, and
deploy the plugin to an internal company repository.
I could not find anything like this in the documentation sets and I
needed it because I need to ensure my build process is working without
waiting for a plugin release. Hopefully it will be of use to other
people that need a stop gap solution.
I'd appreciate any feedback or alternative solutions people have.
My first attempt was to use the SNAPSHOT repositories but as soon as a
new SNAPSHOT was released I lost all my patches! Oops. I believe that
the way I am doing it now will mean I only need to check released
versions of the plugin and to re-apply the process only if my patches
are not in that release.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com