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.
Woodstock themes were found to be incompatible migrating 5.0 -> 5.1 http://www.netbeans.org/issues/show_bug.cgi?id=99063 and we face the same issue if any custom Woodstock theme is migrated from 5.1 -> 6.0. We should prevent the user from receiving a Missing Body Element error on migration. Winston has proposed detecting the custom theme on migration and making a switch to the default Woodstock theme.
The proposed solution - Get the project version and check if it is 5.1 project - Get the theme name from project String themeName = JsfProjectUtils.getProjectProperty(project, JsfProjectConstants.PROP_CURRENT_THEME); if (!themeName.equals("theme-default"){ // Replace the theme to default theme // Display a warning message giving appropriate information }
Hi Po-ting, is there a way to accomplish the steps while opening the project.
Do you mean you want to do some modification after opening a visualweb project? If so, looks into: org.netbeans.modules.visualweb.project.jsf.Install.OpenProjectsListener.propertyChange(...) you can either copy the codes to your module, or insert your actions into the following loop: for (Project project : jsfProjectsSet) { ... }
This should be release noted for Beta1 that users should manually switch to the default theme before migrating.
As we decided during Viusalweb i-team bug status council, downngrading this bug to p2. - Release note issue, so that user can switch to default theme. - Since user may not know why "No body found" error, we should post a dialog if a legacy Java EE 5 project is opened and it has custom theme.
We don't have proper support from Theme Context for this now. So marking this for future release
(When did this become a P3?) If nothing can be done, Migration docs / release notes should suggest the user not attempt to resolve the missing reference of the theme library but instead should remove the reference via Project Properties. They should remove the reference from the Libraries and the Build/Packaging. They will still receive a red Source File Error because no theme will be set by default. They need to explicitly then select the project Themes node and set Web UI Default Theme.
No current plan to resolve it. Moving to 'later'.