[ http://issues.apache.org/jira/browse/MYFACES-134?page=comments#action_66089 ] Matthias Weßendorf commented on MYFACES-134: --------------------------------------------
thanks Sean, I know that drama ;) I'll refactor that component using Jakarta Commons Feedparser and place it in Sandbox (MyFAces sandbox) instead. -mw > commons-digester 1.6 & myfaces-extension don't work together due to rss > ----------------------------------------------------------------------- > > Key: MYFACES-134 > URL: http://issues.apache.org/jira/browse/MYFACES-134 > Project: MyFaces > Type: Bug > Versions: 1.0.9 beta > Reporter: Hal Deadman > Assignee: Matthias Weßendorf > > Myfaces-extensions.jar depends on some org.apache.commons.digester.rss.* > files in commons-digester-1.5.jar that are no longer part of the binary > distribution in commons-digester-1.6.jar. Not sure how you want to resolve > that but I don't think everyone that wants to use myfaces-extensions.jar will > have to choose between switching to commons-digester 1.5 and compiling their > own jar with the digester.rss code or making their own myfaces-extension.jar. > Maybe that myfaces rss component should live in its own jar since it depends > on example code? > This is from the 1.6 release notes: > RSS Support > ----------- > The RSS package present in previous distributions of Digester was only ever > intended to be a "worked example", so the code has been moved to the > "src/examples/api/rss" directory within the CVS repository, and is no longer > part of the standard Digester binary distribution. However the same package > structure has been preserved, so any users who were using the rss code in > production should just have to compile the example code and include that > additional jar in the classpath. These classes are still contained in the > source distribution and so (for those for which such things > matter) > are still officially released (though no longer distributed in the binary). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
