Opened 16 years ago
Closed 16 years ago
#1315 closed defect (fixed)
A plug-in which uses 'execute immediately' can't get the current job from AbstractPlugin.getCurrentJob()
| Reported by: | Nicklas Nordborg | Owned by: | Nicklas Nordborg |
|---|---|---|---|
| Priority: | minor | Milestone: | BASE 2.12 |
| Component: | core | Version: | |
| Keywords: | Cc: |
Description
By looking at the code it seems like the job-id is set when the configuration wizard is started. Since this is before the job is started the id is unknown (=0). When the 'execute immediately' option is used the same plug-in instance is re-used which means that the job id is not updated. It is not a problem for jobs that are added to the job queue since everything is discarded and re-loaded from the database later when the job is about to be executed.
Workaround: Use job.getJob() instead.
Change History (2)
comment:1 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
(In [4941]) Fixes #1315: A plug-in which uses 'execute immediately' can't get the current job from AbstractPlugin.getCurrentJob()