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.
Jdk6u2 and u3 Beta1 build: 09102007 and 09112007 1. Open 5.5 project that uses data sources in NB6. 2. Expand project node. 3. Updating legacy project process does not start. As a consequence no connections are migrated from 5.5 userdir and the migrated folder in the NB6 userdir is not created. 4. The project is badged at this point since data sources need to be resolved. Go through Resolve data sources dialog to fix the project. Since there is a workaround filing it as a P2. Strangely enough if I open an empty 5.5 project in NB6 that uses no data sources the Updating Legacy Project process starts and all connections are migrated. I was able to reproduce the same issue with some 5.5.1 projects but not all.
Created attachment 48593 [details] IDE log
Marking bug as regression as this functionality was working previously
If this is not a filing mistake, then possibly not a database bug. Code hasn't changed in beta1 and migration was working right before the beta1 branch
It seems that the fix for the issue 110480 (Updating Legacy Project process starts everytime legacy project is opened) broke this functionality. I verified this by trying the build right before and after the fix was integrated. I can reproduce this issue with the build after that (200709021200) but not the one right before it. From CVS it seems that a check was added (isRequestedJdbcResourceAvailable()) to fix issue 110480 which checks whether the project already had datasources. If it had it would not go through the Updating legacy Projects process. Apparently this worked for Creator projects by migrating settings when the project was opened the first time but not the second time. For 55 projects the check returns true the first time the project is opened and therefore the database connections are not migrated. This also explains why the updating legacy project process starts for projects that don't have datasources since the check return false and so the migration kicks in.
Testing should have been completed prior to beta1. Code hasn't changed for a week
Unfortunately since I am working part time I had only 2 days last week to do any testing with Monday being a holiday. Other pending migration issues took most of the time I had.
Updating data sources does start, there is a progress bar. Something else is going on
This appears to be unrelated to updating data sources Updating process occurs and APIs invoked. It looks like the connection is not migrated, but the driver is migrated, at least for Oracle.
I do not see the progress bar starting at all. Also for me the oracle driver is not migrated. So basically nothing is migrated.
I cannot reproduce the behavior mentioned. Updating is working
After working with John it seems that the problem is occurring in the beta1 builds. The fix for issue 113272 which was integrated in the trunk fixed this issue as well. I verified this by testing the trunk build : 200709120000 Will reopen this issue and then mark it as fixed to reflect correct resolution.
The fix for issue 113272 fixed this issue as well.
Marking as regression since this was broken before beta1.
This really should have never been a Regression in the first place since this was a bug fix for an issue that turns out to be invalid Made some improved fix though $ cvs commit visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/explorer/ProjectDataSourceNode.java Checking in visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/explorer/ProjectDataSourceNode.java; /cvs/visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/explorer/ProjectDataSourceNode.java,v <-- ProjectDataSourceNode java new revision: 1.19; previous revision: 1.18 done