Conversation
…ts to pass during release as well) TODO: Upgrade itests to use newer pax-exam that allows for running current project version as the version number
|
Strange.. the failure in the integration test is solved by the updating of the project version in the pax-exam setup and works-for-me locally. I imagine travis-ci cleans out the local repo between builds. Thoughts? |
|
Have you tried cleaning your local maven repro? |
|
@laeubi the tests all pass locally. The pax-exam test previously had version 3.0.5-SNAPSHOT specified for the pax-wicket version to be tested. I specified 4.0.0 for it to stabilize temporarily, and not need to be changed every build. see: IssueTest.java#L80 The full fix is to update pax-exam and leverage the feature that allows it to use the current project version as the feature version. That being said, Travis CI build still isn't getting the same results as my local build. |
2 participants
No description provided.