All geek questions in one place

Are there Ant conventions similar to Maven2 conventions?

Over the past 2 years - (ish) I have used Maven2 for my build / continuous integration solution. I used to use Ant , but didn't really get much experience with it. Now I have a new job, and the team I'm in now is using Ant.

What interests me is:

At Maven, we had directory conventions to separate our source and java files from Java test files ( JUnit ). It looked like this:

Project-
  -src/main/java
  -src/test/java

Thus, your tests are separate from your source / production code and will not be created / deployed as such.

Going through the Ant documentation, in fact, I don't see any agreement. Am I missing something? Is there a similar agreement in Ant?

+3
source share
3 answers

My experience with ant - which is our main build tool for the Java source, so do as you want - there are no such formal conventions. Many of the original projects I've seen organize things in a similar way; JBoss uses <module> / src / main for sources, etc. ant simply uses whatever conventions you want, making it the perfect tool to integrate into a larger project structure.

, Maven Ant, , , . , , , - , .

+7

ANT ANT /

+2

An older resource, but, in my opinion, beautiful, ant-best-practices .

0
source

Source: https://habr.com/ru/post/1698257/

More articles:


All Articles