Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Programming > Java Advocacy > Re: Red Hat, Su...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 6 of 9 Topic 2322 of 2478
Post > Topic >>

Re: Red Hat, Sun finally buddy up on Java

by Lew <lew@[EMAIL PROTECTED] > Nov 6, 2007 at 01:26 AM

Ramon F Herrera wrote:
> The one item in my wish list is that all Java IDE providers:
> 
>  - Had a common directory and file structure for projects

NetBeans sets up projects by menu choice according to the Sun Java
Blueprints 
standard or the Apache Tomcat standard.  Eclipse likewise follows the
standard 
layouts for various types of Java projects.  Other than the defaults for
the 
names of certain non-deployed directories, which are easily changed in the

options, the two create the same directory structures.

The IDE-specific directories, such as "nbproject/" for NetBeans, aren't
even 
****table within their own IDE, I've found.  So much of the specific
workspace 
is bound up in them.  Likewise with the "workspace/" directories in
Eclipse. 
Oh, the project files transfer, but somehow you just never can change the 
build or packaging.  OTOH, when you create a new IDE-specific project tree
for 
each workspace, NB or Eclipse, then you can filter that out when you
transfer 
the project around.  Ant is your friend, and it don't need your stinkin' 
project dirs.  That's how you get true ****tability.

Mind you, NB uses Ant for its project management files, so it really is 
****table.  Uhh, except that their Ant files are structured the way they
like, 
and pull in all this stuff you might not necessarily need for your
production 
builds, say.  So even though Ant uses your build files ****tably, your
build 
files might not be ****table.  So, you leave the IDE project files out,
too, 
even build.xml, and use your own build.xml for test and production builds,
and 
you do not transfer the IDE build.xml between workspaces.

>  - Allowed me to easily keep all the *.java files in a separate
> directory, accessible by all the IDEs that I use.

I have never had trouble accessing the Java source directory, always
distinct 
from deployment directories, disk-specific project information, doc 
directories and other source trees such as SQL, for the same project
equally 
well from NetBeans and Eclipse.  It's always a separate directory, and
both 
products read it just fine, without any strain on my part.

They also keep their build and deployment directories separate.

The fault, dear Brutus, lies not in our IDEs, but in ourselves.

-- 
Lew
 




 9 Posts in Topic:
Red Hat, Sun finally buddy up on Java
Ramon F Herrera <ramon  2007-11-05 18:07:37 
Re: Red Hat, Sun finally buddy up on Java
Lew <lew@[EMAIL PROTEC  2007-11-05 22:04:43 
Re: Red Hat, Sun finally buddy up on Java
=?UTF-8?B?QXJuZSBWYWpow7h  2007-11-06 21:32:57 
Re: Red Hat, Sun finally buddy up on Java
Mark Space <markspace@  2007-11-05 19:11:54 
Re: Red Hat, Sun finally buddy up on Java
Ramon F Herrera <ramon  2007-11-05 19:41:41 
Re: Red Hat, Sun finally buddy up on Java
Lew <lew@[EMAIL PROTEC  2007-11-06 01:26:18 
Re: Red Hat, Sun finally buddy up on Java
Owen Jacobson <angryba  2007-11-05 22:59:26 
Re: Red Hat, Sun finally buddy up on Java
Hunter Gratzner <a2490  2007-11-06 07:12:45 
Re: Red Hat, Sun finally buddy up on Java
=?ISO-8859-1?Q?Arne_Vajh=  2007-11-06 21:31:16 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan12V112 Thu Dec 4 1:45:11 CST 2008.