On 02/11/2011 06:13 PM, John B. Matthews wrote:
In article<firstname.lastname@example.org>, Lew<email@example.com>
On 02/11/2011 01:02 PM, markspace wrote:
On 2/11/2011 5:29 AM, Cecil Westerhof wrote:
One question. I prefer to work with Emacs. (I even use it to write
this message.) Can I build the interface in NetBeans and use Emacs
to write my code?
Probably. NetBeans can accept an Ant file for your project build
file. (Ant is like make for Java.) Just use that feature, design
the classes in NetBeans, check them in and you're good to go.
You can, but you probably shouldn't. You'll find the editor in
NetBeans (or Eclipse, JDeveloper, ...) to be sufficient, and giving
up the integration is rather rough.
Also, NetBeans likes to "protect" regions of code. emacs will not
recognize this and will let you futz with generated code.
OP: Amplifying on Lew's and markspaces's observations, the ant build.xml
file used by NetBeans need not require the IDE at all. The default
generated ant file can be customized by overriding the desired pre- and
post-processing targets, as shown here:
NetBeans also supports Free-Form Java Projects. This simple project
contains an ant build.xml file having the minimal targets for such a
Either arrangement allows one to use the most convenient editor locally,
while also working with the same code remotely from the command line.
In any case, the ant targets (either free-form or generated by NetBeans)
can be seen using ant's -p option:
$ ant -p
clean Clean the project.
compile Compile the program.
debug-nb Debug the program in NetBeans.
default Default clean and build.
doc Generate the javadoc.
init Initialize the build process.
jar Build a jar file.
run Run the program.
test Test the program.
Default target: default
can handle regular build.xml-based projects. NB can add a custom Ant script
targets (e.g., "run one file") to coexist with the official build.
Ceci n'est pas une fen??tre.