[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [eclipse-dev] [eclipse-build]Build N20031114 (Timestamp: 200311140010):Automated JUnit Testing complete. Test failures/errors occurred.
|
Unfortunately the Releng JUnit test cannot treat the checkpii warning (W)
as warning since JUnit only allows OK or failed as status. I would not want
to exclude the whole file and fully disable the useful warning is also not
desired. The best solution would be to maintain an ignore list with XML
attributes that need not to be NLSed.
Dani
Kim Moir
<Kim_Moir@xxxxxx.
com> To
Sent by: eclipse-dev@xxxxxxxxxxx
eclipse-dev-admin cc
@eclipse.org
Subject
Re: [eclipse-dev]
14.11.2003 18:12 [eclipse-build]Build N20031114
(Timestamp:
200311140010):Automated JUnit
Please respond to Testing complete. Test
eclipse-dev@eclip failures/errors occurred.
se.org
Here's what the chkpii doc states regarding error 969
969 (W) XML tag attribute (xxxxxx) may contain translatable text
which cannot be translated. Line: nnn
Description:
Since the tag and attribute names in XML are completely user definable, the
XML NLS Guidelines were forced to assume that all translatable text was
defined outside of the XML tags. The tools have no way to automatically and
reliably determine which attribute values contain translatable text. CHKPII
tries to make an educated guess by looking for attribute values which
contain blank separated strings which are a mixture of uppercase and
lowercase letters. The text for this tag's attribute appears to contain
translatable text. The translation tools will not present this text for
translation, so it will remain in English. This may result in the end user
seeing English text in their translated product.
Cause:
Potential translatable text has been found in the value assigned to a tag's
attribute. The text contains blank separated strings which are a mixture of
uppercase and lowercase letters.
Action:
Development needs to determine whether the identified text should be
translatable or not.
1. If the text for this attribute should not be translated, then
contact the CHKPII development team so that CHKPII can be improved to
handle this situation.
2. If the text should be translated, then either redesign the XML
DTD to make this attribute a separate tag or get a lab-specific markup
table created for this
See the XML NLS Guidelines for more information (
http://w3.rchland.ibm.com/projects/TWB/xmlguid.html#trans_attr).
If you'd like this error ignored, please advise and I'll update the build
scripts to do so.
Also, there are other checkpii errors for
org.eclipse.pde.doc
org.eclipse.tomcat
org.eclipse.ui
org.eclipse.jdt.ui
org.eclipse.jface
Please resolve these issues or advise that the files should be ignored.
I've expanded the regexp for org.eclipse.platform.source so these chkpii
errors are ignored.
Kim
Daniel Megert
<daniel_megert@ch To: eclipse-dev@xxxxxxxxxxx
.ibm.com> cc:
Sent by: Subject: Re: [eclipse-dev]
eclipse-dev-admin [eclipse-build]Build N20031114 (Timestamp:
@eclipse.org 200311140010):Automated JUnit Testing complete. Test
failures/errors occurred.
11/14/2003 10:53
AM
Please respond to
eclipse-dev
I assume that the chkpii errors below are due to new rules in the new
chkpii version. The reported text is valid: it are key sequences (e.g. "Esc
V") which contain spaces. How can we get rid of those errors without
disabling the whole file?
ECLIPSE\PLUGINS\ORG.ECLIPSE.UI.WORKBENCH.TEXTEDITOR_3.0.0\
PLUGIN.XML XML-10 969 (W) XML tag attribute (keySequence) may
contain translatable text which cannot be translated. Line: 814
969 (W) XML tag attribute (keySequence) may
contain translatable text which cannot be translated. Line: 832
969 (W) XML tag attribute (keySequence) may
contain translatable text which cannot be translated. Line: 844
969 (W) XML tag attribute (keySequence) may
contain translatable text which cannot be translated. Line: 916
969 (W) XML tag attribute (keySequence) may
contain translatable text which cannot be translated. Line: 940
969 (W) XML tag attribute (keySequence) may
contain translatable text which cannot be translated. Line: 952
Dani
sonia_dimitrov@ca
.ibm.com
Sent by: To
eclipse-dev-admin eclipse-dev@xxxxxxxxxxx
@eclipse.org cc
Subject
14.11.2003 15:41 [eclipse-dev] [eclipse-build]Build
N20031114 (Timestamp:
200311140010):Automated JUnit
Please respond to Testing complete. Test
eclipse-dev@eclip failures/errors occurred.
se.org
Build N20031114 (Timestamp: 200311140010): Automated JUnit testing is
complete. Test failures/errors occurred in the following:
org.eclipse.jdt.debug.tests_linux.gtk
org.eclipse.jdt.ui.tests.refactoring_linux.gtk
org.eclipse.releng.tests_linux.gtk
org.eclipse.releng.tests_winxp
org.eclipse.swt.tests_winxp
org.eclipse.team.tests.cvs_winxp
http://download.eclipse.org/downloads/drops/N-N20031114-200311140010/testResults.php
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
http://dev.eclipse.org/mailman/listinfo/eclipse-dev
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
http://dev.eclipse.org/mailman/listinfo/eclipse-dev