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

Feature/build cleanup #430

Merged
merged 11 commits into from
Aug 12, 2019
Merged

Feature/build cleanup #430

merged 11 commits into from
Aug 12, 2019

Conversation

nedtwigg
Copy link
Member

@nedtwigg nedtwigg commented Aug 9, 2019

Master is passing again. I pushed d5f8251 straight to master and updated our encrypted environment variables to get it working.

I'd like to use this PR as a misc opportunity to cleanup the build. Having a fix for #429 would be great, but I don't have any ideas.

```
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for com.diffplug.spotless:spotless-maven-plugin:maven-plugin:1.25.0-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.codehaus.plexus:plexus-resources:jar -> version ${plexus.resources.version} vs 1.0.1 @ line 71, column 17
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING] 
```
@nedtwigg
Copy link
Member Author

nedtwigg commented Aug 9, 2019

Turns out we are double-specifying the plexus-resources jar, which is causing this warning:

[WARNING] 
[WARNING] Some problems were encountered while building the effective model for com.diffplug.spotless:spotless-maven-plugin:maven-plugin:1.25.0-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.codehaus.plexus:plexus-resources:jar -> version ${plexus.resources.version} vs 1.0.1 @ line 71, column 17
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING] 

I will fix that in the next commit.

@nedtwigg nedtwigg force-pushed the feature/buildCleanup branch from 0b69e3b to 59d3ce4 Compare August 12, 2019 20:18
@nedtwigg nedtwigg merged commit dced8fa into master Aug 12, 2019
@nedtwigg nedtwigg deleted the feature/buildCleanup branch August 12, 2019 22:27
@jbduncan
Copy link
Member

Wow, great work on the build improvements @nedtwigg!

However, I'm unclear as to why not all of the compiles in plugin-maven/build.gradle have been turned into implementations, and I wondered if you could clarify things for me?

@nedtwigg
Copy link
Member Author

The plugin-maven build doesn't use any of the normal gradle tasks. It is just used to populate a maven pom.xml, and the whole build happens inside maven. The plugin-maven jar is actually built by maven, not a gradle compile/jar task.

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.

2 participants