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.

My experience with Maven is that it can make things that are already 
easy, a little bit easier, after a fair bit of work, but things that are 
outside its way of looking at the world become much more cumbersome.   
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 files 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.

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.

-Bob Haschart

On 11/13/2013 5:52 PM, Jonathan Rochkind wrote:
> Aha, Kevin!
>
> I'm not sure, would we?  Is that your advice?  Do you have any 
> interest in taking this on?
>
> There's possibly no current marc4j committers who understand how it's 
> set up now, it's kind of just grown under various people's 
> stewardship, I think it's possible nobody has strong opinions as long 
> as it works and doens't make marc4j any harder to work with for 
> developers.
>
> (If someone _does_ have understanding and/or strong feelings about how 
> marc4j source code is set up (maybe Bob?) then definitely correct me! 
> And maybe work with Kevin on figuring out how to do a release?)
>
> Otherwise, Kevin, you interested in getting committer privs and 
> figuring out what needs to be done?
>
> On 11/13/13 5:23 PM, Kevin S. Clarke wrote:
>> I have experience pushing projects into Maven's central repo through
>> Sonatype.  Maven has a standard structure (that you don't have to 
>> use, but
>> it makes things easier/more-Maven-ish).  Would you want the project
>> reorganized into that structure in the process?
>>
>> Kevin
>>
>>
>>
>> On Wed, Nov 13, 2013 at 5:15 PM, Robert Haschart <[log in to unmask]> 
>> wrote:
>>
>>> I believe that is one of the open issues for Marc4j.   I do not know 
>>> how
>>> to push a jar or a new version of a jar to a Maven repo.
>>> I believe Bill Dueber was looking into this just last month when he 
>>> wrote
>>> the following to the Solrmarc list:
>>>
>>>     I'm trying to get marc4j into maven central, and I don't know who
>>>     owns the domain. If it's one of us, then we can use it. If not,
>>>     well, I'm not sure what we do (except maybe use the github 
>>> location?)
>>>
>>>     --    Bill Dueber
>>>     Library Systems Programmer
>>>     University of Michigan Library
>>>
>>> The last release I did was to merely create the jar in the releases
>>> sub-directory, and reference it in the README.textile file. That 
>>> emulates
>>> the way the releases had been done from the tigris.org site, but its 
>>> not
>>> the right way to do a release.
>>>
>>> -Bob Haschart
>>>
>>>
>>> On 11/13/2013 4:43 PM, Jonathan Rochkind wrote:
>>>
>>>> I am a committer, but I have no idea how to do a marc4j release.
>>>>
>>>> There are some fixes in master repo for marc4j. I can find all the 
>>>> parts
>>>> of the source code that seem to have a version number and change 
>>>> them. I
>>>> can make a git tag with the version number.
>>>>
>>>> But what else is entailed, how do people actually get marc4j?  I 
>>>> need to
>>>> update maven repo somehow or something? Anyone?
>>>>
>>>
>>
>>