NetBeans 5.0入门指南：快速掌握Java IDE

需积分: 10 59 浏览量更新于2024-08-02 收藏 957KB PDF 举报

NetBeans 5.0 IDE 使用指南本指南旨在为NetBeans 5.0这款流行的Java集成开发环境（IDE）的新手提供详细的介绍，无论你是初次接触IDE还是从其他开发环境转换而来，都将在这份文档中找到所需的帮助。首先，我们假设读者对Java编程语言及其相关技术有一定的基本了解。 **设置项目**（Setting Up Projects）在开始之前，确保你已经正确安装了NetBeans 5.0，并根据指南设置了开发环境。第5章介绍了如何设置项目，这是使用IDE的基础，包括创建新项目、配置主项目以及导入已有的项目。这些步骤对于组织和管理你的代码至关重要。 **基本IDE概念**（Basic IDE Concepts）第6章深入讲解了IDE的核心概念，如项目（Projects）、构建工具Ant的运用。Ant在这里扮演着自动化构建任务的角色，可以帮助开发者简化繁琐的构建流程，提高效率。理解这些概念有助于你更有效地利用NetBeans的内置功能。 **创建项目**（Creating a Project）在第10章，你将学习如何通过NetBeans创建一个新的Java项目，这包括选择项目类型、配置项目的源代码目录和资源目录，以及配置项目的构建路径。这个阶段是实战操作，能够帮助你启动并运行你的第一个Java程序。 **设置主项目**（Setting the Main Project）在项目中，每个应用通常有一个主项目（通常包含主类），第11章详细阐述了如何设定主项目，包括指定入口点（main方法）和其他关键设置，这对于项目结构的清晰性非常重要。 **导入项目**（Importing Projects）对于已有项目或想要重用代码的情况，第12节教你如何导入外部项目到NetBeans中，以便于协作和复用代码库。这对于团队开发和维护大型项目特别有用。这份"UsingNetBeans™IDE5.0"指南提供了全面且深入的教程，从项目设置到基本概念，再到实际操作，确保了无论是新手还是经验丰富的开发者都能快速上手和充分利用NetBeans 5.0的强大功能。通过跟随指导，你将能熟练掌握Java IDE的使用，为开发J2EE应用程序和相关的插件模块或富客户端应用打下坚实基础。务必关注相关的J2EE教程和平台提供的额外资源，以进一步扩展你的知识和技能。

Using NetBeans

5.0 IDE

16 Chapter 1 Setting Up Projects

You can add any required projects to your project by right-clicking the Libraries

node in the Projects window, or you can add them by specifying them in the

Compile tab in the Project Properties dialog box. When you want to add a

required project, select the project folder whose JAR files you want to add to the

classpath (the file chooser displays the icon for IDE project folders

Project

folder icon

). When adding projects in the Project Properties dialog box, make sure

that the Build Projects on Classpath checkbox is selected.

If you want to add a free-form project to the classpath of a standard project, you

have to add the free-form project's JAR file to the standard project's classpath. To

do this, you must first declare all of the free-form project's output files in the

Output panel of the free-form project's Project Properties dialog box.

Setting up Free-form Projects

In free-form projects, the IDE uses targets in an existing Ant script to build, run,

clean, test, and debug your application. If the Ant script does not contain targets for

some of these functions, the functions are unavailable. To implement these functions

you write targets either in your Ant script or in a secondary Ant script.

For more on setting up free-form projects, see the following article:

■ Advanced Free-Form Project Configuration

Editing and Running Ant Scripts

The IDE automatically recognizes Ant scripts and displays them as Ant script

nodes (

Ant icon) rather than as normal XML files. You can right-click Ant

scripts in the Projects window, Files window, or Favorites window to access a

pop-up menu of commands. You can also expand the Ant script node to see an

alphabetical list of subnodes representing the Ant script's targets. Each of these

subnodes also has a contextual menu of commands.

In the Projects, Files, and Favorites windows, an Ant script's subnodes are flagged

in the following ways:

Emphasized

Ant target

Emphasized Ant target. These targets include a description

attribute, which is displayed as a tooltip. You define the target's

description attribute in the Source Editor.

Normal Ant

Targ et

Normal Ant target. A target without a description attribute.

Using NetBeans

5.0 IDE

Chapter 1 Setting Up Projects 17

The only way to edit an Ant script is in the Source Editor. Double-click any of the

Ant script's subnodes to jump to that target's location in the Source Editor. All of

the normal XML search tools, selection tools, and keyboard shortcuts are available

for editing Ant scripts, and the IDE provides code completion for all standard Ant

tasks.

When you create a target that you want to run from the command line, give the

target a description attribute. Then, if you forget the names of the targets or what

they do, you can run the ant -projecthelp <script> command from the

command line. With this command, Ant lists only those targets that have a

description attribute, together with their descriptions. Especially when there are

many targets in your Ant build script, emphasizing some and de-emphasizing

others can be a useful way to distinguish between those that you use a lot and

those that you use less often.

The font style of a subnode's label in the Projects, Files, and Favorites windows

indicates the following:

■ Normal

A target that is defined within the current Ant script.

■ Italics

A target that is imported from another Ant script.

■ Greyed out

An internal target that cannot be run directly. Internal targets have names

beginning with '-'.

■ Bold

The default target for the script, if there is one. The default target is declared as

an attribute of the project, together with other project attributes, such as its

name. You define the project's default attribute in the Source Editor.

Targets that are imported from another script but are overridden in the importing

script are not listed. Only the overriding target is listed.

You can run targets in an Ant script from the Ant script's node in the Projects

window, Files window, or Favorites window. To do so, right-click the Ant script

node and choose a target from the Run Target submenu. Targets are sorted

alphabetically. Only emphasized targets are listed. Choose Other Targets to run a

target that has not been emphasized with a description attribute. Internal targets

are excluded from these lists because they cannot be run independently.

Using NetBeans

5.0 IDE

Chapter 1 Setting Up Projects 19

The classpath variable you set in the Project Properties dialog box does not affect

the actual classpath of the project, which is specified in the Ant script. Declaring

the classpath in the Project Properties dialog box does not change the actual

compilation or runtime classpath of the source folders. However, the project

classpath variable must match the classpath used by your Ant script in order to

provide the correct information for code completion, error highlighting, and

refactoring commands. You have to set an explicit classpath in your build scripts

because the IDE ignores your environment's CLASSPATH variable whenever it

runs Ant. If you change the classpath of one, you must change the class path of

the other

Specifying the Classpath for Custom Tasks

In free-form projects, you can call up and run custom Ant tasks in your build

script. For your Ant script to use customs tasks, you must include the tasks in the

Ant script's classpath. For example, you may add a task to your build script to

format your code with Jalopy. In order to do this, however, you have to add the

Jalopy JAR file to Ant's classpath.

You can add custom tasks to Ant's classpath within the IDE by doing either of the

following:

■ Providing an explicit classpath to the tasks in your build script. This is the

recommended method for specifying the location of JAR files that contain

custom tasks used by your Ant script, as it ensures that your build scripts will

be fully portable. You can write your tasks and include instructions to compile

them and produce a JAR file in the build file. To use these tasks, include the

long form of taskdef, which includes a classpath. Here is a simple example of

such a task:

</jar>

<taskdef name="customtask" classname=

"com.mycom.MyCustomTask">

</classpath>

</taskdef>

</target>

</project>

剩余103页未读，继续阅读

xuanyzs

粉丝: 3
资源: 87

NetBeans 5.0入门指南：快速掌握Java IDE

NetBeans 教程(如何使用NetBeans)

Netbeans使用教程

NetBeans使用文档

NetBeans使用文档.pdf

netbeans

Netbeans

netbeans使用教程javaweb

netbeans使用教程java

apache netbeans使用教程

NetBeans IDE 使用指南

最新资源