How standard and interchangeable are XML config files?

[Ramon F Herrera]

I just began playing with NetBeans. My previous IDE was the
traditional (non-Eclipsized) Borland JBuilder, which used a
configuration file called <project_name>.jpx with XML lines inside.

NB creates a folder called 'nbproject' which contains inside a file
called 'project.xml'. That constitutes a bare bones, minimum project.

How standard are those XML configuration files? Can a file created by
NetBeans be read and interpreted by Eclipse, and vice versa?

-Ramon

 

[=?ISO-8859-1?Q?Arne_Vajh=F8j?=]

I just began playing with NetBeans. My previous IDE was the
traditional (non-Eclipsized) Borland JBuilder, which used a
configuration file called <project_name>.jpx with XML lines inside.

NB creates a folder called 'nbproject' which contains inside a file
called 'project.xml'. That constitutes a bare bones, minimum project.

How standard are those XML configuration files? Can a file created by
NetBeans be read and interpreted by Eclipse, and vice versa?

Not standard at all.

The standards are ant and maven build files.

Bot Eclipse and NetBeans support ant build files.

Arne

 

[Lew]

Not standard at all.

The standards are ant and maven build files.

Bot Eclipse and NetBeans support ant build files.

Not only are project files not portable between IDEs, they're not portable
within the same IDE.

Project files contain very specific information about directory locations,
selected options, libraries and the like. Move a project even to a different
hard drive on the same computer, much less to another machine, much, much less
to a different IDE, and things break.

Here's a typical top-level project directory list from my own NetBeans workspace:

$ ls -1p
build/
build.xml
catalog.xml
CVS/
..cvsignore
dist/
logs/
nbproject/
src/
test/
web/

The .cvsignore file excludes the build/, dist/, and logs/ subdirectories. The
NetBeans-specific build.xml and the nbproject/ directories are checked into a
separate branch of the CVS project repository, not the trunk. Exports of
source to another project workspace, for deployment or parallel development,
always go through version control (VC), never directly between workspaces.
The nbproject branch does not go with them.

If there were multiple nbprojects going for one project, say, were there a
team involved, then each nbproject would go into a separate branch, with the
real project trees like src/ and web/ on the trunk. The workspaces would not
share nbproject branches.

 

[Andrew Thompson]

Arne Vajhøj wrote:
...

...
The standards are ant and maven build files.

Bot Eclipse and NetBeans support ant build files.

(small point but) Ant does not need an IDE wrapped around it.
Ant build files can be invoked from the command line.
I suppose you could configure programs like TextPad
to launch common Ant tasks, as well..

--
Andrew Thompson
http://www.athompson.info/andrew/

Message posted via JavaKB.com
http://www.javakb.com/Uwe/Forums.aspx/java-general/200710/1

 

[Almond]

Not only are project files not portable between IDEs, they're not portable
within the same IDE.

Project files contain very specific information about directory locations,
selected options, libraries and the like.

What kind of bullshit is this, herr high-priest?
I thought you could do better than that.

Move a project even to a different
hard drive on the same computer, much less to another machine, much, much less
to a different IDE, and things break.

Wut?

What did you smoke fer breakfast today, yerr holey suckiness?

Do you want me to tell you how to do it?

Enough of this horseshit fer now.

Here's a typical top-level project directory list from my own NetBeans
workspace:

$ ls -1p
build/
build.xml
catalog.xml
CVS/
..cvsignore
dist/
logs/
nbproject/
src/
test/
web/

The .cvsignore file excludes the build/, dist/, and logs/ subdirectories. The
NetBeans-specific build.xml and the nbproject/ directories are checked into a
separate branch of the CVS project repository, not the trunk. Exports of
source to another project workspace, for deployment or parallel development,
always go through version control (VC), never directly between workspaces.
The nbproject branch does not go with them.

If there were multiple nbprojects going for one project, say, were there a
team involved, then each nbproject would go into a separate branch, with the
real project trees like src/ and web/ on the trunk. The workspaces would not
share nbproject branches.

--
The most powerful Usenet tool you have ever heard of.
NewsMaestro v. 4.0.5 - Way Too Cool has been released.

Automatic enablement of all buttons, checkboxes and fields
depending on operation.
Templates generator improvements.

Job list improvements for new installations having no jobs
to begin with.

In some previous releases some class files were missing.
As a result, the program would not run.
Sorry for the inconvenience.

Multi-job support and other important feature additions
and various improvements and optimizations.

Web page:
http://newsmaestro.sourceforge.net/

Download page:
http://newsmaestro.sourceforge.net/Download_Information.htm

Send any feedback to newsmaestroinfo \at/ mail.ru.
Your personal info will not be released and your privacy
will be honored.

 

[Daniel Pitts]

Not only are project files not portable between IDEs, they're not
portable within the same IDE.

Project files contain very specific information about directory
locations, selected options, libraries and the like. Move a project
even to a different hard drive on the same computer, much less to
another machine, much, much less to a different IDE, and things break.

That hasn't been my experience, as long as everything is relative to the
project file. At least with IntelliJ IDEA.

 

[Lew]

That hasn't been my experience, as long as everything is relative to the
project file. At least with IntelliJ IDEA.

That's a point in favor of IDEA, I suppose.

I'm still recommending that moving projects between directories happen only
through VC, for all the other reasons that apply.

In addition, that lets teammates use their own choice for IDE.