[
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