We're pleased to announce that 3.1.0.Beta2 of Portlet Bridge is now available!
Maven coordinates:
For a JSF2 only portlet:
<dependency>
<groupId>org.jboss.portletbridge</groupId>
<artifactId>portletbridge-api</artifactId>
<version>3.1.0.Beta2</version>
</dependency>
<dependency>
<groupId>org.jboss.portletbridge</groupId>
<artifactId>portletbridge-impl</artifactId>
<version>3.1.0.Beta2</version>
<scope>runtime</scope>
</dependency>
For a RichFaces 4 portlet you need the above as well as:
<dependency>
<groupId>org.jboss.portletbridge</groupId>
<artifactId>portletbridge-extension-richfaces</artifactId>
<version>3.1.0.Beta2</version>
<scope>runtime</scope>
</dependency>
Depchain POMs
As part of this release we split out any RichFaces 4 specific code into it's own module to enable cleaner separation of concerns in the code. So to make things simpler now that we have three separate dependencies if you're writing a RichFaces 4 portlet we've also introduced a depchain for JSF2 and RichFaces 4 dependencies.
For a JSF2 portlet the depchain you need is:
<dependency>
<groupId>org.jboss.portletbridge</groupId>
<artifactId>jsf2-depchain</artifactId>
<version>3.1.0.Beta2</version>
</dependency>
For a RichFaces 4 portlet the depchain you need is:
<dependency>
<groupId>org.jboss.portletbridge</groupId>
<artifactId>richfaces4-depchain</artifactId>
<version>3.1.0.Beta2</version>
</dependency>
Keeping up with the latest
One of the best ways to hear about the latest releases and changes with JBoss Portlet Bridge is to follow us on Twitter (@portletbridge).
Don't be a stranger
As always, if you have any questions about or issues with JBoss Portlet Bridge, please .