On Mon, Apr 23, 2012 at 11:17 AM, Benson Margulies <bimargul...@gmail.com> wrote: > On Mon, Apr 23, 2012 at 2:10 PM, Robert Muir <rcm...@gmail.com> wrote: >> On Mon, Apr 23, 2012 at 2:07 PM, Benson Margulies <bimargul...@gmail.com> >> wrote: >>>> >>>> How do we handle situations like >>>> https://issues.apache.org/jira/browse/XERCESJ-1257 (open for 5 years, >>>> still not incorporated in a release), without doing hackish things >>>> (releasing someone elses code, sucking their entire codebase into >>>> ours), or relying upon Uwe Schindler to come up with some clever >>>> workaround? >>> >>> As far as I can tell, you have exactly the same issues solving this >>> issue with and without Maven. >>> >> >> I don't think thats really the case at all. If i want to release a >> patched jar with ivy its pretty trivial. >> >> I simply make a project in github or google code with a build.xml that >> downloads their code, patches it, and produces the patched result. its >> still an open source project: its basically a fork. I put the binaries >> i generate under Downloads and point ivy directly at that jar. >> >> Done. >> >> How to do this with maven? > > If it's a maven project, you do the same thing, patching the pom to > shade to change the packages if you want, or just changing the > coordinates. > > You publish the results to central via OSSRH under your coordinates. >
but note that in either case if you use the same package/namespace you are likely to upset the people who control that package/namespace ryan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
