Skip to content

Conversation

@dscho
Copy link
Contributor

@dscho dscho commented Jul 9, 2014

The whole point of the getCallingCodeLocation() method in the TestUtils
class is to be able to determine a unique location for a directory
inside the target/ directory of the current Maven project.

Therefore, code locations in .jar files are not appropriate: there is
no associated target/ directory.

Thanks, Jaspar Jenkins, for running the regression tests so faithfully
and pointing out that the imagej-plugins-uploader-{ssh,webdav} projects
require this change to run their integration tests properly.

Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de

The whole point of the getCallingCodeLocation() method in the TestUtils
class is to be able to determine a unique location for a directory
inside the target/ directory of the current Maven project.

Therefore, code locations in .jar files are not appropriate: there is
no associated target/ directory.

Thanks, Jaspar Jenkins, for running the regression tests so faithfully
and pointing out that the imagej-plugins-uploader-{ssh,webdav} projects
require this change to run their integration tests properly.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
@dscho
Copy link
Contributor Author

dscho commented Jul 9, 2014

@ctrueden I would like to merge this ASAP in order to get the Jenkins jobs for the WebDAV and SSH uploaders passing again... We'll need to bump to 2.26.0 because of the new APIs, right? Do you have other pending changes to include in that release?

... but maybe I should test on the Jenkins server itself whether this change actually fixes the bug ;-) Let me do that first, tomorrow 10am.

@ctrueden
Copy link
Member

ctrueden commented Jul 9, 2014

👍 Looks good on cursory inspection. Testing on the Jenkins server before merging makes total sense!

dscho added a commit that referenced this pull request Jul 9, 2014
TestUtils: valid calling code locations do not include .jar files
@dscho dscho merged commit fc95366 into master Jul 9, 2014
@dscho dscho deleted the test-utils branch July 9, 2014 20:59
@dscho
Copy link
Contributor Author

dscho commented Jul 9, 2014

Tested on Jenkins, fixes the problem!

@dscho
Copy link
Contributor Author

dscho commented Jul 9, 2014

Deployed the cascade and Jenkins is happy again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants