Resolved in r1900112.
I created both the overlay configurations for Ant and Maven.
Il giorno gio 21 apr 2022 alle ore 13:04 Karl Wright
ha scritto:
> Sounds like a good idea.
> One suggestion: I would not structure the ant logic to overwrite the war.
> I would download one copy and then
Sounds like a good idea.
One suggestion: I would not structure the ant logic to overwrite the war.
I would download one copy and then transfer/create a different copy. Ant
works best that way. So no deletion of the original download.
On Thu, Apr 21, 2022 at 6:59 AM Piergiorgio Lucidi
wrote:
>
I'm going to patch the the WAR file in the download-dependencies task in
Ant :-P
I'll use the download-via-maven for downloading all the libraries to
update, then unzip, delete and the jar task, so it should be enough, what
do you think?
PJ
Il giorno gio 21 apr 2022 alle ore 12:49 Karl Wright
ha
Right now the war is downloaded via ant, I think. We should "patch" it
when we download it, by unpacking, updating, and repacking. We leave it in
a specific place and I don't believe the pom.xml refers to it directly.
If you can confirm that picture, I can suggest ant commands to do the
unpack
Ok I solved the classloading issue :)
I found all the dependencies that we have to update in the OpenCMIS Server
WAR, practically we have to:
1. Update log4j from 2.6.1 to 2.17.2
2. Update CXF from 3.0.12 to 3.5.2
3. Add activation-1.1.1.jar
4. Add jaxws-api-2.3.1.jar
Here the list of
Ok, maybe there's a conflict then. We cannot back out versions of CXF
because we use that for the Livelink connector now.
On Thu, Apr 21, 2022 at 6:20 AM Piergiorgio Lucidi
wrote:
> Sure, I'm investigating the OpenCMIS Server issue, I resolved the Log4j
> issue updating the jar in the WAR but
Sure, I'm investigating the OpenCMIS Server issue, I resolved the Log4j
issue updating the jar in the WAR but now I see a problem with CXF old
dependencies.
The strange thing is that using the same patched WAR in a standard Docker
container based on OpenJDK 11 it works perfectly but trying to use
I can fix the bad pom but not the CMIS issue, which will require more
research.
Karl
On Thu, Apr 21, 2022 at 5:54 AM Piergiorgio Lucidi
wrote:
> Hi Karl,
>
> -1 from me because I found these problems:
>
> 1. Trying to build with Maven I see the following error:
>
> The build could not read 1
