]
Snjezana Peco resolved JBIDE-9361.
----------------------------------
Fix Version/s: (was: 3.2.2)
Resolution: Done
The problem happens when a project isn't a faceted project (helloworld_action_client)
or it doesn't have a primary runtime (webservice_consumer1_client).
There also has been a problem related to defining esb requirements. The
webservice_consumer1_client project hasn't been added to the eclipse-projects
property.
Fixed in the trunk. Please reopen if I need to fix it in the 3.2.x branch too.
Imported project examples with multiple projects don't have build
path set correctly
------------------------------------------------------------------------------------
Key: JBIDE-9361
URL:
https://issues.jboss.org/browse/JBIDE-9361
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 3.2.1.CR3, 3.3.0.M3
Environment: Windows 7, JBDS 4.1 CR3 build installed, 32-bit JDK
Reporter: Brian Fitzpatrick
Assignee: Snjezana Peco
Fix For: 3.3.0.M3
While doing some testing of one of the ESB project examples (ESB for SOA-P 5.0 ->
JBoss ESB HelloWorld Action Example - ESB and ESB for SOA-P 5.0 -> JBoss ESB Web
Service consumer1 Example) in conjunction with JBDS-1716, I discovered an interesting
issue when there are multiple projects in the project-example zip being imported.
The first project in the zip being imported (i.e. helloworld_action) is imported
correctly with the runtime set properly in the build path. But the second project (i.e.
helloworld_action_client) is not updated correctly and still pointing to the wrong
runtime.
To reproduce:
1) In a new workspace with no SOA/EAP 5.x runtime defined, create a new EAP 5.x server in
the Servers view. Name the server "one" and the server runtime "two".
2) Click on Help->Project Examples->ESB for SOA-P 5.0->JBoss ESB HelloWorld
Action Example - ESB.
3) Note that when the projects are imported, helloworld_action is setup correctly and
helloworld_action_client is not.
Now, is this a bug? Or is it working as designed? I would hope that the project examples
code would peer into each project being imported to see if the build path needed to be
updated.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: