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

[issue#65] bannedRepositories configuration changed based on the plugin documentation #66

Merged
merged 1 commit into from
Sep 18, 2019

Conversation

ochaloup
Copy link
Contributor

@ochaloup ochaloup commented Jun 5, 2019

@darranl
Copy link
Contributor

darranl commented Jun 5, 2019

Which maven version are you using?

@ochaloup
Copy link
Contributor Author

ochaloup commented Jun 6, 2019

@darranl correct, I can't reproduce the issue on maven 3.5.2 which I use on my laptop. But our CI fails with older version 3.2.5. I reproduced the same issue at that maven 3.2.5 on my laptop. The #65 then fixes this trouble.

mvn -version
OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T17:29:23+00:00)
Maven home: /home/jenkins/workspace/btny-pulls-narayana-quickstart/tools/maven
Java version: 1.8.0_181, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.181-3.b13.el7_5.x86_64/jre
Default locale: en_US, platform encoding: ANSI_X3.4-1968
OS name: "linux", version: "3.10.0-693.5.2.el7.x86_64", arch: "amd64", family: "unix"

@darranl
Copy link
Contributor

darranl commented Jun 6, 2019

That makes more sense, was wondering why we didn't have reports sooner of issues.

The later maven versions automatically handle it as a single item for the list without error. I will have a look at merging this for version 36.

@psakar
Copy link
Contributor

psakar commented Jun 6, 2019

May be would be better to enforce maven at least 3.3.9
Older version have dependency resolution related issues anyway
According to https://maven.apache.org/docs/history.html version 3.3.9 is already 3 years old
Only reason for 3.2.5 would be java 6 support, but for new versions of projects this is not valid any more, or is it ?

@ochaloup
Copy link
Contributor Author

ochaloup commented Jun 6, 2019

For our CI I think we have the version to support java 6. But I assume I can change the maven version for quickstart compilation if needed (aka. when supported version is moved to 3.3.9).

Anyway, the reported issues is valid, or not? The documentation says there should be used the List. Or, as the newer versions of maven are capable to work with Strings instead of the List, is it the recommended way how to write a pom.xml to use directly Strings and not bothering with listing the xml subelements?

@darranl
Copy link
Contributor

darranl commented Jun 6, 2019

TBH I think we should go ahead and merge this to bring the configuration in line with the documentation and handle the maven bump as a second step before any tagging if we decide to do that.

@psakar
Copy link
Contributor

psakar commented Jun 6, 2019

+1

@dmlloyd dmlloyd merged commit eab76f1 into jboss:master Sep 18, 2019
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.

Enforcer plugin configuration wrongly defines bannedRepository
4 participants