Opened 52 years ago

Last modified 11 years ago

#865 new task

IZ208: Evaluate a tool for checking resource bundles

Reported by: crei Owned by:
Priority: normal Milestone:
Component: hedeby Version: 1.0
Severity: Keywords: misc


[Imported from gridengine issuezilla]

        Issue #:      208          Platform:     All         Reporter: crei (crei)
       Component:     hedeby          OS:        All
     Subcomponent:    misc         Version:      1.0            CC:    None defined
        Status:       NEW          Priority:     P3
      Resolution:                 Issue type:    TASK
                               Target milestone: 1.0u5next
      Assigned to:    marcingoldyn (marcingoldyn)
      QA Contact:     adoerr
       * Summary:     Evaluate a tool for checking resource bundles
   Status whiteboard:

     Issue 208 blocks:
   Votes for issue 208:     Vote for this issue

   Opened: Thu Nov 15 08:35:00 -0700 2007 

   - It would be nice to have such a feature for hedeby (or other java projects)
   - Testsuite should check for unused keys when updating or compiling the java
     source code
               ------- Additional comments from crei Mon Dec 3 01:56:57 -0700 2007 -------
   *** Issue 245 has been marked as a duplicate of this issue. ***
               ------- Additional comments from rhierlmeier Wed Feb 27 06:49:09 -0700 2008 -------

   It can be that some messages are built at runtime.

   May be we can use a third party tool for checking the resource bundles.

               ------- Additional comments from rhierlmeier Wed Feb 27 06:53:10 -0700 2008 -------
   We need a tools which detect unused and duplicate message keys
   in resource bundles

   This issue does not include fixing the problems in the resource bundle, it's
   just the tool.
               ------- Additional comments from marcingoldyn Wed Aug 6 02:19:30 -0700 2008 -------
   We need a tool or code that will check for a unused or duplicated resource
   bundle localization messages.

   This feature can be useful since right now we dont have clear view of how many
   L10N messages is not used or there are duplicated ones among one file.

   Suggested Fix:
   Find and use some external tool or implement solution by ourselfs.

   We should focus on finding some existing tool, our own effort with providing our
   own solution could not be worth of results that we can get.

   How to test:
   Depends on solution that we will consider it probably could be tested using test
   suite test. It might be also incorporated into our build mechanism of SDM.
   Relaying on this we can get some information about missing/unused bundles during
   the build time.

   It depends on complexity of a tool that we are planning to use.

   1 PD

               ------- Additional comments from crei Wed Aug 6 05:15:16 -0700 2008 -------
   changed summary - this is no testsuite task it's evaluation task
               ------- Additional comments from crei Fri Aug 8 07:57:29 -0700 2008 -------
   This testsuite issue depends on this task:
               ------- Additional comments from torsten Tue Oct 28 01:46:39 -0700 2008 -------
   Another thing that could/should be checked by the tool is the number of
   parameters given in the logging call vs. the actual number of parameters in the
   error message.

   The tool does not have to catch all possible cases of mismatch but should find
   the simple ones.
               ------- Additional comments from rhierlmeier Wed Nov 25 07:21:11 -0700 2009 -------
   Milestone changed

Change History (0)

Note: See TracTickets for help on using tickets.