[JBoss JIRA] Created: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
9:29 p.m.
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Fix For: 3.2.2.M2
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why your
editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:23 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick updated JBIDE-9771:
-------------------------------------
Attachment: no_bpel_action_jbide-9771.jpg
Here's a screen shot clearly showing that the BPELInvoke class is in the project
classpath and the New Action menu where we don't see the BPEL Action.
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Fix For: 3.2.2.M2
Attachments: no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:06 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich resolved JBIDE-9771.
------------------------------------------
Resolution: Done
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:06 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich updated JBIDE-9771:
-----------------------------------------
Fix Version/s: 3.3.0.M4
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:30 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick commented on JBIDE-9771:
------------------------------------------
Thanks Slava!
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:15 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick updated JBIDE-9771:
-------------------------------------
Priority: Blocker (was: Major)
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:13 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-9771:
----------------------------------------------
It seems that test is run without rebuilding plugin org.jboss.tools.esb.core. Maybe it was
not enough to just modify resources? Should we also change versions in manifest, pom,
etc?
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:14 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick commented on JBIDE-9771:
------------------------------------------
Yes, there are ripples there. I've asked Nick to comment on the particulars, but
I'm betting it's all related.
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:09 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-9771:
-----------------------------------
@Brian: I've updated the root esb/pom.xml files to better explain how to build w/ mvn.
Note that the profiles got renamed between 32x and 33x (I dropped the confusing
"-trunk" suffix):
http://anonsvn.jboss.org/repos/jbosstools/trunk/esb/pom.xml
http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.x/esb/p...
As to the other issue -- I'm going to try building trunk locally using Tycho 0.13.0,
which should solve the timestamp problem (sometimes Tycho resolves stuff on the server in
GMT-4 (Eastern) as NEWER than something you built locally). This is fixed w/ Tycho 0.13.0,
apparently.
{code}
$ mvn clean install -DmavenVersion=0.13.0
{code}
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:09 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-9771 at 10/3/11 8:09 PM:
------------------------------------------------------------
@Brian: I've updated the root esb/pom.xml files to better explain how to build w/ mvn.
Note that the profiles got renamed between 32x and 33x (I dropped the confusing
"-trunk" suffix):
http://anonsvn.jboss.org/repos/jbosstools/trunk/esb/pom.xml
http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.x/esb/p...
As to the other issue -- I'm going to try building trunk locally using Tycho 0.13.0,
which should solve the timestamp problem (sometimes Tycho resolves stuff on the server in
GMT-4 (Eastern) as NEWER than something you built locally). This is fixed w/ Tycho 0.13.0,
apparently.
{code}
$ mvn clean install -DtychoVersion=0.13.0
{code}
was (Author: nickboldt):
@Brian: I've updated the root esb/pom.xml files to better explain how to build w/
mvn. Note that the profiles got renamed between 32x and 33x (I dropped the confusing
"-trunk" suffix):
http://anonsvn.jboss.org/repos/jbosstools/trunk/esb/pom.xml
http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.x/esb/p...
As to the other issue -- I'm going to try building trunk locally using Tycho 0.13.0,
which should solve the timestamp problem (sometimes Tycho resolves stuff on the server in
GMT-4 (Eastern) as NEWER than something you built locally). This is fixed w/ Tycho 0.13.0,
apparently.
{code}
$ mvn clean install -DmavenVersion=0.13.0
{code}
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:21 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-9771 at 10/3/11 8:19 PM:
------------------------------------------------------------
@Brian: I've updated the root esb/pom.xml files to better explain how to build w/ mvn.
Note that the profiles got renamed between 32x and 33x (I dropped the confusing
"-trunk" suffix):
http://anonsvn.jboss.org/repos/jbosstools/trunk/esb/pom.xml
http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.x/esb/p...
As to the other issue -- I've tried to build trunk locally using Tycho 0.13.0, which
should solve the timestamp problem (sometimes Tycho resolves stuff on the server in GMT-4
(Eastern) as NEWER than something you built locally). This is fixed w/ Tycho 0.13.0,
apparently.
{code}
$ mvn clean install -DtychoVersion=0.13.0
{code}
But this still fails the one test suite:
{code}
[INFO] org.jboss.tools.esb.core.test ..................... FAILURE [35.062s]
testFTPExample(org.jboss.tools.esb.core.test.ESBModelTest) Time elapsed: 1.127 sec
<<< FAILURE!
junit.framework.AssertionFailedError: Wrong entity for jboss-esb-ftp.xml
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at
org.jboss.tools.esb.core.test.ESBModelTest.getFileObject(ESBModelTest.java:528)
at
org.jboss.tools.esb.core.test.ESBModelTest.getFileObject(ESBModelTest.java:520)
etc.
{code}
Next up, building against wholly local built files:
{code}
cd ~/trunk/build; mvn3 clean install -Pesb-bootstrap -DtychoVersion=0.13.0
{code}
was (Author: nickboldt):
@Brian: I've updated the root esb/pom.xml files to better explain how to build w/
mvn. Note that the profiles got renamed between 32x and 33x (I dropped the confusing
"-trunk" suffix):
http://anonsvn.jboss.org/repos/jbosstools/trunk/esb/pom.xml
http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.x/esb/p...
As to the other issue -- I'm going to try building trunk locally using Tycho 0.13.0,
which should solve the timestamp problem (sometimes Tycho resolves stuff on the server in
GMT-4 (Eastern) as NEWER than something you built locally). This is fixed w/ Tycho 0.13.0,
apparently.
{code}
$ mvn clean install -DtychoVersion=0.13.0
{code}
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: buildlog.esb.4.txt, no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:21 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Nick Boldt updated JBIDE-9771:
------------------------------
Attachment: buildlog.esb.4.txt
Log of local build w/ tycho 0.13.0.
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: buildlog.esb.4.txt, no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:23 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-9771 at 10/3/11 8:21 PM:
------------------------------------------------------------
@Brian: I've updated the root esb/pom.xml files to better explain how to build w/ mvn.
Note that the profiles got renamed between 32x and 33x (I dropped the confusing
"-trunk" suffix):
http://anonsvn.jboss.org/repos/jbosstools/trunk/esb/pom.xml
http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.x/esb/p...
As to the other issue -- I've tried to build trunk locally using Tycho 0.13.0, which
should solve the timestamp problem (sometimes Tycho resolves stuff on the server in GMT-4
(Eastern) as NEWER than something you built locally). This is fixed w/ Tycho 0.13.0,
apparently.
{code}
$ mvn clean install -DtychoVersion=0.13.0
{code}
But this still fails the one test suite:
{code}
[INFO] org.jboss.tools.esb.core.test ..................... FAILURE [35.062s]
testFTPExample(org.jboss.tools.esb.core.test.ESBModelTest) Time elapsed: 1.127 sec
<<< FAILURE!
junit.framework.AssertionFailedError: Wrong entity for jboss-esb-ftp.xml
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at
org.jboss.tools.esb.core.test.ESBModelTest.getFileObject(ESBModelTest.java:528)
at
org.jboss.tools.esb.core.test.ESBModelTest.getFileObject(ESBModelTest.java:520)
(see attached file buildlog.esb.4.txt)
{code}
Next up, building against wholly local built files:
{code}
cd ~/trunk/build; mvn3 clean install -Pesb-bootstrap -DtychoVersion=0.13.0
{code}
was (Author: nickboldt):
@Brian: I've updated the root esb/pom.xml files to better explain how to build w/
mvn. Note that the profiles got renamed between 32x and 33x (I dropped the confusing
"-trunk" suffix):
http://anonsvn.jboss.org/repos/jbosstools/trunk/esb/pom.xml
http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.x/esb/p...
As to the other issue -- I've tried to build trunk locally using Tycho 0.13.0, which
should solve the timestamp problem (sometimes Tycho resolves stuff on the server in GMT-4
(Eastern) as NEWER than something you built locally). This is fixed w/ Tycho 0.13.0,
apparently.
{code}
$ mvn clean install -DtychoVersion=0.13.0
{code}
But this still fails the one test suite:
{code}
[INFO] org.jboss.tools.esb.core.test ..................... FAILURE [35.062s]
testFTPExample(org.jboss.tools.esb.core.test.ESBModelTest) Time elapsed: 1.127 sec
<<< FAILURE!
junit.framework.AssertionFailedError: Wrong entity for jboss-esb-ftp.xml
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at
org.jboss.tools.esb.core.test.ESBModelTest.getFileObject(ESBModelTest.java:528)
at
org.jboss.tools.esb.core.test.ESBModelTest.getFileObject(ESBModelTest.java:520)
etc.
{code}
Next up, building against wholly local built files:
{code}
cd ~/trunk/build; mvn3 clean install -Pesb-bootstrap -DtychoVersion=0.13.0
{code}
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: buildlog.esb.4.txt, no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:18 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Nick Boldt updated JBIDE-9771:
------------------------------
Attachment: buildlog.esb.6.txt
Same failure regardless of Tycho version used, or if I build upstream locally or
remotely.
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: buildlog.esb.4.txt, buildlog.esb.6.txt,
no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:42 a.m.
New subject: [JBoss JIRA] (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-9771:
--------------------------------------
BTW last ESB build failed with
{code}[ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.12.0:test
(default-test) on project org.jboss.tools.esb.core.test: Execution default-test of goal
org.eclipse.tycho:tycho-surefire-plugin:0.12.0:test failed: Could not download artifacts
from any repository
[ERROR] osgi.bundle,org.jboss.tools.esb.project.core,1.5.1.v20111003-2023-H484-M4
[ERROR] osgi.bundle,org.jboss.tools.esb.core,1.5.0.v20111003-2023-H484-M4
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.eclipse.tycho:tycho-surefire-plugin:0.12.0:test (default-test) on project
org.jboss.tools.esb.core.test: Execution default-test of goal
org.eclipse.tycho:tycho-surefire-plugin:0.12.0:test failed: Could not download artifacts
from any repository
osgi.bundle,org.jboss.tools.esb.project.core,1.5.1.v20111003-2023-H484-M4
osgi.bundle,org.jboss.tools.esb.core,1.5.0.v20111003-2023-H484-M4{code}
and it is related to JBIDE-8667
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: buildlog.esb.4.txt, buildlog.esb.6.txt,
no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:22 a.m.
New subject: [JBoss JIRA] (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick commented on JBIDE-9771:
------------------------------------------
It's also related to JBIDE-9802 with the deadlock.
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: buildlog.esb.4.txt, buildlog.esb.6.txt,
no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:50 a.m.
New subject: [JBoss JIRA] (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Brian Fitzpatrick resolved JBIDE-9771.
--------------------------------------
Resolution: Done
Test seems to be working now - see blue build -
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_stable_branch.compon...
Waiting to see if fixed on 3.3, but suspect we're ok there as well.
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: buildlog.esb.4.txt, buildlog.esb.6.txt,
no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:09 p.m.
New subject: [JBoss JIRA] (JBIDE-9771) JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action menu selections
[
https://issues.jboss.org/browse/JBIDE-9771?page=com.atlassian.jira.plugin...
]
Len DiMaggio closed JBIDE-9771.
-------------------------------
Verified fixed in:
Version: 4.1.1.CR1
Build id: v20111018-0116-H1068-CR1
Build date: 20111018-0116
JBDS 4.1.1 - ESB OOTB action BPELInvoke not included in OOT action
menu selections
----------------------------------------------------------------------------------
Key: JBIDE-9771
URL: https://issues.jboss.org/browse/JBIDE-9771
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.2.2.M1
Reporter: Len DiMaggio
Assignee: Viacheslav Kabanovich
Priority: Blocker
Fix For: 3.2.2.M2, 3.3.0.M4
Attachments: buildlog.esb.4.txt, buildlog.esb.6.txt,
no_bpel_action_jbide-9771.jpg
See attached screenshots (in JBDS-1865) - if an ESB project is created, and SOA-P 5.2 ER4
server is defined as the runtime - the BPELInvoke action is not included in the OOTB
action list.
I also tried explicitly adding the
server/production/deploy/riftsaw-esb.esb/lib/jbossesb-bpel-2.3.1.Final.jar file to the
runtime and the ESB project classpath.
Slava, can you look into this? If the file is on the classpath, I'm wondering why
your editor tweak (JBIDE-6609) isn't working in SOA-P 5.2.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4633
days inactive
4659
days old
jbosstools-issues@lists.jboss.org
17 comments
7 participants
participants (7)
-
Brian Fitzpatrick (Commented) (JIRA) -
Brian Fitzpatrick (JIRA)
-
Brian Fitzpatrick (Resolved) (JIRA)
-
Denis Golovin (Commented) (JIRA)
-
Len DiMaggio (Closed) (JIRA)
-
Nick Boldt (JIRA)
-
Viacheslav Kabanovich (JIRA)