On 9/8/05, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > From: "Craig McClanahan" <[EMAIL PROTECTED]> > > > This one is likely to become a non-issue, now that MyFaces 1.0.10 is > out. > > My understanding is that the MyFaces folks are eliminating the > requirement > > for registering a listener explicity, which will mean that Shale can > dump > > this particular bit of bit-twiddling. > > There's no 1.0.10 release yet, but I'm working with the MyFaces 20050904 > nightly and the Listener is no longer required in web.xml. > > > We'll still have to deal with the fact that the external dependencies > > differ between the RI and MyFaces versions, but that should be, > > I hope, simpler to deal with. > > Are you talking about myfaces-extensions.jar here, or something else? That > was renamed tomahawk.jar and is not necessary unless you want to use the > extensions, (additional components?) which Shale does not.
I was talking about the other JAR files that MyFaces ships in its lib directory, like commons-el.jar and commons-codec-1.2.jar, which MyFaces needs but the RI doesn't. That doesn't matter for compiling (unless the app wants to use one of those apis directly), but it matters when you are assembling a war's WEB-INF/lib directory. Craig I have the Maven build working in a separate directory structure as James > suggested, and can reproduce all of the artifacts from the Ant build. > (Finally!) I just need to get it to see the xdocs for the website, which > should be a property or two, and look again at the .zip/.tar.gz files in > "dist" to see what it's putting in those. Then if all goes well I'll check > in the changes this weekend. > > Maven2 promises to make things easier with "profiles" for different sets > of > dependencies, though I haven't had a chance to try it yet. > > -- > Wendy > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
