Skip to content

Conversation

@greggdonovan
Copy link

Add a test for Bazel support for the PluginProcessor, which does not work on 2.12.1 due to System.out calls, but works with this PR.

…elease-2.x.

Add a test for Bazel support for the PluginProcessor, which does not work on 2.12.1 due to System.out calls, but works with this PR.
Copy link
Member

@jvz jvz left a comment

Choose a reason for hiding this comment

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

Do you know of any way this can read the project version from the pom.xml instead of using a hard-coded version number in the file names? Also, if you can use bazel to build and run a unit test, you could make a fairly minimal one to verify that the plugin is initialized by the config.

Also, if you rebase from release-2.x, you should get a working Travis config (I think).

@rgoers
Copy link
Member

rgoers commented Dec 7, 2019

I understand the desire to get rid of System.out calls but why is bazel being added?

@rgoers
Copy link
Member

rgoers commented Feb 15, 2020

I committed the change without the bazel stuff.

@rgoers rgoers closed this Feb 15, 2020
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