On 9/14/06, Paul Spencer <[EMAIL PROTECTED]> wrote:
Which version of MyFaces should be used for testing, 1.1.1 or 1.1.3?
My understanding was that 1.1.3 had some fatal bugs, so I've been sticking with 1.1.1 until 1.1.4 finally gets out the door. A note needs to be added in the "release procedure" to update the
MyFaces version number when appropriate.
Yah ... it won't be just tweaking the version numbers, either. It seems prudent to go in and examine the transitive dependencies hierarchy again when you change the version on something with this many dependencies of its own, to make sure that the exclude lists are correct. That was a *real* pain with the refactoring I did last night. Paul Spencer Craig Wendy Smoak wrote:
> On 9/14/06, Gary VanMatre <[EMAIL PROTECTED]> wrote: > >> This test is building the component tree and rendering the output. >> The output is parsed and checked for an embed comment. >> Since the myfaces-impl is not a dependency, the renderers are >> not being loaded and no markup generated. >> >> I could create some mock renderers for this test. That would be >> much easier than starting a wrestling match with maven. > > Gary, if it's easier, you can add myfaces-impl as a dependency in test > scope. That won't affect projects using Clay, it will only be on the > classpath during the test phases. > > <dependency> > <groupId>myfaces</groupId> > <artifactId>myfaces-impl</artifactId> > <version>1.1.1</version> > <scope>test</scope> > </dependency> >
