Community
Participate
Working Groups
Build Identifier: 20100617-1415 This seems to be related directly to web/faceted projects. Classic Java projects are not affected by this bug. Reproducible: Always Steps to Reproduce: 1. Create more then 2 server runtimes 2. Create web project, select one of previously created runtimes 3. Expand project/Java resources/Libraries 4. Select server runtime, properties menu 5. Select 2nd runtime 6. Nothing happens, project explorer displays still the old runtime.
I am moving this to Java EE Tools because this is on a Web project. However, it is possible that the underlying problem is in either the FacetedProjectFramework or Server Tools code.
Libor, I am having a problem recreating your scenario. Here's what I am doing: I create a workspace with a JOnAS 4 and an Apache 5.5 server runtime. I create a Web 2.4 (and do not add to EAR), targeted at Jonas 4. I expand the Web 2.4, expand Java Resources:src, and expand Libraries I select the JOnAS v4 node and bring up properties. I select Apache Tomcat 5.5 and press OK Project Explorer now shows an Apache Tomcat v5.5 node instead of a JOnAS v4 node. Can you try this out and tell me if you see the same? Or alternately, can you provide more details as to your exact steps?
(In reply to comment #2) > Libor, I am having a problem recreating your scenario. Here's what I am doing: > > I create a workspace with a JOnAS 4 and an Apache 5.5 server runtime. > I create a Web 2.4 (and do not add to EAR), targeted at Jonas 4. > I expand the Web 2.4, expand Java Resources:src, and expand Libraries > I select the JOnAS v4 node and bring up properties. > I select Apache Tomcat 5.5 and press OK > Project Explorer now shows an Apache Tomcat v5.5 node instead of a JOnAS v4 > node. > > Can you try this out and tell me if you see the same? Or alternately, can you > provide more details as to your exact steps? Carl, my scenario is same in common, but I use different runtimes. I create a workspace with a Apache 6(1) and an Apache 6(2) server runtimes. I create a Web 2.5/2.4 (reproducible on both) (and do not add to EAR), targeted at Apache 6(1). I expand the Web project, expand Java Resources:src, and expand Libraries I select the Apache 6(1) node and bring up properties. I select Apache Apache 6(2) and press OK Project Explorer still shows Apache 6(1)
I was able to reproduce this (but not reliably) using two "servers" that referenced the same install location. This seems like moreso a corner case and doesn't seem to meet the criteria necessary now that we are shutting down WTP 3.2.4 development- I am retargeting to WTP 3.3
We're having a hard time replicating this- if you still see this issue, then reopen this bug with more information.
