RE: Add jar files to classpath in VAJ?

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> -----Original Message-----
> From: Bruce Jin
>
> I imported xalan.jar into my project and my class compiled!
> My project is now very crowded and I should have imported
> everything into a
> different project.

You can easily move a package from one project to another.  From the
workbench, just right-click on the package, select "Reorganize" and then
"Move".  You'll be prompted for the destination.

> When I use a new version of xalan, I have to import it again. This seems
> annoying. The classpath feature should work

A repository-based solution requires that all classes be imported.  It's the
nature of the environment.  It can be annoying, but how often will you need
to do this?  It seems to me a slight very slight annoyance as compared to
the benefits of instant impact analysis of changes, auto-completion of code,
generation of getters and setters, ability to move methods from one class to
another, and so on.

If you're more comfortable with the edit/compile cycle of a command-line
based environment, you may want to look at one of the more traditional IDEs
like JBuilder.  VAJ definitely forces you into the repository paradigm, but
for me, anyway, the benefits outweigh the drawbacks.