I brought marc4j under ivy; I haven't bothered with the maven artifact
generation tasks, but that would be the way to go.
On Nov 13, 2013 6:16 PM, "Kevin S. Clarke" <[log in to unmask]> wrote:
> On Wed, Nov 13, 2013 at 6:04 PM, Robert Haschart <[log in to unmask]>
> > If you mean re-organize the project so that it corresponds to Maven's
> > conventions for doing things, and then relying on Maven to handle
> > dependencies and build of the project, no thank you.
> Yes, that's what I meant.
> > For instance because building Marc4j requires compiling some of the code,
> > and then using that code to generate a couple of source files, and then
> > compiling those generated files, and then bundling both sets of class
> > to produce the jar, it seemed that to Maven-ify the project would require
> > splitting it into to separate projects with complicated dependencies
> > between them.
> Not necessarily. Is this process represented in the Ant build file
> currently or are there some docs for it? I'm not an active MARC4J user so
> not aware of the process. What I might do is Mavenize it (in my own fork)
> just for fun. If what I do looks more complicated to you, no problem... I
> will have had my fun and I won't mind it not being picked up.
> > If there is any way you can help with getting releases of Marc4j into the
> > central Maven repo that would not require "going all in" with Maven it
> > would be greatly appreciated.
> I'm sure there is a way to do that, but I'm probably not your guy for that.
> I agree there is a fair amount of work to see things Maven's way but, once
> you do, straying from that worldview takes more effort. Someone else will
> probably be better suited than me to take that other path.