Closed jeffmorin closed 3 months ago
Successfully created backport PR for dspace-7_x
:
A 2kB CLASSPATH is not particularly long for a large project, alas! I got into a DSpace instance's 'lib/' directory and ran 'ls | wc'. That instance's 180 required JARs have names adding up to 4311 bytes (including space delimiters).
References
Description
In the original state of the
test_database
target inbuild.xml
, the classpath built within the task becomes too long to be properly handled by the<java>
task that follows, which causes failure of any task that includestest_database
. I fixed the task so that the classpath is stored in an alias that is then used in the<javac>
task, which doesn't fail anymore.Instructions for Reviewers
After building the project using Maven, run
fresh_install
(or any task that hastest_database
in its transitive dependencies) in/dspace/target/dspace-installer/build.xml
.List of changes in this PR:
test_database
target in/dspace/target/dspace-installer/build.xml
.Please note that I am not sure whether this behaviour will be reproducible in all environments. I work in a Windows 10-based environment.
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!
Please note that unchecked entries below are not applicable to non-Java files.
pom.xml
), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.