[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[tigerstripe-dev] FW: Issue: Unable to clear target directory
|
Title: Re: Issue: Unable to clear target directory
Hi Team,
One of the symptoms of this bug is that we can not
delete (manually, or when run doc generation plugin) volocity log file located
at folder target/tigerstripe.gen.
1. When the Velocity engine runs,
org.apache.log.format.Formatter not found (refer to attached
ts-documentation.velocity (error).log)
Reason:
a lib is
missing.
Action:
I add a missing lib (avalon-logkit-2.1.jar) to tigerstripe
workbench:
1. add
avalon-logkit-2.1.jar to
eclipse/plugins/org.eclipse.tigerstripe.workbench.base_0.4.6.v200905071426.jar/lib
2. update
org.eclipse.tigerstripe.workbench.base_0.4.6.v200905071426.jar/META-INF/MANIFEST.MF
In line 237, add "lib/avalon-logkit-2.1.jar"
Result:
1) Now the
exception disappears, and no other exception in velocity log
(ts-documentation.velocity.log). but the issue remains: still can not delete the
log file.
2) but the issue
remains: still can not delete the log file.
Remark:
2. Can not delete velocity log file
even when no related lib missed
We guess the senario is: When we run the
doc plugin for the first time, tigerstripe starts the velocity engine (please refer to
setClasspathLoaderForVelocity method, TemplateBasedRule.java class, tigerstipe workbench.base
plugin), velocity engine
constructs and writes a log file, and generates our pdf file. When we run the doc plugin
again, the engine still refers to the log file, so we cannot delete
it.
If so, a
possible fix is, in all cases or when we choose "Clear target
directory before generate", in tigerstripe workbench code, we should close the
velocity log file once we finished
generation job and create new log
file when we start a new
generation job.
best regards,
Jinzhai
张 晋寨 (ZHANG Jinzhai)
Global Delivery Application Services,
HP
+86 21 6081 3327
+86 139 1731 0846
la structure cachée dans
les choses mathématiques
Hi Zhang,
There is already a bug in Bugzilla
about this ( see https://bugs.eclipse.org/bugs/show_bug.cgi?id=251858
). Unfortunately, we’ve had trouble reproducing it, so we had to
downgrade.
I suggest we move the discussion to that bug or the mailing
list so we have that discussion publicly.
Is there anything specific that
you can think of that would have triggered that? Any
Hint?
Eric
On 5/19/09 1:12 AM, "Zhang, Jin-Zhai (TSG-GDCC-SH)"
<jinzhai.zhang@xxxxxx>
wrote:
Hi Eric,
Richard is not available until May 27th. Would
you please share some ideas on fixing this issue?
best regards,
Jinzhai
张 晋寨 (ZHANG Jinzhai)
Global
Delivery Application Services, HP
+86 21 6081 3327
+86 139 1731
0846
la structure cachée dans les choses mathématiques
From: Zhang,
Jin-Zhai (TSG-GDCC-SH)
Sent: 2009年5月19日 16:06
To:
'Richard Craddock (rcraddoc)'
Cc: Flauw, Marc; cgallen@xxxxxxxxxxx
Subject: Issue:
Unable to clear target directory
Hi Richard,
I'm playing a tigerstripe plugin
(tip doc plugin) with a tigerstripe project (TIP_Test_Model1) to generate PDF
doc. For the tigerstripe project, if I do not choose "Clear target directory
before generate", then the plugin works fine.
If I do choose "Clear target directory before generate" (as showd
below),
then with the new Tigerstripe.xml, I am doing 2 times of
generations in sequence, just one after another without doing anything in
between. I have a problem:
- the first generation when there is no target
directory goes well.
- the second one fails: the log
is:
"[Unable
to clear target directory (C:\Projects\tip\Features\Framework\2_IA\models\Test
Models\TIP_Test_Model1\target\tigerstripe.gen)]
Error: An error was
detected while generating a Tigerstripe project. Generation maybe
incomplete."
We have tested with tigerstripe 0.4.4 and
0.4.6 (official) .
Would you please help to analyze this issue?
张 晋寨 (ZHANG
Jinzhai)
Global Delivery Application Services, HP
+86 21 6081
3327
+86 139 1731 0846
la structure cachée dans les choses mathématiques
Attachment:
ts-documentation.velocity (error).log
Description: ts-documentation.velocity (error).log