mraible wrote:
Now I'm having issues resolving resources in the project that's running my
plugin. Specifically, I'm unable to resolve Spring context files from the
local project.
I haven't any knowledge about Spring. Therefore I can only suggest you try
to narrow the set of possible causes. Try to load the resource directly from
your class loader and see if it's properly setup, i.e.
getClassLoader().getResource("mock-services.xml")
should be non-null. If it's null, fix your class loader setup. It it's
non-null, find yourself some Spring guru ;-) or use your favorite debugger
to step through Spring and see what's going wrong.
<contextPaths>file://${basedir}/src/test/resources/mock-services.xml
Note that this is kind of dangerous: First, ${basedir} might contain spaces
or other characters that are illegal in a URL. Second, there is no single
platform-independent concatenation of "file:" and "${basedir}" that delivers
a proper URL. For instance, for a Win-like basedir "C:/foo/bar" you would
get file://C:/foo/bar" where the drive part "C:" would be intepreted as a
host name. Depending on the RFC-compliance of the consumer, such URLs will
be rejected (e.g. java.net.URI will do). Compare [0].
Benjamin
[0] http://blogs.msdn.com/ie/archive/2006/12/06/file-uris-in-windows.aspx
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
