构建 WSO2 Carbon 标签的合适方法是什么? [英] What is the appropriate way to build WSO2 Carbon tags?

查看:26
本文介绍了构建 WSO2 Carbon 标签的合适方法是什么?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试并排构建 WSO2 Carbon 的多个标签以进行比较,但我担心我可能会遗漏有关目录布局以及如何进行构建的内容.请问我可以帮忙吗?

I'm trying to build multiple tags of WSO2 Carbon side-by-side for comparison purposes, but I'm concerned I may be missing something about the directory layout and how to do the builds. Please could I have some help?

目前,我已经检查了我认为的相关标签来自:

At present, I've checked out what I think are the relevant tags from:

  • https://svn.wso2.org/repos/wso2/tags/carbon/3.0.0/
  • https://svn.wso2.org/repos/wso2/tags/carbon/3.1.0_core/
  • https://svn.wso2.org/repos/wso2/tags/carbon/3.2.0/
  • https://svn.wso2.org/repos/wso2/tags/carbon/3.2.2/
  • https://svn.wso2.org/repos/wso2/tags/carbon/3.2.3/

然后,我尝试从每个结帐的顶级目录运行 Maven 构建(以各种方式,有些涉及跳过测试,有些则不),结果各不相同(几乎所有这些都以一种方式不成功或另一个,无论是由于缺少工件、测试失败还是其他原因).我还尝试从 .../carbon/3.2.2/patch-releases/3.2.2 目录和 .../carbon/3.2.3/patch-releases/3.2.3 构建 3.2.2 和 3.2.3目录,根据@ThiliniIshaka 在这里给出的答案:

I've then tried running Maven builds from the top-level directories of each of the checkouts (in various ways, some involving skipping the tests and others not), with varying results (almost all of them unsuccessful in one way or another, whether due to missing artifacts, failing tests or other reasons). I also tried building 3.2.2 and 3.2.3 from the .../carbon/3.2.2/patch-releases/3.2.2 directory and the .../carbon/3.2.3/patch-releases/3.2.3 directories, as per the answer @ThiliniIshaka gave here:

身份服务器的WSO2源代码(wso2is-3.2.3-src.zip)总是构建错误

这似乎对 3.2.2 有效(经过一些摆弄之后),但是 3.2.3 的一些测试失败了,这会拉低构建(我可以使用 Maven 的 -fn 标志使其工作,但是只会导致看起来不完整的构建).此外,较早的标签似乎没有相应的补丁发布目录,因此即使我将它用于 3.2.3,同样的技术也不适用于它们.

This seemed to work (after some fiddling around) for 3.2.2, but some of the tests for 3.2.3 fail and this pulls down the build (I can make it work with the -fn flag to Maven, but that just results in what looks like an incomplete build). Furthermore, the earlier tags don't seem to have a corresponding patch-releases directory, so the same technique won't work for them even if I get it working for 3.2.3.

顺便说一句,我也对诸如 3.2.2 标签包含补丁发布下的 3.2.3 目录等内容深感困惑.

As an aside, I'm also deeply confused by things such as the 3.2.2 tag containing a 3.2.3 directory under patch-releases, etc.

所有这一切让我觉得我可能在某些基本方面错过了重点:)

All of this leads me to think I may be missing the point in some fundamental manner :)

因此我的问题是:

  1. 我是否首先检查了正确的内容?
  2. 请问我应该从哪些目录以及如何构建每个标签?
  3. 我是否需要为所有标签使用相同版本的 Maven?
  4. 请问是否有针对各种不同版本的良好构建文档来解释其中的一些内容?我找到了各种技术博客,但似乎没有什么万无一失和全面的(我可能找错地方了).

非常感谢.

推荐答案

回答上述问题;

  1. 是的,这些标签是为 carbon 的相关分支和点版本创建的.
  2. 正如上一个帖子所建议的那样 [1]您可以构建源代码,您能否向我们提供构建源代码时遇到的问题?
  3. 是的,你需要用 maven2 构建上面的标签.只有主干 [2] (正常开发的地方)需要 maven 3.
  4. 博文中提供了一些提示.使用 mvn install 从根级别开始(要跳过正在运行的测试,请使用 mvn install -Dmaven.test.skip=true 构建).如果要构建与点发布相关的标签,请从 patch-releases 目录构建.
  1. Yes, these tags are created for relevant branch and point releases of carbon.
  2. As the previous thread suggests [1] you can build the source, could you please provide us with the issues you get when building the source?
  3. Yes, you need to build above tags with maven2. Only the trunk [2] (where the normal developments going on) needs maven 3.
  4. Some hints are provided in this blog post. Start from the root level with mvn install (to skip running tests, build with mvn install -Dmaven.test.skip=true). If you are to build tags related to point releases, build from patch-releases directory.

希望这会有所帮助.

谢谢

这篇关于构建 WSO2 Carbon 标签的合适方法是什么?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆