- 20 Jan, 2022 1 commit
-
-
Matthias Neugebauer authored
* upstream/r/10.x: (27 commits) Fix Javadocs Automatically Update Matrix Room Automated Release Title Forgot the 10.9 release notes Updating Opencast 10.x changelog Spelling issue, and editing Add download artifacts in engage publication ConfigurableRetractWorkflowOperationHandle: fixed exception message Revert order of common and extended metadata in admin ui event endpoint Handle missing common ui adapters for tenants Document Capture Agent Input Selection Fix Scheduler Conflict Checks Updating maven documentation re: automated nexus deploys Warn against using CIFS for Inbox Show input selection only if applicable Update to pax-logging 1.11.13 fixup! add missing unbind methods Remove Unused Additional Log4J remove unused deactivate methods add missing unbind methods ...
-
- 19 Jan, 2022 2 commits
-
-
Greg Logan authored
With Opencast 11 our javadocs broke. In part this was due to the migration from JDK 8 to 11, but the majority of those issues have already been corrected by this point. The current issue, which this commit resolves, is that various Lucene packages (from modules/solr) are not found by javadocs when the aggregation step happens. We have to manually add these to the javadoc plugin to make sure that it can find them. README: When testing aggregation bugs you can massively speed up testing by using the javadocs.sh file generated in target/site/apidocs (from project root). This file disappears as part of the javadoc generation process, so you won't find it unless something goes wrong :) Fixes #2085
-
Greg Logan authored
Pull request #3364 Automatically Update Matrix Room
-
- 18 Jan, 2022 14 commits
-
-
Lars Kiesow authored
This patch automatically updates the Matrix room description once a new tag has been pushed to the Opencast repository.
-
Greg Logan authored
Pull request #3363 Automated Release Title
-
Lars Kiesow authored
This patch should actually set the title in automatically generated GitHub releases. The patch [is based on random information I found in this thing called the internet](https://github.community/t/how-to-get-just-the-tag-name/16241/6). I did not test this but it looks sensible and shouldn't make anything worse. Let's just try this?
-
Greg Logan authored
-
Greg Logan authored
-
Greg Logan authored
Pull request #3361 Fix metadata for multitenancy
-
Greg Logan authored
Pull request #3362 ConfigurableRetractWorkflowOperationHandle: fixed exception message
-
Greg Logan authored
-
Greg Logan authored
Pull request #3359 Document Capture Agent Input Selection
-
Jonas Dühring authored
All download artifacts are now automatically included in the `engage` publication channel.
-
Jonathan L. Komar authored
Corrected WorkflowOperationException text when CHANNEL_ID_KEY is missing
-
Katrin Ihler authored
This order was changed a while ago, but it's actually important for the common adapter to overwrite any extended metadata adapters with the same flavor in case of multi tenancy, where it's currently recommended to have a copy of the common metadata config, but not label it common. Since the common adapter gets some special treatment by the backend like renoving some fields prior to being sent to the frontend, we should use it over the "not-common" tenant-specific ones until there is a more general fix for the whole situation. This means that the copies for the other tenants are actually probably unnecessay right now, at least for the admin ui.
-
Katrin Ihler authored
Currently tenants other than the default tenant don't actually have common metadata configured (or rather, it's not labeled as common). Since this causes NPEs with the most recent changes to the index service, we fall back to the adapter for the default tenant now, similarly to how it worked before. This way, no config changes are necessary for this fix to work.
-
Lars Kiesow authored
This patch finally documents how the capture agent input selection works.
-
- 17 Jan, 2022 2 commits
-
-
Greg Logan authored
Pull request #3339 Fix Scheduler Conflict Checks
-
Lars Kiesow authored
This patch fixes the scheduler's conflict checks which previously broke spectacularly if someone already ingested media to one of the found scheduled events. The scheduler woould then find the conflict but would fail to retrieve the media package since it wouldn't be the owner of that event in the asset manager any longer. That does not make a lot of sense for a conflict check where you just want to get the information.
-
- 13 Jan, 2022 1 commit
-
-
Greg Logan authored
-
- 07 Jan, 2022 1 commit
-
-
Lars Kiesow authored
This patch updates the Inbox documentation, warning against using a CIFS mount for the inbox.
-
- 05 Jan, 2022 2 commits
-
-
Greg Logan authored
Pull request #3251 Inbox may fail at startup
-
Greg Logan authored
Pull request #3300 Fixup osgi services and xmls
-
- 04 Jan, 2022 2 commits
-
-
Lars Kiesow authored
This patch removes the input selection from being marked as required (since it is not) and will no more show an empty selection if a capture agent does not have multiple inputs. This will hopefully avoid some confusion around this option.
-
Lars Kiesow authored
This patch updates pax-logging to version 1.11.13. This fixes CVE-2021-44832. The issue is unlikely to hit Opencast adopters since the affected appender is not configured by default and not commonly used in our community.
-
- 23 Dec, 2021 3 commits
-
-
Greg Logan authored
Pull request #3299 Remove Unused Additional Log4J
-
Greg Logan authored
Pull request #3298 Automate GitHub Release
-
Gregor Eichelberger authored
-
- 21 Dec, 2021 7 commits
-
-
Lars Kiesow authored
Opencast included an additional version of Log4J via its elasticsearch module. The dependency seems to be unused. To avoid confusion, this pull requests removes it completely.
-
Gregor Eichelberger authored
-
Gregor Eichelberger authored
-
Gregor Eichelberger authored
-
Lars Kiesow authored
This patch automates building the release tarballs and creating a release on GitHub. The workflow will only create a `Draft` release, allowing release managers to review the release before publication. This should be a lot faster and less error-prone than release managers building the tarballs at home and uploading them manually.
-
Lars Kiesow authored
Starting Opencast with PostgreSQL configured you end up with a database error being logged: ``` 2021-12-20 21:47:06,778 | WARN | (Activator:172) - Unable to delete temp table oc_temp_808069, please remove this yourself! org.postgresql.util.PSQLException: No results were returned by the query. at org.postgresql.jdbc.PgStatement.executeQuery(PgStatement.java:237) ~[!/:?] at com.mchange.v2.c3p0.impl.NewProxyStatement.executeQuery(NewProxyStatement.java:327) ~[!/:?] at org.opencastproject.db.Activator.start(Activator.java:170) [!/:?] at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:697) [org.apache.felix.framework-5.6.12.jar:?] at org.apache.felix.framework.Felix.activateBundle(Felix.java:2240) [org.apache.felix.framework-5.6.12.jar:?] at org.apache.felix.framework.Felix.startBundle(Felix.java:2146) [org.apache.felix.framework-5.6.12.jar:?] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:998) [org.apache.felix.framework-5.6.12.jar:?] at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:984) [org.apache.felix.framework-5.6.12.jar:?] at org.apache.karaf.features.internal.service.BundleInstallSupportImpl.startBundle(BundleInstallSupportImpl.java:165) [!/:?] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.startBundle(FeaturesServiceImpl.java:1153) [!/:?] at org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:1036) [!/:?] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1062) [!/:?] at org.apache.karaf.features.internal.service.FeaturesServiceImpl.lambda$doProvisionInThread$13(FeaturesServiceImpl.java:998) [!/:?] at java.util.concurrent.FutureTask.run(FutureTask.java:264) [?:?] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [?:?] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [?:?] at java.lang.Thread.run(Thread.java:829) [?:?] ``` While the error is inconsequential and the table is actually even removed, the warning is confusing and not accurate. This patch fixes the problem.
-
Lars Kiesow authored
This patch fixes some pax-logging replacements done when assembling Opencast's distributions. The reason why Opencast works as expected even without this patch is, that we had to make sure to include the new bundles in the distribution and the easiest way of doing that was for Opencast's Karaf features to require the bundles. That is why `pax-logging-log4j2` will automatically be started when starting any of Opencast's Karaf features, automatically mitigating the replacement error. The only side-effect was that the logger's start level was slightly higher than before. In practice, that meant that logging would start about a second later. This patch now ensures the start level again drops to `8` and no one gets confused about why we have `pax-logging-api` twice in the `startup.properties`.
-
- 20 Dec, 2021 3 commits
-
-
Greg Logan authored
-
Greg Logan authored
Update Debian install documentation
-
Greg Logan authored
-
- 19 Dec, 2021 2 commits
-
-
Matthias Neugebauer authored
* upstream/r/10.x: Remove logging-1.11.6 from distributions Update to Pax Logging 1.11.12 Opencast 10.8 Release Notes
-
Greg Logan authored
Pull request #3283 Opencast 10.8 Release Notes
-