Re: Why Maven all of a sudden
Re: Why Maven all of a sudden
- Subject: Re: Why Maven all of a sudden
- From: Ramsey Gurley <email@hidden>
- Date: Wed, 13 Apr 2016 10:58:09 -0700
I’ve sorta been keeping a list :D
Dependency management is one for me too. We have builds where there are literally three different versions of a jar and it seems entirely like luck right now as to which one we get.
The dependency check plugin is also very high on my reasons to switch list. It can tell me if a dependency has any critical CVE vulnerabilities published. Vulnerable dependency? Fail the build.
Maven gpg plugin can verify the jar I have is really the jar signed by the publisher. Bad signature? Fail the build.
Being able to right-click, download sources and javadocs is awesome. Jars are no longer black boxes. Hover for javadocs. cmd click to see/debug source.
Running unit tests on Jenkins just happens with maven builds. I get a nice graph of test results over time.
Jenkins/maven has a maven release plugin to auto increment snapshot version and deploy release artifacts to Nexus. So I have a fixed version to roll out for staging and then to production. If necessary, the old build is there for a quick rollback without rebuild.
License check plugins to determine if builds are pulling in GPL code on my closed source application. If so, fail the build.
Nexus gives more control over what dependencies are allowed. We can blacklist jars/versions that we deem unacceptable for any reason so those don’t accidentally end up in a build.
And I still feel like I’m just scratching the surface with maven. Every time I look for a solution, maven has one. I bet it even craps ice cream*. There’s 5000+ plugins for maven so I’m sure there’s a maven-crap-rainbow-ice-cream-plugin somewhere out there. :D
* https://www.youtube.com/watch?v=dY6GQUDSZ24
There are some things I don’t love. Mainly due to the fact that I can’t just checkout source and go. I need a settings.xml file, and setting up Nexus was sorta painful, and Eclipse wants me to make a lifecycle mappings xml file to ignore build actions it doesn’t understand. And, most painfully, making Maven work with WO. I’ve been at it off and on for a couple months now. It will be worth it when I’m done, but it hasn’t been an easy change to make.
On Apr 13, 2016, at 10:09 AM, Hugi Thordarson <email@hidden> wrote:
> Because dependency management :). At least that’s by far the largest reason for me. Although you also gain several other nice features along the way.
>
> - hugi
>
>
>> On 13. apr. 2016, at 16:01, Paul Yu <email@hidden> wrote:
>>
>> Why are people moving to Maven?
>>
>> Just curious?
>>
>> Sent from my iPhone
>> Please excuse iOS autocomplete
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden