blocks|key|1520351|text|如果你可以可靠地、动态地创建它，那么就不要签入它。这会引起混乱。在这种情况下，它类似于签入.class文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1520352|相反，请签入构建文件和用来创建它的工件，并让构建来处理它。|1520353|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you can reliably, dynamically create it, the don't check it in. That's going to cause confusion. In this situation it's analogous to checking in .class files.

Rather, check in the build file and the artifacts you use to create it, and let the build take care of it.

blocks|key|1024147|text|我们使用Eclipse。我发现，让Eclipse不会隐藏的文件签入对我们来说很好。你签出了这个项目，然后就可以开始了。没有更多的蚂蚁东西要运行，或者记得要运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1024148|如果你总是使用ant构建(例如，如果你来自Netbeans商店)，那么只检入那些原始的文件。所有从其他地方复制的文件都不应该显式检入。|1024149|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

We work with Eclipse. I have found that having the files that Eclipse do not hide checked in work well for us. You check out the project, and you are ready to go. No further ant stuff to run or remember to run.

If you build with ant always (e.g. if you come from a Netbeans shop) then check in only those files which are original. All those that are copied from elsewhere, should explicitly be not checked in.

blocks|key|278905|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|278906|我很欣赏任何开源Java+Web+Apps+repo布局的例子。|blockquote|278907|278908|278909|Here's+an+example+of+web+application，它使用经典的Maven目录布局：|offset|length|278910|hifaces20-demo-messageboard-0.1.0-project.zip|278911|src
++main
++++java
++++resources
++++webapp
++++++WEB-INF
++++++++web.xml
++test
++++java
++++resources
pom.xml|code-block|syntax|javascript|278912|entityMap|0|LINK|mutability|MUTABLE|url|http://confluence.highsource.org/x/JIBM|1|http://repository.highsource.org/maven2/releases/org/hisrc/hifaces20/hifaces20-demo-messageboard/0.1.0/hifaces20-demo-messageboard-0.1.0-project.zip^0|0|0|0|0|0|10|0|0|0|19|1|0|0^^$0|@$1|2|3|-4|4|5|6|10|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|11|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|12|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|13|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|14|7|@]|8|@$H|15|I|16|1|17]]|9|$]]|$1|J|3|K|4|5|6|18|7|@]|8|@$H|19|I|1A|1|1B]]|9|$]]|$1|L|3|M|4|N|6|1C|7|@]|8|@]|9|$O|P]]|$1|Q|3|-4|4|5|6|1D|7|@]|8|@]|9|$]]]|R|$S|$4|T|U|V|9|$W|X]]|Y|$4|T|U|V|9|$W|Z]]]]

<blockquote>
 I'd appreciate any examples with
 opensource Java Web Apps repo layouts.
</blockquote>

<a href="http://confluence.highsource.org/x/JIBM" rel="nofollow noreferrer">Here's an example of web application</a> which is using a classic Maven directory layout:

<a href="http://repository.highsource.org/maven2/releases/org/hisrc/hifaces20/hifaces20-demo-messageboard/0.1.0/hifaces20-demo-messageboard-0.1.0-project.zip" rel="nofollow noreferrer">hifaces20-demo-messageboard-0.1.0-project.zip</a>

<pre><code>src
 main
 java
 resources
 webapp
 WEB-INF
 web.xml
 test
 java
 resources
pom.xml
</code></pre>

blocks|key|1024184|text|我通常会检查WEB-INF文件夹，但不包括lib和classes文件夹。当我需要库时，我使用Maven或Ivy+(ant任务)检索它们。似乎工作得很好，我只在极端情况下才检查库，比如我可能不会有Ivy缓存，或者库是“特殊的”并且不存在于其他任何地方。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1024185|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I generally do check in the WEB-INF folder but exclude the lib and classes folder. When I need the libs I retrieve them using Maven or Ivy (ant tasks). Seems to work well, I only check in the libs if it's an extreme case where it's likely I wont have an Ivy cache or the lib is 'special' and doesn't exist anywhere else.

The Ant "<a href="http://ant.apache.org/manual/Tasks/war.html" rel="nofollow noreferrer">war</a>" task does just that - creates WEB-INF along with META-INF, depending on task attributes.

What is considered a best practice?
Keeping all my libs elsewhere for re-use, like log4j and then build them with "war" task?
Or have everything (including jars) checked-in under WEB-INF? 
I have multiple apps that could re-use same libs, images, htmls, etc. Our developers use RAD7/Eclipse.

I'd appreciate any examples with opensource Java Web Apps repo layouts.

Should I commit WEB-INF into version control, or rather construct it with Ant?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

Ant "“任务就是这样做的-根据任务属性创建WEB-INF和META-INF。什么被认为是最佳实践？将我所有的库保存在其他地方以供重用，比如log4j，然后使用"war“任务构建它们？或者在WEB-INF下签入所有内容(包括jars)？我有多个应用程序，可以重复使用相同的库，图像，htmls等。我们的开发人员使用RA...

问我应该将WEB-INF提交到版本控制中，或者更确切地说，是用Ant构造它？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问我应该将WEB-INF提交到版本控制中，或者更确切地说，是用Ant构造它？EN