[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6170) BPEL source folder should not be hard-coded as "bpelContent"
Feng Qian (JIRA)
jira-events at lists.jboss.org
Wed Aug 4 04:54:49 EDT 2010
[ https://jira.jboss.org/browse/JBIDE-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12542920#action_12542920 ]
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
More information about the jbosstools-issues
mailing list