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

Define "grader" and "haltOnFailingCoverage" Maven properties #349

Open
DavidWhitlock opened this issue Jul 31, 2021 · 2 comments
Open

Define "grader" and "haltOnFailingCoverage" Maven properties #349

DavidWhitlock opened this issue Jul 31, 2021 · 2 comments
Assignees

Comments

@DavidWhitlock
Copy link
Collaborator

Several students have been confused by the "errors" reported by IntelliJ related to the undefined grader and haltOnFailingCoverage properties referenced in the grader Maven profile.

I should investigate if I can define the properties in such a way so that the grader profile still behaves as expected without causing these errors.

Perhaps I can move the declaration of the grader profile to a parent POM.

@DavidWhitlock
Copy link
Collaborator Author

With regards to the use of ${grader} that IntelliJ doesn't like:

      <activation>
        <activeByDefault>${grader}</activeByDefault>
      </activation>

There is a way to activate a profile based on a property being set:

https://maven.apache.org/guides/introduction/introduction-to-profiles.html

However, I have a feeling that it is this way for a reason. I added in 2928338 to get the archetype integration tests to work.

@DavidWhitlock
Copy link
Collaborator Author

I tried using a custom settings.xml file for the tests: https://maven.apache.org/archetype/maven-archetype-plugin/integration-test-mojo.html#settingsFile

But that didn't seem to activate the grader profile.

I tried changing the profile to be activated by a property. Even though I seta <property> in the pom.xml, the profile still wasn't activated.

I can at least get rid of the "haltOnFailingCoverage" warning by defining a property in the top-level POM. The (valid) complain about activeByDefault is that the value isn't a boolean. I don't know how to get rid of that.

@DavidWhitlock DavidWhitlock self-assigned this Nov 21, 2021
DavidWhitlock added a commit that referenced this issue Nov 21, 2021
…ty in the top-level POM so that IntelliJ doesn't complain about it.
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

No branches or pull requests

1 participant