David Walluck <david(a)zarb.org> writes:
Thomas Fitzsimmons wrote:
> What is the symptom of this problem?
If each jar is to be stored in its own directory, then build-classpath
and build-jar-repository need to be updated to be able to find these
jar locations. Otherwise, we just just get
$ build-classpath libreadline-java
/usr/bin/build-classpath: error: Could not find libreadline-java Java
extension for this JVM
/usr/bin/build-classpath: error: Some specified jars were not found
OK, which packages are these errors affecting? You could add the
libreadline-java jar to CLASSPATH after the build-classpath invocation.
In any case I don't think you should change libreadline-java to not
follow the packaging guidelines, if that's what you were planning.