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.
Summary: | Migrated app that uses datasources still starts modeling | ||
---|---|---|---|
Product: | obsolete | Reporter: | Yousuf Haider <yousufh> |
Component: | visualweb | Assignee: | _ potingwu <potingwu> |
Status: | NEW --- | ||
Severity: | blocker | CC: | cnguyencasj, jbaker |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
Simple Project with button only
Project with data sources |
Description
Yousuf Haider
2007-07-25 18:05:30 UTC
Created attachment 45696 [details]
Simple Project with button only
Created attachment 45697 [details]
Project with data sources
if nothing affecting the functionality then I think this should be lowered to a P3 The project version in in the nbproject/project.xml is listed as 2.0 but should be 4.0 once the project has been imported, changed and saved in NB6. The project version is used for 'the general project'. Individual components should maintain their own flag/version. E.g., comp#1 update to new version but not comp#2, project version can't just upgrade then. Per guidelines, downgrading to a P3. But this should be fixed for FCS in my opinion No, individual components should not have to maintain the version. I was told the project module changes the version of the project. This is a project issue. *** Issue 112492 has been marked as a duplicate of this issue. *** I had fixed the migration part for databases such that the Alert dialog no longer appears. Also, I removed the actions on the Data Source Reference node. Currently database migration process is done automatically without user action. The remaining issue is that every time a legacy project is opened (and no page from the designer opens) the database migration starts. In most cases, the user will open a page of the project after opening a project so that the next time the project is opened, migration won't occur. I think the priortity could be reduced to a P4 > The project version is used for 'the general project'. Individual components should maintain their own flag/version.
> E.g., comp#1 update to new version but not comp#2, project version can't just upgrade then.
As I said, you are using wrong API for checking migration. This API is for the 'the IDE that originally created this
project'. We need to design another kind of flag to indicate the task is done or not by individual component. Please
review again the above comment I put.
improved fix: Checking in visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/datasource/DataSourceResolver.java; /cvs/visualweb/dataconnectivity/src/org/netbeans/modules/visualweb/dataconnectivity/datasource/DataSourceResolver.java,v <-- DataSourceResolver.java new revision: 1.19; previous revision: 1.18 done 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.21; previous revision: 1.20 done |