[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly

Snjezana Peco (JIRA) jira-events at lists.jboss.org
Wed Aug 3 17:13:18 EDT 2011


    [ https://issues.jboss.org/browse/JBIDE-9361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618644#comment-12618644 ] 

Snjezana Peco commented on JBIDE-9361:
--------------------------------------

You would set the corresponding runtimes to the projects and export all the projects.
After that, you would define fixes/requirements in the project xml file. 
You could add, for instance, the following entry to the webservice_consumer1 project:
<fixes>
  <fix type="wtpruntime">
    <property name="allowed-types">org.jboss.ide.eclipse.as.runtime.eap.50</property>
    <property name="eclipse-projects">webservice_consumer1,webservice_consumer1_client</property>
    <property name="required-components">esb</property>
    <property name="description">This project example requires the JBoss SOA-P 5.x</property>
  </fix>
</fixes>

This would mean:
- the webservice_consumer1 and webservice_consumer1_client Eclipse projects require JBoss EAP 5.x runtime with the esb component. When the user imports this project example, the appropriate server runtime will be added to these Eclipse projects if it exists in the workspace.

> 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: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list