Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail From: Lew Newsgroups: comp.lang.java.programmer Subject: Re: How to develop without an IDE? Date: Tue, 24 Apr 2012 14:59:56 -0700 (PDT) Organization: http://groups.google.com Lines: 31 Message-ID: <4985868.899.1335304796536.JavaMail.geo-discussion-forums@pbsp7> References: <03kdp7lt6ibmssgfnqsbdhf9ndsc42q7v2@4ax.com> NNTP-Posting-Host: 69.28.149.29 Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: posting.google.com 1335304797 9109 127.0.0.1 (24 Apr 2012 21:59:57 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 24 Apr 2012 21:59:57 +0000 (UTC) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=69.28.149.29; posting-account=CP-lKQoAAAAGtB5diOuGlDQk0jIwmH0T User-Agent: G2/1.0 X-Received-Bytes: 2410 Xref: csiph.com comp.lang.java.programmer:13872 markspace wrote: > BGB wrote: > > personally, I would be more happy with many IDEs (or, at least leaving > > them in control of the "project" and "build process"), if the build > > process were itself readily available and an editable part of the proje= ct. >=20 > Just FYI: NetBeans actually generates an ant build file and uses it=20 > exclusively to build projects. Anytime you want to change the internals= =20 > of how NetBeans builds, just edit the build.xml file. Uh-huh. Have you tried this yourself? In the first place, you don't edit the build.xml but the ancillary build fi= le that build.xml incorporates. In the second place, the generated build script is a tour de force, but ver= bose and heavy. It is likely more than you'd hand-craft. I usually eschew t= he NetBeans build.xml as too IDE-specific, and create one from first princi= ples. I recommend that practice. > I'd recommend checking the project's Properties first, but if you don't= =20 > find what you need there, a little work with the build script will fix=20 > things right up. A "little" work indeed - seriously, have you tried this? --=20 Lew