From 1e988929fcb5a9856906d28d99d5e1531f894631 Mon Sep 17 00:00:00 2001 From: Keith Donald Date: Tue, 13 May 2008 06:57:25 +0000 Subject: [PATCH] maven central --- build-spring-webflow/resources/changelog.txt | 3 +- spring-webflow-reference/src/overview.xml | 49 ++++++++++++++++++-- 2 files changed, 47 insertions(+), 5 deletions(-) diff --git a/build-spring-webflow/resources/changelog.txt b/build-spring-webflow/resources/changelog.txt index 1ed3958f..d0c0bbda 100644 --- a/build-spring-webflow/resources/changelog.txt +++ b/build-spring-webflow/resources/changelog.txt @@ -27,10 +27,11 @@ Bug Fixes This bug fix required a change to how currentEvent attributes are accessed with EL: instead of accessing an event attribute directly like ${currentEvent.attr}, access an attribute through the 'attributes' property like ${currentEvent.attributes.attr}. The reference documentation was updated to reflect this change. * Fixed a bug resulting in loss of JSF ExternalContext state during execution of the JSF Lifecycle. - This bug was affecting integration of the Trindad component library, which requires a special Response object to be set for its Ajax support to work. + This bug was effecting integration of the Trindad component library, which requires a special Response object to be set for its Ajax support to work. Documentation * Added documentation on FlowHandler and externalRedirect: redirect prefixes. +* Added documentation on accessing Web Flow artifacts from Maven Central. * Clarified the conversation-scoped and view-state managed persistence context patterns will be considered for implementation in future Web Flow releases. * Removed unnecessary note about special Spring MVC and JSF model binding semantics; the semantics should be equal between view technologies, even if the underlying technologies differ. diff --git a/spring-webflow-reference/src/overview.xml b/spring-webflow-reference/src/overview.xml index 7b0906b2..e68b5417 100644 --- a/spring-webflow-reference/src/overview.xml +++ b/spring-webflow-reference/src/overview.xml @@ -58,11 +58,10 @@ - How to obtain Web Flow artifacts from Maven or Ivy + How to obtain Web Flow artifacts from the SpringSource Bundle Repository - Each jar in the Web Flow distribution is available in the SpringSource Enterprise Bundle Repository. + Each jar in the Web Flow distribution is available in the SpringSource Enterprise Bundle Repository for use in an OSGi environment. These jars may be accessed using Maven or Ivy dependency managers. - Each jar is also an OSGI-compliant bundle. Accessing Web Flow with Maven @@ -157,6 +156,48 @@ rev="2.0.0.RELEASE" conf="compile->compile" /> ]]> - + + + + How to obtain Web Flow artifacts from Maven Central + + Each jar in the Web Flow distribution is also available in the Maven Central Repository. + The large majority of artifacts retrieved from this repository are not OSGi bundles. + If you wish to run your Web Flows in an OSGi environment, you are encouraged to use the SpringSource Bundle Repository. + + + To access Web Flow jars from Maven Central, declare the following dependencies in you pom: + + + org.springframework.webflow + org.springframework.binding + 2.0.0.RELEASE + + + + org.springframework.webflow + org.springframework.js + 2.0.0.RELEASE + + + + org.springframework.webflow + org.springframework.webflow + 2.0.0.RELEASE + +]]> + + + And if using JavaServerFaces: + + + org.springframework.webflow + org.springframework.faces + 2.0.0.RELEASE + +]]> + \ No newline at end of file