what i'm thinking is this:
if your project root is
x:\\Inetpub\iwsroot\cfusion.war\interact\onlinePayments\_extensions\com,
then you should be able to go into project properties and set the
"component root" value to "com". the plugin will then evaluate the
path to your tests as "com.IWSManagerTest"
or, if that's not right, if the component path as CF sees it is
interact.onlinePayments._extensions.com.IWSManagerTest", then you
could set the project component root property to
"interact.onlinePayments._extensions.com and then the plugin should
resolve it correctly.
marc
?
Marc
dammit man, you found the scenario that one or two other people
found that we knew would be a problem: where you dont' want to use the
"webroot" preference but you need the "component path" project
property to be "empty".
right now, your project is at L:\cfusion.war\interact\onlinePayments,
and if you put that property to "_extensions", it'll create paths like
"_extensions._extensions", which is bad.
now, there is an "easy" way to deal with this, although it's not
ideal. I dont know if you will mind doing htis or not:
1) set the project property for component root to "onlinePayments"
2) add a mapping into cf for onlinePayments =
L:\cfusion.war\interact\onlinePayments
this way, the plugin will resolve the components as
"onlinePayments._extensions", and cf will understand that path.
sorry for the problems bro. It's a known problem... an "edge" case,
but a problem nonetheless.
marc
best,
marc