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 138807 - Project Migration between versions.
Summary: Project Migration between versions.
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 6.x
Hardware: Other Windows XP
: P2 blocker with 1 vote (vote)
Assignee: Tomas Zezula
Depends on:
Reported: 2008-07-02 14:09 UTC by bakarirum
Modified: 2011-08-31 14:07 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description bakarirum 2008-07-02 14:09:51 UTC
Apply to Versions 6.0+

We have a shop with around 30 developers.  We let NetBeans manage our build processes and currently use CVS.  With so 
many developers and each one using NetBeans it is hard to keep everyone on the same version of NetBeans.  Can we add a 
NetBeans migration feature (which works seemlessly in the background)?  The idea is when NetBeans pulls up a project 
(in which NetBeans maintains meaning not a free form project), then NetBeans will migrate the project to the current 
version of NetBeans.   This tool would be forward and backward compatible.  Therefore, if I create a project in 
NetBeans 6.1 and my colleague pulls up the project in NetBeans 6.0 or NetBeans 5.5; the ide would adjust the project 
settings/properties such that it will work smoothly in the current version of the IDE.  I understand that certain 
things cannot be done such as with a web application, you have to choose the Target server.  But the IDE already 
recognizes when it cannot find the target server.  The problem comes in specifically with the and 
the build-impl.xml files.  There are version specific information here and if you take a project with the exact same 
files, set-up, etc and noticed the differences, you would see the changes.  How hard would it be (honestly)?  NetBeans 
already maintains the build-impl and file.  When you make a project change these files are changed 
and/or recreated anyway.  So why can't the IDE automatically handle this migration?  You can even add a dialog box 
when the project is opened to ask if the user wishes to migrate up (or down) to the current IDE version.
Comment 1 _ moser 2008-08-07 09:12:22 UTC
A project related property to define the maximum NB version for the project file format would be better, I think.
Something similar to the using property when compiling with Java 1.6