If you refactor a class and then do a build, the source file is compiled at its new package and name, but the old .class file is left behind until your do a make clean. TestNG then picks up both .class files. Eclipse, on the other hand, is smarter about cleaning out the bin folder after such a change.
On 1/7/07, Kent Tong <[EMAIL PROTECTED]> wrote:
Howard Lewis Ship <hlship <at> gmail.com> writes: > False alarm ... after clean it worked. My bad ... should have done that > earlier. Any idea why this is even necessary? I've been bitten by this several times. The .java file is updated but maven fails to update the .class file. -- Kent Tong Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
