Thought I would update this thread in case anyone has the same question. In the absence of any instructions on how to apply a patch, I decided to try some things on a test server. I made a copy of our DSpace 6.3 production server and went to update the two files, CommunityFiliator.java and Community.java, with the patched files. I couldn't find the files on the server, and I determined that our server had been installed with the precompiled version of DSpace.
So I copied the sources to the [dspace-source] directory. Then I copied the new CommunityFiliator.java and Community.java files to their respective places and recompiled DSpace. Only nothing changed. I tried it a few more times and eventually became aware that the compile process was not using the new sources. I guess this was due to the original installation being precompiled. A colleague who is more of a developer suggested installing a new test system from scratch using the sources. Once the new system was installed, we could copy the dspace binary file from it to our original test system. This worked, but not without a hitch. The build failed with the message, "log4j package does not exist". My developer colleague helped determine that this was a result of the log4j specification in Community.java being different from the existing log4j version in DSpace 6.3. Once we changed the spec in the patch file back to its pre-patch version, the compile operation proceeded. For reference, the line that we changed: org.apache.logging.log4j.Logger; We changed it to: org.apache.log4j.Logger; On Wednesday, June 5, 2019 at 11:00:52 AM UTC-5, Glenn G wrote: > > Apologies if this is a dumb question, but how do you apply a patch? We're > running DSpace 6.3, and we need to get the CommunityFiliator running with > the new functionality described in GitHub pull request DS-3914. > > I replaced CommunityFiliator.java and Community.java files on the system, > but it didn't made any difference. On our system, those file are located > here: > > > [dspace-source]/dspace-api/src/main/java/org/dspace/administer/CommunityFiliator.java > > [dspace-source]/dspace-rest/src/main/java/org/dspace/rest/common/Community.java > [dspace-source]/dspace-api/src/main/java/org/dspace/content/Community.java > > I tried rebuilding, but that didn't make a difference either. I used > these commands to do the rebuild: > > mvn -U clean package -Dmirage2.on=true > ant update > > We still get the following error when we run [dspace]/bin/dspace > community-filiator -r -p xxxxx/xxxxx -c xxxxx/xxxx > > Exception: null > java.lang.UnsupportedOperationException > at java.util.AbstractList.remove(AbstractList.java:161) > at java.util.AbstractList$Itr.remove(AbstractList.java:374) > at java.util.AbstractCollection.remove(AbstractCollection.java:293) > at > org.dspace.administer.CommunityFiliator.defiliate(CommunityFiliator.java:264) > at > org.dspace.administer.CommunityFiliator.main(CommunityFiliator.java:164) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229) > at > org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81) > > What am I missing? > > Thanks, > Glenn > -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/0b1649c6-cda9-4a9d-a222-e16ee271099d%40googlegroups.com.
