10:13 a.m.
BPEL source folder should not be hard-coded as "bpelContent"
------------------------------------------------------------
Key: JBIDE-6170
URL: https://jira.jboss.org/jira/browse/JBIDE-6170
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpm
Affects Versions: 3.1.0.GA
Reporter: Robert (Bob) Brodt
Fix For: 3.2.next
The "bpelContent" folder should not be hard-coded as the only place to search
for BPEL deployment sources - I don't understand why we can't start searching at
the project root.
See also https://jira.jboss.org/jira/browse/JBIDE-5829
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:50 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6170) BPEL source folder should not be hard-coded as "bpelContent"
[
https://jira.jboss.org/browse/JBIDE-6170?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick updated JBIDE-6170:
-------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Component/s: bpel
BPEL source folder should not be hard-coded as
"bpelContent"
------------------------------------------------------------
Key: JBIDE-6170
URL: https://jira.jboss.org/browse/JBIDE-6170
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm
Affects Versions: 3.1.0.GA
Reporter: Robert (Bob) Brodt
Fix For: 3.2.next
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The "bpelContent" folder should not be hard-coded as the only place to search
for BPEL deployment sources - I don't understand why we can't start searching at
the project root.
See also https://jira.jboss.org/jira/browse/JBIDE-5829
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:54 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6170) BPEL source folder should not be hard-coded as "bpelContent"
[
https://jira.jboss.org/browse/JBIDE-6170?page=com.atlassian.jira.plugin.s...
]
Feng Qian commented on JBIDE-6170:
----------------------------------
Hi Bob,
When I look into this issue, I have a idea, we should think about how to merge with
eclipse bpel runtimes.
For now we have a jboss.bpel.runtimes plugin to handle how to deploy into jboss server.
And eclipse bpel
has a eclipse.bpel.runtimes to handle how to deploy into tomcat server. We should think
about how to merge
these two plugins together, then resolve this issue and JBIDE-6588, and others deploy
issues.
Any ideas?
Grid
BPEL source folder should not be hard-coded as
"bpelContent"
------------------------------------------------------------
Key: JBIDE-6170
URL: https://jira.jboss.org/browse/JBIDE-6170
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm
Affects Versions: 3.1.0.GA
Reporter: Robert (Bob) Brodt
Assignee: Feng Qian
Fix For: 3.2.x
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The "bpelContent" folder should not be hard-coded as the only place to search
for BPEL deployment sources - I don't understand why we can't start searching at
the project root.
See also https://jira.jboss.org/jira/browse/JBIDE-5829
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:42 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6170) BPEL source folder should not be hard-coded as "bpelContent"
[
https://jira.jboss.org/browse/JBIDE-6170?page=com.atlassian.jira.plugin.s...
]
Robert (Bob) Brodt updated JBIDE-6170:
--------------------------------------
Fix Version/s: 3.2.0.CR1
(was: 3.2.x)
Moved to 3.2.0.CR1
BPEL source folder should not be hard-coded as
"bpelContent"
------------------------------------------------------------
Key: JBIDE-6170
URL: https://jira.jboss.org/browse/JBIDE-6170
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm
Affects Versions: 3.1.0.GA
Reporter: Robert (Bob) Brodt
Assignee: Feng Qian
Fix For: 3.2.0.CR1
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The "bpelContent" folder should not be hard-coded as the only place to search
for BPEL deployment sources - I don't understand why we can't start searching at
the project root.
See also https://jira.jboss.org/jira/browse/JBIDE-5829
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:44 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6170) BPEL source folder should not be hard-coded as "bpelContent"
[
https://jira.jboss.org/browse/JBIDE-6170?page=com.atlassian.jira.plugin.s...
]
Feng Qian resolved JBIDE-6170.
------------------------------
Resolution: Done
have done
BPEL source folder should not be hard-coded as
"bpelContent"
------------------------------------------------------------
Key: JBIDE-6170
URL: https://jira.jboss.org/browse/JBIDE-6170
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm
Affects Versions: 3.1.0.GA
Reporter: Robert (Bob) Brodt
Assignee: Feng Qian
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The "bpelContent" folder should not be hard-coded as the only place to search
for BPEL deployment sources - I don't understand why we can't start searching at
the project root.
See also https://jira.jboss.org/jira/browse/JBIDE-5829
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:44 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6170) BPEL source folder should not be hard-coded as "bpelContent"
[
https://jira.jboss.org/browse/JBIDE-6170?page=com.atlassian.jira.plugin.s...
]
Feng Qian commented on JBIDE-6170:
----------------------------------
This issue has been fixed by JBIDE-6588
BPEL source folder should not be hard-coded as
"bpelContent"
------------------------------------------------------------
Key: JBIDE-6170
URL: https://jira.jboss.org/browse/JBIDE-6170
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm
Affects Versions: 3.1.0.GA
Reporter: Robert (Bob) Brodt
Assignee: Feng Qian
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The "bpelContent" folder should not be hard-coded as the only place to search
for BPEL deployment sources - I don't understand why we can't start searching at
the project root.
See also https://jira.jboss.org/jira/browse/JBIDE-5829
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:24 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6170) BPEL source folder should not be hard-coded as "bpelContent"
[
https://jira.jboss.org/browse/JBIDE-6170?page=com.atlassian.jira.plugin.s...
]
Pavol Srna commented on JBIDE-6170:
-----------------------------------
Feng, how to verify this Jira? it seems to me that it is not resolved for beta2,
https://jira.jboss.org/browse/JBIDE-6588 is still open.
BPEL source folder should not be hard-coded as
"bpelContent"
------------------------------------------------------------
Key: JBIDE-6170
URL: https://jira.jboss.org/browse/JBIDE-6170
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm
Affects Versions: 3.1.0.GA
Reporter: Robert (Bob) Brodt
Assignee: Feng Qian
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The "bpelContent" folder should not be hard-coded as the only place to search
for BPEL deployment sources - I don't understand why we can't start searching at
the project root.
See also https://jira.jboss.org/jira/browse/JBIDE-5829
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:46 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6170) BPEL source folder should not be hard-coded as "bpelContent"
[
https://jira.jboss.org/browse/JBIDE-6170?page=com.atlassian.jira.plugin.s...
]
Robert (Bob) Brodt commented on JBIDE-6170:
-------------------------------------------
Pavol, this is unrelated to JBIDE-6588, which requires a change in the project facet ID
for BPEL. This JIRA (JBIDE-6170) only addresses the requirement to allow the user to
specify a different folder name (other than bpelContent) for the BPEL process artifacts
(*.bpel, *.wsdl, *.xsd, etc.) when creating a new BPEL project.
BPEL source folder should not be hard-coded as
"bpelContent"
------------------------------------------------------------
Key: JBIDE-6170
URL: https://jira.jboss.org/browse/JBIDE-6170
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm
Affects Versions: 3.1.0.GA
Reporter: Robert (Bob) Brodt
Assignee: Feng Qian
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The "bpelContent" folder should not be hard-coded as the only place to search
for BPEL deployment sources - I don't understand why we can't start searching at
the project root.
See also https://jira.jboss.org/jira/browse/JBIDE-5829
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:59 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6170) BPEL source folder should not be hard-coded as "bpelContent"
[
https://jira.jboss.org/browse/JBIDE-6170?page=com.atlassian.jira.plugin.s...
]
Feng Qian commented on JBIDE-6170:
----------------------------------
Yes, Bob is right. Pavol, if you want to verify this jira, you can change the folder name
when you create a bpel project. Then follow the steps(from jboss bpel doc) to create a
sample bpel projects and files, deploy it into server, if it can run right on server, it
is ok.
BPEL source folder should not be hard-coded as
"bpelContent"
------------------------------------------------------------
Key: JBIDE-6170
URL: https://jira.jboss.org/browse/JBIDE-6170
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm
Affects Versions: 3.1.0.GA
Reporter: Robert (Bob) Brodt
Assignee: Feng Qian
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The "bpelContent" folder should not be hard-coded as the only place to search
for BPEL deployment sources - I don't understand why we can't start searching at
the project root.
See also https://jira.jboss.org/jira/browse/JBIDE-5829
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:24 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6170) BPEL source folder should not be hard-coded as "bpelContent"
[
https://jira.jboss.org/browse/JBIDE-6170?page=com.atlassian.jira.plugin.s...
]
Pavol Srna commented on JBIDE-6170:
-----------------------------------
Guys, I thought that there is something "behind" this, but it is really simple.
Thx. I will close the Jira.
BPEL source folder should not be hard-coded as
"bpelContent"
------------------------------------------------------------
Key: JBIDE-6170
URL: https://jira.jboss.org/browse/JBIDE-6170
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm
Affects Versions: 3.1.0.GA
Reporter: Robert (Bob) Brodt
Assignee: Feng Qian
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The "bpelContent" folder should not be hard-coded as the only place to search
for BPEL deployment sources - I don't understand why we can't start searching at
the project root.
See also https://jira.jboss.org/jira/browse/JBIDE-5829
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:26 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-6170) BPEL source folder should not be hard-coded as "bpelContent"
[
https://jira.jboss.org/browse/JBIDE-6170?page=com.atlassian.jira.plugin.s...
]
Pavol Srna closed JBIDE-6170.
-----------------------------
Verified on JBT 3.2.0.v20101130-1304-H16-Beta2
BPEL source folder should not be hard-coded as
"bpelContent"
------------------------------------------------------------
Key: JBIDE-6170
URL: https://jira.jboss.org/browse/JBIDE-6170
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: bpel, bpm
Affects Versions: 3.1.0.GA
Reporter: Robert (Bob) Brodt
Assignee: Feng Qian
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The "bpelContent" folder should not be hard-coded as the only place to search
for BPEL deployment sources - I don't understand why we can't start searching at
the project root.
See also https://jira.jboss.org/jira/browse/JBIDE-5829
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5605
days inactive
5842
days old
jbosstools-issues@lists.jboss.org
10 comments
4 participants
participants (4)
-
Brian Fitzpatrick (JIRA) -
Feng Qian (JIRA)
-
Pavol Srna (JIRA)
-
Robert (Bob) Brodt (JIRA)