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.
1. Install NB 5.5 beta 2. Install Enterprise Pack add-on early access (which contains AS9) 3. Start NB and click Yes when prompted to import settings 4. Create a web or enterprise project. Only J2EE 1.3 and 1.4 source levels are available It appears that the settings removes the AS9 instance from the Server Manager. When I kill my user dir and start the IDE again (and click No on the import settings prompt), I get all of the proper options. Marking as P2, but it's close to a P1, given the negative impressions one might have at startup, both for NB projects and Enterprise Pack users.
One more piece of information. The install of NB that I imported from included AS8.2 in the Server Manager (installed by the NB/AS bundle).
I am not sure we want to import this setting: Initial state: NB5.0/AS8.2 cobundle: so the AS 8.2 is seen as a 5.0 subcomponent. Imagine that *by* defaut the 5.5 would import the AS8.2 instance, and then you de-install the Nb5.0/AS 8.2 cobundle... If I remember well, this was the desired beahviour... Also, We do not want to OOB migrate easily AS 8.2 with NetBeans 5.5: 5.5 is all about AS 9.0.
I thought the issue was that it was *9.0* that disappeared upon settings import, not 8.2. If that is so, then this is a very valid bug.
The user indicates that the install of imported included AS8.2 in the Server Manager not AS9.0. If that is the case, then Ludo's comments apply. I will test this scenario with AS9.0 as part of the imported settings.
Tested the various install scenarios. The import settings work as expected. Looks like the issue is that the appserver associated with the enterprise pack (9.0) does not show up in the server manager when an existing userdir is used. Only the servers configured in that userdir show up. When a clean userdir is used, the appserver associated with the enterprise pack is automatically added to the ServerManager. Need to investigate to see whether the plugin does the automatic configuration of the ServerManager or not.
Does this happen with the NB 5.5 beta2 + AS 9 cobundle as well? We now have the the cobundle again, will be released on netbeans.org in a couple days. Here is an internal link to the builds: http://smetiste.czech.sun.com/builds/netbeans/5.5/bundles/sjsas_pe-9_0-nb-5_5/beta2/
The problem is with the process that adds the new appserver node automatically associated with the enterprise pack. If a pre-existing user directory is used, server settings defined in that userdir are imported and this new appserver node is not created. I don't see how the bundle will affect this.
So it seems to be a bundle installer issue, no? Peter: who is in charge of this?
I want to register my frustration with the fact that the app server node doesn't show the version as part of the name. Not only would that be more convenient in itself (I always want to know what version I'm using), but if the version were obvious, then even if a bug like this occurred it would be much more obvious to the user why.
I've tested it with NB IDE 5.5 Beta + AS 9.0 bundle -- bug is reproducible. More exactly: - install NB IDE 5.0 +AS 8.2 - run NB IDE 5.0 - exit IDE - install NB IDE 5.5 Beta 2 + AS 9.0 bundle - run NB IDE 5.5 Beta 2 - say "Yes" on import settings question Result: runtime tab displays only AS 8.2 Reassign bug to serverplugins component
Fixed./cvs/serverplugins/sun/appsrv81/src/org/netbeans/modules/j2ee/sun/ide/j2ee/PluginProperties.java,v <-- PluginProperties.java new revision: 1.3.16.5.2.4; previous revision: 1.3.16.5.2.3 Please verify on all platforms. (solaris/linux)