This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 105741 - I18N - Bundle-JSF.properties of visualweb need to be in l10n kits
Summary: I18N - Bundle-JSF.properties of visualweb need to be in l10n kits
Status: RESOLVED FIXED
Alias: None
Product: www
Classification: Unclassified
Component: Builds & Repositories (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: nbbuild-issues@ide
URL:
Keywords:
Depends on:
Blocks: 94655
  Show dependency tree
 
Reported: 2007-06-05 15:05 UTC by Ken Frank
Modified: 2007-06-28 18:33 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Frank 2007-06-05 15:05:23 UTC 
94655 was filed on visualweb, but now that its one product and unified build system,
perhaps the correct place for this issue is in nbbuild ?  Please close if its
not correct.

I realize that solution partially might need to be done by developers also.
Ashvini can give more background on this.

Basically, the Bundle-JSF.properties files are generated after the build so can't 
be in l10n kits.

But it means l10n team needs to separately get the product jars and extract the
Bundle-JSF files and this is something that they should not have to do, and they
have commented before
they would appreciate these files be in l10n kits, just like any other
translatable file.
Comment 1 rbalada 2007-06-28 16:51:05 UTC 
We found possible solution.

Extend existing l10n.list syntax with something like "antcall generate", which is supposed to trigger execution of an
Ant task within current module and execute the "generate" target. This would allow for generic solution, while allowing
for local overrides only where necessary without need to do hacks on higher level.

However this syntax extension could be a way to the hell, if would have been improperly used or abused or too heavily
used. It's because of more difficulties during debugging of such a smarty session.
Comment 2 rbalada 2007-06-28 18:10:48 UTC 
I've checked in two changes. One is infrastructure change to support calling of custom Ant target. The second change is
local override file visualweb/webui/designtime/l10n.list to show an example.

Checking in L10nTask.java;
/cvs/nbbuild/antsrc/org/netbeans/nbbuild/L10nTask.java,v  <--  L10nTask.java
new revision: 1.14; previous revision: 1.13
done

$ cvs ci -m "Issue 105741 - Add generated stuff into L10N kit" l10n.list 
RCS file: /cvs/visualweb/webui/designtime/l10n.list,v
done
Checking in l10n.list;
/cvs/visualweb/webui/designtime/l10n.list,v  <--  l10n.list
initial revision: 1.1
done
Comment 3 Ch Nguyen 2007-06-28 18:33:39 UTC 
Cool.  That was quick!  Thanks a lot Rudolf for resolving this issue.

Ken, please verify in the next l10n-kit build (e.g. tomorrow) at http://deadlock.netbeans.org/hudson/job/l10nkit/.
Comment 4 rbalada 2007-06-28 18:33:59 UTC 
I've updated wiki page http://wiki.netbeans.org/wiki/view/NetBeans6.0L10NListHOWTO to cover this new syntax element.