This repository has been archived by the owner on Nov 9, 2017. It is now read-only.
Maven build as an alternative to Gradle #83
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 3 commits
March 26, 2015 15:55
Also make helper class GitApiMockedResult a static inner class of GitApiTest so as to avoid two classes on top level (looks ugly in IDEs such as IntelliJ IDEA).
Also clean up dependency problems detected by Maven Dependency Plugin (used undeclared and unused declared dependencies). Finally, add a Maven Assembly build step which creates an executable JAR file incl. manifest pointing to entry point com.entagen.jenkins.Main.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi.
I had problems building with Gradle here in my firewalled environment. Also, I am a total Gradle noob. Thus I decided to create a clean Maven build from scratch for your project. See my commit comments for further information. Maybe you even want to consider publishing your plugin on Maven Central as a service to your users. That way it would not be necessary anymore to use Gradle on the Jenkins server (this led to raised eyebrows from our admins) and compile the project on the fly.
Kind regards
Alexander Kriegisch