Perhaps I'm not clear what you are suggesting. I'm not trying to do a release, I'm trying to use a snapshot (that a different division at our company produces). However I need to make a few overrides to this snapshot. yes we do have a process to move our overrides into the snapshot...but that process takes some time. In the meantime I have to build with the snapshot as it exists.
So what I am trying to do is simply unpack the snapshot, compile/replace classes with my overrides, and re-jar. I have chosen to rename the jar so there is no risk of confusing which jar is patched. yes we use a repository manager, all builds get deployed to it. -Dave On Tue, Aug 4, 2009 at 1:01 PM, <[email protected]> wrote: > Hi David, > > If you have all the source code, as you seem to suggest several times > in this convoluted post, then why don't you just deploy a new > -SNAPSHOT yourself to your local repository? You ARE using a > repository manager, right?? > > > http://www.sonatype.com/people/2009/01/best-practices-for-releasing-with-3rd-party-snapshot-dependencies/ > > -jesse > > On Tue, Aug 4, 2009 at 10:25 AM, David Hoffer<[email protected]> wrote: > > What is the maven way of creating a patched jar? > > > > I have a case where I need to apply some overrides to a binary jar which > is > > one of my dependencies. I have the source code for the overrides. So I > > could create a child module with the source and the one dependency that > > needs the overrides applied. What maven plugin would I use to extract > the > > class files from the dependency, combine with the new generated classes > from > > source, and then re-jar? The final artifact would have a new name, i.e. > > _patched, so as to not get confused with the original. How can I then > stop > > the transitive dependency on the original jar? I would want the > dependency > > to be on the new patched version only. > > > > What's the maven way of doing this sort of thing? > > > > -Dave > > > > > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
