maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Stolwijk <>
Subject Re: Managing Modified Dependencies
Date Mon, 04 May 2009 17:01:42 GMT
Normally I just check out the source, apply my patches, update the
deploymentManament section to point to our inhouse repository, update
the version to x.y.z-companyname-1 and do a maven deploy. Then update
the documentation to mention which revision you checked out
(preferably a tag) and for which issues you have applied a patch, so
that the build is reproducible.


Nick Stolwijk
~Java Developer~

Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem

On Mon, May 4, 2009 at 6:10 PM, <> wrote:
> The situation:
> * Company finds a show stopping bug in dependency Foo
> * Company can not wait for the owner of Foo to fix it
> * Company branches the source code locally and applies patch
> * Company now needs to maintained a modified third party dependency
> Currently some crazy system of relative paths and fake version numbers is
> being used to resolve the modified dependencies. However, this is obviously
> an eye soar sore and is cluttering up our source repository. What are some
> solutions for ensuring that changes don't get overwritten and our repository
> stays clean?
> Any suggestion will be welcomed!
> I appreciate your time, thank you at least for that :-),
> Daniel.
> --
> View this message in context:
> Sent from the Maven - Users mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message