The directory structure in that chapter is pretty basic (src/<package structure>, test/<package structure) and pretty typical, and last time I used NetBeans it was easily able to adapt to different structures by mounting the source roots appropriately. I think Eclipse has a tougher time adapting to different directory structures. My philosophy is that an IDE must adapt to _my_ way of doing things rather than me having to make things tougher on myself to accommodate a tool. My builds run in a variety of environments (Anthill, CruiseControl, IDEA, command-line, etc) so tools need to be flexible enough to handle my structure, or I don't use them :)

How are you finding that directory structure incompatible?

As for the ".." issues you mentioned, at the very least you shouldn't have a LOT of them in your build file. Make a property at the top:

<property name="root.dir" location="../../../../../../.."/>

And use the root.dir property wherever needed - or adjust the basedir on the <project>, and use relative paths from there and Ant will happily adjust for you. Your placement of the build file is pretty atypical though, and I question why you want to do it that way.

Erik


On Thursday, December 26, 2002, at 11:38 PM, Ray Tayek wrote:
hi, i like to use netbeans and ant. but the current recommended directory structure (in section 2.5.1-2.5.3 of java development with ant http://www.amazon.com/exec/obidos/ASIN/1930110588) seems pretty incompatible with net beans. then of course there is the problem of where to keep the test files. to make matters worse. i tend to use rcs (as opposed to cvs) and keep the build file in the relevant package (i.e. com/tayek/games/go/sgf/build.xml is where i want the build file for this package to be. this leads to a lot of "../../../../../"'s in the build file which are ugly, but they do not change often. (these build files tend to be just for small parts of things).

has anyone had any luck in consolidating the way netbeans does things with this recommended directory structure?

how about the idea of keeping the build.xml file with the package that it builds?

any pointers would be appreciated.

thanks
---

ray tayek http://home.attbi.com/~rtayek/ actively seeking mentoring or telecommuting work
vice chair orange county java users group http://www.ocjug.org/ mailto:[EMAIL PROTECTED]
hate spam? http://samspade.org/ssw/


--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to