Minor issues with the POM

[anjackson]

There is no organization tag.

I wonder if we should explicitly declare this a Maven 3 project? It already conforms to M3.

The compiler plugin specifies Java 6. Seems like a good time to bump this up to 7.

I notice that there is an assembly plugin defined to create a "jar-with-dependencies". This doesn't seem necessary or useful for a library.

[johnerikhalse]

I did a search for public static void main and found that there are 16 classes which are runnable. Some of them are just for testing, but others are meant as tools. If people actually are using it as a command line tool, then it makes sense to keep the jar-with-dependencies.

A better approach would be to separate command line stuff in its own module and keep webarchive-commons as a plain library.

[kris-sigur]

I think it would be helpful to list the 'tools' in question:
org.archive.
extract.ResourceExtractor
io.arc.ARC2WCDX
io.arc.ARCReader
io.warc.WARCReader
net.md5.Handler
net.rsync.Handler
net.PublicSuffixes
url.SURT
util.binsearch.FileSearchTool
util.binsearch.SeekCDXBenchmarker
util.Grep
util.SURT
util.SurtPrefixSet

Plus two more under src/test

[johnerikhalse]

If we require Java 7, it might also be the right time to remove the classes pulled in from OpenJDK 7 as described in this comment #20 (comment) by @gojomo.

As far as I know, all implementations of Java 7 are using the class library from OpenJDK 7, so this should be safe.

[kris-sigur]

If we move to Java7 that will affect Wayback and Heritrix as well.

[johnerikhalse]

Since Java 6 reached its end of public updates in February 2013 it seems like a good idea to require Java 7, but that need to be agreed on with the wider community. Any ideas how to proceed?

[johnerikhalse]

To sum this up:

1. Missing organization tag was added by @anjackson in November 2013
2. Declare Maven 3 as a prerequisite should not be a very controversial thing to do (proposed version 1.1.5)
3. Require Java 7 has implications for other projects like Heritrix and OpenWayback. Should probably be an issue of its own (proposed version 1.2.0)
4. Remove the "jar-with-dependencies" artifact. If we'd like to support the command line use we should make a separate module depending on this one. Should be a separate issue (proposed version 1.2.0)

[johnerikhalse]

I created issue #28 and #29 for the tasks that influence usage of the library.
Created pull request #30 for requiring Maven 3 which is the remaining part of this issue.

[RogerMathisen]

Seems all requests in this issue either are fixed or moved to new issues under the 1.2.0 release, closing.