Hi,
Okay, I've modified the MARC4J project to be "Mavenized"... to test it out,
you can clone my fork: https://github.com/ksclarke/marc4j (the 'mavenized'
branch)... you'll note all the references to ksclarke/marc4j would need to
be changed to marc4j/marc4j if you all want to go the full-monty-Mav
That would be super awesome if you wanted to do that, and see if you can
come up with something that Bob is okay with, but makes it possible for
us to actually do releases to maven, so people expecting to find
releases there can find them there.
I'm not sure I, or any of the other committers b
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" wrote:
> On Wed, Nov 13, 2013 at 6:04 PM, Robert Haschart
> wrote:
>
> > If you mean re-organize the project so that it correspond
On Wed, Nov 13, 2013 at 5:52 PM, Jonathan Rochkind wrote:
>
> I'm not sure, would we? Is that your advice?
>
That would be my advice, yes, but I understand Robert's perspective.
People have strong feelings one way or the other about Maven.
> Otherwise, Kevin, you interested in getting commit
On Wed, Nov 13, 2013 at 6:04 PM, Robert Haschart wrote:
> 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
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 f
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 opinion
Okay, thanks Bob.
I guess for the moment I might just keep using Marc4J by building it
myself from master without doing an official release.
I think that's probably better than halfway doing a release, like
tagging it in the repo with a release tag, but without doing a proper
maven release,
Hi, I don't know the details of marc4J, but I do know that the Maven
Release Plugin is very very handy for doing Maven releases:
http://maven.apache.org/maven-release/maven-release-plugin/
--
HARDY POTTINGER
University of Missouri Library Systems
http://lso.umsystem.edu/~pottingerhj/
https://MO
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
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 d
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 peop
12 matches
Mail list logo
