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.
Using pseudo localized vwp6, using 0410 or 0405 builds, cannot create a vwp project (and get exception) when there is a pseudo localized webui-jsf-suntheme_ja.jar (even when the messages_ja.properties in it is empty and there are no localized html files) 1. we get this jar from other team and they localize it also, but for testing now, we pseudo localize it. 2. this was not a problem about a week ago. 3. removing this pseudo localized jar from modules/ext - a vwp project can be created. all other pseudo localized jars in all nb module subdirs can be present - its just this one jar. 4. even adding the manifest information to MANIFEST.MF, X-Informational-Archive-Locale: ja as has been done in earlier releases, does not work. 5. running in some other locale for which there are no pseudo localized files, all is ok also. ===> this is a blocking kind of issue since it does help to emulate what the real localzied bits will be; even though we get this jar from other team. 6. exception is attached.
Created attachment 40722 [details] t
using the real localized jar delivered by ws team from shortfin, the problem is still there. I realize eventual woodstock jar for vwp6 might be different but assuming the layout will be same, but in any case, the main experiment uses the one in vwp6 as a basis. ken.frank@sun.com
Please attach 'the real localized jar' for me to test.
I'm not aware of a real localized jar for netbeans 6 since we get those deliveries later. I take the en one and pseudo localize it, so I'll send you that one separately. ken.frank@sun.com
I think this is a web project classpath modifier bug. As I tracked, when adding a jar file (e.g., URL="file:/D:/.../nbbuild/netbeans/visualweb1/modules/ext/locale/webui-jsf-suntheme_ja.jar"), I got this assert error from org.netbeans.modules.web.project.classpath.WebProjectClassPathModifier, at line#128: assert classPathRoots[i].toExternalForm().endsWith("/"); //NOI18N It expects the URL must be ended with "/". Is that a standard that we should follow? After I comment out this line, I do see the jar file has been successfully added into the project.
To developers, I know we are not releasing localized now, but this info or solution is critical now for ongoing vwp testing, which simulates the localized situation. So if you could reply to the question in previous comment soon it will be very helpful and appreciated. ken.frank@sun.com
Classpath modifier works fine in web project as well as in j2se project and there were no changes in last few days in it so if Ken says that this problem wasn't there a week ago I would say that something changed in the visual web. Po-Ting, see how the URL is constructed in org.netbeans.modules.web.project.classpath.WebProjectClassPathExtender.addArchiveFiles(...) method. FileObject fo...; FileObject archiveFile = FileUtil.getArchiveRoot(fo); URL[] archiveFileURL = archiveFile.getURL(); Hopefully it can help.
Fixed. Looks like the new API now requires the archive-root and not allows the file itself.
Created attachment 42605 [details] exception on project creation
ignore latestg attachment; it was meant for another issue.
verified - now the localized suntheme jar and some other localized ones are mounted in project libraries tab. ken.frank@sun.com