[
https://issues.apache.org/jira/browse/AXIS2-5795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353767#comment-15353767
]
Andreas Veithen commented on AXIS2-5795:
----------------------------------------
Can you please condense the description of the issue into a simple sequence of
commands and steps that actually reproduce the issue?
> Failing tests because of SNAPSHOT vs. release changes in pom.xml
> ----------------------------------------------------------------
>
> Key: AXIS2-5795
> URL: https://issues.apache.org/jira/browse/AXIS2-5795
> Project: Axis2
> Issue Type: Bug
> Components: jaxws, UDP transport
> Affects Versions: 1.7.2, 1.7.3
> Environment: Windows 8.1 x64 Prof., Tomcat 7.0.68, JDK 1.8.0_92 x64
> Reporter: Thorsten Schöning
>
> I have a strange problem with release versions of 1.7.2 and 1.7.3 and there's
> even a difference between .2 and .3: With 1.7.2 I get the following two
> exceptions, while with 1.7.3 I only get the first one regarding UDP:
> {CODE}
> Running org.apache.axis2.transport.udp.UDPTest
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.899 sec <<<
> FAILURE!
> testSoapOverUdpWithEchoService(org.apache.axis2.transport.udp.UDPTest) Time
> elapsed: 0.867 sec <<< ERROR!
> org.apache.axis2.AxisFault: The system is attempting to engage a module that
> is not available: addressing
> at
> org.apache.axis2.engine.AxisConfiguration.engageModule(AxisConfiguration.java:576)
> at
> org.apache.axis2.transport.UtilsTransportServer.enableAddressing(UtilsTransportServer.java:83)
> at
> org.apache.axis2.transport.udp.UtilsUDPServer.<init>(UtilsUDPServer.java:37)
> at
> org.apache.axis2.transport.udp.UDPTest.createServer(UDPTest.java:42)
> Running org.apache.axis2.transport.udp.UDPTransportTest
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.524 sec
> {CODE}
> {CODE}
> Running org.apache.axis2.jaxws.dispatch.OMElementDispatchTest
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.154 sec <<<
> FAILURE!
> testOMElementDispatchWithParsedEntityReader(org.apache.axis2.jaxws.dispatch.OMElementDispatchTest)
> Time elapsed: 0.396 sec <<< FAILURE!
> java.lang.AssertionError: Not true that <<test:echoOMElement
> xmlns:test="http://org/apache/axis2/jaxws/test/SOAPENVELOPE";><test:output><test:data>SAMPLE
> RESPONSE MESSAGE</test:data></test:output></test:echoOMElement>> is an
> instance of <org.apache.axiom.om.OMSourcedElement>. It is an instance of
> <org.apache.axiom.om.impl.llom.OMElementImpl>
> at
> com.google.common.truth.FailureStrategy.fail(FailureStrategy.java:24)
> at
> com.google.common.truth.FailureStrategy.fail(FailureStrategy.java:20)
> at
> com.google.common.truth.Subject.failWithBadResults(Subject.java:337)
> at com.google.common.truth.Subject.isInstanceOf(Subject.java:166)
> at
> org.apache.axis2.jaxws.dispatch.OMElementDispatchTest.testOMElementDispatchWithParsedEntityReader(OMElementDispatchTest.java:373)
> [...]
> [INFO] Apache Axis2 - JAXWS Integration Tests ............. FAILURE [05:44
> min]
> {CODE}
> The interesting thing is that I don't get those exceptions if I don't use the
> released versions, but one rev before the release itself. And yes, the last
> rev is only renaming "1.7.2-SNAPSHOT" and such to "1.7.2" and changing some
> SCM URLs and stuff like that. But the first rename is exactly the problem:
> After a lot of trial&error I found that renaming within 2 pom.xml files
> triggers or resolves the problem:
> {CODE}
> apidocs/pom.xml
> modules/transport/udp/pom.xml
> {CODE}
> In 1.7.2 I need to change both files, in 1.7.3 only the latter UDP one. And
> the change really is only the following:
> {CODE}
> <parent>
> <groupId>org.apache.axis2</groupId>
> <artifactId>axis2</artifactId>
> <version>1.7.2</version>
> </parent>
> {CODE}
> to
> {CODE}
> <parent>
> <groupId>org.apache.axis2</groupId>
> <artifactId>axis2</artifactId>
> <version>1.7.2-SNAPSHOT</version>
> </parent>
> {CODE}
> The tests pass right after that change and another ~20 minutes of waiting.
> ;-) I used the following rev for testing:
> {QUOTE}
> Revision: 1741997
> Autor: veithen
> Datum: Montag, 2. Mai 2016 18:10:53
> Meldung:
> [maven-release-plugin] prepare release v1.7.2
> {QUOTE}
> I updated my branch to that rev and reverted the both files mentioned above,
> so those two files kept their SNAPSHOT suffix. The tests pass then. If I
> don't revert the both files, the tests fail each and every time.
> Just to be sure I deleted my local .m2 directory, but that didn't change a
> thing, the tests from the release tags of 1.7.2 and 1.7.3 still fail without
> changing the mentioned files back to "-SNAPSHOT", else they succeed. I tested
> the current 1.7 branch on HEAD as well and those tests succeed without manual
> modifications, I guess because the pom.xml still contains "-SNAPSHOT".
> Any idea on why the releases fail and what "-SNAPSHOT" in some files may
> change?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
