Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add missing catches to allow compilation... #343

Closed
wants to merge 1 commit into from

Conversation

nickboldt
Copy link
Contributor

add missing catches to allow compilation against older testng versions (eg., Fedora 24-25)

Signed-off-by: nickboldt nboldt@redhat.com

…s (eg., Fedora 24-25)

Signed-off-by: nickboldt <nboldt@redhat.com>
@@ -65,6 +65,10 @@ public Object execute(ExecutionEvent event) throws ExecutionException {
TestNGPlugin.log(e1);
} catch (CoreException e) {
TestNGPlugin.log(e);
} catch (ParserConfigurationException e) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

these catch blocks failed the travis build.
actually, I don't mind if you catch a more generic Exception

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it's weird... this worked for me inside a mock build for F24 and F25, and worked in Eclipse using PDE to build automatically. But failed your travis build. So... maybe you're right - a generic Exception catch might be the better solution. I'll concoct a different patch and submit that instead.

@@ -228,6 +231,10 @@ private void createXmlFileFromTemplate(XMLStringBuffer suiteBuffer, String fileN
}
} catch (IOException e) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nickboldt , I think you can catch the generic Exception here rather than add more catch block which fail the travis build

@missedone
Copy link
Collaborator

@nickboldt, would you like to update the PR so that I can make it into 6.12 release?
thx

@nickboldt
Copy link
Contributor Author

Replaced by #353

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.

None yet

2 participants