| Does not match outer scope rule error [message #541231] |
Fri, 18 June 2010 19:00 |
 Benson Ning
Messages: 14
Registered: July 2009 |
Junior Member |
|
|
Hi,
Recently I created a Job which contains some code for creating a Java search scope, in order to make sure the jobs I created to be run one by one, I set my own rule to each job. when I ran the job, I got "Attempted to beginRule: P/, does not match outer scope rule: xxx" error, I guess the error is because that when creating the java search scope, the JDT code creates a separate Job to resolve the classpath and assigns a project rule ("P/") to it, since this job is being run within my job, 2 rules don't match and causes the error. My question is if this is by design, does that mean before we set our own rule to the jobs, we have to really CARE about the job-run implementation code to make sure there is no sub-job will be created with a "conflict" rule? Is there an easy way for doing that? or an easy way to prevent that? Thanks for your time.
|
|
|
Powered by
FUDForum. Page generated in 0.02409 seconds
] 
Search
Help
Register
Login
Home
