This is an automated email from the ASF dual-hosted git repository.
struberg pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/deltaspike.git
The following commit(s) were added to refs/heads/master by this push:
new 4596c6251 DELTASPIKE-1478 fix svnpub URL and docs
4596c6251 is described below
commit 4596c6251b7aaaa58e9e3fff927d99da585e32ad
Author: Mark Struberg <[email protected]>
AuthorDate: Thu Apr 10 08:01:20 2025 +0200
DELTASPIKE-1478 fix svnpub URL and docs
---
deltaspike/pom.xml | 2 +-
documentation/pom.xml | 3 +--
documentation/src/main/asciidoc/overview.adoc | 20 +++++++-------------
pom.xml | 24 +-----------------------
site/pom.xml | 3 +--
site/src/main/asciidoc/index.adoc | 5 ++---
6 files changed, 13 insertions(+), 44 deletions(-)
diff --git a/deltaspike/pom.xml b/deltaspike/pom.xml
index cd9d06de5..74f3bcb6b 100644
--- a/deltaspike/pom.xml
+++ b/deltaspike/pom.xml
@@ -64,7 +64,7 @@
<url>http://deltaspike.apache.org</url>
<properties>
-
<svn.scmPubUrl>https://svn.apache.org/repos/asf/deltaspike/site/trunk/content/javadoc/${project.version}</svn.scmPubUrl>
+
<svn.scmPubUrl>https://svn.apache.org/repos/infra/sites/deltaspike/javadoc/${project.version}</svn.scmPubUrl>
</properties>
<modules>
diff --git a/documentation/pom.xml b/documentation/pom.xml
index a5e6ca43d..8bb46e44e 100644
--- a/documentation/pom.xml
+++ b/documentation/pom.xml
@@ -38,8 +38,7 @@
<url>http://deltaspike.apache.org/documentation</url>
<properties>
-
<svn.scmPubUrl>https://svn.apache.org/repos/asf/deltaspike/site/trunk/content/documentation/</svn.scmPubUrl>
-
<svn.scmPubUrlStaging>https://svn.apache.org/repos/asf/deltaspike/site/trunk/content/staging/documentation/</svn.scmPubUrlStaging>
+
<svn.scmPubUrl>https://svn.apache.org/repos/infra/sites/deltaspike/documentation/</svn.scmPubUrl>
</properties>
<build>
diff --git a/documentation/src/main/asciidoc/overview.adoc
b/documentation/src/main/asciidoc/overview.adoc
index cd652aee6..5cbe2a01b 100644
--- a/documentation/src/main/asciidoc/overview.adoc
+++ b/documentation/src/main/asciidoc/overview.adoc
@@ -23,20 +23,17 @@ the most from this technology.
*Transactional support for non-EJB beans:* The Transactional Interceptor in
DeltaSpike paved the way for
`@Transactional` in Java EE 7.
-
-*Injectable Servlet objects:* Enables CDI injection in Servlets in Java EE
6/CDI 1.0 environments
+Although we not only support JTA transactions but also resource local
transactions and use a slightly different Exception handling.
*Injectable resources:* Configuration, resource bundles,... are easy to inject
when using CDI and Apache DeltaSpike.
*@Exclude annotation:* Lets you prevent classes from being treated as CDI
beans even if they are in a CDI-enabled
-archive in a Java EE 6/CDI 1.0 environment where `@Vetoed` is unavailable or
when you need to veto based on
-ProjectStages or expressions.
-
-*Scheduling tasks*: Async processes in a non-EE7 environment.
+archive in a Jakarta EE project.
+You can even exclude classes based on ProjectStages or configuration
expressions.
-*Bean Validation integration:* Injection of CDI beans and EJBs into Constraint
Validators.
+*Scheduling tasks*: handle Async processes in a non-JakartaEE environment.
-*BeanProvider:* Access the BeanManager and CDI beans even in non-managed
classes like JPA 2.0 EntityListeners or
+*BeanProvider:* Easy Access to the BeanManager and CDI beans even in
non-managed classes like JPA 2.0 EntityListeners or
Spring Beans.
@@ -50,8 +47,6 @@ provides a more solid navigation in case of JSF and helps a
lot in the maintenan
*View-Controller:* Based on type-safe view-configs, view-controller
annotations provide a type-safe alternative to
standard tags.
-*Injection in Converters and Validators:* Inject CDI beans and EJBs into JSF
Converters and Validators.
-
*JSF event broadcasting to CDI:* Allows CDI to be notified about JSF events
=== Productivity Improvements
@@ -64,8 +59,6 @@ standard tags.
*Data Module:* An out of the box entity framework solution complete with
support for container or application managed persistence contexts, as well as
JDBC.
-*Decoupled Exception handling:* Event-based exception handling framework,
similar to the CDI event observer mechanism.
-
*JMX integration:* Any CDI bean can be exposed via JMX easily with a single
annotation.
*Type-safe i18n messages:* Localized messages are easy to use with an
interface and a resource bundle, no more boilerplate and your messages now have
context within the code.
@@ -77,7 +70,8 @@ approach which can be used in CDI-based applications.
=== CDI
Java Contexts and Dependency Injection for the Java EE platform
(link:https://jcp.org/en/jsr/detail?id=299[JSR 299]),
- abbreviated _CDI_ was introduced as part of Java EE 6. The core features of
CDI are as follows:
+ abbreviated _CDI_ was introduced as part of Java EE 6 and is now part of
Jakarta Enterprise.
+The core features of CDI are as follows:
* improved stateful object lifecycles with an additional context named
_Conversation_ that encompasses a series of requests within one session and
lifecycle management by the container according to well-defined contexts
* dependency injection conducted in a type-safe manner, with type checking
conducted at compilation time so errors are exposed earlier and debugging is
easier
diff --git a/pom.xml b/pom.xml
index 696dc0453..c4b72ef32 100644
--- a/pom.xml
+++ b/pom.xml
@@ -48,7 +48,7 @@
<url>http://deltaspike.apache.org</url>
<properties>
- <asciidoctor.version>1.5.2</asciidoctor.version>
+ <asciidoctor.version>1.5.8</asciidoctor.version>
<version.deltaspike.latest.stable>2.0.0</version.deltaspike.latest.stable>
<version.deltaspike.latest.snapshot>2.0.1-SNAPSHOT</version.deltaspike.latest.snapshot>
<svn.scmPubCheckoutDirectory>${project.build.directory}/co-site</svn.scmPubCheckoutDirectory>
@@ -141,26 +141,4 @@
</plugins>
</build>
- <profiles>
- <profile>
- <!-- Profile used to publish documentation and site under staging
- folder. -->
- <id>staging</id>
- <build>
- <pluginManagement>
- <plugins>
- <plugin>
- <groupId>org.apache.maven.plugins</groupId>
- <artifactId>maven-scm-publish-plugin</artifactId>
- <version>1.1</version>
- <configuration>
-
<pubScmUrl>scm:svn:${svn.scmPubUrlStaging}</pubScmUrl>
- </configuration>
- </plugin>
- </plugins>
- </pluginManagement>
- </build>
- </profile>
- </profiles>
-
</project>
diff --git a/site/pom.xml b/site/pom.xml
index a92549ead..a61ba935e 100644
--- a/site/pom.xml
+++ b/site/pom.xml
@@ -38,8 +38,7 @@
<url>http://deltaspike.apache.org</url>
<properties>
-
<svn.scmPubUrl>https://svn.apache.org/repos/asf/deltaspike/site/trunk/content/</svn.scmPubUrl>
-
<svn.scmPubUrlStaging>https://svn.apache.org/repos/asf/deltaspike/site/trunk/content/staging/</svn.scmPubUrlStaging>
+
<svn.scmPubUrl>https://svn.apache.org/repos/infra/sites/deltaspike/</svn.scmPubUrl>
</properties>
<build>
diff --git a/site/src/main/asciidoc/index.adoc
b/site/src/main/asciidoc/index.adoc
index 9613be42c..a24bf2b03 100644
--- a/site/src/main/asciidoc/index.adoc
+++ b/site/src/main/asciidoc/index.adoc
@@ -10,8 +10,7 @@ useful features for Java application developers.
We will also ensure true portability! We are testing DeltaSpike on
different CDI implementations like Apache OpenWebBeans and JBoss Weld,
and also on different Java EE servers like Apache Tomcat and TomEE,
-JBoss AS7, WildFly 8.x and 9.x, Oracle GlassFish 3.1+ and 4.x+, IBM
-WebSphere 8.x, Oracle WebLogic Server 12c, Jetty, and others.
+JBoss Enterprise, WildFly, GlassFish, Liberty, Oracle WebLogic and others.
link:documentation/overview.html[View details »]
|===
@@ -36,7 +35,7 @@ link:/documentation/modules.html[View details »]
[options="header,footer"]
|===
|*News* | *Examples*
-| Apache DeltaSpike 1.9.3 is now out!
+| Apache DeltaSpike 2.0.0 supporting JakartaEE is now out!
link:/news.html[View details »]
