当使用源代码签入相关jar时，使用Maven仍然有意义吗? [英] Does it still make sense to use Maven when dependent jars are checked in with source code?
问题描述
我们将所有源代码的从属第三方JAR都与源代码一起检查到源代码控制中.在需要时，我们手动将更新下载到第三方JAR，然后将源代码控制中的那些JAR替换为较新的版本.我们尚未感觉到需要使用Maven，因为此过程对我们来说似乎很简单.但是我们是否不使用Maven而错过了有价值的东西?还是我们的方案不保证使用Maven?
We check all of our source code's dependent third-party JARs into source control along with our source code. When needed, we manually download updates to third party JARs and replace those JARs that are in source control with the newer versions. We haven't felt the need to use Maven yet as this process seems simple enough for us. But are we missing something of great value by not using Maven? Or does our scenario not warrant using Maven?
推荐答案
"JAR的变化不大"，我一直都在听.....
"JARs dont change much", I hear this all the time.....
在项目开始时，将罐子存储在SCM中很简单.随着时间的流逝，jar的数量越来越大....等待2或3年，没有人记得这些jar的来源，其许可条款以及最常用的版本(分析安全漏洞时必须知道的重要信息) .....
Storing jars in the SCM is simple in the beginning of the project. Over time the number of jars gets larger and larger.... Wait 2 or 3 years and nobody remembers where the jars came from, what their licensing terms were and most commonly what versions are being used (important to know when analysing security vulnerabilities).....
最近我读过的关于仓库管理器的最佳文章是:
The best article I've read recently making the case for a repository manager is:
一点点大胆，但确实说明了人们一直遇到的技术惯性.
A little irreverant, but does make a valid point about the kind of technical inertia one encounters all the time.
将项目团队从ANT转换到Maven可能会令人恐惧.... Maven的工作方式大不相同，因此我发现最好将其部署在未开发的或冒险的项目团队中.对于老式ANT用户，我建议使用 Apache ivy 插件. Ivy允许这样的团队将其依赖项的管理外包，但保留他们熟悉的构建技术.
Switching a project team from ANT to Maven can be scary.... Maven works quite differently, so I find it is best deployed with greenfield or adventurous project teams. For the old-school ANT users, I recommend using the Apache ivy plugin. Ivy allows such teams to outsource the management of their dependencies but keep the build technology they're comfortable with.
最终，使用Maven的最大好处不是依赖管理.这是标准的构建过程.我已经看到创建标准" ANT构建过程的几次失败尝试.每个构建工程师都有关于标准的意见....Maven强迫用户编写构建插件的方法在开始时似乎很严格，但是就像iPhone最终开发人员发现有一个Maven插件"一样: -)
Ultimately the biggest benefit of using Maven are not dependency management. It's the standized build process. I've seen several failed attempts to create a "standard" ANT build process. Problem every build engineer has his opinion on what the standard should be.... Maven's approach of forcing users to write build plugins may appear restrictive in the beginning, but just like the iPhone eventually developers discover "there's a Maven plugin for that" :-)
这篇关于当使用源代码签入相关jar时，使用Maven仍然有意义吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
