Issues developing SE and EE on same machine netbeans

[Ben Kaufman]

Hi,

Are there any issues developing both SE and EE on the same machine in netbeans
environment? (i.e. library/jar mixup)

Thanks.

Ben

 

[Arne Vajhøj]

Are there any issues developing both SE and EE on the same machine in netbeans
environment? (i.e. library/jar mixup)

You can (and always do) develop Java SE code when developing Java EE.
So if you just install the Java EE edition of your IDE, then you should
be all set.

Whether you can have two different edition sof NetBeans running on the
same system I do not know.

I would guess so, because Eclipse can.

Arne

 

[Lew]

Are there any issues developing both SE and EE on the same machine in
netbeans
environment? (i.e. [sic] library/jar mixup)

You can (and always do) develop Java SE code when developing Java EE.
So if you just install the Java EE edition of your IDE, then you should
be all set.

Whether you can have two different edition sof NetBeans running on the
same system I do not know.

I would guess so, because Eclipse can.

You can run two different versions of NetBeans on the same computer at the
same time, though why you'd want to I have no idea.

The only difference between the SE-only version and the EE-inclusive version
of NetBeans is the addition of modules to the latter,

There is no danger of mixup between Java EE JARs and Java SE JARs. There is
danger of mixing up different versions of the same JAR, for example,
third-party libraries often include a particular version of log4j that may
differ from your own preferred version. I resolve that by excluding such
common JARs from the third-party libraries; instead I define my own library of
common code like log4j.

 

[Arne Vajhøj]

Are there any issues developing both SE and EE on the same machine in
netbeans
environment? (i.e. [sic] library/jar mixup)

You can (and always do) develop Java SE code when developing Java EE.
So if you just install the Java EE edition of your IDE, then you should
be all set.

Whether you can have two different edition sof NetBeans running on the
same system I do not know.

I would guess so, because Eclipse can.

You can run two different versions of NetBeans on the same computer at
the same time, though why you'd want to I have no idea.

The only difference between the SE-only version and the EE-inclusive
version of NetBeans is the addition of modules to the latter,

Sometimes it is nice to have different environments for
different purposes.

I would not split between Java SE and Java EE, because it
really is the same thing.

I could split between Java stuff (SE and EE), C/C++ stuff and
Python stuff because they are more distinct.

Arne

 

[Ben Kaufman]

You can (and always do) develop Java SE code when developing Java EE.
So if you just install the Java EE edition of your IDE, then you should
be all set.

Whether you can have two different edition sof NetBeans running on the
same system I do not know.

I would guess so, because Eclipse can.

Arne

I did not realize that there were different netbean IDEs for SE and EE, i just
thought that's how the downloads were bundled.

Ben

 

[Ben Kaufman]

Are there any issues developing both SE and EE on the same machine in
netbeans
environment? (i.e. [sic] library/jar mixup)

You can (and always do) develop Java SE code when developing Java EE.
So if you just install the Java EE edition of your IDE, then you should
be all set.

Whether you can have two different edition sof NetBeans running on the
same system I do not know.

I would guess so, because Eclipse can.

You can run two different versions of NetBeans on the same computer at the
same time, though why you'd want to I have no idea.

The only difference between the SE-only version and the EE-inclusive version
of NetBeans is the addition of modules to the latter,

There is no danger of mixup between Java EE JARs and Java SE JARs. There is
danger of mixing up different versions of the same JAR, for example,
third-party libraries often include a particular version of log4j that may
differ from your own preferred version. I resolve that by excluding such
common JARs from the third-party libraries; instead I define my own library of
common code like log4j.

OK, good to know I don't need two IDEs
I have been developing with SE for a number of years and did not want to
unnecessarily upset this environment as I include EE apps.

Thanks.

Ben

 

[Lew]

I did not realize that there were different netbean IDEs for SE and EE, i [sic] just
thought that's how the downloads were bundled.

That depends on your definition of "different". The only difference
between the SE-only version and the EE-inclusive version of NetBeans
is the addition of modules to the latter. They are the same IDE to
the extent that the core modules are the same. So you were correct -
it is a matter of how the downloads were bundled. Different bundles
differ in the modules bundled with them.

The extensibility of both NetBeans and Eclipse stem from the fact that
they actually are rich-client platforms (RCPs) atop which the IDE
functions are layered. You can add, remove, activate and deactivate
just about everything in NetBeans via the "Tools Preferences" option.
You can also use the RCPs to develop applications that aren't IDEs.
An industrial-process control application atop the NetBeans RCP is, in
some sense, the "same" NetBeans that you downloaded for Java
development.

 

[Lew]

The extensibility of both NetBeans and Eclipse stem from the fact that
they actually are rich-client platforms (RCPs) atop which the IDE
functions are layered. You can add, remove, activate and deactivate
just about everything in NetBeans via the "Tools Preferences" option.

Sorry, that's "Tools Plugins".

 

[Arne Vajhøj]

I did not realize that there were different netbean IDEs for SE and EE, i just
thought that's how the downloads were bundled.

It is.

Same core IDE but with different modules/plugins.

And "download bundles" is the term NetBeans use themselves. Editions
was just my translation.

Arne