changes.txt and eula update

README.md

@@ -34,7 +34,7 @@ _**Documentation:**_
 - [Functions Reference](https://jasperreports.sourceforge.net/function.reference.html)
 - [FAQ](http://community.jaspersoft.com/wiki/jasperreports-library-faqs)
 - [API (Javadoc)](https://jasperreports.sourceforge.net/api/index.html)
-- [Discussion Forums](https://community.jaspersoft.com/project/jasperreports-library/answers)
+- [Discussion Forums](https://community.jaspersoft.com/forums/)
 
 _**Older resources:**_
 
@@ -99,7 +99,7 @@ Building the core and extensions JAR artifacts having local non-committed Git mo
 From time to time, verifying that the core and extensions artifacts are still compatible with JDK version 1.8 is needed and this is done by turning on the enforcer plugin
 while building these artifacts:
 
-    mvn clean install -Denforcer.skip
+    mvn clean install -Denforcer.skip=false -pl '!ext/ejbql, !ext/hibernate, !ext/servlets'
 
 The project has a separate artifact for tests under the `/tests`, which can be run using the following command:
 

changes.txt

@@ -2,6 +2,18 @@
 JasperReports Library Change Log
 =============================================
 
+JasperReports 7.0.1 (2024-09-30)
+---------------------------------------------
+
+- added automatic module names to manifest files and fixed split packages issues in preparation for 
+Java 9 modules compliance; 
+
+- minor bug fixes and improvements;
+
+
+
+
+
 JasperReports 7.0.0 (2024-06-17)
 ---------------------------------------------
 

docs/pom.xml

@@ -58,9 +58,7 @@
 				<version>${xml-maven-plugin.version}</version>
 				<executions>
 					<execution>
-						<goals>
-							<goal>transform</goal>
-						</goals>
+						<phase>NO_PHASE</phase><!-- inhibit plugin with phase that does not exist-->
 					</execution>
 				</executions>
 				<configuration>