Hello Eugene, I've just created a JIRA issue </> for this.
Regards, Stevo. On Sat, Sep 20, 2008 at 8:47 PM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote: > Stevo, > > I read your email about 5 times but couldn't follow your description. If > you are convinced there is a bug, please create simple test projects that > would allow us to reproduce it and submit it along with a bug report into > the project issue tracker. It would be great if you could isolate any > non-standard Eclipse plugins from your issue, eg. try to reproduce it with > regular JUnit tests. > See some hints on the wiki at > http://docs.codehaus.org/display/M2ECLIPSE/Reporting+Issues > > Thanks > > Eugene > > > Stevo Slavić wrote: > >> Hello all, >> >> Recently I've encountered a problem with a Spring TestNG integration test, >> it would successfully run from TestNG plugin, while it would fail when run >> in maven. I've wrote < >> http://mail-archives.apache.org/mod_mbox/maven-users/200809.mbox/[EMAIL >> PROTECTED]> >> about this to maven users list, but later I've found myself where the >> problem was - test was referencing a resource (spring context) as classpath >> resource which on the other hand was present but among test resources of >> another module, of the same multimodule project. Module where the >> integration test is, has dependency defined on that other module with >> context file, but as the context file is in test resources of the referenced >> module, it should not be in the classpath of the referencing module. So, my >> conclusion is that m2eclipse plugin has a bug (wrongly added dependant >> module test resources to the classpath to the depending module) which made >> that resource available as classpath resource to the test when it is run >> from the TestNG eclipse plugin. Other, in my opinion, less likely >> possibility is that the TestNG eclipse plugin (or maybe even Spring >> context/resource loader) has a bug so it is able to access non classpath >> resources as classpath resources. >> >> I'd appreciate if someone from m2eclipse development team can check this >> out, and if it is a bug, please fix it. >> >> Regards, >> Stevo. >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
