Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid dependency on heritrix-commons SNAPSHOT release #11

Closed
anjackson opened this issue Oct 26, 2013 · 2 comments
Closed

Avoid dependency on heritrix-commons SNAPSHOT release #11

anjackson opened this issue Oct 26, 2013 · 2 comments

Comments

@anjackson
Copy link
Member

The code is critically dependent on the heritrix-commons codebase, mainly for the WARC readers/writers. API changes between 3.1.1 and 3.1.2-SNAPSHOT mean that we cannot rely on a proper release at the moment.

This is really rather bad practice for code stability, as the dependant code can shift from underneath us, and this is even more pressing as the two codebases are now under the control of different groups.

Easiest solution is probably for IA to make a 3.1.2 release. Best solution is probably to pull the ARC/WARC code out into a separate project AND/OR shift over to the JWAT implementation. Clumsy fallback would be to make an IIPC release of H3 and depend on that instead.

@egh
Copy link
Contributor

egh commented Jan 9, 2014

I believe this is done?

@anjackson
Copy link
Member Author

Yes, thanks to @nlevitt's work, the critical code for OpenWayback has been moved into commons-web (see his last two most recent commits). The test suite has not been moved over yet, but that perhaps belongs in a separate ticket.

anjackson pushed a commit that referenced this issue Mar 8, 2014
RogerMathisen pushed a commit to nlnwa/openwayback that referenced this issue Sep 23, 2014
pom.xml customizations to allow IA and other 3rd parties to tag builds o...
RogerMathisen pushed a commit to nlnwa/openwayback that referenced this issue Sep 23, 2014
Merge IA changes into IIPC master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants