there are two different versions of the XML processing library (Stax2 / Woodstox).

[Interfud]

Title: Docker image 1.6.0 crash: NoSuchMethodError in org.codehaus.stax2.ri.EmptyIterator
Text: Context startup failed due to BeanCreationException: Error creating bean with name 'sessionFactory'... nested exception is java.lang.NoSuchMethodError: 'org.codehaus.stax2.ri.EmptyIterator org.codehaus.stax2.ri.EmptyIterator.getInstance()'

[kwoot]

Thank you for bringing this to our attention. After June 8th I have time to look into this.

[90rk1]

Fixed error by downloading the file
wget https://repo1.maven.org/maven2/org/codehaus/woodstox/stax2-api/4.2.1/stax2-api-4.2.1.jar -O ./patches/stax2-api-4.2.1.jar
and then mounting it into container.
like this:

volumes:
      - libreplan_data:/opt/libreplan/data
      - ./patches/stax2-api-4.2.1.jar:/usr/local/tomcat/webapps/ROOT/WEB-INF/lib/stax2-api-4.2.1.jar

Now, I don't see any errors in docker container logs, BUT the app still does not working.
at localhost:8080 I see 404.

my docker-compose file:

services:
  libreplan-db:
    image: postgres:18
    container_name: libreplan-db
    restart: unless-stopped
    environment:
      POSTGRES_USER: ${DB_USER}
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_DB: ${DB_NAME}
    volumes:
      - pg_data:/var/lib/postgresql/18/docker/
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"
    deploy:
      resources:
        limits:
          cpus: '1.0'
          memory: 1024M
        reservations:
          memory: 256M
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB"]
      interval: 10s
      timeout: 5s
      retries: 5
      start_period: 15s

  libreplan:
    image: libreplan/libreplan:1.6.0
    container_name: libreplan-app
    restart: unless-stopped
    ports:
      - "${APP_PORT}:8080"
    environment:
      - DB_ENGINE=postgresql
      - DB_HOST=${DB_HOST}
      - DB_PORT=${DB_PORT}
      - DB_NAME=${DB_NAME}
      - DB_USER=${DB_USER}
      - DB_PASS=${DB_PASSWORD}
    depends_on:
      libreplan-db:
        condition: service_healthy
    volumes:
      - libreplan_data:/opt/libreplan/data
      - ./patches/stax2-api-4.2.1.jar:/usr/local/tomcat/webapps/ROOT/WEB-INF/lib/stax2-api-4.2.1.jar
    logging:
      driver: json-file
      options:
        max-size: "10m"
        max-file: "3"
    deploy:
      resources:
        limits:
          cpus: '1.5'
          memory: 2048M 
        reservations:
          memory: 512M


volumes:
  pg_data:
  libreplan_data:

[Interfud]

debian 13

TECHNICAL REPORT: XML PARSER CONFLICT ON JAVA 21 / TOMCAT 9

1. PROBLEM DESCRIPTION
   When building LibrePlan 1.6.0 with the localization profile enabled (-P i18n) on Java 21 using Tomcat 9, the application compiles successfully but crashes during Spring context initialization (LocalSessionFactoryBean).

The following exception is thrown in catalina.out:
"Caused by: java.lang.NoSuchMethodError: 'org.codehaus.stax2.ri.EmptyIterator org.codehaus.stax2.ri.EmptyIterator.getInstance()'"

2. ROOT CAUSE
   When the "-P i18n" profile is activated, the gettext-maven-plugin (or its transitive dependencies) pulls an obsolete XML parser library, "woodstox-core-asl-4.4.1.jar", into the final web archive.

Since the project explicitly declares a modern version ("woodstox-core-6.4.0.jar"), BOTH JAR files end up inside the "/WEB-INF/lib/" directory. This classpath duplication results in Class Shadowing, causing Hibernate to invoke a method from stax2-api that does not exist in the legacy 4.4.1 release.

3. REQUIRED FIXES IN POM.XML FILES
   FIX A: Update the build block in "libreplan-webapp/pom.xml"
   We must wrap the war plugin inside proper "" tags, upgrade its version to 3.4.0 for Java 21 compatibility, and add the exclusion rule.

Locate the "" block near the bottom of the file and replace it exactly with this text:

<build>
    <finalName>libreplan-webapp</finalName>
    <testResources>
        <testResource>
            <directory>src/test/resources</directory>
            <filtering>true</filtering>
        </testResource>
    </testResources>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-war-plugin</artifactId>
            <version>3.4.0</version>
            <configuration>
                <packagingExcludes>WEB-INF/lib/woodstox-core-asl-*.jar</packagingExcludes>
                <archive>
                    <manifest>
                        <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
                    </manifest>
                </archive>
            </configuration>
        </plugin>
    </plugins>
</build>

FIX B: Optimize the localization profile in "libreplan-webapp/pom.xml"
To optimize build times and stop fetching redundant transitive dependencies from unused languages, restrict the gettext plugin using the "" tag.

Find the "i18n" profile and ensure the plugin looks exactly like this:

                <plugin>
                    <groupId>com.googlecode.gettext-commons</groupId>
                    <artifactId>gettext-maven-plugin</artifactId>
                    <configuration>
                        <targetBundle>i18n.Messages</targetBundle>
                        <poDirectory>${project.build.sourceDirectory}/../resources/i18n</poDirectory>
                        <keys>
                            <key>ru</key>
                        </keys>
                    </configuration>
                    <executions>
                        <execution>
                            <id>dist</id>
                            <phase>generate-resources</phase>
                            <goals>
                                <goal>dist</goal>
                            </goals>
                        </execution>
                    </executions>
                </plugin>

FIX C: Add a safety net to the Root "pom.xml"
To prevent other submodules from packing the wrong artifact, declare the old coordinate under the global "" element with a "provided" scope:

<dependency>
        <groupId>com.fasterxml.woodstox</groupId>
        <artifactId>woodstox-core-asl</artifactId>
        <version>4.4.1</version>
        <scope>provided</scope>
 </dependency>

4. CURRENT STATUS
   With these structural fixes applied, the project compiles cleanly using the standard command:
   "mvn clean install -P reports,userguide,i18n -DskipTests -Dliquibase.skip=true"

The deployment directory inside Tomcat 9 ("/WEB-INF/lib/") now correctly contains ONLY ONE clean engine instance: "woodstox-core-6.4.0.jar". The Spring application context and Hibernate schemas initialize flawlessly, rendering a fully localized, stable UI.

[kwoot]

Would be great if people who responded to this issue earlier can retest the code.
If all is well, I can get 1.6.1 out the door.

[90rk1]

It was a bit challenging to build and run project. I was able to run project (Intellij Idea, JDK11, Tomcat 9) with a few tweaks and it works.

But I wasn't able to build libreplan-webapp.war properly (failing tests, tweaks with configs, like bumping the version of maven-war-plugin to 3.3.2, also I had to set validate instead of ${hibernate.hbm2ddl.auto}). I am not really familiar with Java ecosystem.

Anyway, it works.

@kwoot Could you please share, how do you build docker container?

[sanbor]

Hi @90rk1. The file HACKING.rst contains instructions of how build the project. I ran mvn clean install and it worked.

In HACKING.rst it mentions you might want to reset the database content to avoid issues with database migrations (when using docker compose for the DB you can do docker compose down --volumes).

Here are AI generated instructions for building the project:

 # from the repo root
  git clone https://github.com/LibrePlan/libreplan.git
  cd libreplan

  # 1. Wipe any previous Postgres volume (avoids Liquibase checksum mismatches
  #    if you've built before — safe to run even on a fresh checkout)
  docker compose down --volumes

  # 2. Start PostgreSQL — this creates both `libreplandev` and `libreplandevtest`
  #    (libreplandevtest is created by init.sql, mounted in docker-compose.yaml)
  docker compose up -d

  # 3. Wait until Postgres is ready
  until docker exec libreplan-db-1 pg_isready -U libreplan >/dev/null 2>&1; do sleep 1; done

  # 4. Sanity-check both databases exist
  docker exec libreplan-db-1 psql -U libreplan -lqt | cut -d\| -f1 | grep -E 'libreplandev(test)?'

  # 5. Build the WAR — same command CI runs. This is a multi-module reactor build:
  #    libreplan-business → ganttzk → libreplan-webapp. The WAR is produced in
  #    the last step. Run from the repo root, NOT from libreplan-webapp/, so the
  #    sibling modules are built first.
  mvn -Ddefault.passwordsControl=false -Ddefault.exampleUsersDisabled=false clean install

  # 6. Verify the WAR was produced
  ls -lh libreplan-webapp/target/libreplan-webapp.war

  You should end up with libreplan-webapp/target/libreplan-webapp.war (~150 MB).

[90rk1]

@sanbor nvm, got everything from forgejo workflows.

mvn clean install --no-transfer-progress -Ddefault.passwordsControl=false -Ddefault.exampleUsersDisabled=false -DdataSource.url=jdbc:postgresql://postgres:5432/libreplandev -DdataSource.user=libreplan -DdataSource.password=libreplan -DjdbcDriver.className=org.postgresql.Driver

the libreplan-webapp.war in result was working.

[kwoot]

This should now we fixed.