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 134134 - Update of jMaki plugin on Stable 6.1 UC
Summary: Update of jMaki plugin on Stable 6.1 UC
Status: VERIFIED FIXED
Alias: None
Product: updatecenters
Classification: Unclassified
Component: Stable (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: rnovak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-29 09:49 UTC by Jiri Kovalsky
Modified: 2008-04-30 16:48 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
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 Jiri Kovalsky 2008-04-29 09:49:30 UTC 
It is very important to update "jMaki Ajax Support" plugin on Stable 6.1 Update Center this week.

Ludo, can you please attach TESTED new NBM file to this issue? Thanks a lot!
Comment 1 Jiri Kovalsky 2008-04-30 10:27:57 UTC 
Roberte, please stage the plugin [1] as soon as possible.

[1] https://ajax.dev.java.net/files/documents/3115/94899/org-netbeans-modules-sun-jmaki.nbm
Comment 2 rnovak 2008-04-30 11:49:19 UTC 
Module is staged
Comment 3 Jiri Kovalsky 2008-04-30 13:52:44 UTC 
Roberte, it's staged correctly so please publish the plugin on the live Update Center. Thanks!
Comment 4 rnovak 2008-04-30 14:04:10 UTC 
I pushed the module live.
Comment 5 Jiri Kovalsky 2008-04-30 14:26:22 UTC 
Roberte, are you sure you pushed the module to the live UC? I still see its version 1.7. Can you please double check this?
Comment 6 Jiri Kovalsky 2008-04-30 15:01:39 UTC 
OK, it's fixed now. Thanks for re-generation of the catalog!
Comment 7 Jiri Kovalsky 2008-04-30 15:43:26 UTC 
Verified.
Comment 8 Ken Frank 2008-04-30 16:48:47 UTC 
as to it needing to meet i18n requirements and i18n readiness,
I've discussed a bit with some on jmaki team and

a. its not clear to me yet that the needed i18n dev or testing
was done - as I understand it the testing of it in general was
done by developement

b. since it comes from another repository, the providers need to emulate
our i18n readiness processes as to kit, ml build, etc and that has not
yet happened.  I've discussed about these requirements with someone
on that team.



ken.frank@sun.com