[JBoss JIRA] Created: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly
1:11 p.m.
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
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
4:12 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly
[
https://issues.jboss.org/browse/JBIDE-9361?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick updated JBIDE-9361:
-------------------------------------
Fix Version/s: 3.2.2
3.3.0.M3
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.2.2, 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
7:38 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly
[
https://issues.jboss.org/browse/JBIDE-9361?page=com.atlassian.jira.plugin...
]
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: http://www.atlassian.com/software/jira
9:32 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly
[
https://issues.jboss.org/browse/JBIDE-9361?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick commented on JBIDE-9361:
------------------------------------------
@Snjezana - Is there a preferred way to implement supplemental projects to a zip that
needs importing?
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
2:47 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly
[
https://issues.jboss.org/browse/JBIDE-9361?page=com.atlassian.jira.plugin...
]
Snjezana Peco commented on JBIDE-9361:
--------------------------------------
I create/import projects in Eclipse and export them to a zip using Eclipse's Export
action.
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
2:51 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly
[
https://issues.jboss.org/browse/JBIDE-9361?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick commented on JBIDE-9361:
------------------------------------------
Right - that I get. But in the case where we have multiple projects in a single zip, what
needs to be in them (facet-wise, project-setup wise, or whatever) so that they all get
updated with the right runtime reference where needed?
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
4:13 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly
[
https://issues.jboss.org/browse/JBIDE-9361?page=com.atlassian.jira.plugin...
]
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
4:34 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly
[
https://issues.jboss.org/browse/JBIDE-9361?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick commented on JBIDE-9361:
------------------------------------------
Perfect. Thanks. That was the part I was missing. :)
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
5:34 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly
[
https://issues.jboss.org/browse/JBIDE-9361?page=com.atlassian.jira.plugin...
]
Snjezana Peco resolved JBIDE-9361.
----------------------------------
Fix Version/s: 3.2.2
Resolution: Done
Committed to the jbosstools-3.2.x branch.
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.2.2, 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
8:37 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly
[
https://issues.jboss.org/browse/JBIDE-9361?page=com.atlassian.jira.plugin...
]
Libor Zoubek commented on JBIDE-9361:
-------------------------------------
verified on Project Examples 1.2.1.v20110901-1047-H11-M3
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.2.2.M1, 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
8:37 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-9361) Imported project examples with multiple projects don't have build path set correctly
[
https://issues.jboss.org/browse/JBIDE-9361?page=com.atlassian.jira.plugin...
]
Libor Zoubek closed JBIDE-9361.
-------------------------------
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.2.2.M1, 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
5327
days inactive
5376
days old
jbosstools-issues@lists.jboss.org
10 comments
3 participants
participants (3)
-
Brian Fitzpatrick (JIRA) -
Libor Zoubek (JIRA)
-
Snjezana Peco (JIRA)