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 196696 - [70cat] Import settings from 6.9 brokes the Swing Layout Extensions library
Summary: [70cat] Import settings from 6.9 brokes the Swing Layout Extensions library
Status: VERIFIED WORKSFORME
Alias: None
Product: ide
Classification: Unclassified
Component: Import Settings (show other bugs)
Version: 7.0
Hardware: PC Linux
: P4 normal (vote)
Assignee: Yulia Novozhilova
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-14 20:08 UTC by Michel Graciano
Modified: 2011-03-31 12:19 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Library manager details (46.51 KB, image/png)
2011-03-14 20:11 UTC, Michel Graciano
Details
6.8 library configuration file (784 bytes, text/xml)
2011-03-16 16:52 UTC, Michel Graciano
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Graciano 2011-03-14 20:08:26 UTC
[ BUILD # : 201103100000 ]
[ JDK VERSION : 1.6.24 ]

If I import settings from 6.9 the reference to Swing Layout Extensions jar file
is broken and open a project which use it shows up the project references
problem UI. I will attach a image of my library configuration just after open
the IDE importing the settings.
Comment 1 Michel Graciano 2011-03-14 20:11:04 UTC
Created attachment 106990 [details]
Library manager details

Here you can see that the reference is broken. Probably because the library was updated for RC1 to version 1.0.4? Anyway I am not sure if point to the new one is the correct behaviour since it will change the dependent applications behaviour because the library was changed.
Comment 2 Yulia Novozhilova 2011-03-15 17:09:23 UTC
It is strange. NetBeans 6.9, as well as 6.8 uses 1.0.4 version of swing-layout.
I can't reproduce on my Windows machine. Could you please try reproduce this
bug again and attach $USERDIR/.netbeans/$(NB_VERSION)/var/log/messages.log file
here.
Comment 3 Michel Graciano 2011-03-15 19:43:54 UTC
The problem is probably because have I been importing my settings since forever? My user dir is imported probably since 3.6 version so, probably this could be the problem. My guess is that many users import settings from really old versions and it should be fixed. I will try later it again and send you the logs you requested and reopen the issue too.
Comment 4 Yulia Novozhilova 2011-03-16 13:06:40 UTC
Well, I tried to import settings from 6.7 (where swing layout 1.0.3 is used) to 7.0 RC1 and still couldn't reproduce.
Comment 5 Marian Mirilovic 2011-03-16 13:52:27 UTC
removing the keyword - to be fixed in 7.0 HR
Comment 6 Michel Graciano 2011-03-16 16:20:02 UTC
(In reply to comment #4)
> Well, I tried to import settings from 6.7 (where swing layout 1.0.3 is used) to
> 7.0 RC1 and still couldn't reproduce.

I can confirm it is not a bug for 7.0, it is valid until 6.8 at least. My 6.8 installation has this problem so I guess anyone had faced it yet. I will continue figure out how to reproduce it (for me it is consistent). I will reopen it as soon as I can send you steps that you can reproduce.
Comment 7 Michel Graciano 2011-03-16 16:52:05 UTC
Created attachment 107057 [details]
6.8 library configuration file

I will reopen it just for your evaluation but I think it could some problem that happened during 6.8 stabilization. I am attaching my 6.8 library configuration file which was created sometime during 6.8 NetCAT and imported from 6.9 and now 7.0 (My guess is that probably I had reused the user dir from 6.8 stabilization phase for my FCS install).

Anyway, I have just tested again the imports for 6.8, 6.9.1 and 7.0RC, all of them importing from 6.7, and everything has worked fine.

I don't know why I haven't seen it before since I just saw it now because some of my test projects showed me some reference problems with libraries. Since I can't determine exactly how to reproduce it, I will decrease the issue priority, P4 should be good, and I am not sure if you will treat this case anyway.
Comment 8 Michel Graciano 2011-03-24 14:49:21 UTC
Any news on this? Maybe you may just add some comment about it and close it if no necessary change is necessary.
Comment 9 Yulia Novozhilova 2011-03-31 10:14:30 UTC
Since there is no steps to reproduce and there is no another occurrence of this issue I think we can close it as invalid. Anyway thank you for letting me know I'll keep it in mind in case if something like this happen again.
Comment 10 Michel Graciano 2011-03-31 12:05:46 UTC
Thank you for your time to evaluate this. I will keep this in mind too for future releases, but I am pretty sure it was some kind of problem during old NetCAT seasons.
Comment 11 Marian Mirilovic 2011-03-31 12:19:14 UTC
(In reply to comment #9)
> Since there is no steps to reproduce and there is no another occurrence of this
> issue I think we can close it as invalid. Anyway thank you for letting me know

... means INVALID or WORKSFORME, definitely not FIXED