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

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

问题描述

我试图建立WSO2碳并排侧的多个标签出于比较的目的,但我担心我可能会丢失一些有关的目录布局和怎么做的构建。请我可以有一些帮助?

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?

在present,我已经签出什么,我认为是相关标签的:

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从每个检出的顶级目录建立(以不同的方式,有些涉及跳过测试和其他人没有),结果各不相同(以某种方式几乎所有的人不成功或另外,无论是由于缺少文物,测试失败或其他原因)。我也尝试建立从3.2.2和3.2.3 ... /炭/ 3.2.2 /补丁发布/ 3.2.2目录和... /炭/ 3.2.3 /补丁发布/ 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:

<一个href=\"http://stackoverflow.com/questions/10164438/wso2-source$c$c-of-identity-server-wso2is-3-2-3-src-zip-is-always-built-with-e\">WSO2身份认证服务器(wso2is-3.2.3-src.zip)来源$ C ​​$ C总是与错误内置

这似乎工作为3.2.2(一些摆弄周围后),但某些测试为3.2.3失败,这拉低版本(我可以把它与-fn标志Maven的工作,但只是导致看起来像一个不完整的版本)。此外,早期的标签似乎并不具有相应的补丁发布目录,所以同样的技术将不为他们工作,即使我得到它的工作为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.3目录3.2.2标签等。

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. 是否有各种不同版本的解释一些这方面请任何好身材文档?我发现各种技术的博客,但似乎没有什么万无一失和COM prehensive(我可能找错了地方)。

非常感谢。

推荐答案

回答了上面的查询;


  1. 是的,是碳的相关分支点版本创建这些标签。

  2. 作为previous线程建议<一href=\"http://stackoverflow.com/questions/10164438/wso2-source$c$c-of-identity-server-wso2is-3-2-3-src-zip-is-always-built-with-e\">[1]你可以构建源,你可以请向我们提供构建源时,你得到的问题?

  3. 是的,你需要建立上面的标签与Maven2的。
    只有躯干 [2] (其中正在进行的正常发展)需要行家3。

  4. 在此博客文章<中提供了一些提示/一>。
    从根水​​平 MVN开始安装(跳过运行测试,建立与 MVN安装-Dmaven.test.skip =真)。如果你是构建点发布相关的标记,从补丁发布建立目录。

  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碳标签的适当方法?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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