2:52 p.m.
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://jira.jboss.org/jira/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP3, 4.2.1 CP2, 4.2.1 CP1, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
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
11:53 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://jira.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin.s...
]
Kevin Conner closed JBESB-2272.
-------------------------------
Resolution: Out of Date
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://jira.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
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:31 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://jira.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-2272:
--------------------------------
Fix Version/s: 4.9 CP1
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://jira.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Fix For: 4.9 CP1
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
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:31 p.m.
New subject: [JBoss JIRA] Reopened: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://jira.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin.s...
]
Kevin Conner reopened JBESB-2272:
---------------------------------
Looks like this issue has not been addressed so am reopening for investigation.
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://jira.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Fix For: 4.9 CP1
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
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
5:02 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://jira.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin.s...
]
Tom Cunningham reassigned JBESB-2272:
-------------------------------------
Assignee: Tom Cunningham
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://jira.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.9 CP1
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
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
7:19 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://jira.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin.s...
]
Tom Cunningham commented on JBESB-2272:
---------------------------------------
It looks like this issue is limited to qa/junit, qa/quickstarts has nothing that requires
the external binaries.
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://jira.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.9 CP1
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
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
8:08 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://jira.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin.s...
]
Aleksandar Kostadinov commented on JBESB-2272:
----------------------------------------------
I'm not sure how right now tests are organized but at the time of filing the issue I
was thinking about product/ test target. Anyways the idea is to have *all* tests in the
jboss-esb distribution executable against external binaries which means - ability to run
the tests with a classpath pointing at the external binaries.
So if you have tests in other locations then please consider them too.
Hope my explanation makes sense to you.
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://jira.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.9 CP1
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
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
9:29 p.m.
New subject: [JBoss JIRA] Commented: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://jira.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin.s...
]
Tom Cunningham commented on JBESB-2272:
---------------------------------------
Looked at qa/junit and that looks free from references to source/build binaries or
ivy-downloaded third party JARs. The problem must be limited to
product/rosetta/tests.
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://jira.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.9 CP1
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
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
9:04 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://jira.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin.s...
]
Aleksandar Kostadinov commented on JBESB-2272:
----------------------------------------------
I'm not sure which branch are you looking at. But I've run a grep inside the last
ESB version we have tested :
product]$ grep -r "<junit " .
./rosetta/tests/build.xml: <junit printsummary="yes"
haltonerror="${org.jboss.esb.build.haltonerror}"
haltonfailure="${org.jboss.esb.build.haltonfailure}" showoutput="no"
fork="true">
./rosetta/tests/build.xml: <junit printsummary="yes"
haltonerror="${org.jboss.esb.build.haltonerror}"
haltonfailure="${org.jboss.esb.build.haltonfailure}" showoutput="no"
fork="true">
./services/base-project-build.xml: <junit printsummary="yes"
haltonerror="yes" haltonfailure="no" showoutput="no"
fork="true">
./services/soapui-client/build.xml: <junit printSummary="yes"
haltonerror="true" showoutput="true" haltonfailure="true"
fork="true" dir=".">
./etc/schemas/validation/build.xml: <junit printsummary="yes"
haltonerror="yes" haltonfailure="no" showoutput="no"
fork="true">
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://jira.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.9 CP1
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
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
9:38 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://jira.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-2272:
-------------------------------------
I do not believe this is a straight forward a requirement as it first sounds and that work
needs to be done in both product and qa areas.
My understanding is that all our tests should execute against an external set of binaries,
specifically an installation which already has ESB deployed. The complication arises
because of the SOA build process, which selectively installs ESB into the SOA platform,
replacing binaries as necessary.
Another complication is the current effort to mavenise the build, which is being seen as a
higher priority by the platform. It may be better to wait the resolution of that task and
revisit this once it is complete.
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://jira.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.9 CP1
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
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:03 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://issues.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin...
]
Kevin Conner updated JBESB-2272:
--------------------------------
Fix Version/s: 4.9 CP2
(was: 4.9 CP1)
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://issues.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.9 CP2
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:56 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://issues.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin...
]
Martin Vecera updated JBESB-2272:
---------------------------------
Attachment: external-esb.patch
I attached a patch for ESB tag JBESB_4_9_CP1_ER7 used to build SOA-P. It make it possible
to run integration tests against external binaries.
Following features are missing but should be straight forward to implement:
* unit tests running against external binaries
* module tests running against external binaries
Do you think you could implement the missing features and verify my approach?
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://issues.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.9 CP2
Attachments: external-esb.patch
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:04 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://issues.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin...
]
Martin Vecera updated JBESB-2272:
---------------------------------
Attachment: external-esb.patch
I forgot to include one fix so reattaching the file.
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://issues.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.9 CP2
Attachments: external-esb.patch, external-esb.patch
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:08 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://issues.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin...
]
Martin Vecera updated JBESB-2272:
---------------------------------
Attachment: (was: external-esb.patch)
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://issues.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.9 CP2
Attachments: external-esb.patch
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:33 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://issues.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin...
]
Tom Cunningham updated JBESB-2272:
----------------------------------
Fix Version/s: 4.10 CP1
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://issues.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.9 CP2, 4.10 CP1
Attachments: external-esb.patch
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:09 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://issues.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin...
]
Tom Cunningham commented on JBESB-2272:
---------------------------------------
Patch has been checked in, needs to be extended to unit tests.
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://issues.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.9 CP2, 4.10 CP1
Attachments: external-esb.patch
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:35 p.m.
New subject: [JBoss JIRA] Updated: (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://issues.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin...
]
Tom Cunningham updated JBESB-2272:
----------------------------------
Fix Version/s: 4.11
(was: 4.9 CP2)
(was: 4.10 CP1)
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://issues.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.11
Attachments: external-esb.patch
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:55 p.m.
New subject: [JBoss JIRA] (JBESB-2272) ESB testable against external binaries (product test suite)
[
https://issues.jboss.org/browse/JBESB-2272?page=com.atlassian.jira.plugin...
]
Tom Cunningham updated JBESB-2272:
----------------------------------
Fix Version/s: 4.12
(was: 4.11)
ESB testable against external binaries (product test suite)
-----------------------------------------------------------
Key: JBESB-2272
URL: https://issues.jboss.org/browse/JBESB-2272
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Testing
Affects Versions: 4.2.1 CP1, 4.2.1 CP2, 4.2.1 CP3, 4.2.1 CP4
Reporter: Aleksandar Kostadinov
Assignee: Tom Cunningham
Fix For: 4.12
Attachments: external-esb.patch
When running the ESB test suite against external binaries, there is currently a mismatch
between libraries downloaded by the test suite and libraries found in the external
distribution. This makes running the suite against the external JBoss AS distribution
meaningless because doesn't prove ESB will work with the libraries found in the JBoss
AS server.
As a solution I see, the various junit tasks run by the testsuite should have classpath
point at the libraries in the JBoss AS rather than these generated during build and
downloaded by the build script. Running the test suite against external binaries should be
the same as verifying an ESB installation (be it on top of JBoss AS or standalone).
The issue supersedes JBESB-1513 and is the cause of JBESB-1711.
--
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
4468
days inactive
5587
days old
17 comments
4 participants
participants (4)
-
Aleksandar Kostadinov (JIRA) -
Kevin Conner (JIRA)
-
Martin Vecera (JIRA)
-
Tom Cunningham (JIRA)