I dug in a bit more, and actually, only one unit test fails, TestPropertiesConfiguration.testLoadViaPropertyWithBasePath2.
When I change the basepath's to use "src/test-resources": private String testBasePath2 = new File("src/test-resources").getAbsoluteFile().getParentFile().getAbsolutePath (); the resulting file is c:\java\cvs\jakarta-commons\configuration\src. I think this is wrong, becase I don't see how the unit test later would work.. I get a NPE, and it seem reasonable.. So, if no one has an object, I'd like to apply this change. All the unit tests (99.76%) pass. ERic > -----Original Message----- > From: Eric Pugh [mailto:[EMAIL PROTECTED] > Sent: Monday, October 25, 2004 12:10 PM > To: Commons-Dev > Subject: [configuration] Moving test resources to /src/test-resources > > > Hi all, > > I am using the updated Maven Eclipse plugin, and one of the difficulties > that arises is that Eclipse (and therefore Maven) want each directory, if > included as resources on Eclipse's classpath, to be different. Right now, > in configuration we include the /conf directory a ton of times. > > What I want to do is bring [configuration] into line with other > mavenenized > projects where test resources are all in /src/test-resources. And the jar > resources would remain in /conf. Basically just digesterRules.xml. > > However, when I started this, I ran into a couple unit test failures. > Should I do this, and then fix the errors? I have a bunch of questions > about some of the new tests that would be better answered if I > could commit > the changes... > > Eric > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]