http://www.mail-archive.com/ant-user@jakarta.apache.org/msg15374.html
but it seems obvious that 'src' is the way to go.
As for using a variable for 'src', I often go in and work on existing projects where other developers are using other IDE's such as jbuilder and have already created a different directory tree, so in these cases, being able to put the src directory config in just one place is advantageous - I won't have to alter my build.xml at all. But I see your points of view.
Adam
Dominique Devienne wrote:
#1: I believe Drew was saying Java sources should be in src/java, while
other type of sources, like DTDs be in src/dtd, etc... It's a common pattern
used by many Jakarta projects, and that Maven assumes (not sure on the last
part, although I'm sure it's configurable in some kind of layout
specification for the project).
#2: is a matter of choice. I've personally backed away from using variable
for the layout, since the later is fixed in CVS. I don't see the advantage
of using variable for something that fixed...
--DD
-----Original Message-----
From: Adam Hardy [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 10, 2002 9:07 AM
To: [EMAIL PROTECTED]
Subject: ant for dummies question
I've been using ant for a while with struts and tomcat. Now I'm starting
an EJB project and am learning more about ant so I can use it here too.
I'm used to having my java classes in the "src" subdirectory. Yet I was
reading an old post "J2EE config/build best practices" from Drew Davison
recommending calling the source code dir "java" - which is more common?
Also the struts-originated build.xmls hard-coded the directory name in,
but wouldn't it be better to have it in the build.properties?
Instead of
have this:
For additional commands, e-mail:
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
