Manfred, You still need to take action on this.
Nothing has changed on this issue except the url. It's been 18 months. Since the code is in myfaces-shared, I'm guessing it affects both MyFaces Core and Tomahawk. There's some other stuff in Tomahawk now that might qualify it too, but I haven't evaluated it. On Tue, Feb 20, 2007 at 10:52 PM, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > Does this help? > > #Generated by Maven > #Thu Apr 13 14:18:08 EDT 2006 > version=2.0.0 > groupId=org.apache.myfaces.shared > artifactId=myfaces-shared-impl > > So perhaps the change that needs to be made is to have it say > "myfaces-shared 2.0" rather than simply "2.0"? > > http://www.apache.org/licenses/exports/ > > On 2/20/07, Dennis Byrne <[EMAIL PROTECTED]> wrote: >> >> I'm not sure why 2.0 is there. Perhaps I was thinking the version of the >> shared lib. Anyone know which version of the shared lib we had when >> encryption was brought in? >> >> Dennis Byrne >> >> >> On 2/20/07, Mike Kienenberger <[EMAIL PROTECTED]> wrote: >> > Manfred, >> > >> > The crypto page contains the incorrect version numbers for MyFaces. >> > >> > Apache MyFaces Project >> > Product Name Versions ECCN Controlled Source >> > Apache MyFaces development 5D002 ASF >> > 2.0 and later 5D002 ASF >> > >> > I'm not sure where "2.0" came into this, but we started allowing >> > cryptography as of Myfaces version 1.1.2. See >> > http://issues.apache.org/jira/browse/MYFACES-742 for >> details. >> > >> > As pmc-chair, you should have the karma to update this page according >> > the instructions at this url: >> > >> > http://www.apache.org/dev/crypto.html#sources >> > >> >> >> >> -- >> Dennis Byrne >
