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 206938 - spring-framework300.xml with incorrect settings for spring 3.0.6
Summary: spring-framework300.xml with incorrect settings for spring 3.0.6
Status: RESOLVED INVALID
Alias: None
Product: javaee
Classification: Unclassified
Component: Spring (show other bugs)
Version: 7.1
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Martin Fousek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-05 14:55 UTC by tilman
Modified: 2012-01-11 06:47 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description tilman 2012-01-05 14:55:30 UTC 
I just installed Netbeans 7.1 on a PC that had already Netbeans 6.9 installed, it offered to import my settings, which I accepted. My ANT-based spring projects got a lot of red flags, the cause was that the spring library couldn't be found, the "library classpath" dialogbox had paths to 3.0.2 jars.

The cause was the file C:\Documents and Settings\tilman\.netbeans\7.1\config\org-netbeans-api-project-libraries\Libraries\spring-framework300.xml which has a lot of lines with 3.0.2.RELEASE.jar, these must be changed into 3.0.6.RELEASE.jar, and now it works.

Also, commons-logging-1.1.jar must be changed into commons-logging-1.1.1.jar

I don't know if this error is there by default, or if it is the result of accepting the import. 

Amusingly, it might be a result of the fix of bug 202983, which I reported :-)
Comment 1 tilman 2012-01-06 10:16:54 UTC 
I just installed on a PC without a previous Netbeans installation, that one doesn't have the problem. Thus it is related to importing the settings from a previous installation.
Comment 2 Martin Fousek 2012-01-06 12:39:55 UTC 
I'm not fully sure about all situations in which are these library definition files stored in user properties - probably in cases of manual customization of the library? CCing David, he could know when this happens.

If it would be really after customising library, wouldn't it be ok, that the IDE preserved your library settings?
Comment 3 tilman 2012-01-06 17:28:23 UTC 
I just installed Netbeans 7.1 on a W7 PC that has NB 6.9 and NB 7.01 installed, and I agreed with the import of the from NB7.01 settings (Yes, this means I have 3 versions of Netbeans installed, LOL). This time I did not have the problem. Thus I suspect it is the import from NB6.9 to 7.1 that is the source of the trouble.
Comment 4 Martin Fousek 2012-01-11 06:47:44 UTC 
Sorry that I'm closing your issue as invalid, but it looks that the IDE behaved correctly. If you have library XML definition file inside user preferences it means that you did manual changes in the library customizer. So by importing settings from older NB release it just took all your settings (including customized library) and imported it into the new IDE version. But it can't know what in the XML definition should stay and what not. It has bundled updated library but since the IDE has customized version of the library, it uses that definition. 

So you can update your customized library (via Tools->Libraries) to use newer Spring library JARs or delete your "spring-framework300.xml" from the userdir and use so the default IDE's definition.